Configure the Service Manager server as a connected server in Operations Manager i (OMi)

Synchronizing changes between HPE Business Service Management (BSM) Operations Management events and HPE Service Manager incidents requires configuring a Connected Server within OMi to correctly identify the target Service Manager server instance.

To configure the Service Manager server as a target connected server, perform the following steps:

  1. Log on to HPE Business Service Management as a system administrator.
  2. Navigate to the Connected Servers manager in the Operations Management user interface:

    Admin > Operations Management > Setup > Connected Servers

  3. Click the New button to open the Create New Server Connection dialog box.
  4. In the Display Name field, enter a name for the Service Manager server.

    The Name field is filled automatically. If the auto-completed value is not the user name of the BSM user account you created for Service Manager to access the OMi server, change the value to the correct user name. See Create user accounts for the Incident Exchange (OMi - SM) integration.

    Make a note of the Name of the new target server. You need to provide it later on as the username when configuring the Service Manager server to communicate with the OMi server. See Add an integration instance for each Operations Manager i (OMi) server.

    Optionally, enter a description for the new target server.

    Make sure that you check the Active check box.

    Click Next.

  5. Select External Event Processing to choose the server type suitable for an external incident manager like Service Manager.

    Click Next.

  6. Enter the Fully Qualified DNS Name of the target Service Manager server.

    Click Next.

  7. In the Integration Type dialog box, you can choose between using a Groovy script adapter, or the Event Synchronization Web Service.

    1. As an HPE Service Manager Groovy script adapter is provided for integrating with Service Manager, select Call Script Adapter.

    2. In the Script Name field, select sm:ServiceManagerAdapter.

    3. Click Next.
  8. In the Outgoing Connection dialog, enter the credentials (user name, password, and port number) to connect to the Service Manager server and to forward events to that server.

    1. In the User Name and Password fields, enter the Service Manager user credentials you created for the integration. See Create user accounts for the Incident Exchange (OMi - SM) integration.
    2. Repeat the password entry in the Password (Repeat) field.
    3. In the Port field, enter the communications port of the Service Manager server.

      The Service Manager server configuration file (sm.ini) defines the http and http ports. Enter the http port when Service Manager is running in http mode, or enter the https port when it is running in secure http mode.

      Tip Clicking Set default port automatically populates the Port field with the default port (13080 for http or 13443 for secure http). However, your actual Service Manager ports may differ from the default values.

    4. If the Service Manager server uses secure http (SSL) mode, select the Use Secure HTTP check box. If it uses http mode, make sure the check box is not checked.

    5. If the Use Secure HTTP check box is selected, download and install a copy of the Service Manager server’s SSL certificate by clicking the link Retrieve from Server, or Import from File if the certificate is available in a local file.

    6. Make sure that the Enable Synchronize and Transfer Control check box is checked.

      When the Enable Synchronize and Transfer Control flag is set, an Operations Management operator is then able to transfer ownership of the event to the target connected server. If the flag is not set, then the option Synchronize and Transfer Control does not appear in the list of forwarding types when configuring forwarding rules.

      Also, note that if the Enable Synchronize and Transfer Control flag is not set for any target connected server, the Transfer Control to option does not appear at all in the Event Browser context menu.

      If a specific server is configured without the Enable Synchronize and Transfer Control flag set, then that server is not available in the Event Browser context menu as a server to which you can transfer ownership.

    7. Click Test Connection. A Success or ERROR hyperlink appears.

      Click the link to get a more detailed message.

    8. Click Next.
  9. If, in addition to automatically generating Service Manager incidents from OMi events, you want to also be able to drill-down into Service Manager, you need to specify the fully qualified DNS name and port of the Service Manager web application server (for example, Tomcat).

    Note To enable incident drill-down to Service Manager, you must have the Service Manager web tier deployed on a web application server.

    In the Event Drilldown dialog box, configure the Fully Qualified DNS Name and Port of the web application server where the Service Manager web tier is deployed.

    Note If you do not specify a server in the Event Drilldown dialog box, it is assumed that the web tier is deployed on the same machine as the Service Manager server.

    Click Next.

  10. The next thing to do is to enable event changes to be synchronized back from Service Manager to OMi. For this you need to provide credentials for the Service Manager server to access the OMi server in the Incoming Connection dialog box.

    1. Select the Accept event changes from external processing server check box.

      Note If Enable Synchronize and Transfer Control was previously selected, the Accept event changes from external processing server option is assumed, and cannot be disabled.

    2. Enter the password of the user account that you created for the Service Manager server to access the OMi server. See Create user accounts for the Incident Exchange (OMi - SM) integration.

    3. Make sure the User Name (auto-generated) matches the one of the user account you created. If not, click the General tab, and change the Name field to the correct value.

    4. Click Finish. The target Service Manager server appears in the list of Connected Servers.