Installation Guide › Installing a Windows Implementation › How to Install CA RCM Server Components on a JBoss Cluster › Configure the JBoss Cluster Server Image

Configure the JBoss Cluster Server Image

For CA RCM components to use correct communication ports in a clustered JBoss environment, you need to edit CA RCM and JBoss files.

To configure the JBoss cluster server image

1. On the JBoss server image computer, modify the JBoss run script as follows:
   1. Browse to the following folder:

      JBoss_root/bin
      

      Note: JBoss_root is the JBoss installation root directory.

   2. Open the eurekify.bat file you copied for editing.
   3. Locate the following line:

      run.bat -c eurekify -b 0.0.0.0
      

   4. Replace the line with the following line:

      run.bat -c all -b 0.0.0.0 -g CA_RCM_Cluster -u 233.3.4.4 -D 43366
      

   Save changes to the file.

2. Browse to the following folder and delete the listed files:

   JBoss_root/server/all/lib
   

   • hibernate3.jar
   • hibernate.annoations.jar
   • hibernate-entitymanager.jar
3. Edit the jboss.xml file as follows:
   1. Browse to the following folder:

      JBoss_root/server/all/farm/wpServerPlus.ear/wpServer.jar/META-INF/
      

   2. Open the jboss.xml file file for editing.
   3. Locate all instances of the following string:

      <jndi-name>jms
      

      Replace the string with the following string:

      <jndi-name>jnp://localhost:1100/jms
      

      Note: Port 1100 is the default JBoss port. Use the relevant port for your environment.

   4. Locate all instances of this element:

      <resource-ref>
      <res-ref-name>jms/wpConnectionFactory</res-ref-name>
      <jndi-name>jms/wpConnectionFactory</jndi-name>
      </resource-ref>
      

      Change the value of the jndi-name element as follows:

      <jndi-name>jnp://localhost:1100/jms/wpConnectionFactory</jndi-name>
      

   5. Locate all instances of this element:

      <resource-env-ref>
      <res-env-ref-name>jms/wpUtilQueue</res-env-ref-name>
      <jndi-name>queue/wpUtilQueue</jndi-name>
      </resource-env-ref>
      

      Change the value of the jndi-name element as follows:

      <jndi-name>jnp://localhost:1100/queue/wpUtilQueue</jndi-name>
      

   6. Locate all instances of this element:

      <resource-env-ref>
      <res-env-ref-name>jms/wpServAutoActQueue</res-env-ref-name>
      <jndi-name>queue/wpServAutoActQueue</jndi-name>
      </resource-env-ref>
      

      Change the value of the jndi-name element as follows:

      <jndi-name>jnp://localhost:1100/queue/wpServAutoActQueue</jndi-name>
      

   Save changes to the file.

4. Edit the web.xml file as follows:
   1. Browse to the following folder:

      JBoss_root/server/all/farm/eurekify.war/WEB-INF/
      

   2. Open the web.xml file file for editing.
   3. Locate the following statement:

      classpath:/META-INF/txLog/txLogSimpleContext.xml
      

      Replace the statement with the following statements:

      classpath:/META-INF/txLog/txLogJmsContext.xml
      classpath:/META-INF/txLog/jbossmqJmsContext.xml
      

   4. Locate the following statement:

      classpath:/META-INF/schedulerSimpleContext.xml
      

      Replace the statement with the following statements:

      classpath:/META-INF/schedulerClusteredContext.xml
      

   Save changes to the file.

5. Browse to the following folder and delete the cluster-examples-service.xml file:

   JBoss_root/server/all/farm
   

6. Edit the jbossmq-destinations-service.xml file as follows:
   1. Browse to the following folder:

      JBoss_root/server/all/deploy-hasingleton/jms
      

   2. Open the the jbossmq-destinations-service.xml file for editing.
   3. Remove the following two lines to remove the comment marks surrounding the destination definitions in the RCM Queues section of the file:

      <!-- RCM Queus Start
      RCM Queus End -->
      

   Save changes to the file.

7. Configure the JBoss JMS as follows:
   1. Browse to the following folder:

      JBoss_root/docs/examples/jms/
      

   2. Copy one of the JMS configuration files, depending on your database server:
      • For a Microsoft SQL Server, mssql-jdbc2-service.xml
      • For an Oracle Database, oracle-jdbc2-service.xml
   3. Paste the file to the following folder:

      JBoss_root/server/all/deploy-hasingleton/jms/
      

   4. In this folder, delete the hsqldb-jdbc2-service.xml file.
   5. Edit the JMS configuration file you copied:
      1. For Microsoft SQL Server, edit the mssql-jdbc2-service.xml file and locate the following statement:

            "name=jndi/MSSQLDS"
         

      2. For Oracle Database, edit the oracle-jdbc2-service.xml file and locate the following statement:

            "name=OracleDS"
         

      3. Replace the statement with the following statement:

            "name=JDBC/jbossmqDS"
         

8. (Oracle Database only) Edit the quartz-cluster.properties as follows:
   1. Browse to the following folder:

      JBoss_root/server/all/farm/eurekify.war/WEB-INF/classes/META-INF
      

   2. Delete the quartz-cluster.properties file.
   3. Rename quartz-clustered-oracle.properties to quartz-cluster.properties
9. Edit the server.xml file as follows:
   1. Browse to the following folder:

      JBoss_root/server/all/deploy/jboss-web.deployer
      

   2. Open the the server.xml file for editing.
   3. For each JBoss connector, set the following parameter:

      URIENCODING="UTF-8"
      

   Save changes to the file.

10. Delete the following two folders from the JBoss_root/server folder:
    • Default
    • Minimal