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.

Configure web proxy settings (optional)

The Documentumprocessor service controlled by the processing agent requires connectivity to the OpenText Core Data Discovery & Risk Insights cloud components, often located away from the local network where the agent host servers are located. Although direct connectivity is ideal, use of a web proxy may be required in some environments for the agent systems to reach the OpenText Core Data Discovery & Risk Insights cloud.

  1. On the machine hosting the OpenText Core Data Discovery & Risk Insights processing agent, log on to the agent administration UI.

    From the Start menu, click OpenText Core Data Discovery & Risk Insights Agent > Agent Admin.

  2. In the navigation panel, click Advanced Settings.

    The Advanced Settings page opens.

  3. In the Category list, click Documentum Processor.

  4. Complete the following options.

    Option Description
    Proxy address URL

    Type the URL of the web proxy.
    Proxy bypass list

    Type a comma separated list of addresses that do not use the proxy server..
    Proxy Bypass on Local

    Specify whether to bypass the proxy for local addresses.

    • Select True to bypass for local addresses.

    • Select False to not bypass for local addresses.
    Proxy Password

    If the proxy requires authentication, type the password for the user account that will access the proxy server.
    Proxy Username

    If the proxy requires authentication, type the username for the user account that will access the proxy server.

  5. Click Save. You can close the agent administration UI.

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.

CAUTION: Failure to rescan Documentum datasets before the Documentum audit logs are purged will result in items being tracked incorrectly in OpenText Core Data Discovery & Risk Insights. Using the same example, if your Documentum audit trail is configured to be purged after 60 days and your Documentum datasets are updated every 90 days, you will lose 30 days of important information about deleted items—items deleted during this 30 day time frame will not be removed from the application.

The loss of information cannot be reconciled in OpenText Core Data Discovery & Risk Insights; you would have to create a new dataset and start over.