Event sequencing is supported with EIS Export bindings, JMS Export
bindings, native MQ, and WebSphere MQ JMS Export bindings. To ensure that
the Exports process and deliver messages in the correct sequence, you must
configure the Export bindings appropriately.
Consider the following requirements when using event sequencing on a target
component that handles Export bindings:
- An adapter component must use the non-optimized path for a Java Message
Service (JMS) Export when event sequencing is used on the target component.
- To enable event sequencing for JMS Export bindings, you must limit the
number of concurrent Message Driven Beans (MDBs) that are processing incoming
messages. Do this by setting the maxConcurrency custom
property on the ActivationSpec to a value of 1.
- To enable event sequencing for a WebSphere MQ JMS Export , you must limit
the number of concurrent listener threads that will deliver messages to the
Message Driven Bean. Do this by setting the maxSessions property
to a value of 1.
- To enable event sequencing for a native MQ Export, you must
use WebSphere Integration Developer to set the eventSequencing property.
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)