Setting up clusters for JBoss Application Server 5
To improve the performance and availability of your BMC IT Business Management environment, you can run it on a cluster.
To set up a cluster
- Install BMC IT Business Management and JBoss on each node that you want to include in a cluster.
- When you install the products on the first or standalone node, select all the following check boxes:
- BMC IT Business Management Suite 8.1.01 Installation
- Install BMC IT Business Management Core Components 8.1.01
- Install Configuration for BMC IT Business Management Application Service
Install Configuration for JBOSS
- When you install the products on the subsequent nodes, select only the following check boxes:
- Install Configuration for BMC IT Business Management Application Service
Install Configuration for JBOSS
After you complete the standard installation wizard steps, the system automatically sets up a cluster, where all subsequent nodes refer to the BMC Remedy AR System server and database located at the first node.Click on the following image to expand it.
- When you install the products on the first or standalone node, select all the following check boxes:
- Enable the cluster cache invalidation as follows:
- Open the <JBOSS_HOME>/jboss-as/server/production/conf/standardjboss.xml file.
- In the <container-name>cmp2.x jdbc2 pm</container-name> line, change the <min-capacity> and <max-capacity> parameters to 1.
After the installation, you can edit the cluster configuration information in the following files:
OS | File | Parameter | Description |
|---|---|---|---|
Windows | run.conf.bat | - Djboss.messaging.ServerPeerID | The individual unique number assigned to each node in a group (and, correspondingly, in a cluster) |
Windows | ehcache.xml | multicastGroupAddress | The IP address that is accessible from this server. The system uses this IP address to replicate caches in a cluster. The default IP address is 224.0.0.251. Note: the multicast IPs range from 224.0.0.0 to 239.255.255.255. If you are experiencing the slow response time from your default multicast IP, change it to another IP from this range. |
Linux | run.conf (located at <JBOSS_HOME>/bin) | -Djboss.messaging.ServerPeerID=1 | The individual unique number assigned to each node in a group (and, correspondingly, in a cluster) |
To find out which multicast group your server is subscribed to, you can run the following commands:
- (Windows) netsh interface ip show joinsClick on the following image to expand it.
- (Linux) netstat -gClick on the following image to expand it.
The ehcache.xml file comes with a built-in RMI-based distribution system. The listener component is RMICacheManagerPeerListener, which is configured using the RMICacheManagerPeerListenerFactory tag in the ehcache.xml file. The automatic peer discovery process relies on a multicast IP address.