Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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 stoppedpaused 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 NameIBM Connectios Connector
Maven Coordinates
com.searchtechnologiesaccenture.aspire:aspire-ibmconnections-source
Version34.10
InputsAspireObject from a content source submitter holding all the information required for a crawl
OutputsAn AspireObject containing the URL, content, ACLs and Metadata processed for each file.


Configuration


This section lists all configuration parameters available to install the IBM Connections Application Bundle and to execute crawls using the connector.

PropertyTypeDefaultDescription
IBMServerstringnoneThe Url of the IBM Connection server to crawl (you have to specify the protocol).
IBMUserstringnoneThe Username to connect with.
IBMPasswordstringnoneThe password of the Username to connect with.
Page Sizeinteger100Specifies the number of entries per page to return in the crawl
useLTPAbooleanfalsetrue if the connector is going to use LTPA token for authentication.
IBMLoginUrlstringnoneIBM Connections login page (contains the LTPA token)
extractACLbooleanfalsetrue if the connector is going to requires user's GUID from LDAP server
ldapComponentstringnoneLDAP Cache component that was configure in the Services Section.
crawlAllAppsbooleanfalsefalse, All the default endpoints (applications: Activities, Blogs, Bookmarks, Communities, Files, Forums, Profiles, and Wikis) will be crawl.The user should select the applications that want to crawl.

true, The user will select which application wants to crawl.

withLimitedAccessboolean
true if the connector is going to hace limited access to the network or internet
withPatternsboolean

true, if the user defined the accessible servers using patterns

false, if the user defined the accessible server's names or ips

 






Configuration Example

To install the application bundle, add the configuration, as follows, to the <autoStart> section of the Aspire settings.xml.

Panel
titleConfiguration

<application config="com.searchtechnologiesaccenture.aspire:app-ibmconnections-connector">
<properties>
<property name="generalConfiguration">false</property>
<property name="snapshotDir">${dist.data.dir}/${app.name}/scannerTimestamps</property>
<property name="disableTextExtract">false</property>
<property name="extractTextMaxSize">unlimited</property>
<property name="extractTimeout">180000</property>
<property name="workflowReloadPeriod">15s</property>
<property name="workflowErrorTolerant">false</property>
<property name="non-text-document">true</property>
<property name="nonTextDocumentsExtensions">jpg,gif,png,tif,mp3,mp4,mpg,mpeg,avi,mkv,wav,bmp,swf,jar,war,rar,zip,tgz,dll,exe,class</property>
<property name="enableFetchUrl">true</property>
<property name="fullRecovery">incremental</property>
<property name="incrementalRecovery">incremental</property>
<property name="waitForSubJobs">600000</property>
<property name="maxThreads">10</property>
<property name="jobQueue">30</property>
<property name="enableAuditing">true</property>
<property name="emitStartJob">true</property>
<property name="emitEndJob">true</property>
<property name="debug">false</property>
<property name="batchSize">50</property>
<property name="batchTimeout">60000</property>
<property name="fdServiceUrl"/>
</properties>

</application>