Server instance addition for a site

You can add a Java™ Platform, Enterprise Edition (Java EE) application server instance to an existing Content Cortex domain if the server instance is a member of the Java EE application server farm in which the Content Cortex domain resides.

For instructions for installing and deploying Content Platform Engine on additional servers, see Deploying Content Platform Engine instances.

You must ensure that the Java EE application cluster (that is, the virtual server) names and server instance names are unique within the topology in which the Content Cortex domain is configured. Content Platform Engine virtual server and server instance objects are dynamically created in the global configuration database during system initialization; the object names are derived from the names that are assigned to the Java EE application cluster and server instances. Non-unique names can occur under the following conditions:

  • If you do not manually ensure that the Java EE application cluster and server instance names are unique. (The application server software does not typically require uniqueness in the names given to application server instances across servers.)
  • If you use the Move Site Components option in the administration console to reassign a Java EE application server instance to a different cluster (that is, virtual server).
If you have non-unique Java EE application cluster (that is, virtual server) names or server instance names, you can add the appropriate Java virtual machine (JVM) property to the command line that starts the Java EE application server instance that has the duplicate name: 
com.filenet.gcd.VirtualServerName=myUniquelyNamedVirtualServer
com.filenet.gcd.ServerInstanceName=myUniquelyNamedServerInstance

where myUniquelyNamedVirtualServer is the name you assigned to the Java EE application cluster (that is, virtual server) and myUniquelyNamedServerInstance is the name you assign to the application server instance.