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.

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

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

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

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

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

  6. 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).

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

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

  9. (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.

  10. (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).