FileNet P8 Content Engine, Version 5.0.+       Application server:  JBOSS Application Server     

Deploying Content Engine to additional JBoss servers in a cluster

Use the following procedure to deploy a Content Engine Server instance on each additional JBoss Application Server in your cluster.

Important: Because JBoss clusters communicate state over multicast, it is critical that you configure clusters for Content Engine to segregate multicast traffic from each other and from other JBoss clusters. You can find instructions regarding JBoss cluster configuration at http://www.jboss.com.
To deploy Content Engine Server on additional JBoss servers in a cluster:
  1. Leave Content Engine deployed on the application server where you installed it.
  2. Copy the following files from the initial Content Engine instance to each JBoss node you are setting up:
    • All data source (JBoss_HOME/server/all/deploy/*-ds.xml) files created as part of the configuration process.
      Important: Depending on how you installed JBoss, there might be data source files not created by Configuration Manager, such as hsqldb-ds.xml , in the same location. Do not copy these files.
    • JBoss_HOME/server/all/deploy/Engine-ds.xml
    • The JDBC driver in JBoss_HOME/server/all/lib
    • JBoss_HOME/server/all/conf/login-config.xml
    • JBoss_HOME/server/all/deploy/Engine-jbc.ear
      Tip: Clustered JBoss instances are deployed from the "all" directory and not the "default" directory. You can find instructions regarding JBoss cluster configurations at http://www.jboss.com
  3. Start or restart the application server.
  4. Verify that the server.log file located in the JBOSS_home/server/all/log directory lists deployment of the WAR or EAR file you used. If it does, then the deployment of Content Engine is successful.


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)