The external event delivery process

There are two different types of events in the Connect system: document events and message events. Document events are events directly associated with a business document. The Business Processing Engine is responsible for publishing these events to a WBI-C internal queue. In the case of either a Sent or a Failed document state, the Delivery Manager also publishes business document events to this queue. Message events, on the other hand, are published by all components of WBI-C. Message events are not necessarily related to a business document, although one or more message events may be associated with a business document.

Events that are published to the internal queue are sent by the event server to Connect's event store. As of the 4.2.2 release, however, users may also decide to have events delivered to an external JMS queue. Turning external delivery on and off and configuring the external queue are done through the Community Console. See the WBI-C Hub Configuration Guide for help in setting up this up.

Events are delivered to the JMS queue in CBE XML format. The CBE, or Common Base Event, format is a part of a larger evolving IBM initiative, the Common Event Infrastructure, or CEI, designed to standardize the handling of events across applications. CBE structure covers three basic types of information:

The specifics of the CBE format as it is used in external event delivery are detailed in The structure of delivered events.

If external delivery is turned on, all events will be delivered to the external queue. The visibility flag, which limits which type of user may see which type of event in the Console Event Viewer, is not used in external delivery. Event names and descriptions in external delivery are localized in the same manner as they are in the Event Viewer.

Incorrect JMS configuration and/or JMS provider problems can cause errors in external event delivery. If they are not detected on startup, and an external delivery error occurs, the following happens:

Copyright IBM Corp. 2003, 2004