Starting with Discovery Center version 4.11, we have released a new OpenText Content Server connector that offers additional features and improved performance over its predecessor. From release 4.18 onwards this new connector is in General Availability and the previous Opentext Connector is no longer available for use in the Discovery Center application. For a full list of features, see our Connectors Compatibility Matrix within the Discovery Center User Guide.
Setup the Connector in Discovery Center
Licensing
This connector must be licensed in order to use it.
Please contact ActiveNav support for an updated license if you are interested in upgrading your Opentext Connector.
Credentials
Once the connector is activated, you will need to configure credentials within the System Settings > Credential management section of the application. The credentials required are in a Username and Password format and the account chosen should have administrative permissions in the target OpenText Content Server implementation.
Network Map
Enterprise Workspace locations
You can set the location within your network map. The 'Enterprise Workspace' volume is the default location for content within OpenText Content Server and is supported with this connector in all versions of Discovery Center from 4.11 onwards.
As with other connectors a specific URI format is required within the Discovery Center application to identify locations within OpenText Content Server. In this case the requirement for the URI scheme to be: 'contentserver://', so for example, to target the 'Enterprise Workspace' volume you will need to format your start location similar to: 'contentserver://opentexterverinstance/Enterprise Workspace'
Non Enterprise Workspace locations
From Discovery Center version 4.18 non 'Enterpise Workspace' locations within OpenText Content Server, e.g. 'Personal Workspaces' or other Volume Types, can also be targeted. The format of the path to use for these locations in Discovery Center must include the numerical ID of the location being accessed, as derived fron the internal ID of the location within OpenText Content Server. This is referred to as the Object ID in OpenText Content Server and the IDs specific to each user's 'Personal Workspace' and the different Volume Types within the repository may differ between implementations, so the OpenText Content Server documentation should be referred to as necessary to determine the correct paths to use. In many cases though the correct ID to use in the path can be determined from the URL used within the OpenText Content Server UI. For instance, in this instance when selecting the 'Open' option from the 'Admin' user's 'Personal Workspace' the URL navigated to indicates that the ID for the objext is 2004. The correct path to use in the Discovery Center application to target the Admin user's Personal Workspace would therefore be: 'contentserver://opentexterverinstance/2004'
Advanced Configuration
The OpenText Content Server connector is installed in the Discovery Center application with a number of default configuration options set. Depending on the implementation of the OpenText Content Server instance being targeted and the type of data within it some of these advanced configuration options may need to be changed for the Discovery Center application to work optimally. These changes require updates to application configuration files within the installation directory of the Discovery Center application on the application server of the deployed environment and care should be taken when making any changes to these files to ensure the application continues to function correctly. The following details what changes may be required in different circumstances, but in all cases please contact ActiveNav Support for assistance before performing any updates.
- Default scheme - It is assumed the OpenText Content Server instance is accessed over an HTTPS connection, this can be changed to HTTP if required
- Target Container Types - By default Discovery Center recognises standard Folder, email Folder and Physical Item (Container) types as containers within OpenText Content Server. If additional types are required to be identified as containers within the Discovery Center application their individual OpenText Content Server Type IDs must be included in configuration settings.
- Target File Types - By default Discovery Center recognises standard Document and email types as files within OpenText Content Server. If additional types are required to be identified as files within the Discovery Center application their individual OpenText Content Server Type IDs must be included in configuration settings.
- External Dates - OpenText Content Server records each of the Created and Modified dates of files in two separate fields - one holds the internal dates relating to the dates the files were added or updated in OpenText Content Server itself, and should always be populated, while the other relates to the original created and modified dates of the file from outside of OpenText Content Server, and may not have data in all cases. By default Discovery Center will retrieve the date properties from files from the internal properties, but the external dates can be targeted instead by changing this configuration setting.
- Path Map - The Discovery Center application connects to OpenText Content Server through an authenticated API. By default it is assumed that the OpenText Content Server instance being targeted is installed on a standard port with the default API URL being https://opentexterverinstance/OTCS/cs.exe/api. If this is not the case then the Path Map configuration setting can be used to indicate what the default API URL should be instead.
Metadata Configuration
With the release of version 4.18 of Discovery Center there is additional support for both the reading of advanced medatada properties through the new connector during a skim index operation, and the writing of values to specific metadata fields as part of actions within the Discovery Center application. There is further detail around the configuration required in the apllication for these read and write operations in the Discovery Center User Guide and HTML Help pages relating to indexing and actions, but for specific information around considerations for reading file metadata from OpenText Content Server in particular, see the Knowledge Base Article at: https://events.activenav.com/knowledge/hc/en-gb/articles/9632704976285-custom-metadata-retrieval-in-opentext-content-server.