Highlighted
Absent Member.. Absent Member..
Absent Member..
322 views

uCMDB Push Nulls non-discovered field in HPSM

Scenario:


Service Manager WSDL has Serial Number exposed.

 

uCMDB doesnt send an element with the serial number tag the result is in Service Manager Ci record, the serial number field is blanked out. 

 

We have tried to edit the xslt for computer push like the following:

 

<serialnumber></serialnumber> 

 

We have tried to exclude it all together ( not even commenting it out).

 

We have tried removing it from the TQL that is used by the push job. 

 

We have found that as long as the attribute is exposed in the service manage WSDL there is no way to keep it from being blanked out when the push job runs.

 

 

The overall question is, how do we prevent uCMDB from nulling out a field in HPSM when uCMDB has not yet discovered and thus we dont want send anything to that field in HPSM. 

 

Please let me know if you have any questions or concerns. 

 

thanks,

 

Dwayne Whitt

0 Likes
5 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: uCMDB Push Nulls non-discovered field in HPSM

Dwayne;

 

Were it the other way around (SM pushing to UCMDB), you could use reconciliation priority for such a thing.  Since the SM integration is supported by the Service Manager team, they may have ideas or example of how to do this.  I would post this question in their forum to see what they have to say.

Hope this helps,
Keith Paschal
UCMDB Worldwide Support Lead
Micro Focus Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: uCMDB Push Nulls non-discovered field in HPSM

So this doesnt happen really for any other integration there is for HPSM (connect it .etc). I would imagine there is some type of logic on the uCMDB side to handle what happens when we dont send data for an exposed element on the SM WSDL.

 

Is there a way to see what the XML looks like before it is sent to the XSLT? Is there a way to see what the XML looks like after it is sent to the XSLT?

 

This might be able to help us see what it looks like when sent to HPSM.

 

thanks,

 

Dwayne Whitt

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: uCMDB Push Nulls non-discovered field in HPSM

Hello,

 

You can enable the debug in the Probe logs to see that information. All the information is in the fcmdb*.log and the log file of the adapter is:

 

<UCMDB installation Folder>\DataFlowProbe\runtime\log\fcmdb.adapters.<integration_point_name>.log

 

 

These are the steps (you can also find this information in the Integration guide for SM):

 

a) cd to <DataFlowProbe_Install_Dir>\conf\log

b) Edit the fcmdb.properties files as follows:

      Change:

                   loglevel=ERROR   

      to:               

                   loglevel=DEBUG

 

       Or you can only change this line:

              

                                             log4j.category.fcmdb.adapters=${loglevel},fcmdb.adapters

                              To

                                             log4j.category.fcmdb.adapters=DEBUG,fcmdb.adapters

 The change made above will be loaded to the running system without restarting it. It may take up to 1 minute before the changes will take effect.

 

Also edit the integration point and in Development Mode, select True from the list

 

This is an example of the information you will find in the log of the adapter when you push one CI from uCMDB to SM (when you enable the debug):

 

2013-03-27 11:55:50,983 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Starting sync for TQL: SM Running Software Push

2013-03-27 11:55:50,985 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Source tree XML:

<running_software bdmType="RunningSoftware" customer_id="1" display_label="test larw2k3evm03" friendlyType="TestRunningSoftware" global_id="9a25624397ae418920e442b232fc683e" id="9a25624397ae418920e442b232fc683e" name="testrunningsoftware" root_container="UCMDB%0Ant%0A1%0Ainternal_id%3DSTRING%3D64f8a3cd1ad3abfd89df23b245a670bf%0A"><nodes direction="incoming" linkLabel="Composition" linkName="13" linkType="Composition"><node bdmType="Node" customer_id="1" domain_name="WORKGROUP" friendlyType="Windows" id="64f8a3cd1ad3abfd89df23b245a670bf" realRelationType="Composition"/></nodes></running_software>

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Transformed XML:

<CreateucmdbRunningSoftwareRequest><model><keys/><instance><UCMDBId>9a25624397ae418920e442b232fc683e</UCMDBId><CustomerId>1</CustomerId><Type>runningsoftware</Type><Subtype>Running Software</Subtype><CIIdentifier>_test larw2k3evm03</CIIdentifier></instance></model></CreateucmdbRunningSoftwareRequest>

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== in sendMessage!

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== config.getUrl():null

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== config.getUrl():null

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== urls.length is:1

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== config.getUrl():null

2013-03-27 11:55:50,988 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== getNodesSize is:1

2013-03-27 11:55:50,989 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== The mod is:0

2013-03-27 11:55:50,989 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== The connectionIndex is:0

