This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Properties of MQ JMS bindings

MQ JMS bindings can be installed with all the necessary connection factories having been created during deployment, or they can be configured to point to a set of existing resources.

Typically, MQ JMS bindings are created in Integration Designer. You can either create the connections and destinations required for the JMS binding at the time the component is installed on your server, or you can specify the JNDI name of the resources on the server that you intend your MQ JMS import or export to use.

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

In the case where new message provider resources are created (that is, the resources are created on the server during installation), the resources will exist and can be located and administered using the administrative console.

Examples of the JNDI names of the generated artifacts are described in the following tables.
Table 1. MQ JMS imports: Names and JNDI names of resources created at installation on the server
Resource Module name Import name Resource global JNDI name
Outbound Connection Factory mqjms.module my/import mqjms.module/my/import_MQ_CF
Response Activation Specification mqjms.module my/import mqjms.module/my/import_AS
Failed Event Replay 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
Table 2. MQ JMS exports: Names and JNDI names of resources created at installation on the server
Resource Module name Export name Resource global JNDI name
Request Activation Specification mqjms.module my/export mqjms.module/my/export_AS
Failed Event Replay 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.
  • 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 separately in the administrative console.

If you select the other option and the MQ JMS import or export binding is expecting to find on the server resources 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.