Home
Home
German Version
Support
Impressum
20.5 Release ►

    Main Navigation

    • Preparation
      • Connectors
      • Initial Startup for G6 appliances (before January 2018)
      • Initial Startup for G7 appliances
      • Setup InSpire G7 primary and Standby Appliances
    • Datasources
      • Configuration - Atlassian Confluence Connector
      • Configuration - Best Bets Connector
      • Configuration - Data Integration Connector
      • Configuration - Documentum Connector
      • Configuration - Dropbox Connector
      • Configuration - Egnyte Connector
      • Configuration - GitHub Connector
      • Configuration - Google Drive Connector
      • Configuration - GSA Adapter Service
      • Configuration - HL7 Connector
      • Configuration - IBM Connections Connector
      • Configuration - IBM Lotus Connector
      • Configuration - Jira Connector
      • Configuration - JiveSoftware Jive Connector
      • Configuration - JVM Launcher Service
      • Configuration - LDAP Connector
      • Configuration - Microsoft Dynamics CRM Connector
      • Configuration - Microsoft Exchange Connector
      • Configuration - Microsoft File Connector (Legacy)
      • Configuration - Microsoft File Connector
      • Configuration - Microsoft SharePoint Connector
      • Configuration - Salesforce Connector
      • Configuration - SAP KMC Connector
      • Configuration - SemanticWeb Connector
      • Configuration - ServiceNow Connector
      • Configuration - SharePoint Online Connector
      • Configuration - Web Connector
      • Data Integration Guide with SQL Database by Example
      • Indexing user-specific properties (Documentum)
      • Installation & Configuration - Atlassian Confluence Sitemap Generator Add-On
      • Installation & Configuration - Caching Principal Resolution Service
      • Installation & Configuration - Jive Sitemap Generator
      • Mindbreeze InSpire Search Apps in Microsoft SharePoint 2010
      • Mindbreeze InSpire Search Apps in Microsoft SharePoint 2013
      • Mindbreeze InSpire Search Apps in Microsoft SharePoint Online
      • Mindbreeze Web Parts for Microsoft SharePoint
      • User Defined Properties (SharePoint 2013 Connector)
    • Configuration
      • CAS_Authentication
      • Cognito JWT Authentification
      • Configuration - Alternative Search Suggestions and Automatic Search Expansion
      • Configuration - Back-End Credentials
      • Configuration - Chinese Tokenization Plugin (Jieba)
      • Configuration - CJK Tokenizer Plugin
      • Configuration - Collected Results
      • Configuration - CSV Metadata Mapping Item Transformation Service
      • Configuration - Entity Recognition
      • Configuration - Exporting Results
      • Configuration - GSA Late Binding Authentication
      • Configuration - Index-Servlets
      • Configuration - Item Property Generator
      • Configuration - Japanese Language Tokenizer
      • Configuration - Kerberos Authentication
      • Configuration - Management Center Menu
      • Configuration - Metadata Enrichment
      • Configuration - Metadata Reference Builder Plugin
      • Configuration - Notifications
      • Configuration - Personalized Relevance
      • Configuration - Plugin Installation
      • Configuration - Principal Validation Plugin
      • Configuration - Profile
      • Configuration - Reporting Query Logs
      • Configuration - Reporting Query Performance Tests
      • Configuration - Request Header Session Authentication
      • Configuration - Vocabularies for Synonyms and Suggest
      • Configuration of Thumbnail Images
      • Cookie-Authentication
      • Documentation - Mindbreeze InSpire
      • Google Search Appliance Migration to Mindbreeze InSpire
      • I18n Item Transformation
      • Installation & Configuration - Outlook Add-In
      • Installation - GSA Base Configuration Package
      • Language detection - LanguageDetector Plugin
      • Mindbreeze Personalization
      • Mindbreeze Prediction Service Text Classification
      • Mindbreeze Property Expression Language
      • Mindbreeze Query Expression Transformation
      • Non-Inverted Metadata Item Transformer
      • SAML-based Authentication
      • Trusted Peer Authentication for Mindbreeze InSpire
      • Using the InSpire Snapshot for Development in a CI_CD Scenario
    • Operations
      • app.telemetry Statistics Regarding Search Queries
      • Configuration Usage Analysis
      • Deletion of Hard Disks
      • Handbook - Backup & Restore
      • Handbook - Command Line Tools
      • Handbook - Distributed Operation (G7)
      • Handbook - Filemanager
      • Handbook - Synchronized Operation (G6)
      • Index Operating Concepts
      • Indexing and Search Logs
      • Inspire Diagnostics and Resource Monitoring
      • InSpire Support Documentation
      • Mindbreeze InSpire SFX Update
      • Provision of app.telemetry Information on G7 Appliances via SNMPv3
      • Restoring to As-Delivered Condition
    • User Manual
      • Cheat Sheet
      • iOS App
      • Keyboard Operation
    • SDK
      • api.v2.alertstrigger Interface Description
      • api.v2.export Interface Description
      • api.v2.personalization Interface Description
      • api.v2.search Interface Description
      • api.v2.suggest Interface Description
      • api.v3.admin.SnapshotService Interface Description
      • Debugging (Eclipse)
      • Developing an API V2 search request response transformer
      • Developing Item Transformation and Post Filter Plugins with the Mindbreeze SDK
      • Development of Insight Apps
      • Java API Interface Description
    • Release Notes
      • Release Notes 20.1 Release - Mindbreeze InSpire
      • Release Notes 20.2 Release - Mindbreeze InSpire
      • Release Notes 20.3 Release - Mindbreeze InSpire
      • Release Notes 20.4 Release - Mindbreeze InSpire
      • Release Notes 20.5 Release - Mindbreeze InSpire
      • Release Notes 2018 Spring - Mindbreeze InSpire
      • Release Notes 2018 Winter - Mindbreeze InSpire
      • Release Notes 2019 Fall - Mindbreeze InSpire
      • Release Notes 2019 Winter - Mindbreeze InSpire
    • Security
      • Known Vulnerablities
    • Product Information
      • Product Information - Mindbreeze InSpire - Standby
      • Product Information - Mindbreeze InSpire
    Home

    Path

    Jive Software Jive Connector

    Installation and Configuration

    Copyright ©

    Mindbreeze GmbH, A-4020 Linz, 2020.

    All rights reserved. All hardware and software names are brand names and/or trademarks of their respective manufacturers.

    These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes or other protected rights.

    The dissemination, publication or reproduction hereof is prohibited.

    For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.

    .

    Configuration of MindbreezePermanent link for this heading

    Configuration of index and crawlerPermanent link for this heading

    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 pagePermanent link for this heading

    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 parametersPermanent link for this heading

    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.

    ProxyPermanent link for this heading

    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 loginPermanent link for this heading

    Basic AuthenticationPermanent link for this heading

    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 LoginPermanent link for this heading

    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 rulesPermanent link for this heading

    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 URLPermanent link for this heading

    Jive URL

    Base URL of the Jive Server

    Grant Access to Configured Principals if Key Matches

    Regular expression used to set static ACL grants to documents. The Regex matches the document key and the entries can be configured with the next option.

    Grant Access to Principal

    Specifies which grants are set when the document matches the previous Regex. This allows certain users or groups to be given access to the documents.

    Check Tags For Update

    List of tags which should be checked for new documents. Otherwise changes of tags cannot be updated reliably. This option should only be used for important tags.

    Integrating Kaltura videosPermanent link for this heading

    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:

    Enable

    If checked, Kaltura videos will be indexed and the following options will be applied:

    Video URL Pattern

    Regular expression to extract the embedded video IDs from the IFrame URLs (<iframe src={URL}</iframe>). The first capture group in the regex shows the ID of the video. For example: https?\Q://cdnapi.kaltura.com/p/999999/\E.*entry_id=([^&\/]*).*

    Kaltura URL

    The Kaltura URL, normally https://www.kaltura.com

    Secret

    “Administrator Secret” (recommended) or “User Secret.” This can be found in the Kaltura management console (KMC) under "Settings" "Integration Settings”.

    Partner ID

    This can be found in the Kaltura management console (KMC) under "Settings" "Integration Settings”.

    Privileges

    This field can be left empty. Otherwise you can restrict session authorizations here (see Kaltura's API Authentication and Security).

    Session Expiration

    Number of seconds before the session should expire. One day is recommended (86400 seconds)

    Jive Principal ResolutionPermanent link for this heading

    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.

    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.

    Download PDF

    • Configuration - JiveSoftware Jive Connector

    Content

    • Configuration of Mindbreeze
    • Jive Principal Resolution

    Download PDF

    • Configuration - JiveSoftware Jive Connector