Adding a Jive Source

You can add the content of a Jive 9 community to your Coveo organization. The source can be private, shared or secured (see Source Permission Types).

The Coveo Jive Plugin available for on-premises Jive instances allows the Coveo Platform to manage permissions associated with each Jive items so that users only see Jive content in Coveo search results to which they have normally access in Jive itself.

Source Features Summary

Features Supported Additional information
Jive version 9
Searchable content types
  • Communities (also known as Spaces), social groups (also known as groups), projects, people and their profile, direct messages (requires Coveo plugin), items (private and public), discussions (private and public), blog posts (for spaces, projects, users, groups and system blogs), announcements, polls, comments (for items, blog posts, and polls), attachments (for items, blog posts, and discussions), ideas (private and public), and videos (private and public).
  • Support phrase substitutions (requires Coveo plugin), tags, and categories.
Content update Incremental refresh

Full refresh or rebuild needed to retrieve (due to Jive REST API limitations):

  • Comments on comments and replies on replies

  • Deleted file items.

The Coveo plugin is required to:

  • Remove recently deleted Jive items

  • Properly refresh discussions

Full refresh
Rebuild
Permission types Secured

Requires the Coveo plugin.

Private
Shared

Add a Jive Source

To edit a Jive source, see Edit the Source Configuration to Re-index its Content or Re-authorize the Access, and then follow the steps below, starting from step 6.

  1. Ensure your environment meets the following requirement:

    • Jive 9

      Deprecated support versions: 6, 7, and 8 (see Repository Version Support Deprecation)

    • Jive server accessible to Coveo Cloud

      When the access to communication ports between Coveo Cloud and the Jive server is restricted, the appropriate port(s) must be opened in the network infrastructure such as in firewalls to allow Coveo Cloud to access the content.

  2. On your Jive server:

    1. When you want, among other things, Jive item permissions and phrase substitutions to be supported, you must download and install the Coveo Jive Plugin (see Installing the Coveo Plugin on Your Jive Server).

      If you use an unsupported Jive version (6.2 to 7.x), you have to download the following plugin:

      Coveo plugin for Jive 6.2 to 7.0

    2. Select or create a user that the source will use to retrieve your Jive content.

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

  3. If not already done, log in to your Coveo organization.

  4. In the navigation bar on the left, under Search Content, select Sources, and then click Add Source.

  5. On the Add Source page, click Jive.

    When you create a source, you become the owner of the source.

  6. In the Add/Edit a Jive Source dialog box:

    Admin-AddJiveSource

    1. In the Source Name box, enter a descriptive name of your choice for the source.

    2. In the URL box, enter the web address of the Jive Community that you want to index.

    3. In the security drop-down menu, select if you want your Jive content to be Secured, Private, or Shared (see Source Permission Types).

      If you select Shared, but didn’t install the Coveo Jive Plugin or properly configured previous steps, in search results, users can see all the items that the indexing account can access.

    4. Enable the Jive Instance Allow Anonymous Access toggle when you want all users (authenticated and anonymous) to see the Jive content allowed to Jive Everyone in search results.

    5. In the Username and Password boxes, enter the credentials of the dedicated indexing account with Full Access permissions you selected or created before in step 2.

    6. Click Content To Include to show more parameters and select the type of Jive content to index.

      • We recommend that you create a separate source for Users content using parameters suggested in the following table:

        Type of Jive content to index Main source Users content source
        Communities
        Projects
        Social Groups
        System Blogs
        Users content
      • By default, all Jive content (regardless of its status) under the Jive Community domain is indexed.

      • By selecting Users content, the source indexes the user profiles, personal blogs, and private items (messages, items and discussions).

    7. (Optional) When you use phrase substitutions in your Jive community (see the Jive item Substituting Phrases in the UI), click Phrase Substitutions to show more parameters and configure the needed parameters. Otherwise, leave them blank.

      1. In the Locale box, enter the phrase substitution locale that the source should use. The default locale is default, meaning that the actual machine locale is used.

        Enter the locale in any of the following three formats:

        • Language only (e.g., en)

        • Language and country (e.g., en_US)

        • Language, country, and variant (e.g., en_US_NY)

      2. In the Theme box, enter the phrase substitution theme that the source should use. The default theme is custom.

    8. Click Start Indexing (or Refresh Index when editing the source).

  7. Back on the Sources page, you can review the progress of your Jive source addition (see Review the State of Sources Available to You).

What’s Next?

  • When you include Jive users content, schedule source incremental and full refresh to maintain your source content up to date (see Modify a Source Schedule).

    Permission changes in Jive for Users content type can’t be updated in the index with incremental refresh like for other types of Jive content. When you want to index Users content, keep permissions as up-to-date as possible in the index, and optimize the load to your Jive server, we recommend that you create a separate source for Users content using the following source refresh schedules:

    Source Options Main source Users content source
    Source update Retrieve New Content (Every 5 minutes)
    Rescan all content for changes (Every Sunday)
    Rescan all content for changes (Every day)
  • Ensure source item titles are correctly set in search results by reviewing the title selection sequence (see Decide How Item Titles Are Determined in Search Result Lists).

What's Next for Me?