Troubleshooting the Collection of Events

When unexpected events (alerts) appear in OMi or you miss specific OEM entities, the root cause of the problem may be improper integration configuration, inadequate definition of entity mapping or rules in the corresponding Operations Connector policies, or some other reason. To ease the inspection of data flow between OEM and Operations Connector, Ops Connector for OEM can create output files with collected events (alerts). Such output files contain the XML formatted data acquired from the integrated OEM instance, but they are not used in data forwarding to Operations Connector.

Because the topology and metric integration of Ops Connector for OEM use a different data relaying pipeline, this troubleshooting method is not available for OEM topology and metrics.

To generate the event output file on the Operations Connector host, perform the following steps:

1. Change the current directory to <OvDataDir>/conf/HPBsmIntOEM/genint and open the appropriate integration configuration file in a plain text editor. To determine which configuration file to modify, see Configuration Options topic.

2. In the processor subsection of the nodes section, change the value of the copy-count option to 1.

3. In the pipe section, uncomment the line with the following definition:

   • For the event integration: copysplitter -1-> eventxmlsink

4. Optional: To fine‑tune the output file generation, adjust the options in the following subsection of the nodes section:

   • For the event integration: sink (eventxmlsink)

5. Save your changes.

6. Restart the event integration service as described in Restarting the Services topic.

The output file with the XML-formatted event data is created at the location defined with the filename option in the sink (eventxmlsink) subsection of the integration configuration file.

Related topics

Configuration Options

Restarting the Integrations