This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with UCMDB to ServiceNow push adapter

I have tried to set up an integration of Windows CI using the out-of-the-box Service-Now Push adapter.

 

ServiceNow is accessed via https over proxy and I have checked that I have access from the data flow probe server I am using for the integration.

 

The additional classpath is added according to instructions. My query returns 258 CI´s and my mapping file have the same name as the query according to the instructions and I have also tried with the sample query/mapping.

 

A test run gives the error message pasted below.

 

 

<2014-08-22 13:33:55,433> [ERROR] [AdHoc:AD_HOC_TASK_PATTERN_ID-81-1408707266802] (ExecutionEngineImpl.java:400) - Failed execute ad hoc script: Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "pushToServiceNow", line 736, 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] [processCIs:add] Error connecting to Service-Now while processing CIT <cmdb_ci_win_server>

<2014-08-22 13:33:55,434> [ERROR] [AdHoc:AD_HOC_TASK_PATTERN_ID-81-1408707266802] (AbstractProbeProcessor.java:62) - Failed executing probe request [com.hp.ucmdb.discovery.probe.request.GenericPushProbeRequest] for integration [ServiceNow push test]

 

Does anybody have an idea what could be wrong?

 

Kind regards,

Malin

Parents
  • 0

    Hi Malin,

     

    I have successfully integrated uCMDB 9.05, CUP 14 with Service Now Calgary.

     

    Here are a few things I'm curious about which might lead us to the solution to your problem:

    1: May I know what version of uCMDB you are on ?

     

    2: I have seen this error pop up when we did not set our proxy correctly and because of wrong previleges to write to the S-Now CMDB. So, please check on Proxy Server port and Proxy Server Name/IP.

     

    3: Are you using Direct web services that came out of the box ?

     

    Thanks,

    Praveen

  • 0 in reply to 
    Hi Praveen,
    1: We are on 10.11.224, content pack 14.0.168
    2: I have double checked proxy settings.
    3: We are using the adapter out-of-the box.
    Kind regards,
    Malin

     


    wrote:

    Hi Malin,

     

    I have successfully integrated uCMDB 9.05, CUP 14 with Service Now Calgary.

     

    Here are a few things I'm curious about which might lead us to the solution to your problem:

    1: May I know what version of uCMDB you are on ?

     

    2: I have seen this error pop up when we did not set our proxy correctly and because of wrong previleges to write to the S-Now CMDB. So, please check on Proxy Server port and Proxy Server Name/IP.

     

    3: Are you using Direct web services that came out of the box ?

     

    Thanks,

    Praveen


     

  • 0 in reply to 

    HI Praveen

     

    Sorry for addng my question here and not as seperate thread.

     

    I am new for this integration in past never did third party integrations. I looked into document for adapater. My question is about Jar files, you have mentioned in some other threads (ServiceNow) that you created several jar files (HP doc also mention same but no details). I want to know more clarity on that. I couldn't find any doc explaining how to do that. I saw your post so thought to check with you as you have successfull did this integration.

     

    Can you please provide guidence on this.

     

    Thanks
    Sushil

  • 0 in reply to 

    Hi Susheil,

     

    Sorry, I missed this post completely.

     

    Let me see if I can answer your question about .jar files.

     

    1: The OOTB service now push adapter comes with the basic jar files required for the integration. But in our case, we used Scripted Web services to push CI and relationship data from uCMDB to Snow.

     

    2: when we implemented scrpited web services, we also had to build custom WSDL's for each CI type. Custom WSDL's would include extra attributes on top of OOB attributes.

     

    3: Once the WSDL's were built, we generated the jar files by using Apache Axis 2 software and by following a few steps that were provided by HP. The JAR files contain web service stubs.

     

    (The only case in which you will NOT need to regenerate the JAR files is if the structure of your ServiceNow target tables matches the structure in the JAR files that are used by ServiceNow integration in uCMDB.)

     

    4:  Once we have all the components, we build the Integration queries and the XML mapping files to match the attribute names on the WSDL's.

     

    Let me know if it makes sense.


    Thanks,

    Praveen

Reply
  • 0 in reply to 

    Hi Susheil,

     

    Sorry, I missed this post completely.

     

    Let me see if I can answer your question about .jar files.

     

    1: The OOTB service now push adapter comes with the basic jar files required for the integration. But in our case, we used Scripted Web services to push CI and relationship data from uCMDB to Snow.

     

    2: when we implemented scrpited web services, we also had to build custom WSDL's for each CI type. Custom WSDL's would include extra attributes on top of OOB attributes.

     

    3: Once the WSDL's were built, we generated the jar files by using Apache Axis 2 software and by following a few steps that were provided by HP. The JAR files contain web service stubs.

     

    (The only case in which you will NOT need to regenerate the JAR files is if the structure of your ServiceNow target tables matches the structure in the JAR files that are used by ServiceNow integration in uCMDB.)

     

    4:  Once we have all the components, we build the Integration queries and the XML mapping files to match the attribute names on the WSDL's.

     

    Let me know if it makes sense.


    Thanks,

    Praveen

Children
  • 0 in reply to 

     

    Hi Praveen

     

    Thanks for your detaild response.

     

    Yes I spoke with HP and doing the same.

     

    I downloaded the https://abc.service-now.com/cmdb_ci_ip_address.do?WSDL and then used the AXIS 2 to create the Jar files.

    I started with only node and created the Jar for cmdb_ci_win_server.do?WSDL and pushed the nodes. It created the rows in Service now database but with empty value.

     if i don't recreate the Jar files then i get error as

     

    ============================================================

    java.lang.Exception: Traceback (most recent call last):
      File "<string>", line 2, in <module>
      File "pushToServiceNow", line 736, 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] [processCIs:add] Error connecting to Service-Now while processing CIT <cmdb_ci_ip_address>

    ============================================================

     

    then i did consult support again and they mentioned the way we are doing the jar recreation used to work fine with 9. version.

    Now i am waiting from HP to see if this recreation a jar need to be change or something else in this new version UCMDB 10.11 CUP 14

     

    Any suggestion would appreciate and once again thanks for reply.

     

    Merry Christmas!

     

    -Sushil