Administer > Setup and Configuration > How to Configure Operations Connector to Communicate with OMi

How to Configure Operations Connector to Communicate with OMi

To enable the connection between Operations Connector and OMi, the Operations Connector certificate must be approved on the OMi side, and the Operations Connector instance must be configured as an Operations Connector connected server in OMi.

When you add an Operations Connector integration to OMi, the Operations Connector instance must be accessible to OMi.

  1. Prerequisite. Install and configure Operations Connector.

    For details, see the interactive Operations Connector Installation and Upgrade section.

  2. On the Operations Connector server, close any running instances of the command ovconfchg -edit.

  3. Prerequisite. In a distributed OMi environment with a load balancer or reverse proxy, configure Operations Agent manually.

    In a distributed OMi environment with a reverse proxy or a load balancer, the OMi Data Processing server and the Operations Connector server may not be able to communicate with each other in order to request and install a certificate. To provide the agent with a certificate, you must issue the certificate manually on the OMi certificate server and then import it manually on the Operations Connector system. In addition, you must manually set the MANAGER_ID configuration variable. The MANAGER_ID defines who is allowed to access the agent from outside. For details, see How to Configure Operations Connector to Communicate with a Distributed OMi topic.

  4. Prerequisite. Make sure the Operations Connector certificate request is granted on the OMi side.

  5. In OMi, open the Connected Servers manager from Administration, select:

    Administration > Setup and Maintenance > Connected Servers

    In the Connected Servers pane, click New and select Operations Connector. The Create Operations Connector Server dialog pane opens.

    The information you need to enter depends on the type of integration data you want to collect with this Operations Connector:

    • General

      Complete the mandatory Display label and Identifier fields. Additionally complete also the Description field..

    • Server Properties

      Set the Target Server:

      • Enter the Fully qualified domain name of the server and click + to add it to the list of servers. If you configure a highly-available setup, add all nodes on which Operations Connector is installed.

      • To synchronize the event status back to the Operations Connector server, select the Sync event updates back to Operations Connector server check box.

      Optionally, set the Advanced Delivery Options. You can select between Serial, Serial per source, or Parallel delivery.

      Set the Policy Management options:

      • Set the communication port. To restore the port to the default value (30000), click Set default port.

        You can test the launch of the Operations Connector policy management by clicking Test Launch.

    • Event Drilldown

      Event drilldown enables OMi users to launch the user interface of the third-party system in the context of an event collected through Operations Connector. Enter the URL.

    • To test the connection for the selected server, click Run Test.

    • To activate Operations Connector server after creation, enable the option Activate after save.

  6. Click Create to save the new Operations Connector integration.

    After the wizard is successfully completed, a new connected server is created.

  7. Results. You can view the collected data in OMi, depending on the type of integration data that you collect. For example, you can view data in RTSM or Service Health.

    You must first configure and activate policies in Operations Connector to start the data collection. To stop data collection, deactivate the policies.

For full details about how to configure an Operations Connector connected server, see the OMi online help or OMi Administration section.

Related topics

How to Configure Operations Connector to Communicate with a Distributed OMi