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

How to Prepare the JBoss Cluster Server Image Computer

To populate the JBoss cluster, you install a supported version of JBoss Application Server on a Windows computer. You perform all customization and configuration steps on this server. When you are done, you copy this server image to all Windows computers in the cluster. This helps ensure uniform configuration of all servers in the cluster.

When you prepare the initial server image, do the following:

• Verify that the computer meets the prerequisite hardware, software, and connectivity requirements for clustered JBoss implementation.

  Note: For more information about prerequisites, see the Release Notes.

• Use only JBoss packages that are compatible with this release of CA RCM.

  Note: For more information about supported JBoss versions, see the Release Notes and the Support Matrix, which are available on Technical Support at http://ca.com/support.

• Create a message queue database for the cluster, and define a JNDI datasource that points to the database. You can locate datasource definition files under the /server/all/farm folder of the JBoss installation directory. The following example shows a typical message queue datasource definition.

  Note: For more information about defining a JNDI datasource, see the JBoss documentation at http://www.jboss.org/jbossas/docs/.

Examples: JNDI Datasource Definition

This example shows you a snippet from a sample -ds.xml datasource definition file that specifies a JNDI databsource for a Microsoft SQL Server implementation:

<datasources>
   <local-tx-datasource>
      <jndi-name>jdbc/jbossmqDS</jndi-name>
      <connection-url>jdbc:jtds:sqlserver://db_host:db_port/db_name</connection-url>
      <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>
      <user-name>username</user-name>
      <password>password</password>
      <min-pool-size>10</min-pool-size>
      <use-java-context>false</use-java-context>
      <check-valid-connection-sql>select 1</check-valid-connection-sql>
   </local-tx-datasource>
</datasources>

This example shows you a snippet from a sample -ds.xml datasource definition file that specifies a JNDI databsource for an Oracle Database implementation:

<datasources>
   <local-tx-datasource>
      <jndi-name>jdbc/jbossmqDS</jndi-name>
      <connection-url>jdbc:oracle:thin:@db_host:db_port/db_name</connection-url>
      <driver-class>oracle.jdbc.OracleDriver</driver-class>
      <user-name>username</user-name>
      <password>password</password>
      <min-pool-size>10</min-pool-size>
      <use-java-context>false</use-java-context>
      <check-valid-connection-sql>select 1 from dual</check-valid-connection-sql>
      <connection-property name="defaultNChar">true</connection-property>
   </local-tx-datasource>	
</datasources>

Enter local values for the following variables:

db_host

Defines the hostname of the database server.

db_port

Defines the communications port the message queue database uses.

db_name

Defines the name of the message queue database.

username, password

Defines the user name and password the datasource uses to access the message queue database.