Platform Deployment Guide › Object Storage › Integrating with IBM DB2 Content Manager › About IBM Content Manager Integration › How the IBM Content Manager Integration Works

How the IBM Content Manager Integration Works

Content Manager integration with CA DataMinder is controlled by the CMS. If the integration is enabled, when an event is replicated to the CMS from a client machine or gateway, the blob file is first saved to the object store \Data folder. It is then copied to the Content Manager and the source blob file deleted from the CMS.

Note: The blob file is not deleted immediately; it is cached in case it is needed again soon.

The database entry on the CMS is subsequently updated to reflect the new location for the blob, replacing the blob file system location with the Content Manager resource identifier.

• If the Content Manager is temporarily unavailable: CA DataMinder maintains a database table containing a list of blobs that need to be migrated to the Content Manager. This list can build up if the Content Manager is offline or if the configuration settings are incorrectly optimized for the installation. We recommend that you monitor the size of this database table as a health check.
• Migrating existing blob files to a Content Manager: There is no built-in mechanism for migrating to Content Manager those blobs that were stored on the CMS before Content Manager integration was implemented. It is possible to do this, however. You will need to write a custom SQL procedure to add a blob queue record for each blob to be migrated.

Note: Any custom SQL procedure to migrate existing blobs must be carefully designed to ensure that the migration queue is properly managed. We strongly recommend that you contact Technical Support for guidance if you need to write a migration procedure; see CA Technical Support.

More information:

Managing the Temporary Object Store