JMS bindings provide connectivity between the service component architecture (SCA) environment and external JMS systems.
JMS Import binding provide outbound connectivity from Service Component Architecture (SCA) applications to JMS providers.
The connection that is part of a JMS Import is made up of a connection factory. A connection factory is the object a client uses to create a connection to a provider. A connection factory encapsulates a set of connection configuration parameters that has been defined by an administrator. Each connection factory is an instance of the ConnectionFactory, QueueConnectionFactory, or TopicConnectionFactory interface.
The destination element of a JMS Import is a send message which initiates the destination.
Two types of JMS Import binding are supported:
For both one-way and two-way usage scenarios dynamic and static header properties can be specified, some of these properties have special meanings to the SCA JMS runtime.
JMS Export binding provides inbound connectivity from JMS to the SCA System.
The connection that is part of a JMS Export is an activation specification.
A JMS Export has send, receive and callback destinations. The receive destination is where the incoming message for the target component should be placed. The send destination is where the reply will be sent, unless the incoming message has superseded this using the JMSReplyTo header property.
An MDB is deployed to listen to requests incoming to the receive Destination specified in the export binding. The Destination specified in the send field is used to send the reply to the inbound request if the invoked service provides a reply. The Destination specified in the JMSReplyTo field of the incoming message overwrites the Destination specified in the send. The Destination specified to in the callback field of the export is used to store callback information. This is required for two-way or request/response operations on the interface for the JMS Service.
JMS bindings are configured by default to have a maximum failed delivery of 5. JMS bindings require a value for the maximum failed delivery of at least 2 for the underlying SIB destination of the JMS destination. This is required for the receive destinations on both Import and Exports to enable the failed event manager to store failed messages. If you set a value for the maximum failed delivery of less than 2, messages to the target component that fail will not be available in the failed event manager. A failure in the target component constitutes a runtime exception. Failed messages that do not reach the failed event manager are routed to the exception destination as specified by the underlying SIB destination.
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)