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

Integrate > SAP Solution Manager > Troubleshoot > Troubleshooting the Collection of Events

Troubleshooting the Collection of Events

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

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

Change the current directory to <OvDataDir>/conf/HPBsmIntSapSolma/genint and open the event configuration file in a plain text editor.
In the processor subsection of the nodes section, uncomment the copy-count option and make sure it is set to 1.
Optional: To fine‑tune the output file generation, adjust the options in the sink(eventsink) subsection of the nodes section.
Save your changes.
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(eventsink) subsection of the event configuration file.

Troubleshooting the Collection of Events

Related topics