Netcool integrations

IBM Cloud Pak for AIOps can integrate with IBM Tivoli Netcool/OMNIbus and IBM Tivoli Netcool/Impact to leverage existing event data (IBM Tivoli Netcool/OMNIbus), and policies (IBM Tivoli Netcool/Impact).

With these integrations in place IBM Cloud Pak for AIOps provides AI and visualization features in a modernized UI with an IBM Tivoli Netcool/OMNIbus integration providing additional data and an IBM Tivoli Netcool/Impact integration providing additional automation. You can continue to take advantage of all of your alerts and integrations for IBM Tivoli Netcool/OMNIbus and IBM Tivoli Netcool/Impact to obtain and send data.

Note: Each Netcool integration that you configure requires an additional 1 vCPU and 3GB memory. For example, if you configure three Netcool integrations then you will require an additional 2 vCPUs and 6GB memory.

Integrating with IBM Tivoli Netcool/OMNIbus

You can integrate IBM Cloud Pak for AIOps with an existing IBM Tivoli Netcool/OMNIbus deployment to send event data through the integration to IBM Cloud Pak for AIOps. With this integration, you can see IBM Tivoli Netcool/OMNIbus event data in the IBM Cloud Pak for AIOps Alert Viewer. These events are converted into alerts on the IBM Cloud Pak for AIOps side.

You can then take advantage of the IBM Cloud Pak for AIOps AI features to manage and visualize the alerts. For example, event data can be correlated into incidents, data can be viewed and analyzed in a topology, and runbooks can be used to automate operations for managing the alerts.

To integrate IBM Cloud Pak for AIOps with IBM Tivoli Netcool/OMNIbus, you need to create an IBM Netcool Operations Insight ObjectServer integration with the IBM Cloud Pak for AIOps UI Integrations page. This integration defines the settings for communication from IBM Cloud Pak for AIOps to IBM Tivoli Netcool/OMNIbus. For more information about how to define this integration, see Creating IBM Netcool Operations Insight ObjectServer integrations.

After you integrate with IBM Tivoli Netcool/OMNIbus, use IBM Cloud Pak for AIOps and the IBM Cloud Pak for AIOps UI for AI and visualization features. Use IBM Tivoli Netcool/OMNIbus and the associated UI tools for obtaining and sending data to IBM Cloud Pak for AIOps.

Note: If you have integrated IBM Cloud Pak for AIOps and IBM Tivoli Netcool/OMNIbus, and you are not yet ready to move to using the IBM Cloud Pak for AIOps UI, you can continue to use the IBM Tivoli Netcool/OMNIbus DASH custom dashboards and Web GUI event viewer as you transition to using the IBM Cloud Pak for AIOps UI. If you need to continue to use IBM Tivoli Netcool/OMNIbus tools, you can configure launch-in-context links from the Web GUI Event Viewer and the main DASH navigation to the IBM Cloud Pak for AIOps UI to help users access and use the IBM Cloud Pak for AIOps UI.

Integrating with IBM Tivoli Netcool/Impact

You can integrate IBM Cloud Pak for AIOps with an existing IBM Tivoli Netcool/Impact deployment so that IBM Cloud Pak for AIOps can then run automation policies that you manage with IBM Tivoli Netcool/Impact. New and existing policies can continue to be used to run operations in IBM Tivoli Netcool/Impact for data retrieval, drive automation, create tickets, leverage other integrations with IBM Tivoli Netcool/Impact, and more. These policies can be invoked by IBM Cloud Pak for AIOps or send events to IBM Cloud Pak for AIOps.

IBM Tivoli Netcool/Impact policies can reference the extension framework API for IBM Cloud Pak for AIOps. With these policies, you can write automation processes in IBM Tivoli Netcool/Impact to complete operations in IBM Cloud Pak for AIOps, such as to query alerts and incidents, and request changes to alerts.

In some cases, an event source might have an API through which it can retrieve the events. In this case, IBM Tivoli Netcool/Impact can be employed to retrieve these events. IBM Tivoli Netcool/Impact is commonly used to retrieve data from third-party systems for the purposes of event enrichment. The IBM Tivoli Netcool/Impact policy GetHTTP function is key for interacting with APIs. For more information about IBM Tivoli Netcool/Impact functions, see List and overview of functions.

To create this integration between IBM Cloud Pak for AIOps and IBM Tivoli Netcool/Impact, you need to first create an IBM Tivoli Netcool/Impact integration with the IBM Cloud Pak for AIOps UI Integrations page. This integration defines the settings for communication from IBM Cloud Pak for AIOps to IBM Tivoli Netcool/Impact. For more information about how to define this integration, see Creating IBM Tivoli Netcool/Impact integrations.

Then to complete the integration, you need to edit the RESTful DSA configuration in IBM Tivoli Netcool/Impact. This configuration defines the settings for communicating from IBM Tivoli Netcool/Impact to IBM Cloud Pak for AIOps. For more information about editing the RESTful DSA configuration, see Configuring an integration in IBM Tivoli Netcool/Impact for IBM Cloud Pak for AIOps .

Key event integrations

IBM Cloud Pak for AIOps deployments might include requirements to integrate with third-party systems, such as a source of information for event enrichment or for ticketing purposes. You can use the following two ways to achieve key event integrations:

  • Events in ObjectServer: If the nature of the integration is a simple or a one-time action, events can be picked up by IBM Tivoli Netcool/Impact directly from the IBM Tivoli Netcool/OMNIbus ObjectServer. Any updates to the event, such as custom field enrichment or a ticket number can be written back to the event. These updates are propagated to IBM Cloud Pak for AIOps by using the Netcool Connector.

  • Alerts in IBM Cloud Pak for AIOps : An alternative approach is to create an IBM Cloud Pak for AIOps automation policy that sends the event to IBM Tivoli Netcool/Impact by using the IBM Tivoli Netcool/Impact integration under the preferred criteria. IBM Tivoli Netcool/Impact policy can write any updates or enrichments back to the IBM Tivoli Netcool/OMNIbus ObjectServer or back to IBM Cloud Pak for AIOps directly.