Adding New Node to FileNet Cluster

Hello! Last week a client asked me to add a new node to FileNet cluster. In this article i’ll show you how to add a new node to a FileNet cluster.

Why You Should Deploy FileNet to a Cluster?

During FileNet deployment process, you have three options:

  • Standard
  • Network
  • Cluster

Standard Deployment: Option you use for WebSphere standard edition. FileNet license comes with WebSphere standard edition and in most of the cases we use that option due to licensing. Each additional WebSphere node installed and configured separately, that means, you need to run FileNet Configuration tool for each node and re-deploy.

Network Deployment: If you are using WebSphere Application Server Network Deployment you can use this option. WebSphere Network Deployment is centrally managed version of Standard edition. You can manage multiple JVM’s from a central console. In Network deployment mode you need to run deploy step for each JVM. In large enterprises, we deploy FileNet up to 16 JVM’s, and that takes a lot of time.

Cluster Deployment: Cluster is a term for logical grouping and load balancing of JVMs in WebSphere. FileNet Configuration Tool also supports cluster deployment modal. You can create a cluster with 6 JVMs and deploy application to all of them with one click in configuration tool.

IBM FileNet

How to Add New Node to FileNet Cluster

If your organization is growing, you might need to add new nodes to your WebSphere architecture. (or new JVMs). Adding a JVM to a WebSphere cluster is a very straightforward operation for a WebSphere administrator. When you add a JVM to a cluster, applications automatically being deployed to your new JVM.

For most of the applications that work. But not for FileNet. If you start new JVM and visit acce on browser, you will see new domain creation page.

How to Make FileNet Work?

In general, the first step should be checking WebSphere variables, your new JVM is probably missing JDBC driver path settings. Set the correct value for JDBC driver’s location, and ensure JDBC drivers are located under that directory.

The second and most important step is adding custom JVM properties to your new JVM to add a new node to FileNet Cluster. Go to Java And Process Management -> Process Definition -> Java Virtual Machine -> Custom Properties page of an existing JVM. Copy those values and add them to your new JVM and start new JVM.

Ta daaa!

Your new FileNet cluster member is ready.

Leave a Reply

Your email address will not be published. Required fields are marked *