Troubleshoot

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Connector10.11

Troubleshoot

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.
In the Options page of the policy, under Unmatched Events, select are forwarded to OMi Server.
Save the policy and activate it. The activation starts the opcmsgi process on the Operations Connector server.
Use the opcmsg command-line tool to submit messages to the open message interface policy.
In OMi, navigate to the Event Browser and verify that the events you submitted using opcmsg have 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.

Troubleshoot

Related topics