Connector Integrations › Connector Integration Example Scenarios › Event Connector Integration

Event Connector Integration

The Event connector uses the integration adaptors provided with the CA Event Integration installation, which is deployed with CA SOI. The adaptors support a variety of sources and are driven by CA Event Integration source policy, which you can tailor based on your specific needs. The following are the integration adaptors:

LogReader

Scans file system log files local to the application system.

Policy File: Applog-src

WinSysLog

Scans Windows system, application, or security event logs.

Policy File: Syslog-src

SNMPplugin

Receives SNMP traps on the configured port.

Policy Files: Snmp-src, hpbac-src, mfopsmvs-src, and mfsysview-src

UniEvent

Reads CA NSM events. It is local to the CA NSM Event Manager.

Policy File: Nsmevent-src

WSEventing

Defines an event publisher from which to collect web service notifications and the event details of the publisher.

Policy File: Wsevent-src

You can develop a policy-based Event connector integration if the integrated application already writes events to log files or uses another of the provided adaptor method (such as SNMP trap communication). The Event connector processes this information with the following considerations:

• You create or modify a CA Event Integration source policy that instruments the appropriate adaptor.
• Depending on the adaptor type, you might need an Event connector installation that is local to the integrated application. You can use central event receivers on existing CA Event Integration manager installations.
• The connector retrieves events from the source, uses the policy to transform the events, and forwards them to CA SOI.
• Depending on the configured reconciliation level, the connector implicitly creates event-related, device-level, and instance-level CIs.
• You cannot create services and relationships.
• Full synchronization is not provided; therefore, the status for Event connector CIs might not be current after a CA SOI server restart or in newly created service models

Note: For more information about developing CA Event Integration source policy, see the CA Event Integration Product Guide.