The JMS export binding may be installed with all the necessary connection factories created, or it can be designed to point to a pre-configured set of artifacts on the server.
Typically, your JMS export bindings are created in WebSphere Integration Developer. At development time you have an option to create the connections and destinations required for the JMS export at install time, i.e., when the component is installed on your WebSphere Process Server. The alternative is to specify the JNDI name of the resources on the WebSphere Process Server that you intend your JMS export to utilize.
Configuring the JMS export binding depends upon which option was selected.
Resource | Module name | Export name | Resource global JNDI name |
---|---|---|---|
Connection Factory | jms.module | my/export | jms.module/my/export_CF |
Activation Spec | jms.module | my/export | jms.module/my/export_AS |
Destination | jms.module | my/export | jms.module/my/export_SEND_D, jms.module/my/export_RECEIVE_D, jms.module/my/export_CALLBACK_D |
SIB Destinations | jms.module | my/export | jms.module.my.export_SEND_D_SIB, jms.module.my.export_RECEIVE_D_SIB, jms.module.my.export_CALLBACK_D_SIB |
In the alternative case, where the JMS export is expecting to find resources on the server that it will use, you must have these resources installed and the Export file must contain their JNDI names. The association between the JMS export and the resources will then be made.
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)