Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax (800 Views)
Reply
Frequent Advisor
Mastron_s
Posts: 111
Registered: ‎05-05-2010
Message 1 of 6 (800 Views)

Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Hi all

I have integration with Atrium CMDB by Atrium Import adapter that setting up on HP UCMDB side.

 

I succesfully seted up mapping between BMC Ci types, relationships and HP ci
types and relationships, but after running import process i found in UCMDB ci`s that exist in Atrium CMDB sandboxes.

 

I want to filter ci`s that importing from BMC Atrium CMDB by condition "DatasetId=BMC.ASSET".

 

In Adapter docs i see that i can use param in mapping file "query", but i have not any examples how to use this query.

 

I tryed followed in mapping file:

<source_ci_type
name="BMC_Rack" nameSpace="BMC.CORE" query="DatasetId=BMC.ASSET">

<target_ci_type
name="GPB_CI_03_01_Rack">

 

In UCMDB logs I have error from Atrium
CMDB with missing symbols (see below end of error), so I can`t correct query, because i don`t see text of error ERROR (4558).

 

Please tell which syntax I must use for correct query from BMC Atrium CMDB?

 

Where i can find text of error by error number?

 

 

Which atrium logs can contain this error? I checked folders «/opt/bmc/arsystem/Logs» and «/opt/bmc/atriumcore/Logs» but was no changes in logs after import procedure finished.

 

Error from Atrium CMDB:

jvm 1 | <2013-05-14 12:49:27,310>
1536406783 [INFO ] [JobExecuterWorker-0:DS_Atrium5_Import data from Atrium]
(?:?) - Query data for: Class <BMC_Rack>, Namespace <BMC.CORE>,
Query <DatasetId=BMC.ASSET>, Attributes List <['ShortDescription',
'TagNumber', 'PartNumber', 'SerialNumber', 'OwnerName', 'OwnerContact',
'Description', 'Height', 'InstanceId', 'Name']>, Children List <[]>,
Parent List <[]>

jvm 1 | <2013-05-14 12:49:27,348>
1536406821 [ERROR] [JobExecuterWorker-0:DS_Atrium5_Import data from Atrium]
(ExecutionEngineImpl.java:312) - Discovery Error: Traceback (innermost last):

jvm 1 |
File "<string>", line 2, in ?

jvm 1 |
File "atrium_query", line 504, in DiscoveryMain

jvm 1 | File "atrium_query", line 118, in
pullDataFromAtrium

jvm 1 | ERROR (4558): пїЅпїЅпїЅпїЅпїЅпїЅ пїЅ
пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ;

jvm 1 |

jvm 1 | ERROR (2297): пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ
пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ;
пїЅпїЅпїЅпїЅпїЅпїЅпїЅ 19
(...setId=BMC.ASSET^)

jvm 1 |

