Troubleshooting the Collection of Events and Topology

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

Troubleshooting the Event Collection

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

1. Change the current directory to <OvDataDir>/conf/HPBsmIntTivoli and open the appropriate integration configuration file in a plain text editor.

2. In the nodes section's Tracing Options, in the processor subsection, uncomment the copy‑count option and set its value to 1.

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

   copier -1-> xmltrace

4. Optional: To fine‑tune the output file generation, adjust the options in the sink (xmltrace) 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 integration configuration file.

Troubleshooting the Topology Collection

If you experience issues with topology collection, check if files relevant for creating configuration items are being generated:

• <OvDataDir>/datafiles/HPBsmIntTivoli/discovery-event.json,
  <OvDataDir>/datafiles/HPBsmIntTivoli/discovery-metric.json
• <OvDataDir>/datafiles/HPBsmIntTivoli/tivoli_topology.xml
• <OvDataDir>/datafiles/HPBsmIntTivoli/self_discovery.xml

If any of the files are not being generated properly:

1. Check if the tivolie, tivolim, and tivolit services are running. To build the topology, Operations Connector for IBM Tivoli requires that tivolie and/or tivolim services are running besides tivolit.
2. Carefully follow the related installation and configuration instructions in this document, and check if configuration options are properly set in both the event and topology configuration files.

Related topics

Restarting the Services