UCMDB 10.01 and Asset Manager 9.4

Hello,

 

Has anyone managed to get UCMDB AM Push integration working with the newly released AM9.4? We have had AM9.32 working fine, but cannot configure UCMDB to work with AM9.4.

 

 

  • Dear Cuffy,

    UCMDB AM Push is officially supported (http://support.openview.hp.com/sc/solutions/integrations.jsp?intid=616).

    Would you mind sharing more info on errors you're failing with and configuration steps that were taken please?

     

  • Did you manage to get this working? We are having the same problem.
    Cheers
  • Please check Chapter 9 - "HP Asset Manager Push Integration" of  HP Universal CMDB Discovery and Integration Content Guide - Integrations.

    Open support case if you have a problem.

  • It looks like there is a chance of known problem with AM9.40. I'm waiting for some explanations from R&D side. You could expect the answer during next week.

  • I have got the same issue

     

    Here is what I was doing:

     

    1. followed the HP Asset Manager Push Integration" of  HP Universal CMDB Discovery and Integration Content Guide - Integrations to create AMPushAdapterAPI_9.4.zip and deployed on uCMDB

     

    2. Created integration pointer on CMS where it will call am94.dll

     

    I have got the following issue:

     

    Caused by: Error (12,006): Value 
    'AmApiDll=E:\hp\UCMDB\DataFlowProbe\bin\..\runtime\probeManager\discoveryResources\AMPushAdapter\amVersion\9.4\aamapi94.dll' 
    is not a valid integer (32-bit)

     

     

     

  • R&D confirmed integration is worked as expected.

    Please raise support case.

  • Hi, Cuffy,

     

    Did you install the Update 6 (or 7) for uCMDB 10.01 CP12? CP 12 Updates can be found at: https://hpln.hp.com/node/11274/contentfiles

     

    Best Regards,

    Eugene

     

     

  • Hello Experts...,

    Good day! 

    I'm also facing the similar kind of problem but with uCMDB 10.01 and AM 9.32

    The problem is the integration connection is getting succeeded when tried for the first time but later when I try to run the test connection I get an error message saying  General error in integration.

    The error message is as follows

    com.hp.ucmdb.discovery.probe.request.ProbeSideProcessorException: [ErrorCode [802] General 
    Integration Error{Test}]
    Asset Manager DLLs and/or Jars are missing.

    Verify that the package <AMPushAdapterAPI_{AM Version 
    Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value> contains needed DLLs 
    and Jars.

    In case they are missing You should do the following steps :
    1. Create a package named AMPushAdapterAPI_{AM Version Number}.zip.
    2. Copy files both from :
    <Asset Manager Installation folder>\x64\*.dll and <Asset Manager Installation 
    folder>\websvc\lib\*.jar into the created zip under the following path <AMPushAdapterAPI_{AM 
    Version Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value - Example : 
    9.3>.
    3. Deploy AMPushAdapterAPI_{AM Version Number}.zip

    --- Start of probe-side exception 
    ---
    com.mercury.topaz.cmdb.shared.fcmdb.dataAccess.exception.AdapterAccessGeneralException: [ErrorCode 
    [802] General Integration Error{Test}]
    Asset Manager DLLs and/or Jars are missing.

    Verify that the package <AMPushAdapterAPI_{AM Version 
    Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value> contains needed DLLs 
    and Jars.

    In case they are missing You should do the following steps :
    1. Create a package named AMPushAdapterAPI_{AM Version Number}.zip.
    2. Copy files both from :
    <Asset Manager Installation folder>\x64\*.dll and <Asset Manager Installation 
    folder>\websvc\lib\*.jar into the created zip under the following path <AMPushAdapterAPI_{AM 
    Version Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value - Example : 
    9.3>.
    3. Deploy AMPushAdapterAPI_{AM Version Number}.zip
    at 
    com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessGeneralException(ExceptionConverter.java:331)
    at 
    com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:150)
    at 
    com.hp.ucmdb.dataAccess.exceptions.ExceptionConverter.createAdapterAccessException(ExceptionConverter.java:65)
    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:59)
    at 
    com.hp.ucmdb.discovery.probe.agents.probemgr.taskdispatcher.AdHocTaskDispatcher.dispatchTask(AdHocTaskDispatcher.java:73)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at 
    com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111)
    at 
    com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45)
    at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235)
    at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
    at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:250)
    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:791)
    at 
    javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305)
    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:202)
    at $Proxy48.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:599)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
    at java.lang.Thread.run(Thread.java:722)
    Caused by: com.hp.ucmdb.federationspi.exception.DataAccessGeneralException: Asset Manager DLLs 
    and/or Jars are missing.

    Verify that the package <AMPushAdapterAPI_{AM Version 
    Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value> contains needed DLLs 
    and Jars.

    In case they are missing You should do the following steps :
    1. Create a package named AMPushAdapterAPI_{AM Version Number}.zip.
    2. Copy files both from :
    <Asset Manager Installation folder>\x64\*.dll and <Asset Manager Installation 
    folder>\websvc\lib\*.jar into the created zip under the following path <AMPushAdapterAPI_{AM 
    Version Number}.zip>\discoveryResources\AMPushAdapter\amVersion\<AM Version Value - Example : 
    9.3>.
    3. Deploy AMPushAdapterAPI_{AM Version Number}.zip
    at com.hp.ucmdb.adapters.ampush.AMApiUtil.loadDLLs(AMApiUtil.java:310)
    at com.hp.ucmdb.adapters.ampush.AMApiUtil.createApiWrapper(AMApiUtil.java:295)
    at com.hp.ucmdb.adapters.ampush.AMPushAdapter.createApiWrapper(AMPushAdapter.java:240)
    at com.hp.ucmdb.adapters.ampush.AMPushAdapter.testConnection(AMPushAdapter.java:48)
    at 
    com.hp.ucmdb.adapters.push.AbstractInstancePushAdapter.testConnection(AbstractInstancePushAdapter.java:40)
    at com.hp.ucmdb.adapters.push.PushAdapter.testConnection(PushAdapter.java:528)
    at 
    com.hp.ucmdb.discovery.probe.processor.TestConnectionProbeRequestProcessor.processFederationNoneLifeCycle(TestConnectionProbeRequestProcessor.java:18)
    at 
    com.hp.ucmdb.discovery.probe.processor.TestConnectionProbeRequestProcessor.processFederationNoneLifeCycle(TestConnectionProbeRequestProcessor.java:12)
    at 
    com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:63)
    ... 25 more
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at com.hp.ucmdb.adapters.ampush.AMApiUtil.loadDLLs(AMApiUtil.java:308)
    ... 33 more
    Caused by: java.lang.UnsatisfiedLinkError: Native Library 
    E:\hp\UCMDB\DataFlowProbe\lib\amjni93.dll already loaded in another classloader
    at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1905)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1864)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1825)
    at java.lang.Runtime.load0(Runtime.java:792)
    ... 38 more
    --- End of probe-side exception ---

    Later when I try deploying the package as explained in the error message, I'm still getting the same error.

    Can any of you kindly help me in troubleshooting this issue.

    Also attached are the screen shots of the integration points.

  • are you integrating with one or multiple version of AM? IF it with just one version, I find it work best to just copy the .dll and .jar file to the probe /lib directory.

    Restart the probe afterward and it should work
  • Hello Ctruong..
    I did copy the .dll* and the .jar* files and also did a restart probe server and the ucmdb server even then getting the same error.