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

Properties of JMS bindings

The JMS import and export 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, JMS import and export bindings are created in Integration Designer. When you configure the binding, you can either create the connections and destinations required for the JMS binding (by selecting Configure new messaging provider resources, which is the default), or you can select Use pre-configured messaging provider resources. If you choose pre-configured, you add the JNDI names for the connection factory and the send destination (for a one-way operation) or the send and receive destinations (for a request-response operation).

Configuring the JMS binding depends upon which option was selected.

Table 1 and Table 2 show examples of the resources you specify when you select Use pre-configured messaging provider resources.

Note: The JNDI name takes the form:

moduleName/importName_resourceAbbreviation

moduleName/exportName_resourceAbbreviation

For example, for a module named Inventory and an import named Import1, the JNDI name for the connection factory would be:

Inventory/Import1_CF

The fields and associated values for import bindings are shown in the following table:

Table 1. Example values for import bindings
Property	Example
JNDI name for connection factory	`moduleName/importName_CF`
JNDI name for send destination	`moduleName/importName_SEND_D`
JNDI name for receive destination	`moduleName/importName_RECEIVE_D`

The fields and associated values for export bindings are shown in the following table:

Table 2. Example values for export bindings
Property	Example
JNDI name for activation specification	`moduleName/exportName_AS`
JNDI name for receive destination	`moduleName/exportName_RECEIVE_D`
JNDI name for send destination	`moduleName/exportName_SEND_D`

Note: The resources are created at the server scope. The scope in the administrative console is initially set to All Scopes. You must set the scope to cell or node to create a new resource. You can select an existing resource from the default list.