user manual

262 BES Developer’s Guide
Creating a clustered JMS service
initial-monitor="true" type="redundancy-group">
<redundancy-group member="2" desired-range-max="2">
<member mo-ref="${tmp.agent1}/${tmp.master.name}"/>
<member mo-ref="${tmp.agent2}/${tmp.slave.name}"/>
</redundancy-group>
</managed-object>
</managed-objects>
</configuration>
Note The Tibco servers in the example above are running on different hosts.
Configuring clients for fault tolerant Tibco connections
To connect to a backup server in the event of failure of a primary server, a
client application must specify multiple server URLs in the jndi-object XML for
the connection factories as below:
<jndi-object>
<jndi-name>serial://jms/XAQueueConnectionFactory</jndi-name>
<class-name>com.tibco.tibjms.TibjmsXAQueueConnectionFactory</class-name>
<property>
<prop-name>serverUrl</prop-name>
<prop-type>String</prop-type>
<prop-value>localhost:7222,hnguyen:7222</prop-value>
</property>
</jndi-object>
<jndi-object>
<jndi-name>serial://jms/QueueConnectionFactory</jndi-name>
<class-name>com.tibco.tibjms.TibjmsQueueConnectionFactory</class-name>
<property>
<prop-name>serverUrl</prop-name>
<prop-type>String</prop-type>
<prop-value>localhost:7222,hnguyen:7222</prop-value>
</property>
</jndi-object>
<jndi-object>
<jndi-name>serial://jms/XATopicConnectionFactory</jndi-name>
<class-name>com.tibco.tibjms.TibjmsXATopicConnectionFactory</class-name>
<property>
<prop-name>serverUrl</prop-name>
<prop-type>String</prop-type>
<prop-value>localhost:7222,hnguyen:7222</prop-value>
</property>
</jndi-object>
<jndi-name>serial://jms/TopicConnectionFactory</jndi-name>
<class-name>com.tibco.tibjms.TibjmsTopicConnectionFactory</class-name>
<property>
<prop-name>serverUrl</prop-name>
<prop-type>String</prop-type>
<prop-value>localhost:7222,hnguyen:7222</prop-value>
</property>
</jndi-object>