Borland Enterprise Server (BES) 5.1 uses a definitions archive (DAR) module for deployment of administered objects. Administered JMS objects such as queues, topics, and their respective connection factories are defined in the jndi-definitions.xml
file. This file is used to build the DAR module that defines objects to be loaded into the Borland Partition’s Naming Service. You must build a DAR module that specifies TIBCO Enterprise Message Service objects.
The Borland Enterprise Server installation contains several copies of the jndi-definitions.xml
file. Modify the file located in C:\<
BES-install-dir
>\examples\ejb\mdb
and use the modified file to build the DAR module.
In this file, there are several XML elements named <jndi-object>
that define the SonicMQ JMS classes. These classes must be replaced with TIBCO Enterprise Message Service classes.
The following illustrates the replacements to make in bold:
<jndi-definitions> <jndi-object><jndi-name>serial://jms/tibqcf</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandQueueConnectionFactory
</class-name>
<property><prop-name>serverUrl</prop-name>
<prop-type>String</prop-type><prop-value>localhost:7222</prop-value>
</property> </jndi-object> <jndi-object><jndi-name>serial://jms/tibtcf</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandTopicConnectionFactory
</class-name>
<property><prop-name>serverUrl</prop-name>
<prop-type>String</prop-type><prop-value>localhost:7222</prop-value>
</property> </jndi-object> <jndi-object><jndi-name>serial://jms/tibxaqcf</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandXAQueueConnectionFactory
</class-name>
<property><prop-name>serverUrl</prop-name>
<prop-type>String</prop-type><prop-value>localhost:7222</prop-value>
</property> </jndi-object> <jndi-object><jndi-name>serial://jms/tibxatcf</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandXATopicConnectionFactory
</class-name>
<property><prop-name>serverUrl</prop-name>
<prop-type>String</prop-type><prop-value>localhost:7222</prop-value>
</property> </jndi-object> <jndi-object><jndi-name>serial://jms/tibq</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandQueue</class-name>
<property>
<prop-name>address</prop-name>
<prop-type>String</prop-type><prop-value>TibQ1</prop-value>
</property> </jndi-object> <jndi-object><jndi-name>serial://jms/tibt</jndi-name>
<class-name>
com.tibco.tibjms.appserver.borland.TibjmsBorlandTopic</class-name>
<property>
<prop-name>address</prop-name>
<prop-type>String</prop-type><prop-value>TibT1</prop-value>
</property> </jndi-object> </jndi-definitions>
Save the changes to the jndi-definitions.xml
file and build a new DAR module using the following command:
Deploy the TIBCO Enterprise Message Service JAR files, tibjms.jar
and tibjmsapps.jar
, then deploy the ems-resources.dar
file in the target partition using the Borland Enterprise Server Console. The deployment steps are similar to an EJB JAR file. Refer to the Borland Enterprise Server 5.1 User’s Guide for details.
TIBCO Enterprise Message Service™ Application Integration Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |