Key features of WebSphere MQ JMS bindings

Key features of WebSphere® MQ JMS bindings include headers, Java EE artifacts, and created Java EE resources.

Headers

A JMS message header contains a number of predefined fields containing values used by both clients and providers to identify and to route messages. You can use binding properties to configure these headers with fixed values, or the headers can be specified dynamically at run time.

JMSCorrelationID
Links to a related message. Typically, this field is set to the message identifier string of the message that is being replied to.
TargetFunctionName
This header is used by one of the supplied function selectors to identify the operation being invoked. Setting the TargetFunctionName JMS header property in messages sent to a JMS export allows this function selector to be used. The property can be set directly in JMS client applications or when connecting an import with a JMS binding to such an export. In this case, the JMS import binding should be configured to set the TargetFunctionName header for each operation in the interface to the name of the operation.

Correlation schemes

The WebSphere MQ JMS bindings provide various correlation schemes that are used to determine how to correlate request messages with response messages.

RequestMsgIDToCorrelID
The JMSMessageID is copied to the JMSCorrelationID field. This is the default setting.
RequestCorrelIDToCorrelID
The JMSCorrelationID is copied to the JMSCorrelationID field.

Java EE resources

A number of Java EE resources are created when an MQ JMS import is deployed to a Java EE environment.

Parameters

MQ Connection Factory
Used by clients to create a connection to the MQ JMS provider.
Response Connection Factory
Used by the SCA MQ JMS run time 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:
    • Imports: Where the request or outgoing message is sent.
    • Exports: Where the response message will be sent if it is not superseded by the JMSReplyTo header field of the incoming message.
  • Receive destination:
    • Imports: Where the response or incoming message should be placed.
    • Exports: Where the incoming or request message should be placed.