Oracle Knowledge Connector Deployment Overview

The following procedure outlines the steps needed to deploy the Oracle Knowledge connector. The steps indicate the order in which you must perform configuration tasks on both the Oracle Knowledge and Coveo servers.

To deploy the Oracle Knowledge connector

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

2. On the Oracle Knowledge instance, create a Knowledge Administrator user to be used as a crawling account (see Create a Knowledge Administrator).

3. On the machine hosting Oracle Knowledge, copy the IQServiceClientCS.dll file located in the MSFT folder.

   Example: C:\Oracle\Knowledge\IM\InfoManager\clientLibrary\MSFT\Release

4. On the machine hosting CES, paste the IQServiceClientCS.dll file in the Bin folder of CES.

   Example: C:\Program Files\Coveo Enterprise Search 7\Bin

5. On the Coveo server:

   1. Create a user identity.

      The connector needs an account that has at least read access to all item types and security permissions of the Oracle Knowledge instance. Create a CES user identity that must contain the credentials (username and password) of a console user with one or more security roles (custom or built-in) allowing him to view all content and permissions of the Information Manager repository you want to index (see Adding a User Identity).

   2. (Optional) Create security providers

      When you want to index Oracle Knowledge permissions, you must create two security providers to get Oracle Knowledge item permissions and resolve and expand groups.

      In Oracle Knowledge, users are identified by their email addresses. Consequently, permissions returned by the Oracle Knowledge security provider for each item are email addresses. The Oracle Knowledge security provider then requires another security provider to uniquely identify users from their email addresses.

      1. Start by selecting or creating an Email or an Active Directory security provider that the Oracle Knowledge security provider will use to resolve and expand groups. The security provider type to use depends on how users are authenticated when they access the search interface:

         • When authenticated with their email address, use an Email security provider (see Configuring an Email Security Provider).

         • When authenticated with an Active Directory account, use an Active Directory security provider (see Configuring an Active Directory Security Provider).

           Notes:

           • CES comes with an Active Directory security provider that you can configure to connect to the default domain. When your environment contains more than one domain, you can select an Active Directory security provider that you created for other domains.

           • An Active Directory security provider is appropriate only when the User Principal Name (UPN) matches the email address for all users.

         Note: You may require to also use a REGEX Transform Member Name security provider in between the two other security providers to map member types. Contact Coveo Support for assistance.

      2. Then create an Oracle Knowledge security provider that the connector uses to resolve indexed permissions (see Configuring an Oracle Knowledge Security Provider).

   3. Create an Oracle Knowledge field set.

      It is recommended to import the out-of-the-box Oracle Knowledge field set ([CES_Path]\Bin\Coveo.CES.CustomCrawlers.OracleKnowledge.FieldSet.xml to be able to easily add Oracle Knowledge specific facets to your Coveo search interfaces (see Exporting and Importing a Field Set) .

   4. Configure and index the Oracle Knowledge source.

      The Coveo connector needs to know details about your Oracle Knowledge instance to be able to index its content (see Configuring and Indexing an Oracle Knowledge Source).