Key features of a MQ JMS Import binding

There are a number of key features of a MQ JMS Import. These features include headers, J2EE artifacts and created J2EE resources.

Headers

A JMS message header contains a number of predefined fields that contain values that both clients and providers use to identify and to route messages.

Parameters

JMSCorrelationID
Link 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 on the export binding to map from native method to operation method. Setting the String JMS Header property TargetFunctionName will indicate to the JMSFunctionSelectorImpl of the export the native method that should be used to map to the operation method. To use this, specify the native method as in the method binding as the value. You must set this as a JMS Header property in the import binding definition if you expect the export to use the JMSFunctionSelectorImpl.

Correlation schemes

The WebSphere® MQ JMS Import binding provides various correlation schemes that are used to determine how to correlate request messages with response messages.

Parameters

The response message correlation schemes are:

RequestMsgIDToCorrelID
The response service is expected to copy the request JMSMessageID to the JMSCorrelationID field of the response message. This is the default setting.
RequestCorrelIDToCorrelID
The response service is expected to copy the request JMSCorrelationID to the JMSCorrelationID field of the response message.

J2EE resources

A number of J2EE resources are created when a MQ JMS Import is deployed to a J2EE 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 runtime when the send destination is on a different Queue Manager than the receive destination.
Listener Port
Specifies an association between a connection factory, a destination, and a message-driven bean. This enables deployed message-driven beans associated with the port to retrieve messages from the destination.
Destinations
  • Send destination - Where the request or outgoing message is sent.
  • Receive destination - Where the response or incoming message should be placed.

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)