jvm 1 | at
com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ProxyJRpc.ARExecuteProcess(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ARServerUser.executeProcess(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ARServerUser.executeProcess(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ARServerUser.executeSpecialCommand(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ARServerUser.parseQualification(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.arsys.api.ARServerUser.parseQualification(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.cmdb.api.CMDBProxy.CMDBGetListInstance1(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.cmdb.api.CMDBInstance.find(Unknown Source)

jvm 1 |

jvm 1 | at
com.bmc.cmdb.api.CMDBInstance.find(Unknown Source)

jvm 1 |

jvm 1 | at
sun.reflect.GeneratedMethodAccessor87.invoke(Unknown Source)

jvm 1 |

jvm 1 | at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

jvm 1 |

jvm 1 | at
java.lang.reflect.Method.invoke(Method.java:601)

jvm 1 |

jvm 1 | at
org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)

jvm 1 |

jvm 1 | at
org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)

jvm 1 |

jvm 1 | at
org.python.core.PyObject.__call__(PyObject.java)

jvm 1 |

jvm 1 | at
org.python.core.PyObject.invoke(PyObject.java)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx22.pullDataFromAtrium$13(atrium_query:118)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx22.call_function(atrium_query)

jvm 1 |

jvm 1 | at
org.python.core.PyTableCode.call(PyTableCode.java)

jvm 1 |

jvm 1 | at
org.python.core.PyTableCode.call(PyTableCode.java)

jvm 1 |

jvm 1 | at
org.python.core.PyFunction.__call__(PyFunction.java)

jvm 1 |

jvm 1 | at
org.python.core.PyObject.__call__(PyObject.java)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx22.DiscoveryMain$19(atrium_query:504)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx22.call_function(atrium_query)

jvm 1 |

jvm 1 | at
org.python.core.PyTableCode.call(PyTableCode.java)

jvm 1 |

jvm 1 | at
org.python.core.PyTableCode.call(PyTableCode.java)

jvm 1 |

jvm 1 | at
org.python.core.PyFunction.__call__(PyFunction.java)

jvm 1 |

jvm 1 | at
org.python.core.PyObject.invoke(PyObject.java)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx56.f$0(<string>:2)

jvm 1 |

jvm 1 | at
org.python.pycode._pyx56.call_function(<string>)

jvm 1 |

jvm 1 | at
org.python.core.PyTableCode.call(PyTableCode.java)

jvm 1 |

jvm 1 | at
org.python.core.PyCode.call(PyCode.java)

jvm 1 |

jvm 1 | at
org.python.core.Py.runCode(Py.java)

jvm 1 |

jvm 1 | at
org.python.core.Py.exec(Py.java)

jvm 1 |

jvm 1 | at
org.python.util.PythonInterpreter.exec(PythonInterpreter.java)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.executeScript(ExecutionEngineImpl.java:214)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.executeScript(ExecutionEngineImpl.java:189)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.executeScript(ExecutionEngineImpl.java:185)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.library.execution.impl.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:102)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.services.dynamic.core.TablesProcessorUtil.processDestinationTables(TablesProcessorUtil.java:136)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.services.dynamic.core.DynamicService.discover(DynamicService.java:71)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1238)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launch(JobExecuter.java:993)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:930)

jvm 1 |

jvm 1 | at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:836)

jvm 1 |

jvm 1 |

jvm 1 | com.bmc.arsys.api.ARException: ERROR
(4558): пїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅпїЅпїЅпїЅпїЅ
пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ;

jvm 1 |

jvm 1 | ERROR (2297): пїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅ
пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅ;
пїЅпїЅпїЅпїЅпїЅпїЅпїЅ 19
(...setId=BMC.ASSET^)

Please use plain text.
Occasional Contributor
MiguelMartins
Posts: 5
Registered: ‎05-05-2010
Message 2 of 6 (743 Views)

Re: Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Hello Mastron_s,

 

we are trying to implement exactly the same integration, but using UCMDB 10.01.

 

The documentation refers that we need to use the Atrium SDK instead of the default JAR/DLL files for the Atrium 7.6.04 version. Our problem is that we don't know how to import/use the SDK. 

 

We tried to copy the SDK file structure to the integration classpath, but the adapter is always returning the following error:

 

"BMC Remedy/Atrium JARs were not found on the probe classpath. Refer to integration documentation for JAR/DLL files required for this integration.

 

Can you help us with the SDK utilization in the UCMDB?

 

Regards,

 

Miguel Martins

Please use plain text.
Frequent Advisor
Mastron_s
Posts: 111
Registered: ‎05-05-2010
Message 3 of 6 (730 Views)

Re: Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Hi, Miguel

Did you copy all SDK files or just SDK files that described in Atrium Integration guide?

What is it "integartion classpath"?

In Atrium Integration guide for UCMDB 9.05 (CUP11) i see that we must do folowing:

b.Edit the WrapperGateway.conf file (or WrapperManager.conf if the Probe Manager and

Gateway are running in separate mode) in the following directory:

C:\hp\UCMDB\DataFlowProbe\bin.

Add the following line after the

wrapper.java.library.path.2=%content_dll% line:

 

wrapper.java.library.path.3=%runtime%/probeManager/discoveryResources/AtriumPushAdapter

 

c. Add the complete path to the Atrium DLL files (for example, C:\hp\UCMDB\DataFlowProbe\runtime\probeManager\discoveryResources\AtriumImportAdapter) to the Windows System Path on the Data Flow Probe machine.

 

d. Restart the Data Flow Probe service.

 

Did make this steps or it is not properly for ucmdb 10?

Please use plain text.
Occasional Contributor
MiguelMartins
Posts: 5
Registered: ‎05-05-2010
Message 4 of 6 (723 Views)

Re: Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Hello Mastron_s,

 

yes we did that step.

 

One of the problems is that we are following the "HP UCMDB discovery and integration content guide" for 10.01. In this document we have this note: "The AR System Java API is forward and backward compatible with other versions of the AR System, except Atrium version 7.6.0.4 where you must use the SDK of the same version. "

 

So we need to import the files from SDK. 

 

At this moment we have imported the SDK and we are obtaining some results from the probe. 

 

I will update with news as soon as possible.

 

Thank you for the help.

 

Regards 

 

Miguel Martins

Please use plain text.
Occasional Contributor
MiguelMartins
Posts: 5
Registered: ‎05-05-2010
Message 5 of 6 (715 Views)

Re: Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Hello,

 

Currently this is what we’ve got, concerning the integration with Atrium:

  1. Running the integration job, an XML file is created with the CI’s from Atrium 
  2. We are running into an error at RemoteProcess.log :
      File "atrium_map", line 40, in DiscoveryMain
                   at com.hp.ucmdb.adapters.push9.IntegrationAPI.processMap(IntegrationAPI.java:787)
                   at com.hp.ucmdb.adapters.push9.IntegrationAPI.mapIntermediateFileResults(IntegrationAPI.java:649)
                   at com.hp.ucmdb.adapters.push9.IntegrationAPI.processTql(IntegrationAPI.java:384)
                   at com.hp.ucmdb.adapters.push9.IntegrationAPI.processDir(IntegrationAPI.java:331)
                   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)

    java.lang.NullPointerException: java.lang.NullPointerException

 

Besides this error, the RemoteProcesses.log states “Number of CIs of type BMC_DataBase is 201” but the XML created with data from Atrium has more than 201 CI’s (211 to be exact)

 

Regards,

 

Miguel

Please use plain text.
Respected Contributor
Konstantin.Kornienko
Posts: 250
Registered: ‎12-25-2005
Message 6 of 6 (689 Views)

Re: Import CI`s from BMC Atrium CMDB 7.6 to HP UCMDB 9.05. BMC query syntax

Miguel, try this syntax:

 

<source_ci_type name="BMC_Rack" nameSpace="BMC.CORE" query="DatasetId=&quot;BMC.ASSET&quot;">

 

You need quote all parameters in query (BMC API requirements).

Tested your case in my environment, it works fine.

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation