IBM BPM, V8.0.1, All platforms > Get started with IBM BPM > Key concepts > Bindings > Binding types > WebSphere MQ bindings
Key features of a WebSphere MQ binding
Key features of a WebSphere MQ binding include headers, Java EE artifacts, and created Java EE resources.
Correlation schemes
A WebSphere MQ request/reply application can use one of a number of techniques to correlate response messages with requests, built around the MQMD MessageID and CorrelID fields. In the vast majority of cases, the requester lets the queue manager select a MessageID and expects the responding application to copy this into the CorrelID of the response. In most cases, the requester and responding application implicitly know which correlation technique is in use. Occasionally the responding application will honor various flags in the Report field of the request that describe how to handle these fields.
Export bindings for WebSphere MQ messages can be configured with the following options:
Response MsgId options:
- New MsgID
- Allows the queue manager to select a unique MsgId for the response (default).
- Copy from Request MsgID
- Copies the MsgId field from the MsgId field in the request.
- Copy from SCA message
- Sets the MsgId to be that carried in WebSphere MQ headers in the SCA response message, or lets the queue manager define a new Id if the value does not exist.
- As Report Options
- Inspects the Report field of the MQMD in the request for a hint as to how to handle the MsgId. The MQRO_NEW_MSG_ID and MQRO_PASS_MSG_ID options are supported and behave like New MsgId and Copy from Request MsgID.
Response CorrelId options:
- Copy from Request MsgID
- Copies the CorrelId field from the MsgId field in the request (default).
- Copy from Request CorrelID
- Copies the CorrelId field from the CorrelId field in the request.
- Copy from SCA message
- Sets the CorrelId to be carried in WebSphere MQ headers in the SCA response message or leaves it blank if the value does not exist.
- As Report Options
- Inspects the Report field of the MQMD in the request for a hint as to how to handle the CorrelId. The MQRO_COPY_MSG_ID_TO_CORREL_ID and MQRO_PASS_CORREL_ID options are supported and behave like Copy from Request MsgID and Copy from Request CorrelID.
Import bindings for WebSphere MQ messages can be configured with the following options:
Request MsgId options:
- New MsgID
- Allows the queue manager to select a unique MsgId for the request (default).
- Copy from SCA message
- Sets the MsgId to be carried in WebSphere MQ headers in the SCA request message or lets the queue manager define a new Id if the value does not exist.
Response correlation options:
- Response has CorrelID copied from MsgId
- Expects the response message to have a CorrelId field set, per the MsgId of the request (default).
- Response has MsgID copied from MsgId
- Expects the response message to have a MsgId field set, per the MsgId of the request.
- Response has CorrelID copied from CorrelId
- Expects the response message to have a CorrelId field set, per the CorrelId of the request.
Java EE resources
A number of Java EE resources are created when a WebSphere MQ binding is deployed to a Java EE environment.
Parameters
- MQ Connection Factory
- Used by clients to create a connection to the WebSphere MQ provider.
- Response Connection Factory
- Used by the SCA MQ runtime when the send destination is on a different Queue Manager than the receive destination.
- Activation specification
- An MQ JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
- Destinations
- Send destination: where the request or outgoing message is sent (import); where the response message will be sent (export), if not superseded by the MQMD ReplyTo header field in the incoming message.
- Receive destination: where the response/request or incoming message should be placed.