Use the InfoSphere® MDM event notifications and the notification configuration parameters.tab to define the destinations that receive
Enabling event notification allows messages from the InfoSphere MDM 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 an BPM XML format that can be used by the Business Process Management tools.
- Event manager - manages the internal event queue and passes events to the event work manager. Event manager configuration is done during the creation of the InfoSphere MDM instance.
- Event work manager - creates external event messages based on the internal events and passes the message to the event handler. The event work manager is configured in InfoSphere MDM Workbench.
- Event handler - publishes the event message to the consumer (JMS Queue is the supported message service).
The event work manager configuration consists of a list of destinations to be published to (stored in the mpi_evtdest database table) and a list of events to be published (this list is stored in the mpi_evtlist table). The list of published events 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 event types supported for event notification are preconfigured in your InfoSphere MDM data model. Before configuring event notification, verity that the event types listed in the event notification supported event types table exist in the mpi_evttype database table. To verify, go to the Events view and select the Event Types tab. These events have a category specified as EVENT NOTIFICATION.
|Entity Created||This event occurs when a new entity is created. New entity creation can occur when a new member is added to the system or when a member unlinks from an existing entity to form a new entity. The event represents a change in the number of entities for each entity type that participates in the system.|
|Entity Deleted||The entity deleted event occurs when an entity
ceases to exist in the system. These changes can occur when all members
of an existing entity join another existing entity or when a member
is dropped and that member was a singleton entity. The event represents
a change in the number of entities for each entity type that participates
in the system.
If a member delete interaction (member deleted event) is processed for a singleton entity, the entity deleted event is also triggered.
|Entity Updated||The entity updated event occurs when a change
is made to the composition of an existing entity, or when the composite
view for the entity changes, or when a relationship is created, updated,
or deleted. Composition changes manifest themselves as members that
join or leave an entity. The composite view changes are represented
by changes to attribute values that participate in the view. It is
possible for a single member update to trigger this event twice, one
time for the attribute changes and again for the entity composition
The entity update event can be configured to include relationship
information. If so configured, the relationship information is contained
|Member Created||The member created event occurs when either a create member interaction runs, or as part of a member put interaction that also includes a member update. A member created event occurs only once during the lifetime of a member record.|
|Member Deleted||The member deleted event occurs when a member
delete interaction is processed. A member delete does not physically
remove the member data from the system. Rather the event prevents
that member from participating in candidate selection processes. A
member might be deleted multiple times because of the member undelete
interaction. The event represents a change to the member status (from
Active to Delete) and not the member attribute data.
If a member delete interaction is processed for a singleton entity, the entity deleted event is also triggered.
|Member Linked||The member linked event occurs when entity management links a member to a new entity. A member might link multiple times during the lifespan of the record. The event represents a change in the member entity participation but not in member status or attribute data.|
|Member Merged||The member merged event occurs when a member merge interaction is processed by the MDM operational server. A member might be merged multiple times because of the unmerge capability. The event represents a change to the member status and not the member attributes data.|
|Member Reprocessed||The member reprocessed status is used as an internal indicator when a member is being reprocessed as the result of being unlinked from an entity. Member reprocessed is used only for trusted source and best match linking. The event is not meant for general consumption outside the MDM operational server (as it has no meaning for outside systems), but is available for rare situations if needed. Note that event notification is not supported for implementations that use trusted source linking.|
|Member Undeleted||The member undeleted event is triggered when a record status (recstat) for a member is set from 'D' (deleted) to 'A' (active). A status of active marks the member for consideration in candidate selection and update processes.|
|Member Unlinked||The member unlinked event occurs when entity management unlinks a member from an existing entity. A member might unlink multiple times during its life span. The event represents a change in the member entity participation but not in the member status or attribute data.|
|Member UnMerged||The member unmerge event occurs when a previously merged member is the target of a member unmerge interaction. A member might be unmerged multiple times because of the merge capability. The event represents a change to the member status and not the member attribute data.|
|Member Updated||The member updated event occurs when member
data is initially created. A member update also occurs each time that
these actions take place:
Depending on the operational server configuration options, the change might or might not result in any change to the persisted member data.
|Task Created||The task created event occurs when a task (review identifier, potential linkage, suspected duplicate, or potential overlay) is created in the MDM database (either manually by a user or automatically based on threshold settings), or when a custom implementation-defined task (IDT) is imported into the MDM database.|
|Task Deleted||The task deleted event occurs when a task is deleted.|
|Task Resolved||The task resolved event occurs when a task is
marked with a resolved status. Task resolved event supports both predefined
system tasks (review identifier, potential linkage, suspected duplicate,
and potential overlay) and custom implementation-defined tasks.
In some cases, the Task Deleted and Task Resolved events might overlap in underlying functionality. This overlap might result sending either one of the events.
|Task Updated||The task updated event occurs when a change is made to a task. The change can include task status (for example, changing an unexamined status to deferred), a new record is added or removed from the task set, or task type. Task updated event supports both predefined system tasks (review identifier, potential linkage, suspected duplicate, and potential overlay) and custom implementation-defined tasks.|
|Member Process||If a member is added and links to an existing entity, then the entity manager sends a Member Process event to the event manager. The event manager then sends a Member Created message and an Entity Updated message in the XML header. This event type is an internal-use only event.|
|Member No-link||If member is added and does not link to another member, then the entity manager sends a Member No-link event to the event manager. In this case, the XML header contains a Member Created and an Entity Created message. This event type is an internal-use only event.|
The Member Dropped event type is no longer supported for event notification. When you upgrade to 11.0, all existing Member Dropped event types that are configured for your project in InfoSphere MDM Workbench are converted to the Member Delete event type. If you have enabled event notification, a member drop interaction should be executed only when your consuming external systems no longer need information or notifications for that member.