Forwarding events from XClarity One

ServiceNow provides access to device events and alerts using data forwarders in Lenovo XClarity One to forward event data to ServiceNow.

Procedure

To set up event forwarding, complete the following steps.

1. Set up an API key to be used for authentication and authorization with ServiceNow.

   1. From the XClarity One portal, click API keys on the context menu from the Settings view, and then click the Add icon ().

   2. Provide a name for this API key, such as ServiceNow.

   3. In the list of privileges, select ServiceNow Integration.

   4. Click Generate key.

   5. Immediately copy and record the access-token request URI, client ID, and client secret in a safe location.

      The secret is shown as plain text only when the API key is first created. In the Details view, only the last three characters of the secret is viewable for security purposes. If you lose the client secret, you can regenerate a new secret for the API client by clicking the Regenerate secret icon ().

2. Enable forwarding events from XClarity One to ServiceNow.

   1. From the ServiceNow portal, click Lenovo XClarity Configuration under the Administrator Configuration in the left pane.

   2. Remove an existing (duplicate) configuration, if appropriate, by selecting the configuration and then clicking Delete from the actions menu. Duplicate configurations are not allowed.

   3. Click Newon the far-right side of the banner

   4. Fill in the appropriate fields, including the XClarity One hostname or IP address, client ID and secret that you created in step 1, and the MID server that you want to use to invoke the outbound calls.

   5. Enable Event Forwarder.

   6. Provide the REST user credentials for the event forwarder that you want to use.

   7. Click Add.

3. Verify the configuration.

   1. From the ServiceNow portal, go to the XClarity One integration area where configurations are listed.

   2. Confirm that the new configuration is listed.

   3. Confirm the integration can authenticate and that there are not auth errors.

   4. Monitor the events that are occurring in ServiceNow to ensure that XClarity One is forwarding them correctly.

   If any of these checks fail, consider the following.

   • Ensure there is not an existing configuration for XClarity One. If there is, delete the existing configuration, and then repeat the steps.

   • If outbound calls fail or never happen. Ensure that MID server is set correctly.

   • If authentication fails, ensure that you copied the client secret correctly. If necessary, regenerate the secret from the XClarity One portal.

     Note

     This secret expires after 6 months. When the key expires, the API key is disabled. The only way to re-enable (activate) the key is by regenerating the secret. From the API keys page, select the API key, and then click the Regenerate secret icon (). Each time that you regenerate the secret, you then need to update the secret in the XClarity One configuration.

   • If events are not forwarded or there are errors depending on your ServiceNow app logging to ensure that the REST forwarder credentials are correct.