web server - Borland Technical Publications

Tibco
Creating Clustered JMS Service for Tibco
The Tibco JMS server works in pairs to provide fault tolerance. When working in pairs,
one acts as the primary server and the other acts as a secondary server, with only the
primary server accepting client connections and handling JMS messages. For the
secondary server to take over active connections and properly handle persistent
messages, both the servers must have access to a shared state. The primary and
backup servers must both have access to a shared state. This shared state can be
shared storage devices or other mechanisms such as replication.
The shared state must be accessible to both of the servers (primary and secondary).
Some common ways to implement shared storage are Network Attached Storage
(NAS) or Storage Area Network (SAN) devices. Replication schemes can also be used
for replicating the shared state.
For more information on Tibco shared state and storage, refer to Tibco's
documentation, located in /jms/tibco/doc/html.
The clustering of Tibco servers can be done visually using the BES Management
Console. To cluster Tibco servers:
1 Create a shared directory that both of the Tibco servers have full access to.
2 Right-click the your Configuration and select Add Managed Object from Template/
jms/Clustered Tibco.
3 Select a group to add clustered Tibco to from the drop-down menu.
4 Make the following changes to the template properties for the second Tibco server:
■
2nd Management Agent=hub.name where hub.name is the name of your Management
Hub.
■
■
■
Name - this is the name of the second Tibco server.
Tibco Slave URL - this is the port for the second Tibco server. The default is
7222. If the primary and secondary servers are on different machines the port
numbers can be the same or different, but if they are on the same machine, they
must be different.
Data Directory - This is the path to the shared datastorage for both primary and
secondary servers.
224 BES Developer’s Guide