Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
72 views

Question about delta sync (push mode)

Hello:


We have a requirement to push all CI's (windows computers) that has scanned in a day (24 hours) to Asset Manager.

So, to accomplish this task we have an integration point using AMGenericAdapter an a integration job with push mode data.
The integration job is scheduled with delta sync everyday at 04:00pm.

The query associated with this integration job results in all windows computers that has scanned in the last 24 hours (windows CI's type whose have a InventoryScanner which have the LastDiscoveredTime changed during 24 hours).

This scenario works well, every computer which is scanned in a day puts in the query and later those data puts in AssetManager.

The question is:

Imagine the integration job is running more than 24 hours (ex: 28 hours) because we have many CI's and a lot of information.The job is running from 04:00pm (today) to the 08:00pm (next day)

What will happen with the next Delta sync scheduled at 04:00pm (next day)?
Will this scheduled job running when the current job is stopped or will wait for the next day?
If the delta sync will run at 08:00pm the query gets windows computers that have InventoryScanner changed during 24 hours (from 08:00pm today to 08:00pm yesterday). So what will happen with those windows computers that have scanned between 04:00-08:00pm yesterday

Any other way to resolve this requirement.

 

thanks in advanced.

0 Likes
3 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Question about delta sync (push mode)

At the next delta it will check only for the nodes changed in the last 24 hours so you will lose some of them. This is due to the integration TQL.
We don't have a mechanism to tag the nodes which were sent or not.
The root cause is why discovery takes so much time. You can add more probes, fine tune the existing probes, filter what you scan so you avoid losing time on useless nodes, etc. There are multiple tips and tricks to resolve this so your integration is unchanged but working.
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Question about delta sync (push mode)

The problem is not in discovery mechanism, the probes discovered and scanned nodes well and in time.
All the discovered CI's are send to the UCMDB.

The issue is with the time to complete the Data Push integration job sync.

If we scheduled a delta sync every day (based on InventoryScanner changed during 24 hours), if one day the sync spends more time than 24 hours, in the next execution we loose some CI's,.
We will try to change the threads.pool.size and chunk.size to see if these options speed up the sync, so that it ends before 24 hours.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Question about delta sync (push mode)

So the slowness is on the integration part.
What makes it slow? The CI count?
What's the difference between a failed and a successful push?
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
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.