Troubleshooting the Collection of Events

When unexpected events appear in OMi or you miss specific SIM 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 SIM and Operations Connector, OpsCx for SIM can create output files with collected events. Such output files contain the XML formatted data acquired from the integrated SIM instance, but they are not used in data forwarding to Operations Connector.

Because the topology integration of OpsCx for SIM uses a different data relaying pipeline, this troubleshooting method is not available for SIM topology.

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

1. Change the current directory to <OvDataDir>/conf/HPBsmIntSIM and open the sim_events.conf file in a plain text editor.

2. In the nodes section in the processor subsection, set the copy‑count option to 1.

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

   eventcopysplitter -1-> xmleventsink

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

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 (xmleventsink) subsection of the integration configuration file.

Related topics

Restarting the Services