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 |
|
External systems - Operations Manager i integration
Service Management provides a framework to create and update incidents in Service Management based on events in Operations Manager i (OMi). The case exchange framework enables you to define an external system with which information will be exchanged.
For example, you could use the integration to configure CI Status alerts in OMi to automatically open a corresponding incident in Service Management. The OMi Event management console determines which events should generate incidents and be added to an ITSM process to:
- Resolve the incident
- Alert agents and end users
To set up the integration:
- It is best to create a user account for purposes of integration. Create a Service Management integration user and log in using the credentials you defined.
- Download and install the On-Premise Bridge Agent and specify the OMi credentials using the Endpoint Credentials Manager. For more information, see How to use On-Premise Bridge agents on Windows or How to use On-Premise Bridge agents on Linux.
-
Add an agent and deploy the agent's server-connections.conf file to the On Premise Bridge.
-
Create an endpoint and configure it. Select REST Executor 1.0 as the endpoint type.
For the Location field, enter the URL for the OMi server. The URL should end with /opr-gateway/, for example: http://sample.omi.hostname/opr-gateway/.
The available values for the Credentials field come from the credentials defined in the On-Premise Bridge. As a result, the drop-down list of values may not appear immediately.
For more information, see How to use endpoints.
- Add an external system record for your OMi integration. For the Authorized user, select the user account for this integration. For information, see Working with external systems.
-
Apply the external predefined configuration to the external system you created:
- Select the external system and click Edit.
-
Select the endpoint created in Step 4.
- Click Apply configuration and select the OMi 9.2x configuration. Click Confirm.
- Click Save to save the changes to the external system.
-
Download the OMi Groovy script and documentation from ITOM Marketplace. To download the script, access the following OMi page: OMi Integration with Service Management Automation. You may need to log in with your Software Passport.
-
Edit the script for integration with Service Management. The following table displays the parameters to be edited:
Parameter Description Required/Optional SAW_TENANTID The Service Management tenant ID Required EXTERNAL_SYSTEM_ID The System ID of the OMi external system (which you entered when you defined the external system in Service Management). Required BSM_ADMINISTRATOR_LOGIN_NAME The default user UPN to be used for the RequestedBy property of system-generated incidents
Required DESCRIPTION A default description used for the created incident when no description is entered for the event. Optional COMPLETION_CODE The completion code to use when posting a solution from the event to the incident. The default value is SuccessfulDiagnosis.
Optional URGENCY Defines the Severity of the incident in Service Management when the property is not specified for the event. Optional IMPACT_SCOPE Defines the Impact of the incident in Service Management when the property is not specified for the event. Optional SERVICE Defines the Service of the incident in Service Management when the property is not specified for the event. Optional SERVICE_DESK_GROUP Defines the Service desk group of the incident in Service Management when the property is not specified for the event. Optional CATEGORY Defines the Category of the incident in Service Management when the property is not specified for the event. Optional Use this edited script to create a new Groovy Script Adapter within OMi. For more information, refer to the OMi documentation.
-
In OMi, define Service Management as a connected server. The outgoing connection credentials used should match the credentials of the authorized user in the external system record. The incoming connections credentials should match the credentials specified in the Endpoint Credentials Manager in step 2.
The standard SSL ports and Service Management SSL certificates should be used for a secure connection.
- In OMi, configure an Event Forward Rule, which includes configuring a filter to determine which events trigger incidents in Service Management.
-
When an incident is created, you can click a link from the event in OMi to launch Service Management and take you to the created incident. Use your Service Management credentials to log in.
If you make a change to an incident in the Resolution metaphase in Service Management, it will be reflected in OMi. Go to the External assignment section of the General tab of the incident. Click the URL link next to the OMi remote system to launch OMi and go directly to the event. The event details should be updated.
Note For an OMi integration to work properly, the affected incidents must be in the Resolution metaphase. Further, you should check Service Management > Administration > Utilities > Integration > External Systems and ensure that you are not logged in there as the Authorized user.
Related topics