Previous Topic: Configure Event Connector CI Creation and AssociationNext Topic: Event Connector Troubleshooting


Event Connector Scenario: Integrating with CA OPS/MVS EMA

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:

  1. Configure a trap destination in CA OPS/MVS EMA for the Event connector server.
  2. Access the CA Event Integration administrative interface.

    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.

  3. Select View Policies.

    The View Policies displays.

  4. Select mfopsmvs-src.xml.

    The Policy Configuration: SAMAdapter displays.

  5. Enter the port number you want to use for receiving traps in the port field, then click Save.

    The CA OPS/MVS EMA source policy is configured. The SNMP source sends all traps to the CA Event Integration host on this port.

  6. Select the Catalogs tab, select samevent, and click Edit.

    The Edit Catalog displays.

  7. Add mfopsmvs-src.xml to the Selected Sources pane on the Select Source Policies page and click Next.

    The Select Destination Policies displays.

  8. Verify that the Selected Destination Policies pane contains sampc-dest.xml and click Next.

    The Select Enrichment Policies displays.

  9. Click Finish.

    The catalog is saved and the View Catalogs page displays again.

  10. Select the Connectors tab.

    The View Connectors displays. The samevent catalog should already be assigned to the Event connector.

  11. Select the connector corresponding to the Event connector system and click Deploy.

    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.

  12. Model a service in CA SOI with the Server class CIs created by the CA OPS/MVS EMA alarms.

    The alarms display as infrastructure alerts in the Alerts tab of the Operations Console for the associated CIs.