Multiple Deployments with Version 9.x/10.x CMDBs Using Data Push
When you use the UCMDB 9.x or UCMDB 10.x adapter to create an integration point, you are able to synchronize data between different CMDB instances using either population or data push. For details on the population method, see Multiple Deployments with Version 9.x/10.x CMDBs Using Population.
For details on the data push flow for setting up an integration between multiple CMDBs, see Set Up Integrations Between Two OMis.
Limitations
The following limitations apply to the data push method:
- An integration point for data push can only be defined in UCMDB version 10.01 or above.
- The target CMDB must be either UCMDB version 9.05 CUP 9 and later CUPs, or UCMDB version 10.01 and above (it is not supported for UCMDB version 10.00).
- A single TQL query in the data push flow is limited to 5 million CIs and relationships. This limitation is only for a single query; multiple TQL queries in multiple jobs may exceed this limit.
-
Data Push is not supported for virtual links.
In the data push flow, a local TQL query collects data from the local CMDB and pushes this data to the remote CMDB. The adapter filters out unsupported CITs and relationships, and it also filters out any invalid-links and attributes.
Note Data push is also supported for CIs and relationships from federation adapters with their LastModifiedTime property.
Auto Complete Reconciliation
When pushing CIs or relationships to a remote CMDB, any CI or attribute that is needed for reconciliation (according to the remote CMDB reconciliation rules) is automatically added to the CIs and attributes already requested. This is necessary to ensure that the identification process is executed accurately and no CIs are incorrectly merged.
Note This may cause more data than originally selected in the TQL query to be transferred.