Operation > Data Flow Management > Integrations > Integrating Multiple CMDBs > How to Protect CIs from Being Deleted on Target CMDBs during Data Push

How to Protect CIs from Being Deleted on Target CMDBs during Data Push

For data push integrations of multiple CMDBs using Cmdb10xAdapter, you can protect CIs of specified CI Types from being deleted on the target CMDBs during data push to keep a record of historical changes, by specifying CI Types that you want to protect from deletion in the <remove-cis> tag section of the Cmdb10xAdapter source.

Note This feature is supported for data push integrations from CMDBs of version 10.30 (or later) to other CMDBs of version 10.xx using Cmdb10xAdapter.

To protect CIs from being deleted on target CMDBs during data push:

  1. Log in to the source UCMDB server of version 10.30 (or later), and access Cmdb10xAdapter in either of the following ways:

    • Go to Data Flow Management > Integration Studio. In the Integration Point pane, right-click the integration point of your choice, and select Go To Adapter from the context menu. Then right-click the selected Cmdb10xAdapter in the Resources pane of the Adapter Management module, and select Edit adapter source from the context menu.
    • Go to Data Flow Management > Adapter Management . In the Resources pane, right-click Cmdb10xAdapter and select Edit adapter source from the context menu.
  2. Edit the Cmdb10xAdapter source to enable CI Type protection and to specify CI Types to protect.

    1. In the Adapter Source Editor, locate the <remove-cis> tag section, which looks like the following:

      <remove-cis isEnabled="false">
          <ci-type>link</ci-type>
          <ci-type>object</ci-type>
      </remove-cis>
      
    2. Change the value of the isEnabled setting from false to true.

    3. Modify the values in the <ci-type> tags to include the CI Types that you want to protect from deletion only.

      Add more <ci-type> tag lines if necessary.

      Note

      • CI Types names are case-sensitive. You can get the correct CI Types names from Modeling > CI Type Manager
      • You can only specify and protect CI Types that already exist on the target CMDBs. Otherwise you will see warning messages that the CI type may not exist on target UCMDB in C:\hp\UCMDB\UCMDBServer\integrations\runtime\log\<integration_point>.log.
    4. Click Save.
    5. Click Finish.

    The changes take effect right away, and the specified CI Types are protected from being deleted on the target CMDBs during the future data push.

  3. (Optional) Delete a CI of protected CI Type from the source CMDB, and the go to Data Flow Management > Integration Studio, and run the data push integration job by clicking Run Job - Synchronize Changes or Run Job - Synchronize All Data .

    The CI of the protected CI Type should still exist on the target CMDB.

Related Topics Link IconRelated Information