Highlighted
Frequent Contributor.. SansarChoinyambuu Frequent Contributor..
Frequent Contributor..
117 views

When / how does push back of uCMDB ID to Service Manager happen?

Hello,

We are populating data from Service Manager to uCMDB and pushing uCMDB ID's back to SM.

Chunk size is configured to 500 and we have over 12k CI's to import from SM on the integration job.

When / how does pushing back of uCMDB ID happen? From what we have seen, uCMDB is doing the following:

  • Import CI's in batch of 500
  • After every batch push back the uCMDB ID's for 500 CI's one by one (500 push requests) - even if uCMDB id has not changed
  • Import the next batch and repeat until all data is imported / IDs pushed back

On Probe server, discovery_probe.exe process is opening new TCP connection for every one of those uCMDB ID push back requests. Also on SM side we can see that hundreds of REST requests are coming to push back uCMDB IDs.

Is this a designed/wanted behaviour? Is there any configuration option available for SM adapter to handle this differently?

Cheers,

Sansar

 

uCMDB 2018.11 using ServiceManagerEnhancedAdapter9-41

0 Likes
3 Replies
popadiyski Acclaimed Contributor.
Acclaimed Contributor.

Re: When / how does push back of uCMDB ID to Service Manager happen?

Unfortunately I haven't seen a good pushback implementation for any MicroFocus adapter - even the native UCMDB to RTSM is not working very well.

Outside of that, the pushback should happen in a batch (ucmdbid_pushback.xsl describes it). if there is even one failure in the batch, the adapter will go pushback one by one. That's why you can decrease the batch size to be sure it will not fail so often.

Regards,

Petko Popadiyski

Freelance Microfocus CMS UCMDB Consulting

 

Likes are appreciated!
0 Likes
Frequent Contributor.. SansarChoinyambuu Frequent Contributor..
Frequent Contributor..

Re: When / how does push back of uCMDB ID to Service Manager happen?

@popadiyskiThanks for pointing out how push back should work.

In our ucmdbid_pushback.xslt, If I'm interpreting it correctly, I see actually that the adapter is configured to push back IDs one by one.

Is the content of your ucmdbid_pushback.xslt different than this:

 

<xsl:stylesheet version="1.0" xmlns:xsl="<a href="http://www.w3.org/1999/XSL/Transform" target="_blank">http://www.w3.org/1999/XSL/Transform</a>" xmlns:ns="<a href="http://schemas.hp.com/SM/7" target="_blank">http://schemas.hp.com/SM/7</a>">
    <xsl:template match="/ucmdbIDPushBack/ci">
        <model>
            <keys/>
            <instance>
                <xsl:for-each select="@id">
                    <ConfigurationItem><xsl:value-of select="."/></ConfigurationItem>
                </xsl:for-each>
                <xsl:for-each select="@ucmdbid">
                    <UcmdbID><xsl:value-of select="."/></UcmdbID>
                </xsl:for-each>
            </instance>
        </model>
    </xsl:template>
</xsl:stylesheet>

 

 

0 Likes
popadiyski Acclaimed Contributor.
Acclaimed Contributor.

Re: When / how does push back of uCMDB ID to Service Manager happen?

@SansarChoinyambuu how did you conclude it is configured to do it one by one by reading this configuration? for-each takes each instance, but then puts them into a batch, configured in the sm.properties by calling "/ucmdbIDPushBack/ci"  SM service.

 

Increase the debugging of the adapter so you can see every REST request and you will be able to validate what the adapter is doing in reality.

Petko

 

Likes are appreciated!
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.