ERoom Application Bundle (Aspire 2)

The Eroom Connector performs full and incremental scans over a Eroom Site and will extract security, metadata, and content from each object scanned. The connector allows you to select whether you wish to index folders in the results, and if you wish to fetch security. 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.

ERoom Application Bundle (Aspire 2)
AppBundle Name	Eroom Connector
Maven Coordinates	com.searchtechnologies.appbundles:app-eroom-connector
Versions	2.2.2
Type Flags	scheduled
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

Property	Type	Default	Description
snapshotDir	string	${aspire.home}/snapshots	The directory for snapshot files to be stored.
disableTextExtract	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.
workflowReloadPeriod	int	15m	The period after which to reload the business rules. Defaults to ms, but can be suffixed with ms, s, m, h or d to indicate the required units.
workflowErrorTolerant	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 sucessfully. If not set, exceptions in workflow rules will be re-thrown and the job will be moved to the error workflow.
useGE	boolean	false	true if group expansion is going to be used.
geSchedule	string	0 0 0 * * ?	Indicates how often the group expasion is going to fetch all the security groups.
url	string	none	The url to the Jive Community.
username	string	none	The user used to fetch the security groups.
password	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.

  <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://test_server/eroom/test_eroom</property>
      <property name="username">Admin</property>
      <property name="password">encrypted:63AA72A7708C8999DEE56A41894EBEEB</property>
      <property name="debug">true</property>
    </properties>
  </application>

Note: Any optional properties can be removed from the configuration to use the default value described on the table above.

Source Configuration

Scanner Control Configuration

The following table describes the list of attributes that the AspireObject of the incoming scanner job requires to correctly execute and control the flow of a scan process.

Element	Type	Options	Description
@action	string	start, stop, pause, resume, abort	Control command to tell the scanner which operation to perform. Use start option to launch a new crawl.
@actionProperties	string	full, incremental	When a start @action is received, it will tell the scanner to either run a full or an incremental crawl.
@normalizedCSName	string		Unique identifier name for the content source that will be crawled.
displayName	string		Display or friendly name for the content source that will be crawled.

Header Example

  <doc action="start" actionProperties="full" actionType="manual" crawlId="0" dbId="0" jobNumber="0" normalizedCSName="FeedOne_Connector"
   scheduleId="0" scheduler="##AspireSystemScheduler##" sourceName="ContentSourceName">
    ...
    <displayName>testSource</displayName>
    ...
  </doc>

All configuration properties described in this section are relative to /doc/connectorSource of the AspireObject of the incoming Job.

Element	Type	Default	Description
url	string	none	The url to the Jive Community.
username	string	none	The name of the user that is going to be use for the crawl
password	string	none	The password of the user.
indexContainers	boolean	false	true if folders (as well as files) should be indexed.
fileNamePatterns/include/@pattern	regex	none	Optional. A regular expression pattern to evaluate file urls against; if the file name matches the pattern, the file is included by the scanner. Multiple include nodes can be added.
fileNamePatterns/exclude/@pattern	regex	none	Optional. A regular expression pattern to evaluate file urls against; if the file name matches the pattern, the file is excluded by the scanner. Multiple exclude nodes can be added.

Scanner Configuration Example

  <doc action="start" actionProperties="full" normalizedCSName="testFile">
    <connectorSource>
      <url>http://test_server/eroom/test_room</url>
      <user>Admin</user>
      <password>encrypted:63AA72A7708C8999DEE56A41894EBEEB</password>
      <indexContainers>true</indexContainers>
      <fileNamePatterns>
        <include pattern=".*place.*"/>
        <exclude pattern=".*people.*"/>
      </fileNamePatterns>
    </connectorSource>
    <displayName>testFile</displayName>
  </doc>

Note: To launch a crawl, the job should be sent (processed/enqueued) to the "/EroomConnector/Main" pipeline.

Output

<doc>
  <sourceType>eroom</sourceType>
  <fetchUrl>http://server/eRoom/Facility_Name/Eroom_Name/0_99d</fetchUrl>
  <docType>container</docType>
  <dataSize>2</dataSize>
  <lastModified>2013-09-05T12:25:29-07:00</lastModified>
  <url>http://server/eRoom/Facility_Name/Eroom_Name/0_99d</url>
  <crawlId>64</crawlId>
  <id>http://server/eRoom/Facility_Name/Eroom_Name/0_99d</id>
  <displayUrl>http://server/eRoom/Facility_Name/Eroom_Name/0_99d</displayUrl>
  <connectorSpecific type="eroom">
    <field name="name">ROOT_DB</field>
    <field name="id">0_99d</field>
    <field name="description">
As you respond to RFPs, look through this database for answers that have already been addressed. Cut and paste the responses into the RFP you are responding to. If you find a question that has not been entered into the database, create a new entry and and insert the appropriate content.</field>
    <field name="path">/ROOT_DB</field>
    <field name="relativeUrl">/eRoom/Facility_Name/Eroom_Name/0_99d</field>
    <field name="type">database</field>
  </connectorSpecific>
  <repItemType>aspire/database</repItemType>
  <sourceName>Eroom Test Crawl</sourceName>
  <snapshotUrl>002 http://server/eRoom/Facility_Name/Eroom_Name/0_99d</snapshotUrl>
  <action>add</action>
  <acls>
    <acl name="C*" fullname="server@C*" scope="global" entity="group" domain="http://server/eRoom/Facility_Name/Eroom_Name/0_99d" access="allow"/>
    <acl name="slancet" fullname="server@slancet" scope="global" entity="user" domain="http://server/eRoom/Facility_Name/Eroom_Name/0_99d" access="allow"/>
    <acl name="GroupGroupCreators" fullname="server@GroupGroupCreators" scope="global" entity="group" domain="http://server/eRoom/Facility_Name/Eroom_Name/0_99d" access="allow"/>
    <acl name="Administrator" fullname="server@Administrator" scope="global" entity="user" domain="http://server/eRoom/Facility_Name/Eroom_Name/0_99d" access="allow"/>
  </acls>
  <hierarchy>
    <item name="0_99d" type="aspire/database" url="http://server/eRoom/Facility_Name/Eroom_Name/0_99d" id="84AE4E58C1C08BF2C94A5CDAD97145F3" level="2">
      <ancestors>
        <ancestor name="Eroom Test Crawl" parent="true" url="http://server/eRoom/Facility_Name/Eroom_Name/" type="aspire/eroom" id="B0AB8682C5824C63A19C2FEE541026FB" level="1"/>
      </ancestors>
    </item>
  </hierarchy>
  <connectorSource>
    <username>Administrator</username>
    <indexContainers>true</indexContainers>
    <scanRecursively>true</scanRecursively>
    <displayName>Eroom Test Crawl</displayName>
    <password>encrypted:BE2C7CE47EF6B481FEA01ADA2BFE03BA</password>
    <url>http://server/eRoom/Facility_Name/Eroom_Name/0_99d</url>
  </connectorSource>
</doc>

Page tree