Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
794 views

servicenow integration fails on test connection

Jump to solution

Hi,

I'm trying to setup an integration point in ucmdb 10.33 cup2.214 cp 28 using the ServiceNOW enhanged genaric addapter. based on the instruction given in the thirdparty integration guide. However when i've defined the integration properties and want to test or activate the integration it gives an error. 

integration "servicenow" could not connect to host="null", using adapter = servicenowgenaricadaptat

 

anyone an idea what might be wrong here?

 

full error trace

com.hp.ucmdb.discovery.probe.request.ProbeSideProcessorException: [ErrorCode [800] Couldn't connect
to Integration{servicenow, ServiceNowGenericAdapter, null}]
Integration[servicenow]: Unable to
execute GET request for 'api/now/table/cmdb_ci' with query
'sysparm_exclude_reference_link=true&sysparm_limit=1'.

--- Start of probe-side exception
---
com.hp.ucmdb.dataAccess.exceptions.AdapterAccessCommunicationException: [ErrorCode [800] Couldn't
connect to Integration{servicenow, ServiceNowGenericAdapter, null}]
Integration[servicenow]:
Unable to execute GET request for 'api/now/table/cmdb_ci' with query
'sysparm_exclude_reference_link=true&sysparm_limit=1'.
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessCommunicationException(ExceptionConverter.java:293)
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:104)
at
com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:67)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:74)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:27)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks.AdHocProbeRequestOperation.performAction(AdHocProbeRequestOperation.java:64)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskdispatcher.AdHocTaskDispatcher.dispatchTask(AdHocTaskDispatcher.java:70)
at sun.reflect.GeneratedMethodAccessor680.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
at javax.management.StandardMBean.invoke(StandardMBean.java:405)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:298)
at
org.springframework.jmx.access.MBeanClientInterceptor.doInvoke(MBeanClientInterceptor.java:405)
at
org.springframework.jmx.access.MBeanClientInterceptor.invoke(MBeanClientInterceptor.java:353)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy82.dispatchTask(Unknown Source)
at
com.hp.ucmdb.discovery.probe.agents.probegw.managementtasks.adhoctasks.AdhocThread.run(AdhocThread.java:54)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
--- End of probe-side exception ---

 

 

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: servicenow integration fails on test connection

Jump to solution

You have to give certain permissions to the ServiceNow user. If you want it for test purposes, you can try with admin user. Be sure it also has soap and rest roles assigned. You can also try to login manually with the integration user and see if the connection is successful. 

From the error I see that the user you use doesn't have permissions to access cmdb_ci table. So when you enter into ucmdb see if you can open cmdb_ci.list.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

Likes are appreciated!

View solution in original post

0 Likes
4 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: servicenow integration fails on test connection

Jump to solution

You have to give certain permissions to the ServiceNow user. If you want it for test purposes, you can try with admin user. Be sure it also has soap and rest roles assigned. You can also try to login manually with the integration user and see if the connection is successful. 

From the error I see that the user you use doesn't have permissions to access cmdb_ci table. So when you enter into ucmdb see if you can open cmdb_ci.list.

Cheers,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

Likes are appreciated!

View solution in original post

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: servicenow integration fails on test connection

Jump to solution

Thanx, this helped in the correct direction. what helped was to reset the account of the integration user. 
- only thing now is that I get on the OOB push (there is no customisation done yet) an error like

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:

D:\hp\UCMDB\DataFlowProbe\runtime\probeManager\discoveryConfigFiles\ServiceNowGenericAdapter\mappings\scripts\SNOWPushFunctions.groovy: 154: Apparent variable 'AssetStatusMapping' was found in a static scope but doesn't refer to a local variable, static field or class. Possible causes:

You attempted to reference a variable in the binding or an instance variable from a static context.

You misspelled a classname or statically imported field. Please check the spelling.

You attempted to use a method 'AssetStatusMapping' but left out brackets in a place not allowed by the grammar.

 @ line 154, column 16.

           return AssetStatusMapping[status]==null?status:AssetStatusMapping[status];

                  ^

Followed by some simular errros. any Idea on this

By the way a population works without issues

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: servicenow integration fails on test connection

Jump to solution

The error is caused by including the groovy file with errors to every population mapping:

    <import>
        <scriptFile path="mappings.scripts.SNOWPushFunctions"/>
    </import>

You can either delete these import statements, since you are not using them, or fix/comment the function which is issuing the error. In both the cases when you install new CP, the configurations will be rewritten. That's why I recommend you with the time to configure your own TQLs and mapping files, instead of using the OOB ones. 

Likes are appreciated!
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: servicenow integration fails on test connection

Jump to solution

I am having this issue with a new adapter from support. I tried commenting out the import but i am still getting the errors. Any other fixes i should try?

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.