Data Discovery & Risk Insights 26.2.0 Help Center

# Content Manager integration

If you will be creating datasets that process data in Content Manager or creating targets that send data to Content Manager, you must complete additional tasks to enable this processing. Review the Content Manager requirements and complete the integration tasks.

## Content Manager requirements

Prior to processing data from Content Manager, you must have the following in place.

- Content Manager 23.4.x or 25.3.x fully installed and functioning.

- You must fully install and configure the Content Manager ServiceAPI component, following the Content Manager installation instructions.

  - The ServiceAPI website must be configured for SSL. The processing agent connects to the ServiceAPI using basic authentication. To ensure security of the username and password, TLS communication is required. You need to configure SSL for the Content Manager sites in IIS Manager, following the typical Windows model.

  - By default, the Content Manager ServiceAPI may have been configured to use only Windows authentication. Ensure that the ServiceAPI is configured to use basic authentication and is secured using TLS.

  - The certificate presented by the Content Manager ServiceAPI must be fully trustable by the OpenText Core Data Discovery & Risk Insights agents that will be connecting to it.

  - In the Service API `hptrim.config` file, locate the `hptrim` tag. Set the `requireAntiForgeryToken` attribute to `false`.

- OpenText Core Data Discovery & Risk Insights does not support `VMBX` files. All `VMBX` files must be converted to `EML` or `MSG` prior to starting any processing by OpenText Core Data Discovery & Risk Insights.

- Create a Content Manager user account.

- Allow holds within Content Manager containers.

- Enable hold tracking.

- Enable delete tracking.

- Create an origin object in Content Manager.

- Increase the upload size (optional).

- Configure dataset rescanning (optional)

- Configure web proxy settings (optional)

## Create a Content Manager user account

For OpenText Core Data Discovery & Risk Insights to process Content Manager records or to send data to Content Manager, you must create a user account in Content Manager with the necessary permissions. You will enter the credentials for this account when you create Content Manager sources and Content Manager targets.

TIP: If accessing multiple Content Manager origin objects, you may need to create multiple Content Manager user accounts. Additionally, creating separate accounts for use by sources and targets may allow for greater flexibility.

The permissions in the following procedure are recommendations and may vary from what is required for your OpenText Core Data Discovery & Risk Insights and Content Manager implementations.

To create a user account for use by the processing agent

1. Create an active directory user account to be used as the "OpenText Core Data Discovery & Risk Insights Agent Worker” account.

   This account must be in the same domain (or a trusted domain) as Content Manager.

   - For the user account password, set the options that the password does not expire and that the user cannot change the password.

2. In Content Manager, create a CM Person Location (“OpenText Core Data Discovery & Risk Insights Agent Worker”).

   - On the profile tab, configure this Person Location to “Accept logins for this user using credentials:” for the created active directory user.

   - Set the User Type for this Person Location to “Records Manager” with the "Bypass all access controls" permission enabled.

     NOTE: The "Bypass all access controls" permission is required so that this user can perform all necessary actions in OpenText Core Data Discovery & Risk Insights, ignoring other Content Manager access controls or security on records.

   - Set the Security to "<Highest>".

## Allow holds within Content Manager containers

In Content Manager, a container is a folder in which records exist. By default, individual records within Content Manager containers cannot be placed on hold.

The hold in OpenText Core Data Discovery & Risk Insights is placed on the Content Manager record itself. If that record is a compressed file, the compressed file is placed on hold, not the individual items within the compressed record file (such as a ZIP or PST).

To allow holds to be placed on records within Content Manager containers

1. Log on to Content Manager as a user with permission to update system options.

2. Click the ADMINISTRATION tab.

   The ADMINISTRATION page opens.

3. In the Options section of the ADMINISTRATION ribbon, click System.

   The System Options dialog opens.

4. In the left pane, click Miscellaneous.

5. If not already selected (check mark is not present), click to the left of Allow a hold to be placed on a record that is within a container to select this option (a check mark displays).

6. Click OK.

   The changes are saved and the System Options dialog closes.

## Enable hold tracking

OpenText Core Data Discovery & Risk Insights honors holds on managed Content Manager records. For Content Manager holds deleted in Content Manager, OpenText Core Data Discovery & Risk Insights reports an error when you attempt to add a document to that hold or if you attempt to release a document from that hold. This error displays on the Agent Activity page in Connect. To include the Content Manager user that deleted the Content Manager hold, you must enable the Content Manager audit option that allows hold tracking.

To enable hold tracking in Content Manager

1. Log on to Content Manager as a user with permission to update audit options.

2. Click the ADMINISTRATION tab.

   The Administration page opens.

3. In the Options section of the ADMINISTRATION ribbon, click Audit.

   The Audit Options dialog opens to the General tab.

4. Click the Active Audit Events tab.

5. If not already selected (check mark is not present), click to the left of Hold to select this option (a check mark displays).

6. Click OK.

   The changes are saved and the Audit Options dialog closes.

## Enable delete tracking

OpenText Core Data Discovery & Risk Insights needs to be aware when records are deleted in Content Manager. To do this, you must enable a specific event type in Content Manager for each record type processed by OpenText Core Data Discovery & Risk Insights and enable a specific audit option.

To enable delete tracking

