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 Manager i10.62

Develop > Integrate external event processes > Error handling

Error handling

The OMi event synchronization interface that forwards events and subsequent changes uses the error handling algorithms described in this section to determine if a forward request should be retried or discarded.

Error handling is different depending on the type of integration:

Groovy Script Integration

If you implement a Groovy script to integrate your application, error handling is as follows.

For forwardEvent()and forwardChange():

Return of true: The request is marked as FORWARDED and the forward request is removed from the queue.
Return of false: The request will be put back in the queue. Retries are done once a minute until the request succeeds or the request is in the queue longer than the Event Forwarding Expiration Time (default is 12 hours and may be changed in the Infrastructure Settings). New events and updates are forwarded in the order the forward request was received. Should a request fail due to a Non-RuntimeException error it will block all other requests for this server. All new events in the queue are delivered before delivering any outstanding updates.

For forwardEvents():

Return of true: All forward event requests are marked as FORWARDED and the forward requests are removed from the queue. If all events have had the forward status set to FORWARDED, the exception is logged.
Return of false: If there are events that are not marked as FORWARDED, then the first event without a result is handled in the normal exception processing. The remaining events are left queued and retried later.

See also standard error handling for forwardEvent() defined in the com.hp.opr.api.ws.adapter.ExternalProcessAdapter interface.

For forwardChanges():

Return of true: All forward change requests are marked as FORWARDED and the forward requests are removed from the queue. If all change requests have had the forward status set to FORWARDED, the exception is logged.
Return of false: If there are changes that are not marked as FORWARDED, then the first change without a result is handled in the normal exception processing. The remaining changes are left queued and retried later.

See also standard error handling for forwardEvent() defined in the com.hp.opr.api.ws.adapter.ExternalProcessAdapter interface.

For receiveChanges():

Error handling is the same as for receiveChange() defined in the com.hp.opr.api.ws.adapter.ExternalProcessAdapter interface.

If the Groovy script throws an exception, it is handled as follows:

org.apache.wink.client.ClientWebException: The exception is queried for the HTTP status code returned by the server. If an HTTP status code is found the status code is handled just as in the Web Service Integration case described in Error handling. If the status code does not exist, the exception is handled just as any other exception, see below for more information.
Any exception other than ClientWebException: The exception is recursively searched for the root cause exception and then interpreted as follows:
- RuntimeException: Error is logged to the opr-event-sync-adapter.log log file and the request is marked as FAILED. There is no retry for this request.
- Non-RuntimeException: Examples would be IOException, SocketException, and so on. Error is logged to the opr-event-sync-adapter.log log file. In this case it is expected that the connection to the server will recover at some future time and be able to send the request. The request will be put back in the queue. Retries are done once a minute until the request succeeds or the request is in the queue longer than the Event Forwarding Expiration Time (default is 12 hours and may be changed in the Infrastructure Settings). New events and updates are forwarded in the order the forward request was received. Should a request fail due to a Non-RuntimeException error it will block all other requests for this server. All new events in the queue are delivered before delivering any outstanding updates.

Send Help Center feedback