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.41

Integrate > HPE Operations Manager i (OMi) > Incident Exchange (OMi - SM) integration > Incident Exchange (OMi - SM) integration setup > Add an integration instance for each OMi server

Add an integration instance for each OMi server

Applies to User Roles:

System Administrator

Once you have completed your configuration in Operations Manager i (OMi), and have changed the Instance Count setting in the SMOMi integration template (which is needed only when you have multiple OMi servers), you are ready to add and enable a separate integration instance in Service Manager for each OMi server. For example, if you have two OMi servers, you must configure two SMOMi integration instances.

Support of multiple OMi servers

As of version 9.34, Service Manager can integrate with multiple OMi servers. This is implemented through the Instance Count setting and the omi.mgr.id parameter in the SMOMi integration template.

By default, the SMOMi integration template supports only one integration instance. If you have multiple OMi servers, before you proceed, make sure you have already updated the Instance Count setting in the SMOMi integration template. For details, see Configure the Instance Count in the SMOMi integration template.

When using the omi.mgr.id parameter, keep the following in mind:

If you have only one OMi server (and hence need only one SMOMi integration instance), you must either correctly configure this parameter or clear the entire row of this parameter (both the parameter name and value) in the SMOMi integration instance, otherwise the integration will not work.
If you have multiple OMi servers (and hence need multiple SMOMi integration instances), you must correctly configure this parameter in all SMOMi integration instances. Only those correctly configured integration instances will work. If none of the SMOMi integration instances are correctly configured, none of them will work.
Users can view the OMi event details from an OMi incident record only when you specify the omi.mgr.id parameter correctly. If the value you specify in the corresponding SMOMi integration instance does not match the Universally Unique Identifier (UUID) which is automatically generated in the OMi server for the target Service Manager server and stored in the Incident record, users will not see the View OMi Event option from the Incident record.

To add and enable an Incident Exchange (OMi - SM) integration instance:

Log on to Service Manager as a system administrator.
Click Tailoring > Integration Manager.
Click Add.

The Integration Template Selection wizard opens.
Select SMOMi from the Integration Template list.

Note Ignore the Import Mapping check box, which has no effect on this integration.
Click Next.
Complete the integration instance information:
- Modify the Name and Version fields to the exact values you need.
- In the Interval Time (s) field, enter a value. For example: 600. If an OMi opened incident fails to be synchronized back to OMi, Service Manager will retry the failed task at the specified interval (for example, 600 seconds).
- In the Max Retry Times field, enter a value. For example: 10. This is the maximum allowed number of retries for each failed task.
- (Optional) In the SM Server field, specify a display name for the Service Manager server host. For example: my_Local_SM.
- (Optional) In the Endpoint Server field, specify a display name for the BSM server host. For example: my_BSM_1.
- (Optional) In the Log File Directory field, specify a directory where log files of the integration will be stored. This must be a directory that already exists on the Service Manager server host.
- (Optional) In the Log Level field, change the log level from INFO (default) to another level. For example: WARNING.
- (Optional) If you want this integration instance to be automatically enabled when the Service Manager Server service is started, select Run at system startup.
Click Next. The Integration Instance Parameters page opens.

On the General Parameters tab, complete the following fields as necessary:

Field	Sample Value	Description
omi.server.url	http://<servername>:<port>/opr-gateway/rest/synchronization/event	This is the URL address of the OMi server's RESTful web service. Replace <servername> and <port> with the fully qualified domain name and port number of your OMi server.
http.conn.timeout	30	The HTTP connection timeout setting in seconds. Note The out-of-box value is 30 (seconds), and 15 (seconds) is used if this field is empty.
http.rec.timeout	30	The HTTP receive timeout setting in seconds. Note The out-of-box value is 30 (seconds), and 15 (seconds) is used if this field is empty.
http.send.timeout	30	The HTTP send timeout setting in seconds. Note The out-of-box value is 30 (seconds), and 15 (seconds) is used if this field is empty.
sm.mgr.id	55436DBE-F81E-4799-BA05-65DE9404343B	The Universally Unique Identifier (UUID) automatically generated for this instance of Service Manager. Note This field is automatically completed each time when you add an SMOMi integration instance. Do not change it, otherwise the integration will not work properly.
omi.reference.prefix	urn:x-hp:2009:opr:	The prefix of the BDM External Process Reference field, which will be present in incoming synchronization requests from the OMi server. Note This field is automatically completed and has a fixed value. Do not change it.
sm.reference.prefix	urn:x-hp:2009:sm:	The prefix of the BDM External Process Reference field, which will be present in outgoing synchronization requests from Service Manager. Note This field is automatically completed and has a fixed value. Do not change it.
omi.eventdetail.baseurl	http://<servername>/opr-console/opr-evt-details.jsp?eventId=	The basic URL address of the event detail page in OMi. Replace <servername> with the fully qualified domain name of your OMi server.

On the General Parameters and Secure Parameters tabs, enter three parameter values that you specified when configuring the Service Manager server as a connected server in BSM OMi. The following table lists the parameters, whose values you can copy from your BSM OMi server.

To copy the parameter values from BSM OMi, follow these steps:

Log on to BSM as a system administrator.
Navigate to Admin > Operations Management > Setup > Connected Servers.
Locate your Service Manager server configuration entry and double-click anywhere on the entry pane.
On the General tab, copy the ID string at the bottom into the omi.mgr.id field in Service Manager.
On the Incoming Connection tab, copy the User Name and Password to the username and Password fields in Service Manager, respectively.

Field	Sample Value	Description
omi.mgr.id (on the General Parameters tab)	f3832ff4-a6b9-4228-9fed-b79105afa3e4	The Universally Unique Identifier (UUID) automatically generated in OMi for the target Service Manager server. Note This parameter was introduced to support multiple OMi servers. Service Manager uses the UUID to identify from which OMi server an incident was opened. Be aware that if you delete the connected server configuration for the Service Manager server in OMi and then recreate the same configuration, OMi generates a new UUID. You need to reconfigure the integration instance by changing the old UUID to the new one. Tip If you have only one OMi server, you can simply remove this parameter (remove both the parameter name and value) from the integration instance. See Support of multiple OMi servers.
username omi.mgr.id (on the General Parameters tab)	SM_Server	This is the user name that the Service Manager server uses to synchronize incident changes back to the OMi server.
Password (on the Secure Parameters tab)	SM_Server_Password	This is the password that the Service Manager server uses to synchronize incident changes back to the OMi server.

Click Verify Connection.

If everything is fine, the following message is displayed: Verification succeeded.
Click Next twice, and then click Finish.

Note Leave the Integration Instance Mapping and Integration Instance Fields settings blank. This integration does not use these settings.

Service Manager creates the instance. You can edit, enable, disable, or delete it in Integration Manager.
Enable the integration instance.
If you have multiple OMi servers, repeat the steps above for the rest of your OMi servers.

Next, you can optionally enable Lightweight Single Sign-On (LW-SSO) in both OMi and Service Manager so that users can bypass the log-in prompts. For details, see Enable LW-SSO for the Incident Exchange (OMi - SM) integration.

Send Help Center feedback