Add/Edit a Source - Panel
- Amazon S3 Source
- Box (Personal) Source
- Box Business V2 Source
- Box Business Legacy Source
- Confluence Cloud Source
- Confluence Legacy Source
- Confluence Self-Hosted Source
- Database Source
- Dropbox (Personal) Source
- Dropbox Business Source
- Exchange Enterprise Source
- Exchange Online (Personal) Source
- File System Source
- Generic REST API Source
- Gmail for Work Source
- Gmail (Personal) Source
- Google Drive (Personal) Source
- Google Drive for Work Source
- Jira Software Cloud Source
- Jira Software Self-Hosted Source
- Jive Cloud Source
- Jive Server Source
- Lithium Source
- Microsoft Dynamics Source
- OneDrive for Business Source
- Push Source
- RSS Source
- Salesforce Source
- SharePoint Online Source
- SharePoint Online Legacy Source
- SharePoint Server Source
- Sitecore Source
- Sitemap Source
- Twitter Source
- Web Source
- YouTube Source
- Zendesk Source
Add/Edit a Jive Server Source - Panel
By default, your Jive Server source starts a refresh every 15 minutes to index Jive Server file changes (additions, modifications, or deletions).
While most of the parameters can be configured through the Add/Edit a Jive Server Source panel, other parameters, such as rarely used parameters or new parameters that are not yet editable through the user interface, can only be changed or added in the JSON configuration (see Edit a Source JSON Configuration: [SourceName] - Panel, Add a Hidden Source Parameter, and Jive Source JSON Modification).
If you have issues with file download requests timing out too early for larger files, you may want to add a
RequestTimeouthidden parameter in the source JSON.
Source refresh limitations that require you to configure source rescans or rebuilds (see Edit a Source Schedule: [SourceName] - Panel):
Due to a Jive REST API limitation, only changes to the first level of comments on items and replies on discussions are captured by a refresh, meaning that comments on comments and replies on replies cannot currently be retrieved.
Since the Jive REST API does not provide the list of deleted File items, a refresh does not take the deletion of File items into account.
Source Features Summary
|Searchable content types||
Rescan or rebuild needed to retrieve (due to Jive REST API limitations):
The Coveo plugin is required to:
Requires the Coveo plugin.
Supported Jive Version
The source supports Jive 9.
Deprecated support versions: 6, 7, and 8 (see Repository Version Support Deprecation)
Jive Administrator Account
When you want to include Jive permissions, you must create a specific Jive administrator account with Full Access permissions that is only used for the source.
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.
At least, the following ports must be opened:
443: standard port for secured internet connections (HTTPS)
8080: Jive default port
The action that you must perform before configuring source parameters:
Add or Edit a Jive Server Source
Ensure your Jive server meets the source requirements (see Requirements).
If not already in the Add/Edit a Jive Server Source panel, go to the panel:
- To add a source, in the main menu, under Content, select Sources > Add Source button > Jive > Jive Server.
- To edit a source, in the main menu, under Content, select Sources > source row > Edit in the Action bar.
In the Configuration tab:
Under Supported Versions, check if your version of Jive is supported.
Under Content Update and Security Requirement:
If you are using a supported Jive version, download the Coveo plugin for Jive by clicking Download Plugin and then install the plugin on your Jive server (see Installing the Coveo Plugin for Jive).
If you use an unsupported Jive version (6.2 to 7.x), you have to download the following plugin:
If you want to include permissions and perform source refreshes, you must install the Coveo plugin for Jive on your Jive server (see Source Features Summary).
Enter appropriate values for available parameters:
A descriptive name for your source under 255 characters (not already in use for another source in this organization).
The web address of the Jive instance that you want to index.
(Optional) The URL of a Jive Community where the crawling begins.
Only communities (also known as spaces) under the starting community are indexed.
By default, the root community (also known as root space) is used.
Content outside the starting community can be indexed if you select the following options in the Content to include section (see Content to include section):
Include social groups (also known as groups)
Include system blogs
Select by whom the Jive Community content is searchable (see Source Permission Types):
Private - Only you, the source creator
Shared - Everyone
Secured - Only users authenticated in the search interface can see the source items for which they have read permission.
Allow anonymous access
Select to map the Everyone group in Jive to the Everyone group of the Email identity security provider.
When selected, all users (authenticated and anonymous) can see the Jive content allowed to Jive Everyone in search results.
The Jive account with Full Access permissions to the Jive instance.
The corresponding password.
Content to include section
Consider changing the default value of the settings in this section when you want to fine-tune how your Jive instance is crawled.
By default, all Jive content is indexed, regardless of its status (except private users content under the Jive Community domain).
Turn off one or more of the following settings when you want to prevent specific Jive places from being included in the index:
Communities (also known as spaces)
Social groups (also known as groups)
Optionally turn on the following option:
Includes user profiles, personal blogs, and private items (items and discussions). Private messages (also known as direct messages) are not included.
Since Coveo cannot index content permissions, it is STRONGLY recommended NOT to enable the Include people setting. Private information could then be disclosed, even if private messages are not indexed. Also, turning on this setting significantly increases the crawling time. If you need to index people content, you should create a separate source and only turn on the Include people setting.
Published items only
Includes Jive items for which the status is
Published. Items with other statuses (such as
Unknown) are not included.
Source refresh catches Jive item status changes and respects the configuration of this parameter.
In the Configuration Access tab, determine whether each group and API key can view or edit the source configuration. In the Access Level column, select View or Edit for each available group. On the left-hand side of the tab, if available, click Groups or API Keys to switch lists.
If you remove the Edit access level from all the groups of which you are a member, you will not be able to edit the source again after saving. Only administrators and members of other groups that have Edit access on this resource will be able to do so. To keep your ability to edit this resource, you must grant the Edit access level to at least one of your groups.
Optionally, consider editing or adding mappings (see Edit the Mappings of a Source: [SourceName]).
You can only manage mapping rules once you build the source (see Add/Edit a Source - Panel).
Finish adding/editing your source:
Click Add Source/Save when you want to save your source configuration changes without starting a build/rebuild, such as when you know you want to do other changes soon.
Click Add and Build Source/Save and Rebuild Source when you are done editing the source and want to make changes effective.
Back in the Coveo Cloud administration console Sources page, you can review the progress of your Jive source addition or modification (see Sources - Page).
Once the source is built or rebuilt, you can review its content in the content browser (see Content Browser - Page).