Moving deprecated instances to BMC Helix Intelligent Integrations

Use the instructions provided in this topic if you want to configure integrations for the same Dynatrace or SolarWinds NPM instances for which you had configured integrations by using BMC Helix Developer Tools. To configure integrations for new Dynatrace or SolarWinds NPM instances, see Integrating-with-Dynatrace-via-API or Integrating-with-SolarWinds-NPM. 

1. To stop the incoming events from Dynatrace or SolarWinds NPM, disable the integrations that you have configured by using BMC Helix Developer Tools. 

2. Close the Dynatrace and SolarWinds NPM existing events received via integrations configured using BMC Helix Developer Tools. For instructions, see Performing event operations. 

3. Delete the following classes from BMC Helix Operations Management by using the /events/classes/DELETE API. For information about the API, see Event management endpoints in the REST API.

   • DynatraceAlert
   • DynatraceEvent
   • SolarWindsAlert
   • SolarWindsEvent
4. Configure new Dynatrace and SolarWinds NPM integrations by using BMC Helix Intelligent Integrations. For instructions, see Integrating-with-Dynatrace-via-API and Integrating-with-SolarWinds-NPM.

5. List the classes in BMC Helix Operations Management by using the /events/classes/GET API. For information about the API, see Event management endpoints in the REST API.

6. Ensure that the following classes are present in the API output depending upon the source type (Dynatrace and SolarWinds NPM) and the type of data you have chosen to receive while configuring the integration.
   • DynatraceAlert
   • DynatraceIIEvent
   • SolarWindsAlert
   • SolarWindsEvent
7. Ensure that BMC Helix Operations Management is receiving alerts and events via the configured integrations in BMC Helix Intelligent Integrations.
8. (Optional) Delete the Dynatrace and SolarWinds NPM integrations that you disabled in step 1. 
9. Stop the connector associated with a deprecated Dynatrace or SolarWinds NPM when all the integrations associated with the connector are not in use.
   1. Find out the container ID of the connector

      1. On the server where you installed the connector, open the command line interface.
      2. Run the following command to obtain the container ID.
         docker ps | grep <connectorName>
   2. Run the following command to stop the connector:
      docker stop <containerID>