user manual

260 BES Developer’s Guide
Creating a clustered JMS service
Sonic
Using the DDEditor, you can configure a name (JMS service URL, sequential,
loadBalancig) a type, and a value in the XML <jndi-object>, as shown in the
example below:
<jndi-object>
<jndi-name>serial://jms/message</jndi-name>
<class-name>progress.message.jclient.QueueConnectionFactory</class-
name>
<property>
<prop-name>connectionURLS</prop-name>
<prop-type>String</prop-type>
<prop-value>localhost:2506</prop-value>
</property>
<property>
<prop-name>sequential</prop-name>
<prop-type>Boolean</prop-type>
<prop-value>false</prop-value>
</property>
<property>
<prop-name>loadBalancing</prop-name>
<prop-type>Boolean</prop-type>
<prop-value>true</prop-value>
</property>
</jndi-object>
Creating a clustered JMS service
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 <install_dir>/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.