System Automation Application Manager v.Next continues to send EIF events to an event console like IBM NetCool/OMNIbus or Tivoli Enterprise Console, including simplified configuration and enhanced performance.
Until System Automation Application Manager version 3.2.2, the configuration to integrate with an event console is partly done in the end-to-end automation configuration tool and partly in the WebSphere Application Server (WAS) configuration:
Configuration tool: Enable the check box "Enable EIF event generation for TEC or OMNIbus".
WAS configuration: Enable the Common Event Infrastructure (CEI) service.
WAS configuration: Define the event console host name and port number within a Java Messaging Service (JMS) queue connection factory.
Defining an event filter at the event sender side requires to perform several additional configuration tasks in CEI, including the creation of an XPath event selector string.
In System Automation Application Manager v.Next, the configuration is consolidated on one single tab in the end-to-end automation configuration tool:
System Automation Application Manager v.Next passes these configuration data and the EIF events directly to the IBM NetCool/OMNIbus EIF toolkit (evd.jar).
Benefits of this change:
Eliminates the need for two intermediate technology layers (including CEI, which has been deprecated by WAS).
Eliminates the need to convert events to an intermediate event format (Common Base Event, which is the event format required by CEI).
Several installation steps are removed.
Run time performance for sending EIF events is improved.
Note that the same run time improvements for sending events apply to EIF event integration with Globally Dispersed Parallel Sysplex (GDPS). There are two separate configuration files for the primary GDPS server and the backup GDPS server that may be edited directly.