1. Open the Content Manager Desktop application.

   1. Click the MANAGE tab.

      The MANAGE page opens.

   2. In the Records section of the MANAGE ribbon, click Record Types.

      The list of record types displays.

   3. For each record type that is being processed,

      1. Right-click the record type, and then click Properties.

         The record type properties dialog opens.

      2. Click the Audit tab.

         The list of audit event types displays.

      3. In the list of audit event types, click the Deleted option.

         A check mark displays next to Deleted.

      4. In the list of audit event types, click the Record Disposition Changed option.

         A check mark displays next to Record Disposition Changed.

      5. Click OK.

         The changes are saved and the properties dialog closes.

   4. Close the Content Manager Desktop application.

2. Open the Content Manager administrator application.

   1. Click the ADMINISTRATION tab.

      The ADMINISTRATION page opens.

   2. In the Options section of the ADMINISTRATION ribbon, click Audit.

      The Audit Options dialog opens to the General tab.

   3. On the General tab, select the Deleting an item checkbox.

   4. Click OK.

      The changes are saved and the Audit Options dialog closes.

   5. Close the Content Manager administration application.

## Create an origin object in Content Manager

An origin object must exist in Content Manager for each Content Manager target defined in OpenText Core Data Discovery & Risk Insights. You can create separate destinations for a single Content Manager target to define multiple locations within a single Content Manager resource. You will need the origin object ID when creating a Content Manager target.

In Content Manager, create an origin of the "generic" type. Follow the normal guidelines for creating the origin. For more information, see "Origins" in the Content Manager Help.

## Increase the upload size (optional)

To accommodate sending large files to Content Manager, you can increase the upload size restrictions in the Content Manager web configuration file at the root of the website. The default upload size is 4 MB (4194304 bytes or 4096 kilobytes).

If you have multiple Content Manager application hosts, this must be performed on each host.

CAUTION: In addition to the desired file size, consider the available memory, available hard disk space, processor speed, and current network traffic when defining the maximum upload size.

To increase the Content Manager upload size

1. Log on to the machine hosting the Content Manager application.

2. With a text editing tool, open `<ContentManagerInstallDirectory>\Service_API\web.config`,

   where `<ContentManagerInstallDirectory>` is the location where the agent was installed (such as `C:\Program Files\Micro Focus\Content Manager`).

   Make a backup copy of this file.

3. Under the root `<system.web>` configuration, add the `maxRequestLength` attribute to the `<httpRunTime>` configuration and set the value to the desired file size, in kilobytes.

       <httpRuntime maxRequestLength="<fileSize_inKilobytes>" executionTimeout="1200"
       requestValidationType="HP.HPTRIM.Services.Common.RequestValidator" />

   where `<fileSize_inKilobytes>` is the desired maximum file size, in kilobytes, allowed to be uploaded to Content Manager.

   Example after update: set the maximum file size to 15 MB, which is 15360 kilobytes

       <system.web>

         <httpRuntime maxRequestLength="15360" executionTimeout="3600"
         requestValidationType="HP.HPTRIM.Services.Common.RequestValidator" />

       ...

4. Under the root `<system.webserver>` configuration, add the following configuration section.

       <security>
         <requestFiltering>
           <requestLimits maxAllowedContentLength="<fileSize_inBytes>" />
         </requestFiltering>
       </security>

   where `<fileSize_inBytes>` is the desired maximum file size, in bytes, to allow to be uploaded to Content Manager.

   IMPORTANT: `maxAllowedContentLength` is measured in bytes, and must be equivalent to the value set for `maxRequestLength`.

   Example after update: set the maximum file size to 15 MB, which is 15728640 bytes.

       <system.webserver>

         <security>
           <requestFiltering>
             <requestLimits maxAllowedContentLength="15728640" />
           </requestFiltering>
         </security>

       ...

5. Save the file.

6. Repeat on any additional Content Manager application hosts.

## Configure dataset rescanning (optional)

When a rescan (update) is triggered for a Content Manager repository, OpenText Core Data Discovery & Risk Insights ignores metadata changes when determining if a file has changed. This lets you rescan a repository that previously completed with errors to identify changes to a file itself. If you prefer to scan and process metadata changes in addition to Content Manager file changes, you must update the configuration to disable the option to ignore metadata changes.

CAUTION: If you disable the option and include metadata changes, the amount of time to rescan a repository that previously completed with errors can significantly increase.

To include metadata changes when rescanning a Content Manager repository (disable the option)

1. On an agent host in the agent cluster assigned to the Content Manager dataset, open the agent Administration UI.

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

2. In the navigation pane, click Advanced Settings.

3. In the Category list, click Content Manager Processor.

4. Locate the Ignore Metadata Changes on Rescans option. This option is enabled () by default.

   Click the toggle to disable ().

5. Click Save.

6. Repeat on each agent host in the agent cluster assigned to the Content Manager dataset.

IMPORTANT: To enable this configuration and again skip metadata changes during a rescan, re-enable () the option on all agent hosts in the agent cluster assigned to the Content Manager dataset.

## Configure web proxy settings (optional)

The Content Manager processor 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.

To configure the web proxy for the Content Manager processor

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 pane, click Advanced Settings.

3. In the Category list, click Content Manager 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.

Copyright 2019-2026 Open Text
Version 26.2.0 | Last updated April 2026
Connect
Marketplace
Learn
Support portal
Documentation
Contact
Submit or view service request