Documentum connection

If you will be creating datasets that process Documentum data, review the following information before creating sources and datasets to be processed by OpenText Core Data Discovery & Risk Insights.

• You will define a user to access the Documentum sources. On the Connection page of the Source creation wizard, you must define a user that has the appropriate permissions to access and read from the selected data type and connection.

• When creating OpenText Core Data Discovery & Risk Insights sources, consider the following.

  • If assigned to a cloud agent cluster, you must define the Documentum host URL using a secure protocol (HTTPS). A secure connection is always recommended, but not required for non-cloud agent clusters.

  • The Documentum host URL must be unique across sources.

• When creating OpenText Core Data Discovery & Risk Insights datasets, consider the following.

  • You can define a single Documentum repository per dataset.

  • The Documentum repository must be unique across datasets within the source.

  • SmartScan is not supported.

Documentum deletion tracking

OpenText Core Data Discovery & Risk Insights tracks deletions of managed Documentum items using the Documentum audit trail. OpenText Core Data Discovery & Risk Insights uses the dm_destroy event from the Documentum audit trail to identify deleted Documentum items to be removed from the application. Without this information, items deleted from your Documentum environment cannot be removed from the application. Documentum items that have been added or modified are appropriately updated in OpenText Core Data Discovery & Risk Insights.

For example, if your Documentum audit trail is configured to be purged after 90 days, verify that your Documentum datasets are updated at least every 89 days.