The application-client.xml
file does not need to be changed for this example. However, the application client deployment descriptor application-client-borland.xml
file must be changed. The following highlights the changes to make in bold:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE application-client PUBLIC "-//Borland Software Corporation//DTD J2EE Application Client //EN" "http://www.borland.com/devsupport/appserver/dtds/application-clie nt_1_3-borland.dtd"> <application-client> <resource-ref> <res-ref-name>jms/qcf</res-ref-name> <jndi-name>serial://jms/tibqcf
</jndi-name> </resource-ref> <resource-ref> <res-ref-name>jms/tcf</res-ref-name> <jndi-name>serial://jms/tibtcf
</jndi-name> </resource-ref> <resource-env-ref> <resource-env-ref-name>jms/q</resource-env-ref-name> <jndi-name>serial://jms/tibq
</jndi-name> </resource-env-ref> <resource-env-ref> <resource-env-ref-name>jms/t</resource-env-ref-name> <jndi-name>serial://jms/tibt
</jndi-name> </resource-env-ref> </application-client>
After changing application-client-borland.xml
, build the example MDB and example, by changing to the directory C:\<
BES-install-dir
>\examples\ejb\mdb
and issuing the make_all
command. This results in two files in that directory: message_beans.jar
and message_beans_client.jar
.
Deploy the message_beans.jar module to the target partition using the Borland Enterprise Server Console. See the Borland Enterprise Server 5.1 User’s Guide for more information about deploying modules.
TIBCO Enterprise Message Service™ Application Integration Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |