OPS/MVS Interface with ServiceNow via CA NIM SM

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

I am looking to setup the interface with ServiceNow so that I can automatically create incidents for events that occur, which we currently only send a highlighted message and the computer operators must then manually create one. There seems to be a lot of documentation but I'm still a bit confused. I see that there is also some custom endpoints that can be done but that seems like more than what we may need for creating an incident.

From what I see, we need to spin up a CA NIM SM server, which appears to be something we can run on our LPARs. I'm new to spinning up web servers but I'm assuming this would be a started task?

Are there any configuration or permissions that have to be granted on the ServiceNow side?

Also, from what I read, there will be some configuration on the CA NIM SM server? I found the below table that appears to be required information, some of which may need to be provided by the ServiceNow administrators?

 

ServiceNow

 

 

Property	Description	Default Value
URL	Specifies the URL to connect to ServiceNow.  Example:  https://xxx.service-now.com
Username	Specifies the Username to connect to ServiceNow.  Example:  johndoe
Password	Specifies the Password to connect to ServiceNow.
ServiceNowClientURL	Specifies the ServiceNowClientURL that is used to connect to ServiceNow.  Default:  https://servicenow_client_host_name
ProxyProtocol	Specifies the ProxyProtocol to connect to ServiceNow SOAP Web Services.   Example:  http
ProxyServer	Specifies the ProxyServer to connect to ServiceNow.  Example:  proxy.xxx.com
ProxyPort	Specifies the ProxyPort to connect to ServiceNow.  Example:  80
ProxyUser	Specifies the ProxyUser to connect to ServiceNow.
ProxyPassword	Specifies the ProxyPassword to connect to ServiceNow.
useCustomEndpoint	Set the value of useCustomEndpoint to true when CA NIM has to communicate with ServiceNow through Custom Endpoint.   Section: NIM Configuration for ServiceNow Custom Endpoints explains more about CA NIM integration with ServiceNow through Custom Endpoint (or Scripted Web Service)

 

Environment

Release : 13.5

Component : OPS/MVS

Resolution

CA NIM SM can be deployed to an already existing current web server, if one exists.  Otherwise, the requirement is to setup and configure a new CA Common Services Apache Tomcat.   This web server can run on any platform, and does not have to be on the mainframe.

The following areas of documentation are specific to the above questions:

• https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/normalized-integration-management-for-service-management-/3-2/getting-started.html
• https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/installing/installing-and-configuring-optional-components135/set-up-client-rest-api-to-interface-with-ca-nim-sm.html
• https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/normalized-integration-management-for-service-management-/3-2/getting-started/configure-ca-normalized-integration-management-service-management/configure-service-desk-product.html

As far as security, your setup must be able to accept REST requests.  A USERID that has the authority to create ServiceNow tickets is also required.  A username and password should be enough.

Once NIM-SM is deployed and started, the Service Now administrators will need to provide the information needed to populate the ServiceNow Option under NIM-SM as follows: