Highlighted
Micro Focus Expert
Micro Focus Expert
78 views

uCMDB Tip : Unable to push the customized CI's of customized CIT into ServiceNow and the job fails

Question:   Why does the ServiceNow integration job fail to run with the below error message if the mapping file is customized while the job works with OOB (Out of Box) mapping file without any problem?

           

java.lang.Exception: java.lang.Exception: [DiscoveryMain] [processCIs] [getReferenceFieldSysId] [getReferenceFieldSysId] Error connecting to Service-Now while processing CIT <cmdb_model>

[ERROR] [AdHoc:AD_HOC_TASK_PATTERN_ID-19-1423126548089] (ExecutionEngineImpl.java:400) - Failed execute ad hoc script: Traceback (most recent call last):

File "<string>", line 2, in <module>

File "pushToServiceNow", line 744, in DiscoveryMain

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)          at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)               at java.lang.reflect.Constructor.newInstance(Constructor.java:525) at org.python.core.PyReflectedConstructor.constructProxy(PyReflectedConstructor.java:210)

java.lang.Exception: java.lang.Exception: [DiscoveryMain] [processCIs] [getReferenceFieldSysId] [getReferenceFieldSysId] Error connecting to Service-Now while processing CIT <cmdb_model>

 

 

Solution :  uCMDB is bundled with the service-now jar file which is relevant for each specific CIT which is supported by the integration adatper.

 

For example to push the computer CIs, there is a file by name ServiceNow_cmdb_ci_computer-test-client.jar and it is located in the following location:

<drive>:\hp\UCMDB\DataFlowProbe\runtime\probeManager\discoveryResources\Service-Now

          

If changes are done to the mapping file of the integration to push the customized attributes to ServiceNow then the jar files must be re-generated.

In the process of re-generating the jar files, the axis2 library should be used and the library should be of version 1.5.4.

The jar files generated using the latest library will not work with the integration.

Labels (1)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.