IBM BPM, V8.0.1, All platforms > Administer applications and processes in the runtime environment > Administer service applications and service modules > Work with imports and exports > Administer bindings > Administer Generic JMS bindings
Properties of Generic JMS bindings
The Generic 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, the Generic 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 JMS import or export to use.
Configure the Generic 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. The JNDI names of the generated artifacts are described in the following tables.
Generic JMS imports: Names and JNDI names of resources created at installation on the server Resource Generated resource JNDI name Outbound Connection [moduleName]/[importName]_CF Response Connection [moduleName]/[importName]_RESP_CF Send destination [moduleName]/[importName]_SEND_D Receive destination [moduleName]/[importName]_RECEIVE_D Callback destination [moduleName]/[importName]_CALLBACK_D
Generic JMS exports: Names and JNDI names of resources created at installation on the server Resource Generated resource JNDI name Inbound Connection [moduleName]/[exportName]_LIS_CF Response Connection [moduleName]/[exportName]_RESP_CF Receive destination [moduleName]/[exportName]_RECEIVE_D Send destination [moduleName]/[exportName]_SEND_D Callback destination [moduleName]/[exportName]_CALLBACK_D 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.
If you select the other option and the JMS import is expecting to find required resources on the server, you must have these resources installed and the import and export files must contain the JNDI names. The association between the JMS binding and the resources will then be made.