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 WebSphere MQ bindings

Migrating WebSphere MQ Bindings from version 6 to later versions

Migration is only required for WebSphere MQ bindings that contain pre-configured resources.


Specifying an activation specification

In WebSphere ESB version 7, the WebSphere MQ binding uses the WebSphere MQ resource adapter to receive messages, which requires an activation specification.

If a WebSphere MQ binding has pre-configured WebSphere MQ resources, define an additional activation specification JNDI name in the end-point configuration of the binding. This JNDI name must refer to an existing activation specification JMS resource on the server.


Modify connection factory properties

You must remove these custom properties from the pre-configured connection factories:


Modify destination properties

Add these custom properties in the pre-configured destinations:

Custom properties for WebSphere MQ queue destinations
Destination Type Property Name Property Value Property Type
Send destination MDWRITE YES java.lang.String
MSGBODY MQ java.lang.String
MDMSGCTX SET_ALL_CONTEXT java.lang.String
Receive destination MDREAD YES java.lang.String
MSGBODY MQ java.lang.String
MDMSGCTX SET_ALL_CONTEXT java.lang.String

Administer WebSphere MQ bindings