Event Manager

The Event Manager is a component that detects events and activities.

You can customize the Event Manager to meet your business needs.

Event Manager business rules
Business rules are used to detect an event that occurs after the passage of time, or when an event is the result of a transaction, unless the event is explicitly recorded as a result of a customer interaction.
Event Manager design overview
The InfoSphere MDM Event Manager consists of five major subsystems: services layer, event detector message-driven bean (MDB) with process controller, event analyst or detector, event persistence module, and notification module.
Events detected by the passage of time
When using the time-based detection process, Event Manager selects all business objects with a next process date that is set to the current date or earlier.
Events triggered by a transaction
When InfoSphere MDM performs a transaction that modifies data related to the business object, it needs to inform Event Manager about the data change. Event Manager re-executes all the business rules to see if there are new occurred or pending events.
Explicit events
Event Manager can persist information about explicit events.
Event Manager with InfoSphere MDM
The Event Manager services layer consists of two InfoSphere MDM stateless session beans: ProcessController bean and EventService bean.
The Event Manager data model
Event Manager data is managed by a set of database tables.
Definition tables for Event Manager
Setting up business systems and business entities
You must determine which business system and which business entities (that is, the types of business objects from that business system) for which Event Manager should be detecting events.
Event definitions and categories
Every type of event that you want Event Manager to monitor is determined by an event definition. For example, to monitor whether a business entity is turning 65 years old, you create an event definition (such as Turning65) in the CDEVENTDEFTP table. Since you can monitor more than one type of event for the same business entity, you can define other event definitions (such as Turning70 and RRSP).
Business rules for event definitions
Events are detected by executing business rules. For example, to detect whether an entity is over 65 years old, a rule can compare the entity's birth date with the current date. If the difference is over 65 years, the Turning65 event has occurred.
Processing options for event detection
When the business system calls Event Manager to detect events, Event Manager checks the PROCESSCONTROL and PROCESSACTION operational tables, calls the business adapter to get the business object, executes the business rules, and finally updates the EVENT table if the event is successfully detected.
Manual maintenance of operational data
You can maintain the PROCESSCONTROL and PROCESSACTION records using SQL statements.
Operational table maintenance
Three operational tables hold the data pertaining to the business objects and their occurred events as the events are being detected by Event Manager.
The PROCESSCONTROL table
The PROCESSCONTROL table contains a reference to each business object in InfoSphere MDM. It has a foreign key relationship with PRODENTITY table, which contains information about the business entity of that business object.
The PROCESSACTION table
After you populate the PROCESSCONTROL table, for each type of event category you want to monitor for the business object, you need to create a PROCESSACTION record.
Operational data and transactions
You can use various transactions to maintain the PROCESSCONTROL and PROCESSACTION records.
Business rules
Business rules are responsible for detecting the occurrence of events and predicting the time future events may occur. Event Manager uses the externalized rules component to configure the business rules.
Business rule implementation using Java
To implement business rules as Java™ code, write the class that implements the com.dwl.base.externalrule.Rule interface.
The business adapter
The business adapter implements the IEventBusinessAdapter interface.
Calls to Event Manager from the business system
To notify Event Manager about business transactions, the business system can call one of the processTask() methods of the ProcessController bean.
Event detection for all configured event categories
To detect events for all the configured event categories for the business system or business entity combination, use the following processTask() method.
Event detection for explicit event categories
To detect events for event categories that you want to specify explicitly, use the following processTask() method.
User explicit events
To add a user explicit event, call the processTask() method of ProcessControllerBean.
Time-based event detection
When the PROCESSCONTROL and PROCESSACTION tables are set up properly, either automatically as a result of the business system calling into Event Manager or by manually adding records to these tables. Events can be reevaluated by starting the EventDetectionScheduleController.
The EventDetectionScheduleController
The EventDetectionScheduleController class calls the ProcessControllerInternal session bean. The location of the bean is configured in the EventManagerClient.properties file in the property ProcessControllerInternal.PROVIDER_URL.
The notification topic
Event Manager uses the notification component to send XML messages to the topic, which is a publish-subscribe type of JMS destination. Notification is issued for each event if that event's definition is configured in the CDEVENTDEFTP table with the ENABLE_NOTIFY field set to Y.

Parent topic: Platform and core feature overview

Last updated: 12 August 2019