Previous Topic: Event Connector ImportNext Topic: CA NSM Events


Configure the Event Connector

If the Event connector installs correctly, it registers with the SA Manager and CA Event Integration manager. If you installed on a Windows system, a catalog named samevent is created and deployed in the CA Event Integration manager. By default, this catalog dispatches events from the following sources to CA SOI:

Each event source is controlled by a source policy file. While the default sources do not require policy configuration, other available sources do require you to configure policy by adding attributes that let the connector establish a connection with the event source. To customize the Event connector configuration, you may need to refine how events are collected from the default sources, add and configure additional sources, or remove the default sources.

Note: You must include the CIs created by the Event connector in services only if you want to see the alerts in the context of services. Event connector events appear in the Event Store and in alert queues even if they are not associated with services.

You can configure the sources that the Event connector collects from the CA Event Integration administrative interface.

Note: This procedure covers a full configuration scenario, which is required for a connector installed on a Solaris or Linux system. You may not need to perform all steps in this procedure if the Event connector on Windows preconfigured correctly or if you want to leave the default sources. No configuration is required if you installed on a Windows system and want to keep the default configuration.

Follow these steps:

  1. (Optional) Complete any required configuration on the event sources.

    HP BAC, CA OPS/MVS EMA, and CA SYSVIEW PM require domain manager configuration before the connector can integrate with these sources.

    Note: For more information, see the topics specific to these sources.

  2. Select Start, Programs, CA, Event Integration, Manager User Interface to launch CA Event Integration.

    The CA Event Integration administrative interface login page displays.

  3. Enter the credentials you provided for the CA Event Integration interface user during installation, and click Log In.

    The CA Event Integration administrative interface displays with the Dashboard tab visible.

  4. Select the Policies tab.

    The View Policies page displays.

  5. Do the following for each source whose events you want to collect:
    1. Select the source-src.xml file.
    2. Configure the source policy attributes.

    Note: For more information about configuring policy for each source, see the source-specific topics that follow or the CA Event Integration Online Help.

  6. Select the sampc-dest.xml file.

    The Policy Configuration: SAMAdapter page displays.

  7. Verify that all connection settings are entered correctly, make any necessary changes to connect to the appropriate SA Manager, and click Save.

    Note: This file should be configured correctly if the preconfiguration was successful. Do not change the topicout field value. For more information about the reconcile_level field, see Configure Event Connector CI Creation and Association.

    The connection to CA SOI is configured.

  8. Select the Catalogs tab.

    The View Catalogs page displays.

  9. Do one of the following:

    The Edit Catalog or New Catalog page displays.

  10. Edit the source policy included in the catalog so that all necessary sources are represented in the Selected Sources pane and click Next.

    The Select Destination Policies page displays.

  11. Ensure that sampc-dest.xml is in the Selected Destinations pane and click Next.

    The Select Enrichment Policies page displays.

  12. Click Next.
  13. (Optional) Name the catalog and click Finish.
  14. Select the Connectors tab and do one of the following:
  15. (Optional) Create services in CA SOI that contain the associated CIs.

    Note: You can search for CIs by source in the Service Modeler to view all CIs created by the Event connector.

    The events appear as infrastructure alerts associated with the appropriate CIs in the Operations Console.