Highlighted
Visitor.
1126 views

uCMDB 10 - XLS import job is failing

Hi,


Have installed uCMDB 10 on RH linux. Probe is running on the same host.
I'm trying to import CIIImports.xls (sample file which comes with the software).


Getting the following error when running the integration job:
[ERROR] [JobExecuterWorker-0:DS_XLS_test_Import topology from Excel Workbook] (ExecutionEngineImpl.java:334) - Discovery Error: Traceback (innermost last):
  File "logger", line 17, in ?
ImportError: no module named traceback

Content of WrapperEnv.conf  file:

##########################
# Environment global vars
##########################
set.BASE_DIR=..
set.JRE_HOME=%BASE_DIR%/bin/jre
set.bin=%BASE_DIR%/bin
set.dll=%BASE_DIR%/dll
set.conf=%BASE_DIR%/conf
set.deploy=%BASE_DIR%/deploy
set.content=%BASE_DIR%/content
set.jython=%BASE_DIR%/jython
set.LIB=%BASE_DIR%/lib
set.runtime=%BASE_DIR%/runtime
set.content_dll=%content%/dll
set.CONTENT_LIB=%content%/lib
set.jce=%CONTENT_LIB%/jce
set.nnm=%CONTENT_LIB%/nnm
set.sap=%CONTENT_LIB%/sap
set.systinet=%CONTENT_LIB%/systinet
set.xml=%CONTENT_LIB%/xml
set.vmware=%CONTENT_LIB%/vmware
set.webservice=%CONTENT_LIB%/webservice
set.probeManager=%runtime%/probeManager
########################
# Environment Gateway vars
########################
set.GATEWAY_MIN_MEM=512
set.GATEWAY_MAX_MEM=1024
set.IP_GATEWAY_ADDRESS=139.188.89.202
set.IP_GATEWAY_PORT=8083

########################
# Environment Manager vars
########################
set.MANAGER_MIN_MEM=512
set.MANAGER_MAX_MEM=1024
set.IP_MANAGER_ADDRESS=139.188.89.202
set.IP_MANAGER_PORT=8082
########################
# Environment Discovery Path
########################
set.CM_REDIRECT_CLASSES=%deploy%/cm/classes
set.XML_CLASSES=%xml%/xmlParserAPIs.jar:%xml%/xercesImpl.jar:%xml%/xalan.jar:%xml%/crimson.jar:%xml%/jaxp.jar:%xml%/jaxen-core.jar:%xml%/jaxen-jdom.jar:%xml%/saxpath.jar
set.SAP_CLASSES=%sap%/sapjco.jar:%sap%/com_sap_pj_jmx.jar:%sap%/exception.jar:%sap%/logging.jar:%sap%/sapj2eeclient.jar:%sap%/sapxmltoolkit.jar
set.CONTENT_JARS=%CONTENT_LIB%/discovery-content_30.jar:%CONTENT_LIB%/discovery-content_29.jar:%CONTENT_LIB%/discovery-content_28.jar:%CONTENT_LIB%/discovery-content_27.jar:%CONTENT_LIB%/discovery-content_26.jar:%CONTENT_LIB%/discovery-content_25.jar:%CONTENT_LIB%/discovery-content_24.jar:%CONTENT_LIB%/discovery-content_23.jar:%CONTENT_LIB%/discovery-content_22.jar:%CONTENT_LIB%/discovery-content_21.jar:%CONTENT_LIB%/discovery-content_20.jar:%CONTENT_LIB%/discovery-content_19.jar:%CONTENT_LIB%/discovery-content_18.jar:%CONTENT_LIB%/discovery-content_17.jar:%CONTENT_LIB%/discovery-content_16.jar:%CONTENT_LIB%/discovery-content_15.jar:%CONTENT_LIB%/discovery-content_14.jar:%CONTENT_LIB%/discovery-content_13.jar:%CONTENT_LIB%/discovery-content_12.jar:%CONTENT_LIB%/discovery-content_11.jar:%CONTENT_LIB%/discovery-content_10.jar:%CONTENT_LIB%/discovery-content_9.jar:%CONTENT_LIB%/discovery-content_8.jar:%CONTENT_LIB%/discovery-content_7.jar:%CONTENT_LIB%/discovery-content_6.jar:%CONTENT_LIB%/discovery-content_5.jar:%CONTENT_LIB%/discovery-content_4.jar:%CONTENT_LIB%/discovery-content_3.jar:%CONTENT_LIB%/discovery-content_2.jar:%CONTENT_LIB%/discovery-content_1.jar:%CONTENT_LIB%/discovery-content.jar
set.FLOW_CLASSES=%runtime%/probeManager/netlinks
set.JYTHON_CLASSES=%jython%/jython.jar
set.SYSTINET_CLASSES=%webservice%:%systinet%/activation.jar:%systinet%/builtin_serialization.jar:%systinet%/core_services_client.jar:%systinet%/jaas.jar:%systinet%/jaxm.jar:%systinet%/jaxrpc.jar:%systinet%/jetty.jar:%systinet%/runner.jar:%systinet%/saaj.jar:%systinet%/security_providers_client.jar:%systinet%/security2-ng.jar:%systinet%/security-ng.jar:%systinet%/uddiclient_api_v3.jar:%systinet%/uddiclient_api_v3_ext.jar:%systinet%/uddiclient_core.jar:%systinet%/wasp.jar:%systinet%/wsdl_api.jar:%systinet%/xercesImpl.jar:%systinet%/xml-apis.jar:%xml%/xmlParserAPIs.jar:%webservice%/wsdl4j.jar
set.VMWARE_CLASSES=%vmware%/vim.jar:%vmware%/vim25.jar
set.NNM_CLASSES=%nnm%/ucmdb_wrapper.jar:%runtime%/probeManager/discoveryResources/nnm/nnm_sdk.jar
set.COMMON_CLASSPATH=%conf%:%XML_CLASSES%:%JYTHON_CLASSES%:%NNM_CLASSES%:%content_dll%:%FLOW_CLASSES%:%SAP_CLASSES%:%VMWARE_CLASSES%:%SYSTINET_CLASSES%:%CM_REDIRECT_CLASSES%
set.POI_CLASSES=%probemanager%/discoveryResources/geronimo-staxapi_1.0_spec-1.0.jar:%probemanager%/discoveryResources/poi-3.7-beta1-20100620.jar:%probemanager%/discoveryResources/poi-ooxml-3.7-beta1-20100620.jar:%probemanager%/discoveryResources/poiooxml-schemas-3.7-beta1-20100620.jar:%probemanager%/discoveryResources/xmlbeans-2.3.0.jar
set.COMMON_CLASSPATH=%LIB%/wrapper.jar:%POI_CLASSES%:%COMMON_CLASSPATH%
set.GATEWAY_RESOURCES=%runtime%/probeGateway/discoveryConfigFiles:%runtime%/probeGateway/discoveryResources

