Custom mapping via NIM not maintained after Tomcat restart

Products

• DX NetOps

Issue/Introduction

When mapping Spectrum attributes to Service Desk attributes using NIM (http://OCServer/ca-nim-sm/ui/login.jsp). The updated mappings are lost after a restart of the OneClick Tomcat.

e.g in the following example the Spectrum severity attribute is mapped to the ServiceNow impact attribute:

After the restart of Tomcat, the mapping reverts to the default mapping:

severity --> severity

 

Environment

Spectrum 21.x
ServiceNow

Resolution

In order for the custom mapping of the of the Spectrum and Service Desk tool attributes to be maintained after a Tomcat restart, you need to set the mapping in the $SPECROOT>\custom\svdsk\config\nim-mappings-config.xml file.

See the following example:

<custom-mappings>
 <incident>
  <ServiceNow>
   <mappings>
    <Mapping>
     <NIMField>severity</NIMField>
     <MDRField>impact</MDRField>
     <DefinedValues>Critical=1,Major=2,Minor=3</DefinedValues>
    </Mapping>
   </mappings>
  </ServiceNow>

Save the file and the change will be maintained after a Tomcat restart. You should also be able to see the updated mapping in NIM.

Additional Information

Customize DX NetOps Spectrum to CA NIM Field Mapping

Attribute Mapping

CA NORMALIZED INTEGRATION MANAGEMENT FOR SERVICE MANAGEMENT