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 Fusion.
Requirements in Extended ECM
-
To ensure appropriate presentation of items originating from Extended ECM, review the regions definition file,
LLFieldDefinitions.txt
file.The
TimeStamp
regionOTObjectUpdateTime
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 aDROP
orREMOVE
statement.NOTE: If your Extended 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 Fusion. To resolve this, re-index the old data in Extended ECM.
Requirements when defining sources and datasets in Fusion
-
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 Fusion 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 Fusion 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.