Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Incident Exchange (OMi - SM) integration
- Incident Exchange (OMi - SM) integration setup
- Create user accounts for the Incident Exchange (OMi - SM) integration
- Configure the Service Manager server as a connected server in OMi
- Configure an event forwarding rule in OMi
- Enable incident drill-down from OMi Event Browser
- Configure SSL for the Incident Exchange (OMi - SM) integration
- Configure the Instance Count in the SMOMi integration template
- Add an integration instance for each OMi server
- Enable LW-SSO for the Incident Exchange (OMi - SM) integration
- Configure automatic closure for OMi incidents
- Change the default assignment group for OMi incidents
- Synchronization of incident changes back to OMi
- Working with the 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 Business Service Management (BSM) systems.
-
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 Operations Manager i (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 Operations Manager i (OMi).
Perform this task in BSM OMi. If you need to integrate Service Manager with more than one OMi server, perform this task on each of the OMi servers.
-
Enable incident drill-down from Operations Manager i (OMi) Event Browser.
This task configures the Service Manager web tier in the sm:ServiceManagerAdapter script in OMi.
-
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 have more than one OMi server. The Instance Count setting defines the allowed number of SMOMi integration instances in Service Manager (default: 1).
-
Add an integration instance for each Operations Manager i (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.
-
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 BSM.
-
(Optional) Configure automatic closure for OMi incidents.
This task is optional. 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.
This task is optional. 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).
Related concepts
Integrations
Integration Manager
HPE Business Service Management (BSM)
BSM Business Impact Report (BIR)
Synchronization of incident changes back to Operations Manager i (OMi)
Related tasks
Add an integration instance for each Operations Manager i (OMi) server
Enable LW-SSO for the Incident Exchange (OMi - SM) integration
Configure LW-SSO in the Service Manager Web tier
Edit an integration instance
Enable or disable an integration instance
Configure automatic closure for OMi incidents
Mark an incident for automatic closure
View related OMi event details from an incident
Change the default assignment group for OMi incidents
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM@hp.com.
Help Topic ID:
Product:
Topic Title:
Feedback: