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)`

Service Manager9.51

Integrate > HPE Operations Manager i (OMi) > Incident Exchange (OMi - SM) integration > Incident Exchange (OMi - SM) integration setup

Incident Exchange (OMi - SM) integration setup

The Incident Exchange (OMi - SM) integration requires the following configuration tasks be completed on the HPE Service Manager and Operations Manager i (OMi) systems.

Note Configuring Service Manager web service integrations in a network environment using a firewall or proxy server requires additional configuration. For details, see Web Services with a proxy server.

Create user accounts for the Incident Exchange (OMi - SM) integration.

This task creates a user account on each product side for the two systems to connect to each other and to synchronize data.
Configure an event forwarding rule in OMi.

This task configures a rule for the OMi server to forward events to the Service Manager server.
Configure the Service Manager server as a connected server in OMi.

This task configures the connection settings for the target Service Manager server. If you need to integrate Service Manager with more than one OMi server, perform this task on each of the OMi servers.
(Optional) Add custom attributes and map to SM fields.

This task adds your own custom attributes in the Groovy script selected for the SM server and maps the attributes to appropriate fields in SM.
Enable event drill-down from Service Manager into OMi

This task sets up Service Manager operators as valid users with appropriate permissions in OMi. These permissions are required for the users to perform event drill-down from Service Manager to OMi.
Enable incident drill-down from the OMi Event Browser.

This task configures the Service Manager web tier in the sm:ServiceManagerAdapter script in OMi.
(Optional)Configure SSL for the Incident Exchange (OMi - SM) integration .

This task is needed if your OMi server requires HTTPS connections. If SSL is not configured in this case, changes on incidents that are created from OMi will not be able to be synchronized back to OMi.
Configure the Instance Count in the SMOMi integration template.

This task is needed only when you use more than one OMi server. The Instance Count setting defines the allowed number of SM-OMi integration instances in Service Manager (default: 1).
Add an integration instance for each OMi server.

This task creates and enables an instance of this integration in Integration Manager (SMIS). A separate integration instance is required for each OMi server.
(Optional) Enable LW-SSO for the Incident Exchange (OMi - SM) integration.

Lightweight Single Sign-On (LW-SSO) is optional but recommended for the Incident Exchange (OMi - SM) integration. This task includes enabling LW-SSO in the Service Manager server and Web tier, as well as in OMi.
(Optional) Configure automatic closure for OMi incidents.

By default, automatic closure is disabled for OMi incidents. System administrators can enable automatic closure and further configure under what conditions OMi incidents can be automatically closed.
(Optional) Change the default assignment group for OMi incidents.

When created, OMi incidents are automatically assigned with an assignment group based on their certain field values and a predefined default assignment group. System Administrators can change the default assignment group setting ( Application).
Test the connection

This task sends an event to the OMi server that matches the filter you defined (in our example filter, the severity value is Critical), and then verifies that the event is forwarded to Service Manager as expected.
(Optional) Synchronize attributes

Not all attributes are synchronized back from SM to OMi by default. This task changes the out-of-box behavior regarding which attributes are synchronized upon change.

Send Help Center feedback