Enabling event notification allows messages from the MDM
operational server to be sent to external source systems each time
a specific event (or set of events) occurs within the operational
server. You can configure the notifications as standard XML messages
or in a BMP XML format that can be used by the IBM® Business
Process Manager Express.
Note: Trusted source linking is not supported
in event notification.
JMS is the most commonly used platform
for event notification. If you use an external JMS provider (other
than IBM WebSphere® Default Messaging or IBM WebSphere MQ) then the provider must support
standard JMS point-to-point queue mechanism. The provider must have
queues set up to which the operational server publishes and to which
the external source subscribes.
The event notification
logic uses three components:
- Event manager - manages the internal event queue and passes events
to the event work manager. You can choose to use an embedded event
manager (configured during the creation of the operational server
instance) or create a stand-alone instance. Properties that determine
how the event manager processes events are set in the com.ibm.mdm.mds.event.manager.cfg file.
- Event work manager - creates external event messages based on
the internal operational server events and passes the message to the
event handler. The event work manager uses a list of publish destinations
and associated events to create the messages that are passed to the
event handler. Configured in InfoSphere® MDM
Workbench,
destination configuration is stored in the mpi_evtdest table and the
list of published events is stored in the mpi_evtlist table. The event
list also has configuration parameters that identify which attributes
are included in the message based on the selected composite view,
control when messages are created, and determine the message format.
The associated destination JMS/JNDI configuration is completed when
you configure the event handler.
- Event handler - publishes the event message to the consumer.
The event handler implements standard JMS/JNDI protocol. (JMS Queue
is the supported message service.)