Product DocsMenu

Alfresco One Connector Deployment Overview

The following procedure outlines the steps needed to deploy the Alfresco One connector. The steps indicate the order in which you must perform configuration tasks on both the CES and Alfresco One systems.

  1. Validate that your environment meets the requirements (see Alfresco One Connector Requirements).

  2. In the Alfresco One system:

    1. Select or create the crawling account.

      The connector needs an Alfresco One account with which it can crawl all the Alfresco One content that you want to index (see Selecting an Alfresco One Full Read Account).

    2. Enable auditing of content

      Note: When auditing is not enabled, incremental refreshes are performed as full refreshes.

      1. With a text editor, open the Alfresco One global properties file located in the Alfresco One folder.

        Example: C:\Program Files\Alfresco\tomcat\shared\classes\alfresco-global.properties

      2. Add one of the following property:

        • audit.enabled=true

          to enable audit in general.

        • audit.cmischangelog.enabled=true

          to implement the change log feature on your CMIS server.

          Note: The logs contain all create, read, update, and delete operations that users performed on objects in the Alfresco One repository.

      3. Save the file.

      4. Restart the Alfresco Enterprise service to apply changes.

  3. On the Coveo server, in the Coveo Administration Tool:

    1. Configure the user identity

      You must assign the selected Alfresco One full-read account to a Coveo user identity (see Adding a User Identity) .

    2. Optionally create an Email security provider

      When an email is defined for each of your users in Alfresco and this email is used to authenticate them in your Coveo search interface, you can create an Email security provider to allow you to map your Alfresco users to their email (see Configuring an Email Security Provider).

    3. Create a security provider.

      When you want to index permissions, you must configure a security provider (see Configuring an Alfresco One Security Provider).

    4. Create an Alfresco One field set.

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

    5. Configure and index the Alfresco One source

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

    6. Optionally, modify hidden source parameters

      Once your Alfresco One source is up and running, if you encounter timeout or performance issues, consider modifying some hidden source parameters to try resolving the issues (see Modifying Hidden Alfresco One Source Parameters).

    7. Optionally, customize the mapping file to fine-tune indexed content

      You can customize the connector mapping file to fine-tune the indexed content or to index other default entities in your Alfresco One system (see Creating a Custom Alfresco One Mapping File).

People who viewed this topic also viewed