Jive Connector Deployment Overview

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

To deploy the Jive connector

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

2. On the Jive server:

   1. Choose a Jive crawling account

      You must choose which Jive account the Coveo connector uses to crawl the content of your Jive communities (see Creating a Jive Crawling Account).

   2. Optionally install the Coveo for Jive plugin

      Install the Coveo plugin used by the connector on your Jive server. The plugin is optional but enables several connector features such as allowing to index permissions (see Installing the Coveo Plugin on Your Jive Server).

      Note: Because you cannot install the Coveo for Jive plugin in Jive cloud, Coveo cannot index permissions for this content.

      Tip: In rare cases where the Jive 6+ browse index is not synchronized with the master data, the Jive API may not return all documents to the Coveo connector. To prevent missing some Jive documents in your Coveo index, ensure that your Jive indexes are up to date (from the Jive Admin Console System > Settings > Browse > Re-synchronize browse index).

3. On the Coveo server:

   1. Create a user identity

      You must create a user identity to hold the credentials of the Jive crawling account that you selected (see Adding a User Identity).

   2. CES 7.0.7711+ (June 2015) Optionally create an email security provider

      When the primary email is defined for each of your users in Jive 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 Jive users to their email (see Configuring an Email Security Provider).

   3. Optionally create a Jive security provider

      When you installed the Coveo plugin and want to index Jive permissions, you must create a security provider that the connector uses to resolve indexed permissions into a list of Jive users and groups (see Configuring a Jive Security Provider).

   4. CES 7.0.8541+ (September 2016) Create a Jive field set

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

   5. Create and index a source

      You must create a source describing the Jive community to index (see Configuring and Indexing a Jive Source).

4. Troubleshooting

   1. Review known issues (see Troubleshooting Jive Connector Issues).

   2. Consider modifying some hidden source parameters to try resolving other issues (see Modifying Hidden Jive Source Parameters).

5. Allow Jive users to be authenticated in a Coveo search interface

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