There are a number of key features of a JMS Export binding. These features include headers and created J2EE resources.
JMS Export bindings differ from EIS export bindings in their handling of the return of the result. A JMS Export explicitly sends the response to the JMSReplyTo destination specified on the incoming message. If none is specified the send destination is used.
When the JMS Export is deployed, a Message Driven Bean (a different MDB than the one used for JMS Imports) is deployed. It listens for the incoming requests on the receive Destination and then dispatches the requests to be processed by the SCA runtime.
Special header properties are used in an export to indicate to the target export binding information on how the message should be handled.
Parameters
A special header is provided for the export binding to inform the export how to handle messages.
A number of J2EE resources are created when a JMS Export is deployed to a J2EE environment.
Parameters
The installation task creates the set of resources similar to the one for JMS Import, an ActivationSpec, ConnectionFactory used for sending a reply and three destinations - send, receive and callback. All the properties of these resources are specified in the export file.
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)