The Event connector can integrate alarms from CA OPS/MVS EMA to expose mainframe data for management in CA SOI.
When you dispatch alarms to CA SOI, you can model services with the CA OPS/MVS EMA Server class CIs created by the connector to view mainframe alarms from the Operations Console and enable functionality such as escalation policy and enrichment for these alarms.
In this scenario, you configure CA OPS/MVS EMA alarm collection through SNMP traps and dispatch the alarms to CA SOI as infrastructure alerts.
Note: This scenario assumes that the Event connector was installed successfully with all preconfiguration complete.
Follow these steps:
The CA Event Integration administrative interface displays. CA OPS/MVS EMA source policy requires a basic configuration before you can use it in a catalog.
The View Policies displays.
The Policy Configuration: SAMAdapter displays.
The CA OPS/MVS EMA source policy is configured. The SNMP source sends all traps to the CA Event Integration host on this port.
The Edit Catalog displays.
The Select Destination Policies displays.
The Select Enrichment Policies displays.
The catalog is saved and the View Catalogs page displays again.
The View Connectors displays. The samevent catalog should already be assigned to the Event connector.
The catalog deploys and the connector begins collecting CA OPS/MVS EMA alarms and dispatching them to CA SOI.
Generated alarms publish as SNMP traps, where the connector collects, processes, and publishes them to CA SOI as infrastructure alerts.
The alarms display as infrastructure alerts in the Alerts tab of the Operations Console for the associated CIs.
|
Copyright © 2013 CA.
All rights reserved.
|
|