Integrate > OMi - Service Manager integration overview

OMi - Service Manager integration overview

There are two variations of integrating Service Manager (SM) with OMi. One case uses the RTSM contained in OMi as the CMDB, and needs only one data flow probe (DFP1), which is installed in the OMi deployment. The other case uses a UCMDB, and needs two data flow probes (DFP1 installed on the UCMDB server and DFP2 in the OMi deployment).

Point to point integration

OMi is integrated with Service Manager directly, using OMi's Run Time Service Model (RTSM) as CMDB, as shown in the following figure.

OMi is integrated with Service Manager directly, using OMi 's Run Time Service Model (RTSM):

 

We recommend installing the Data Flow Probe 1 (DFP1) in the OMi deployment.

Integration using a Universal Configuration Management Database (UCMDB)

OMi is set up using an external UCMDB, as shown in the following figure.

OMi is set up using a UCMDB:

We recommend to install the Data Flow Probe 1 (DFP1) on the UCMDB server and the Data Flow Probe 2 (DFP2) in the OMi deployment.

Data flow probes

Two different data flow probes need to be installed. They have different purposes.

  • DFP1 is needed for the following:

    • Populating the RTSM with CIs (Data Population)

    • Federation

    • Topology synchronization (CIs) between RTSM and SM in the case of a point to point integration

      OR

    • Topology synchronization (CIs) between UCMDB and OMi and between UCMDB and SM in case of using an external UCMDB

  • DFP2 is needed for federation only.

Prerequisites

If you are using a standalone CMDB, you need to do the following before continuing with the OMi- SM integration:

  • Set up the integration between OMi and UCMDB.

  • Integrate UCMDB with SM to synchronize CIs from UCMDB to SM.

For details, see Micro Focus Universal CMDB.

Integration options

  • Incident exchange between SM and OMi. OMi enables you to forward events from OMi to SM. Forwarded events and subsequent event changes are synchronized back from SM to OMi. You can also drill down from OMi events to SM incidents. For details, see Incident Exchange (OMi - SM) integration.

  • Downtime exchange between OMi and SM. OMi enables you to forward downtimes (also known as outages) from OMi to SM, and from SM to OMi. The downtime defined in OMi is directed to SM as an incident, and vice versa. For details, see Downtime Exchange between OMi and Service Manager.

  • View planned changes and incident details in Service Health. This integration enables you to view planned changes and incident details in the Changes and Incidents tab in the 360° View page in Service Health. For details, see OMi - Service Manager integration overview.

  • The Business Impact Report integration is part of the Closed Loop Incident Process (CLIP) solution. When deployed as part of the OMi solution, Incident Management users can launch an impact report from an incident in context with the incident's affected CI. Service desk agents can validate the updated status of the business impact to categorize and prioritize the incident accordingly.

    For details, see the CLIP page in the Solutions Portal and BSM Business Impact Report (BIR).

Note  

  • Service Manager Query Security: If you have set up an integration from OMi to SM, there is a CI context menu that enables you to access SM from OMi Service Health. This drill-down option is not available if you have enabled Service Manager query security.

  • Troubleshooting Multiple Domains: If OMi and SM are in different domains, and you are using Internet Explorer as your browser, you may need to add the domains to the list of allowed domains in the Privacy tab (Internet Options > Privacy > Sites).