Asynchronous event considerations for events from IBM BPM V8.5.0 and earlier
The flow from an emitting application to the common event infrastructure (CEI) can be synchronous or asynchronous. With synchronous event transmission, an application waits for successful event delivery before proceeding with the rest of its transaction. With asynchronous event transmission, an application places events on a queue and proceeds with processing.
When you use asynchronous event transmission, you can minimize the impact on the emitting application, which might be important when monitoring mission-critical applications. However, with asynchronous event transmission, events can be received by a monitor model in a different order than they occurred in the emitting application.
For models where event order is important, incorrect event sequence order can result in model processing exceptions and incorrectly calculated data. If you need the order of events to be guaranteed, make sure that the application that is emitting events to IBM® Business Monitor uses synchronous event emission, or define an event sequence path in the monitor model to provide information about the event processing order.
One way to tell whether the events are being emitted asynchronously is to check the administrative console under . Select the emitter factory, which might be named something like Default Common Event Infrastructure emitter. The panel that is displayed has an Event transmission area with settings that control how events are emitted. JMS transmission is asynchronous and event service transmission is synchronous.
If you decide to use asynchronous event emission and it is important that the events be processed in the order in which they were produced, define an event sequence path in the monitor model. For more information about how to define event sequence paths, see the related links.