Does anyone know how to resolve this issue?

Thanks in advance

0 Likes
8 Replies
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: uCMDB 10 - XLS import job is failing

Hi,

Please be sure that RedHat box you're runing has "dos2unix" installed? http://www.rpmfind.net/linux/rpm2html/search.php?query=dos2unix

Please be aware that Probe installed on Linux box could only be used for integrations purposes, not discovery.

The easiest way to go is to install additional (or move existent) probe to Windows server.

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Visitor.

Re: uCMDB 10 - XLS import job is failing

Yes I do have dos2unix installed:

 

dos2unix.x86_64                        3.1-27.2.el5               installed

Regards

 

0 Likes
Highlighted
Visitor.

Re: uCMDB 10 - XLS import job is failing

Does anyone know if XLS import is supported on linux?
From DFM guide: “The Data Flow Probe installed on a Linux platform is intended only for
integrations, and not for discovery”.
Is XLS import considered as an integration or discovery?
0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: uCMDB 10 - XLS import job is failing

It is discovery not integration...

Support of Windows proprietary protocols on Linux isn't stable enough. HP tried to stabilized it but this is too complicated task.

Data Flow Management Guide contains following statement:  "The Data Flow Probe that runs on a Linux platform is intended only for integrations, and not for discovery".

Some of discovery jobs will work although. But it's not officially supported. Sorry about it. 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Visitor.

Re: uCMDB 10 - XLS import job is failing

Have installed UCMDB 10.01 CUP6 on Windows.

 

Now I can't even run the job.
 After creating an integration point I'm getting the following error:

"Could not find Probe <my probe name>. Task for trigger CI will not be created"

 

In Data Flow Probe Setup I can see that my probe IS connected.

 

Please help.

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: uCMDB 10 - XLS import job is failing

Please be sure that you choose the probe name according to what you was installed in "Data Flow Probe" field.

I'm attaching screenshot for your convinience.

 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
0 Likes
Highlighted
Visitor.

Re: uCMDB 10 - XLS import job is failing

Yes, the probe name is exactly the same as on Data Floe Probe Setup screen.
0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: uCMDB 10 - XLS import job is failing

Did you try to change to Auto?

How many names you have there?

Could you try to change the name of the probe in appilog.collectors.probe.name parameter of C:\hp\UCMDB\DataFlowProbe\conf\DataFlowProbe.properties file and set the integration for the new name?

 

Regards
-Dmitry Gomel, PMP
Click the Like button at the bottom to say 'Thanks'.
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.