Extended ECM connection

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

Requirements in Extended ECM

• To ensure appropriate presentation of items originating from Extended ECM, review the regions definition file, LLFieldDefinitions.txt file.

  The TimeStamp region OTObjectUpdateTime is enabled by default and not defined in the definition file, unless you have made an explicit change. If is present in the file, it must not be explicitly disabled with a DROP or REMOVE statement.

  NOTE: If yourExtended ECM environment includes old data sets and have not been re-indexed (by Extended ECM) since this region was introduced, that data may not be processed by OpenText Core Data Discovery & Risk Insights. To resolve this, re-index the old data in Extended ECM.

Requirements when defining sources and datasets in OpenText Core Data Discovery & Risk Insights

• You will define a user to access the Extended ECM 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 Extended ECM host URL using a secure connection (HTTPS). A secure connection is always recommended, but not required for non-cloud agent clusters.

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

  • You can create only one dataset per Extended ECM source.

  • SmartScan is not supported.

• Documents sent to Extended ECM destinations are saved to the Enterprise Workspace.

Configure web proxy settings (optional)

The Extended ECM 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.