Key features of a JMS Import binding

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

The JMS Import service differs from an EIS import in its runtime invocation with respect to handling of responses. The JMS implementation is asynchronous and the SCA programming model requires it to support three invocations, one-way, two-way (also known as request-response) and callback.

When the JMS Import is deployed, a Message Driven Bean (MDB), provided by the runtime environment is deployed. The MDB listens for replies to the request message. The MDB is associated (listens on) the destination sent with the request in the JMSReplyTo header field of the JMS message.

Special headers

Special header properties are used in an import to indicate to the target export binding information on how the message should be handled.

Parameters

A mapping from the native method to the operation method is provided through a special header.

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.

J2EE resources

A number of J2EE resources are created when a JMS Import is deployed to a J2EE environment.

Parameters

ConnectionFactory
Used by clients to create a connection to the JMS provider.
ActivationSpec
Used for receiving the response to a request.
Destinations
  • Send destination - Where the request or outgoing message is sent.
  • Receive destination - Where the response or incoming message should be placed.
  • Callback destination - SCA JMS System destination used for correlation information. Do not read/write to this destination.

The installation task creates the ConnectionFactory and three destinations from the information in the import file. In addition, it creates the ActivationSpec to enable the runtime MDB to listen for replies on the receive destination. The properties of the ActivationSpec are derived from the destination/ConnectionFactory properties.


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)