The IBM Connections Connector performs full and incremental scans over a IBM Connections site and will extract security, metadata, and content from each object scanned. The connector allows you to select whether you wish all applications or only some of them (Activities, Blogs, Files, etc). Each scanned object will be tagged with one of three possible actions--add, update, or delete--and can be routed to any Aspire pipeline as desired.
The connector, once started, can be stopped, paused or resumed via the Scheduler Component. Typically the start job will contain all information required by the job to perform the scan. When pausing or stopping, the connector will wait until all the jobs it published have completed before updating the statistics and status of the connector.
| IBM Connections Application Bundle | |
|---|---|
| AppBundle Name | IBM Connectios Connector |
| Maven Coordinates | com.searchtechnologies.aspire:aspire-ibmconnections-source |
| Version | 3.1 |
| Inputs | AspireObject from a content source submitter holding all the information required for a crawl |
| Outputs | An AspireObject containing the URL, content, ACLs and Metadata processed for each file. |
Configuration
This section lists all configuration parameters available to install the Jive Application Bundle and to execute crawls using the connector.
| Property | Type | Default | Description |
|---|---|---|---|
| crawlAllApps | string | ${aspire.home}/snapshots | The directory for snapshot files to be stored. |
| IBMSSLPassword | boolean | false | By default, connectors use Apache Tika to extract text from downloaded documents. If you wish to apply special text processing to the downloaded document in the workflow, you should disable text extraction. The downloaded document is then available as a content stream. |
| IBMSSLDir | int | 15m | The period after which to reload the processing rules. Defaults to ms, but can be suffixed with ms, s, m, h or d to indicate the required units. |
| useSSL | boolean | false | When set, exceptions in workflow rules will only effect the execution of the rule in which the exception occurs. Subsequent rules will be executed and the job will complete the workflow successfully. If not set, exceptions in workflow rules will be re-thrown and the job will be moved to the error workflow. |
| Page Size | boolean | false | true if group expansion is going to be used. |
| IBMServer | string | none | The url to the Jive Community. |
| IBMUser | string | none | The user used to fetch the security groups. |
| IBMPassword | string | none | The password for the user |
| debug | Boolean | false | Controls whether debugging is enabled for the application. Debug messages will be written to the log files. |
Configuration Example
To install the application bundle, add the configuration, as follows, to the <autoStart> section of the Aspire settings.xml.
Configuration
<application config="com.searchtechnologies.aspire:app-jive-connector">
<properties>
<property name="generalConfiguration">false</property>
<property name="snapshotDir">${dist.data.dir}/${app.name}/snapshots</property>
<property name="disableTextExtract">false</property>
<property name="workflowReloadPeriod">15s</property>
<property name="workflowErrorTolerant">false</property>
<property name="useGE">true</property>
<property name="geSchedule">0 0 12 ? * *</property>
<property name="url">http://searchtechnologies.jive.com</property>
<property name="username">Admin</property>
<property name="password">encrypted:63AA72A7708C8999DEE56A41894EBEEB</property>
<property name="debug">true</property>
</properties>
</application>
Overview
Content Tools