CMDBtoSaaS adapter for Delta Sync with push.chagnes.based.on.attribute

Emil Dutsov 1 month ago

Hi,

We are having On-prem UCMDB synced to SaaS UCMDB using CMDBtoSaaS adapter.

I was trying to set this attribute to true in the CMDB to SaaS adapter with the idea that if an attribute from the Query Element layout is changed it will be pushed in the next delta.

For example if i add LastDiscoveredTime in the element layour attrbutes even if the node LastModifiedTime is not changed I was expecing the DeltaSync to push the CI and update LastDiscoveredTime.

Any idea how this really suppose to work ? Does the Last Modified Time should be always changed for the Delta to detect changes, or Delta can be triggered based on a change on any attribute if push.changes.based.on.attributes" is set to true.

Here is the actual setting.

<adapter-setting name="push.changes.based.on.attributes">true</adapter-setting>

Here is the documentation

https://docs.microfocus.com/doc/UCMDB/24.4/IntegDeltaSync

Kind Regards

Emil Dutsov

Tags:

OBM

SaaS

cmdbtosaas

uCMDB

Integration

RTSM

push

Top Replies

0 Misaq 1 month ago

I think this setup is to limit the Delta sync to only attributes that are in layout.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Emil Dutsov 1 month ago in reply to Misaq

I think the same.
What we found out is that it works only if LastModifiedTime is changed too.
If lastModifiedTIme is not changed it doesn't push any attributes.

In our scenario we want to push LastDiscoveredTime attribute, but when LastDiscoveredTime is updated by the discovery, the LastModified isn't.

Any idea how to push LastDiscovedTime with Delta ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
Suggested Answer

0 Misaq 1 month ago in reply to Emil Dutsov

It might be that lastDiscoveredTime and LastModifiedTime both are meta attributes(or system attributes).Hence LastModifiedTime is not affected(my guess).

My crude workaround would be to add enrichment rule to update LastModifiedTime when LastDiscoveredTime has changed. But that just a guess. Maybe there is a better way or explanation.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
Suggested Answer

0 Zhe 'Leslie' Nian 1 month ago

When a CI is touched by discovery jobs, its LastDiscoveredTime changed but LastModifiedTime does not. This is documented in the following online help page.

https://docs.microfocus.com/doc/UCMDB/24.4/ITUCiProp

Because delta push uses the LastModifiedTime to detect CIs to be pushed, CIs being touched are not in the scope.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Menu

Universal Discovery & CMDB Discussions

Verified Answers

CMDBtoSaaS adapter for Delta Sync with push.chagnes.based.on.attribute

Tags:

Top Replies

Suggested Answer

Suggested Answer

Resources