Product DocsMenu

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.

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

  2. On the Jive server:

    1. Choose a crawling account

      You must choose which Jive account the Coveo connector uses to crawl the content of your Jive communities. The account must have read access to the whole Jive content that you want to index. You can use an administrator account such as SysAdmin but the best practice is to create a dedicated user with full read permissions.

    2. Enable the web services

      You must ensure that the native Jive web services used by the Coveo connector are enabled on your Jive server (see Enabling the Jive Web Services).

    3. Upload the Coveo plugin

      You must upload to your Jive server the Coveo plugin used by the connector (see Uploading the Coveo Plugin on your Jive Server).

    4. Configure authentication

      With SBS 3 and Clearspace 2.5 installations only, you must configure your SBS/Clearspace server to allow .NET web service authentication (see Configuring Authentication with Jive Web Services Using .NET).

  3. On the Coveo server:

    1. Create a user identity

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

    2. Create a security provider

      You must create security provider that the connector uses to map Jive users/groups to Microsoft Active Directory users/groups (see Configuring a Jive Security Provider).

    3. Create and index a source

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

    4. Add support for CA SiteMinder

      When your Jive server uses CA SiteMinder for user authentication, you need to add parameters to the connector (see Adding CA SiteMinder Parameters to the Jive Connector).

  4. Troubleshooting

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

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