OpenText Content Server Connector Deployment Overview

The following procedure outlines the steps needed to deploy the OpenText Content Server (OTCS) connector. The steps indicate the order in which you must perform configuration tasks on both the OTCS and Coveo servers.

To deploy the OpenText Content Server connector

1. Validate that your environment meets the requirements (see OpenText Content Server Connector Requirements).

2. In OpenText Content Server:

   1. Enable the Web Services.

      The Coveo connector requires OTCS Web services to operate. You must ensure that these Web services are available (see Enabling the OpenText Content Server Web Services).

   2. Select or create the crawling account.

      The Coveo connector needs an OTCS account with which it can fully crawl the OTCS content (see Setting Up an OpenText Content Server Crawling Account).

3. In the Coveo Administration Tool:

   1. Configure a user identity.

      The Coveo connector needs to know the OTCS account that you previously selected or created. You must create a CES user identity to use this account. Use either the Screen Name or the Email Address of the dedicated OTCS account (see Adding a User Identity. You will later assign this user identity to the security provider and the source used by the connector to crawl the OTCS content.

   2. Configure a security provider.

      The Coveo connector needs a security provider to be able to get the permissions for each indexed OTCS item, and therefore fully support the OTCS security model (see Configuring an OpenText Content Server Security Provider).

   3. Configure and index the OpenText Content Server source.

      The Coveo connector needs to know details about OTCS to be able to index its content (see Configuring and Indexing an OpenText Content Server Source).

4. Enrich your OTCS indexed content

   1. Optionally, create and use a mapping file to fine-tune indexed content

      Consider customizing the connector mapping file to fine-tune the indexed content or to index other entities in your OTCS (see Creating an OpenText Content Server Connector Mapping File).

   2. Optionally, modify hidden source parameters.

      Once your OTCS source is up and running, if you encounter issues, consider modifying some hidden source parameters to try resolving the issues (see Modifying Hidden OpenText Content Server Source Parameters).

5. Customize your search interfaces with OTCS content

   1. Add OTCS facets to your search interfaces

      You can create facets using fields such as the OTCSFileType metadata to allow users to easily filter OTCS documents (see Managing Built-in Facets and Related Results Appearing in a .NET Search Interface).

   2. Allow OTCS users to be authenticated in a Coveo search interface

      When your OTCS is not integrated with Active Directory, your end-users need to sign in to OTCS in a Coveo search interface to be able to see search results from OTCS. In this case, you need to add the OTCS security provider to your search interface to allow end-user to sign in to OTCS (see Adding Security Providers to a .NET Search Interface).