Troubleshooting and Limitations
This section provides help in troubleshooting problems relating to Operations Connector in general.
Tomcat Logging
Tomcat log output is written to the <OvDataDir>/log/Tomcat/stderr.log file.
Verify That Operations Connector Can Send Events to OMi
You can use the following procedure to verify that Operations Connector events actually arrive in the Event Browser.
-
Create an open message interface policy. For details, see Open Message Interface Policies (Events only).
-
In the Options page of the policy, under Unmatched Events, select are forwarded to OMi Server. For details, see Configuring Options in Open Message Interface Policies.
-
Save the policy and activate it. The activation starts the
opcmsgiprocess on the Operations Connector server. -
Use the
opcmsgcommand-line tool to submit messages to the open message interface policy. For details, see opcmsg Command-Line Tool. -
In OMi, navigate to the Event Browser and verify that the events you submitted using
opcmsghave arrived.
Debug Trace Logging for Events
To enable debug trace logging for an event, add the custom attribute __TRACE__ and set it to any value. The attribute creates flow trace logs at the INFO level for this event.
The attribute can be set in the Custom Attributes tab of the policy that sends the event. Whenever this custom attribute is set on an event, trace output for this event appears in the trace logs:
-
OMi Data Processing Server:
log/opr-backend/opr-flowtrace-backend.log -
OMi Gateway Server:
log/wde/opr-gateway-flowtrace.log
By default, only events with the custom attribute __TRACE__ set are logged to the flow trace log files. To enable flow tracing for all events, set the flow trace log level to DEBUG.