Configuring MQ JMS export bindings

The MQ 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 MQ 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 MQ 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 MQ JMS export to utilize.

Configuring the MQ JMS export binding depends upon which option was selected.

In the case where new message provider resources are created (i.e., the resources are created on the server at install time), the resources will exist and can be located and administered using the administrative console. The JNDI names of the generated artifacts are described in the table.
Table 1. The names and JNDI names of resources created at the installation of a MQ JMS Export binding on WebSphere Process Server.
Resource Module name Export name Resource global JNDI name
Listener Port mqjms.module my/export mqjms.module.my.export_LP (Note: This is just a name, not JNDI)
Inbound Connection Factory mqjms.module my/export mqjms.module/my/export_LIS_CF
Response Connection Factory mqjms.module my/export mqjms.module/my/export_RESP_CF
Receive mqjms.module my/export mqjms.module/my/export_MQ_RECEIVE_D
Send mqjms.module my/export mqjms.module/my/export_MQ_SEND_D
SIB Callback Destination mqjms.module my/export mqjms.module/my/export_MQ_CALLBACK_D
SIB Callback Connection Factory All modules my/export SCA.MQJMS/Callback_CF
Note: The resources are created at the server scope. The default scope in the administrative console is cell. You must change the scope in order to locate and administer the resources.
Note: The SIB Callback Destination and SIB Callback Connection Factory are SIB JMS resources. The other entries in the table are MQ JMS resources. The two types of resources are administered.

In the alternative case, where the MQ JMS export is expecting to find resources on the server that it will use, you must have these resources installed and the import file must contain their JNDI names. The association between the MQ 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)