For JBoss application server, JMS server runs within EJB server. Thus when EJB clustering takes place, JMS is also clustered.
To configure EJB cluster:
1. In the left pane, under the node BusinessManager, click Cluster.
2. Under the Cluster node, click EJB to specify the EJB cluster configuration. You can change the default EJB cluster name, if needed.
3. Enter Cluster Name for the EJB cluster.
4. Enter MultiCast Address or use the default values.
IP multicast is a simple broadcast technology that enables multiple applications to "subscribe" to a given IP address and port number and listen for messages. A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255.
If Multicast IP address is not specified, then it is derived from the specified IP address of the first EJB node.
5. Click Add Node. The Node Details are displayed.
6. Enter Name for the node to identify the EJB server node uniquely in the cluster. This name is used for starting and stopping the EJB server on this node.
Note: EJB server node name should be different for each node in the cluster. Only alphabets, numerals and underscore character ( _ ) are allowed.
7. Specify the IP Address of the node.
8. Use the default port numbers, or enter unique port numbers for HTTP Port, HTTPS Port, JNDI Port, and Advance Port Range on which the node listens.
Note: Ensure that the computer can be identified by the IP Address in the network and it is unique across the network.
Ensure that a range of 40 consecutive port numbers starting from the Advance Port Range port number you specify are available. Also, make sure that all the cluster members have a unique set of ports.
In case of vertical clustering, the port numbers must be different on all nodes as all the nodes are on the same computer.
9. Enter the location of OEBPS Home, which is the BusinessManager installation folder.
10. Click Add to add the node to the EJB cluster. Click Add & Continue to add more nodes. Click Cancel to go back to the previous page.
Note: The BusinessManager instance on which cluster configuration is performed also needs to be added as a cluster node explicitly.
