Use the following steps as a checklist to configure and use IBM® Relationship
Resolution Event Manager.
About this task:
The following steps must be completed before you can process events
using Event Manager.
Procedure:
- Required: Create an event business rules XML file for
CEP, the IBM external complex event processor.
- Install the complex
event processor tool for Event Manager. This tool is included
in a ZIP file in the IBM Relationship Resolution v4.2. fix pack CD or download.
- Start with the default cep.xml event business
rules provided. This file contains the required configurations and parameters. The default files for the IBM Relationship Resolution v4.2. fix pack
releases are:
- cep.xml
- The default event business rules file installed with IBM Relationship
Resolution v4.2 fix pack 1
- cep.xml.example_4.2.0.2
- The default event business rules file installed with IBM Relationship
Resolution v4.2 fix pack 2. If you have upgraded to IBM Relationship Resolution
v4.2 fix pack 2 from IBM Relationship Resolution v4.2 fix pack 1, the installer
does not overwrite your existing cep.xml file.
Note: This file must be renamed to cep.xml in order
to enable the IBM Relationship
Resolution Event Manager if you are not upgrading from IBM Relationship Resolution
v4.2 fix pack 1.
- Customize the event business rules configuration to meet your
business needs and situations, using the CEP EclipseTM-based business
rule authoring tool.
- Copy the resulting updated event business rules XML file to
the directory.
- Rename the XML file to cep.xml. IBM Relationship
Resolution Event Manager is configured to only use the cep.xml file.
Backup or rename your existing cep.xml file before renaming
your new cep.xml file.
- Required: Run
the post-installation database specific SQL scripts. These
scripts update the IBM Relationship Resolution schema to include the event
tables, indexes, and default parameter values for Event Manager.
- Required: Configure
Event Manager system parameters.
- Required: Configure
event types.
- Optional: Run
a Configuration report. Whenever you change or update system
configuration (such as system parameters and event types), it is a good idea
to review the Configuration report.
- To see event alerts in the Visualizer, do the following:
- Optional: The Visualizer already contains default
activity codes for dealing with event alerts (Pending, Assigned, and Closed).
But you can create
additional activity codes for event alerts in the Configuration Console,
if you wish. Stop all running pipelines before creating the activity codes,
and then re-start the pipelines after the activity codes are created.
- You can review
event alerts, change
the status of event alerts, assign
event alerts to yourself, or assign
event alerts to another Visualizer analyst group.
- If you want to view the full details about a specific event
alert, you can generate an Event
Alert Detail report.
- You can view
the event alert history for an entity on the entity resume.
- From the entity resume, you can click the Show Events button
to view all the
events for the entity. Or you can click the Report button
to print an All Events
report for an entity.
- Required: Use the
EVENT data segment data definitions to include event processing information
in the UMF data that you
convert to send to the
IBM Relationship Resolution pipelines.
- Optional: If you want to send IBM Relationship Resolution
messages (including Event Manager messages) to your client application, make
sure to use an HTTP pipeline, and make sure that your client application can
receive messages from the standard SYSTEM_MESSAGE return document.
- After Event Manager processes events, you can review the Event Manager log files and the associated Configuration Console log files.