Setting up clusters for JBoss Application Server 6

To improve the performance and availability of your BMC IT Business Management environment, you can run it on a cluster.

Note

To run the product on a cluster, the system can use only IPv4 or both IPv4 and IPv6 for JBoss Application Server 6.

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 completing the standard installation wizard steps, the system automatically sets up a cluster, where all subsequent nodes refer to the same AR server and database.
    
    Click on the following image to expand it.
Depending on whether you want to use IPv4 or both IPv4 and IPv6, you need to perform the following actions:
- For IPv4:
  - In the ehcache.xml file, uncomment the cacheManagerPeerProviderFactory parameter.
  - (Windows) In the standalone.conf.bat file, change the value of the -Djboss.server.default.config parameter from standalone-full.xml to standalone-full-ha.xml.
  - (Linux) In the standalone.conf file, change the value of the -Djboss.server.default.config parameter from standalone-full.xml to standalone-full-ha.xml.
- For both IPv4 and IPv6:
  - In the ehcache.xml file, add the hostname parameter for each <cache> tag.
    Example
    replicateUpdates=false,hostName=[<IPv6Address>], replicatePutsViaCopy=false
  - In the ehcache.xml file, add the the hostname parameter IP in the IPv6 format.
    Example
    class="net.sf.ehcache.distribution.RMICacheManagerPeerListenerFactory" properties="hostName=[2001:500:100:1161:89fb:2ddd:48a4:2e76]"
  - (Windows) Before you start JBoss by running the standalone.bat file from the command line, add the -Djava.net.preferIPv6Addresses=true and -Djava.net.preferIPv4Stack=false parameters to the standalone.conf.bat file.
  - (Linux) Before you start JBoss by running the standalone.sh file from the command line, add the -Djava.net.preferIPv6Addresses=true and -Djava.net.preferIPv4Stack=false parameters to the standalone.conf file.

After the installation, you can edit the cluster configuration information in the following files:

OS	File	Parameter	Description
Windows	standalone.conf.bat (located at ...\jboss-eap-6\bin)	- Djboss.messaging.ServerPeerID	The individual unique number assigned to each node in a group (and, correspondingly, in a cluster)
Windows	ehcache.xml (located at ...\jboss-eap-6\server\production\conf)	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	standalone.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 RMICacheManagerPeerListenerFactory tag in the ehcache.xml file. The automatic peer discovery process relies on a multicast IP address.

Note

The multicast IP address can be blocked by routers. Also, the virtualisation technologies like Xen and VMware might block the multicast. In this case, you must enable the multicast IP address manually.

You can also run JBoss from command line and specify the - b parameter that corresponds the IP address of the current node, and the - Djboss.messaging.ServerPeerID parameter from there.

Example

standalone.bat -b [<IPv6Address>] -Djboss.messaging.ServerPeerID=1

Setting up clusters for JBoss Application Server 6

To set up a cluster

On this page