Versions Compared

Old Version 5

changes.mady.by.user Danny Herrera

Saved on

compared with

New Version Current

changes.mady.by.user Ricardo Fonseca

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The JIVE connector will crawl content from any JIVE Community with an enabled REST API v3. The connector will retrieve documents stored in spaces, groups, projects and blogs and any sub-folders contained in it.


Panel
titleOn this page

Table of Contents

Features

Some of the features of the JIVE connector include:

  • Performs incremental crawling (so that only new/updated documents are indexed) and push incremental crawl (it only fetches the most important updates from the community).
  • Metadata extraction.
  • Is search engine independent.
  • Runs from any machine with access to the given community.
  • Fetches access control lists (ACLs) for JIVE document-level security (For this feature you need to install the Jive Security Mapper Plugin on your Community).
  • Filter the crawled documents by paths (including file names) using regex patterns.
  • Supports Windows/Linux/MacOS file systems.


Content Retrieved

The JIVE connector retrieves several types of documents, listed below are the inclusions and exclusions of these documents.

Include

  • Jive Spaces
  • Jive Groups
  • Jive Blogs
  • Jive Documents
  • Users
  • Discussions
  • Announcements
  • Files/Attachments


Limitations 

Due to API limitations, JIVE connector has the following limitations:

    • The Creation Date Filter is only available in Jive version 8 or greater.
    • Entitlements API does not support "User Overrides". In this case, ACLs will not be retrieved for Jive version 8 or greater.
    Without Places support
    • In large crawls, the Jive API produces server slowdowns and crashes which will prevent the crawl from continuing. The Jive Connector has two feature to help with these scenarios: a “Progressive Retries” and the “Use Creation Date Filter”.
    • Under some circumstances page corruptions happens in the Jive database which produces malformed JSON responses. The connector cannot crawl the data in this particular scenario.