Oracle UCM Connector Deployment Overview

The following procedure outlines the steps needed to deploy the Oracle UCM connector. The steps indicate the order in which you must perform key CES configurations. When needed, the step refers to a detailed procedure.

1. Validate that your environment meets the requirements (see Oracle UCM Connector Requirements).

2. On your Oracle UCM server:

   1. Allow access for the Coveo connector to the Oracle UCM server.

      You must configure the Oracle UCM server to grant direct access from the Coveo server (see Configuring Oracle UCM to Allow Access from the Coveo Server).

   2. Create a dedicated crawling user on the Oracle UCM server.

      You must create a user with the same roles as the legacy sysadmin user that the crawler will use to access your Oracle UCM content (see Creating an Oracle UCM Crawling Account).

3. On your Coveo server:

   1. Configure the user identity.

      The Coveo connector needs to know the credentials of the Oracle UCM crawling account that you created (see Adding a User Identity).

   2. Configure the security provider.

      The Coveo connector needs to resolve mappings between users and groups from the Oracle UCM system and Microsoft Active Directory (see Configuring an Oracle UCM Security Provider).

   3. Configure and index the Oracle UCM source.

      The Coveo connector needs to know details about the Oracle UCM system to be able to index its content (see Configuring and Indexing an Oracle UCM Source).

   4. Optionally, create and use a custom mapping file.

      Create a custom mapping file only when you want to modify the default mapping of metadata retrieved from Oracle UCM documents (see About the Oracle UCM Mapping File).

What's Next?

Review the connector requirements (see Oracle UCM Connector Requirements).