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 |
|
Integrate Service Manager downtimes with OMi
To enable downtimes defined in SM to be sent to OMi, again, you need to distinguish between the two cases of where the CMDB is:
If you are using OMi's RTSM as CMDB, no further steps are required. See also Point to point integration.
If you are using an external UCMDB, you need to install the DFP2 in the OMi deployment. See also Integration using a Universal Configuration Management Database (UCMDB)
Important:
-
Following the initial integration, a large amount of data may be communicated from SM to OMi. It is highly recommended that you perform this procedure during off-hours, to prevent negative impact on system performance.
-
The integration consists of two parts: SM > CMS/UCMDB, and CMS/UCMDB > OMi adapter. You should configure both parts of the integration as one flow, without a significant time lag between setting up the two parts. If you set up the SM > CMS/UCMDB part, and then wait a long time before setting up the CMS/UCMDB > OMi adapter part, the number of downtimes communicated to OMi initially may be extremely high.
Note
-
The following procedure does not describe the SM > CMS/UCMDB connection setup. SM should be configured to create its CIs in the CMS. This procedure connects the adapter between the CMS/UCMDB and OMi.
-
The default job synch frequency is one minute.
Create a new integration point as follows:
-
Create the integration point credentials:
-
Access the Data Flow Probe Setup on OMi or UCMDB depending on whether you use the OMi's RTSM or use a CMS.
Note You do not need a probe to perform this integration. Nevertheless you create credentials using the Data Flow Probe Setup tab.
-
Click Add domain or probe, and enter a name and description of your choice.
-
Expand the submenus and select HTTP protocol.
-
Click the + sign (Add new connection details) and enter the OMi Gateway host name, Port 80, and the OMi username and password. Leave the Trust fields blank. When you are done, click OK to save the credentials.
-
-
Create a new integration point:
-
Access the Integration Studio on your OMi or UCMDB depending on whether you use OMi or use a CMS.
-
Click New Integration Point, enter a name and description of your choice, and select BSMDowntimeAdapter/SM scheduled Downtime Integration into BSM.
-
Enter the following information for the adapter: OMi Gateway hostname and port, the integration point credentials you just created, communication protocol, and the context root (if you have a non-default context root).
-
Click OK, then click the Save button above the list of the integration points.
-
-
You can use the Statistics tab in the lower pane to track the number of downtimes that are created or updated. By default, the integration job runs every minute. If a job has failed, you can open the Query Status tab and double-click the failed job to see more details on the error.
If there is an authentication error, verify the OMi credentials entered for the integration point.
If you receive an unclear error message with error code, this generally indicates a communication problem. Check the communication with OMi. If no communication problem is found, restart the MercuryAS process.
A failed job will be repeated until the problem is fixed.