2013-03-27 11:55:50,989 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== The urls:[Ljava.lang.String;@639d4911

2013-03-27 11:55:50,989 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== The current URL string is:http://16.77.50.221:13080/sc62server/ws

2013-03-27 11:55:50,989 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== start run soap message

2013-03-27 11:55:50,991 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Run soap message <?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelop/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><CreateucmdbRunningSoftwareRequest><model><keys/><instance><UCMDBId>9a25624397ae418920e442b232fc683e</UCMDBId><CustomerId>1</CustomerId><Type>runningsoftware</Type><Subtype>Running Software</Subtype><CIIdentifier>_test larw2k3evm03</CIIdentifier></instance></model></CreateucmdbRunningSoftwareRequest></SOAP-ENV:Body></SOAP-ENV:Envelope> for URL http://16.77.50.221:13080/sc62server/ws

2013-03-27 11:55:50,991 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ========== create connection required time = 0

2013-03-27 11:55:51,114 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Response soap message from SM:

<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><CreateucmdbRunningSoftwareResponse xmlns="http://servicecenter.peregrine.com/PWS" xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" message="Success" returnCode="0" schemaRevisionDate="2008-06-09" schemaRevisionLevel="0" status="SUCCESS" xsi:schemaLocation="http://servicecenter.peregrine.com/PWS http://edo:13080/sc62server/ucmdbRunningSoftware.xsd"><model><keys><CIIdentifier type="String">_test larw2k3evm03</CIIdentifier></keys><instance recordid="_test larw2k3evm03 - runningsoftware - Installed" uniquequery="logical.name=&quot;_test larw2k3evm03&quot;"><CIIdentifier type="String">_test larw2k3evm03</CIIdentifier><Type type="String">runningsoftware</Type><CIName type="String">CI14511</CIName><Subtype type="String">Running Software</Subtype><UCMDBId type="String">9a25624397ae418920e442b232fc683e</UCMDBId></instance></model><messages><cmn:message type="String">Configuration Item record added.</cmn:message></messages></CreateucmdbRunningSoftwareResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

2013-03-27 11:55:51,114 [70949201@Default-256] DEBUG - SM 9_30 Integration >> ======== stop run soap message. The required time = 125

2013-03-27 11:55:51,114 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Response message from SM:

<CreateucmdbRunningSoftwareResponse xmlns="http://servicecenter.peregrine.com/PWS" xmlns:cmn="http://servicecenter.peregrine.com/PWS/Common" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" message="Success" returnCode="0" schemaRevisionDate="2008-06-09" schemaRevisionLevel="0" status="SUCCESS" xsi:schemaLocation="http://servicecenter.peregrine.com/PWS http://edo:13080/sc62server/ucmdbRunningSoftware.xsd"><model><keys><CIIdentifier type="String">_test larw2k3evm03</CIIdentifier></keys><instance recordid="_test larw2k3evm03 - runningsoftware - Installed" uniquequery="logical.name=&quot;_test larw2k3evm03&quot;"><CIIdentifier type="String">_test larw2k3evm03</CIIdentifier><Type type="String">runningsoftware</Type><CIName type="String">CI14511</CIName><Subtype type="String">Running Software</Subtype><UCMDBId type="String">9a25624397ae418920e442b232fc683e</UCMDBId></instance></model><messages><cmn:message type="String">Configuration Item record added.</cmn:message></messages></CreateucmdbRunningSoftwareResponse>

2013-03-27 11:55:51,114 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Report 0 failed CIs!

2013-03-27 11:55:51,115 [70949201@Default-256] DEBUG - SM 9_30 Integration >> Report 0 failed Relations!

 

In the first part you have the “Source tree XML” information. This is the output of the TQL you are using in the integration job. After that you will see the output after the transformation is done “Transformed XML”. Here you can identify if there is any issue with the configuration you have in the transformation file of the TQL. The last part is the result you receive from SM “Response soap message from SM” and “Response message from SM”. You can see all the information of the CI that it is created in SM.

 

Please open a support case with SM team so they can further investigate this issue. You can upload the logs with the debug enable to show how the information is sent from uCMDB and the response.

 

Regards,

 

Rosario

Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: uCMDB Push Nulls non-discovered field in HPSM

Thanks for the information! So is there any way from stopping a field from uCMDB being sent to HPSM in the computer push job via the XSLT or any other method in uCMDB? For example we dont want to send serial number to HPSM when updating or creaing Cis. 

 

I have already put this on the HPSM forums. But there seems to be something we can do on the uCMDB to control what fields we are sending to HPSM, i am just not sure where to look. 

 

thanks,

 

Dwayne Whitt

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: uCMDB Push Nulls non-discovered field in HPSM

Hello,

 

You can remove the field from the TQL, I understand that you already tried that. I attached a document with the steps to verify that. You can also enable the debug to verify that the attribute is not sent. If you already removed the attribute from the TQL and you still see that the CIs are created with a null value on that field you need to verify this issue with SM team.

 

Regards,

 

Rosario

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.