Jive Software Jive Connector

Installation and Configuration

Configuration of Mindbreeze

Configuration of index and crawler

Click on the “Indices” tab and then click the “Add new index” icon to create a new index.

Enter the index path, for example, “C:\Index”. If necessary, adjust the Display Name of the index service and the associated filter service.

The Option “Use ACL References” has to be activated.

Add a new data source with the symbol “Add new custom source” on the lower right.

If not already selected, select “Jive Software Jive” with the “Category” button.

Using the setting “Crawler Interval” you can configure the amount of time that should elapse between two indexing runs.

Web page

In the field Crawling Root, you can specify a URL where a Jive sitemap is accessible. If the Mindbreeze sitemap generator add-on is installed on your Jive server and a sitemap is generated, the URL <Jive URL>/rpc/rest/mindbreeze/sitemap?jobid=full should be here.

In the field “URL regex” you can define a regular expression, which sets a pattern for the links that should be indexed.

If certain URLs are excluded from the crawl, they can be configured using a regular expression in “URL Exclude Pattern”.

If the DNS resolution of certain Web servers doesn’t work due to network-related reasons, you can specify the Ips using the “Additional Hosts File”.

If you want to add specific HTTP headers (for example, Accept-Language), you can adjust this using “Accept headers”.

With the “Use Stream Parser” option, a stream parser for processing the sitemaps is used. This option is suitable for sitemaps with a lot of URLs.

The “Max Retries” option determines how often the connector tries to download a document when temporary errors (e.g. socket timeouts) occur. The default value is 0. (No further download attempts). If you are crawling across an unstable network (that causes timeouts), this value should be increased to 10, for example. If the timeouts are caused by an overloaded data source, the value should be left at 0 so that the data source is not loaded even further.

The “Retry Delay Seconds” option determines the waiting time (in seconds) between download attempts (see "Max Retries"). The default value is 1.

Resource parameters

In this section (available only when “Advanced Settings” is selected) the crawl speed can be adjusted.

With the number of crawler threads (“Number Of Crawler Threads”) you can define how many threads should simultaneously pick sites from the web server.

“Request Interval” defines the number of milliseconds that the crawler (crawler thread) should wait between the individual requests. However, a “crawl-delay” robots instruction is always taken into consideration and overrides this value.

Proxy

In the “Proxy” section you can enter a proxy server if your infrastructure requires it. Enter the computer name and the port of the proxy server in “Proxy host” and “Proxy Port”.

The Jive Connector can also log in to the proxy using HTTP-BASIC. Enter the user into the “Proxy User” and the corresponding password in “Proxy Password” if the connections should be made through a proxy with authentication.

Jive login

Basic Authentication

In the section “Basic access authentication”, a “credential” can be selected, which is used in the basic authentication for HTTP requests. A credential of the type “Username/Password” should be entered here.

This credential can be added and configured in the “Network”-tab in the section “Credentials”.

Form Based Login

If the Jive sitemap is accessible with HTTP form authentication, the login parameters in section “Form Based Login” can be configured as follows:

• Login URL: the Jive URL to which the login form is to be sent: for instance,
• Form Elements: An element with the name “username” must be added here. The value
• should be the user who is authorized to download the sitemap.
• Form Password Elements: An element with the name “password” must be added here. The value should be the password for the previously specified user.
• In section “Jive URL”, the base URL of the Jive server must be specified.
• 

Access check rules

You can also define so-called access rules, which consist of the following options:

• “Access Check Principal,” the user names can be in the format “username@domain," “domain\username,” or “distinguished name.” The group names can only be in the distinguished name format. In addition, a reference to a capture group in the selection pattern can be used here.
• “Access Check Action,” grant or deny.
• “Metadata Key for Selection,” a metadata name; can be empty (all documents are selected)
• “Selection Pattern,” a regular expression; can be empty (all documents are selected).

Jive URL

Integrating Kaltura videos

The Jive connector also provides the ability to index Kaltura videos embedded in Jive. The important thing here is that the videos are integrated in Jive as HTML iframe (see also Embedding Kaltura Media Players in Your Site). The embedded videos in Mindbreeze InSpire inherit the authorizations of the Jive page in which they were embedded. Please also note that multiple embedded (i.e. identical) videos are found multiple times in a search.

The following options must be configured:

Jive Principal Resolution

Open the “Indices” tab in the Mindbreeze configuration and add a Caching Jive Principal Resolution Service.

Specify the “Jive Server URL.” If access for Jive is allowed for unregistered users, please enable the option "Jive Guest Access enabled." The "Groups Containing All Users" option allows groups to be defined so that all users are treated as if they were members of these groups. In order to improve performance select “Keep Groups Containing All Users in Memory”.

1. The necessary credentials to access the "Jive Server URL" have to be configured in the "Network" tab and mapped to the "Jive Server URL" endpoint.

Specify the directory path for the cache in the “Database Directory Path“ field and change the “Cache In Memory Items Size” if necessary, depending on the available memory capacity of the JVM. In the “Cache Update Interval“ field, specify the time (in minutes) that should elapse before the cache is updated. This time interval is ignored the first time the service is started. The next time the service is started, this time will be taken into account. The settings “Health Check Interval“, “Health Check max. Retries On Failure“ and “Heath Check Request Timeout“ allow this service to be restarted if, for instance, there are persistent connection problems.

The service will be available at the specified “Webservice Port”. If multiple principal resolution services are configured, make sure that the "Web service port" parameters are different and that the configured ports are available.

The option "Lowercase Principals" allows all principals from the cache to be returned in lower case.

If users cannot be resolved for a search query, a request will be sent directly to Jive if the option "Suppress JIVE Service Calls" is not enabled. However, for performance reasons, it is recommended that you enable this option so that no live requests are made to Jive.

To test the caching principal resolution service, you can use the Principal Resolution Service REST API.

If the provided usernames after authentication in the client service do not correspond to the usernames inside the JIVE groups and there is a cache that provides these usernames as aliasnames, then it is possible to use that cache as a “Parent Principals Cache”. The parent cache settings should be configured in “Parent Principals Cache Setting” section. Select „Use Parent Principals Cache Service” and provide the port „Parent Principals Cache Service Port“. The „Parent Cache Principals Include Patterns“ and the „Parent Cache Principals Exclude Patterns“ can be used to filter the resolved usernames. If the resolved usernames from parent cache are not directly members of JIVE groups but they are aliasnames, then the „Parent Principals Are Unique IDs“ checkbox must not be selected.