How the outbound messaging system works -- long description

The messaging system uses a plug-in model that implements the Java 2 Enterprise Edition Connector Architecture (J2EE/CA) to provide a common interface between the system and the various transports. During administration of the system, Site Administrators can perform the following tasks:

• Add, enable, and configure transports. The administrator creates the settings using the Administration Console. Communication between the messaging system and the transports take place through a singular administration interface.
• Maintain profiles, assigning transports to individual message types and indicating the settings to be used for each one. The administrator does this using the Administration Console.

At run time, when a message is generated by a WebSphere Commerce messaging system, the following events occur:

1. The appropriate profile is retrieved for the message type. Profiles can be created by assigning the message type to the desire transport. The transport being assigned and used must be in active state. If the transport is not in active state, the profile will be ignored and considered as not exist. If no store profile exists for that message with the corresponding active transport, the site profile is used. The profile is used to determine what transport method and settings are used.
2. If the message uses the composition service, a JSP page is used to generate the message.
3. The message is sent through the run time interface to the transport, which delivers the notification.

The use of a common interface with external transports allows the implementation details of the transport to be kept separate from the operation of the messaging system. This architecture makes it possible to plug in additional transports that adhere to the J2EE/CA interface.

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.