{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30628,"path":"it-operations-management/event-management/t_EMUpgradeNetcoolConnector.md","title":"Configure event collection from IBM Netcool","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure event collection from IBM Netcool\n\nConfigure the IBM Netcool\\_V2 connector to receive events from IBM Netcool/OMNIbus Object Servers and Impact Servers. The IBM Netcool\\_V2 connector uses REST API calls and is bidirectional.\n\n## Before you begin\n\nFor the IBM Netcool\\_V2 connector:\n\n-   Role required: evt\\_mgmt\\_admin\n-   Perform connector validation on IBM NetCool/OMNIbus version 8.1.0.\n\n## About this task\n\nTo use IBM Netcool\\_V2 connector, configure a connector instance for the MID Server.\n\n**Note:** The IBM Netcool connector is deprecated and only IBM Netcool\\_V2 connector is supported.\n\n## Procedure\n\n1.  Navigate to **Event Management** &gt; **Integrations** &gt; **Connector Instances**.\n\n2.  Click **New** and create a connector instance with the following details:\n\n    |Field|Value|\n    |-----|-----|\n    |Name|Specify a unique name for the Netcool connector instance.|\n    |Description|Type a description for the use of the Netcool event collection instance.|\n    |Host IP|Specify the Netcool IP address.|\n    |Credential|In the Credentials form, click **New**, and create the required credentials. Save the credentials using a unique and recognizable name, for example, NetcoolOPS.|\n    |Event collection last run time|The last run time value is automatically updated.|\n    |Last event collection status|The last run time status is automatically updated.|\n    |Event collection schedule \\(seconds\\)|The frequency in seconds that the system checks for new events from Netcool. The default value is 120 seconds.|\n    |Last error message|The last error message is automatically updated.|\n    |Connector definition|Select IBM Netcool\\_V2 to gather events from the external event source.|\n    |MID Servers \\(MID Server for Connectors section\\)|Specify a MID Server that is up and is valid. You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on. MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section. If no MID Server is specified, an available MID Server that has a matching IP range is used.|\n\n3.  Right-click the form header and click **Save**.\n\n    The connector instance values are added to the form and the parameters that are relevant to the connector appear.\n\n4.  In the Connector Parameters section, specify the value of the required Netcool parameters.\n\n<table id=\"choicetable_ict_hmx_n4b\"><thead><tr><th align=\"left\" id=\"d213770e250\">\n\nConnector\n\n</th><th align=\"left\" id=\"d213770e253\">\n\nRequired parameters\n\n</th></tr></thead><tbody><tr><td id=\"d213770e259\">\n\n**IBM Netcool\\_V2**\n\n</td><td>\n\n-   **additional\\_alert\\_columns**: comma separated list of columns to include in event additional information from net cool alert. Specify here if the desired columns are not already part of event.\n-   **debug**: Boolean flag to enable debug logs. Default: false.\n-   **initial\\_sync\\_in\\_days**: The number of days of data fetched on first pull. The default value is 3, but can be changed according to your requirements.\n-   **message\\_key\\_delimiter**: Separate hierarchical parts of a message key, enabling structured namespacing.\n-   **port**: The port number on which IBM Netcool is running. For example: 8080.\n-   **Protocol**: Protocol to use when connecting to the Netcool server. Default: https.\n\n\n</td></tr></tbody>\n</table>5.  Verify that Netcool servers are up and running:\n\n    For the IBM Netcool\\_V2 connector, use this REST API call to verify that the Netcool API is up and running: `http://hostname:port/objectserver/restapi/alerts/status`\n\n6.  Right-click the form header and click **Save**.\n\n7.  Click **Test connector** to verify the connection between the MID Server and the Netcool connector.\n\n8.  If the test fails, follow the instructions that are issued by the error to correct the problem and then run another test.\n\n9.  After a successful test, select the **Active** check box and then click **Update**.\n\n\n**Parent Topic:**[Configure a pull connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/t_EMConfigureConnectorInstance.md)\n\n**Related topics**  \n\n\n[Configure a pull connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/t_EMConfigureConnectorInstance.md)\n\n"}}