Configuring MQ JMS Import bindings

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

Configuring the MQ JMS Import 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 Import binding on WebSphere Process Server.
Resource Module name Import name Resource global JNDI name
Outbound Connection Factory mqjms.module my/import mqjms.module/my/import_MQ_CF
Response Listener Port mqjms.module my/import mqjms.module.my.import_RESP_LP (Note: This is only a name, not JNDI)
Response Connection Factory mqjms.module my/import mqjms.module/my/import_RESP_CF
Send mqjms.module my/import mqjms.module/my/import_MQ_SEND_D
Receive mqjms.module my/import mqjms.module/my/export_MQ_RECEIVE_D
SIB Callback Destination mqjms.module my/import mqjms.module/my/import_MQ_CALLBACK_D
SIB Callback Connection Factory All modules my/import 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 import 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 import 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)