The CIFS Scanner component performs full and incremental scans over a shared folder (including NTFS), maintaining a snapshot of the filesystem, and comparing it with the current content to establish which content has been updated. Updated content is then submitted to the configured pipeline in AspireObjects attached to Jobs. Including the URL of the changed item, the AspireObject also contains metadata extracted from the repository. Updated content is split into three types - add, update, and delete. Each type is published as a different event so that it can be handled by different Aspire pipelines.

The scanner reacts to an incoming job. This job may instruct the scanner to start, stop, pause or resume. Typically, the start job contains all of the information required by the job to perform the crawl. However, the scanner can be configured with default values via the application.xml file. When pausing or stopping, the scanner waits until all of the jobs it published have completed before completing itself.

Note: CIFS Application Bundle has malfunctions when another CIFS Application is installed on the same server and configure for another server on another domain. This also applies to the Publish To SharePoint 2013.

CIFS Scanner
Factory Namecom.searchtechnologies.aspire:aspire-cifs-connector
subTypedefault
InputsAspireObject from a content source submitter holding all the information required for a crawl
OutputsJobs from the crawl

Configuration

This section lists all configuration parameters available to configure the CIFS Scanner component.

General Scanner Component Configuration

Basic Scanner Configuration

ElementTypeDefaultDescription
snapshotDirStringsnapshotsThe directory for snapshot files.
numOfSnapshotBackupsint2The number of snapshots to keep after processing.
waitForSubJobsTimeoutlong600000
(=10 mins)		Scanner timeout while waiting for published jobs to complete.
maxOutstandingTimeStatisticslong1mThe max about of time to wait before updating the statistics file. Whichever happens first between this property and maxOutstandingUpdatesStatistics will trigger an update to the statistics file.
maxOutstandingUpdatesStatisticslong1000The max number of files to process before updating the statistics file. Whichever happens first between this property and maxOutstandingTimeStatistics will trigger an update to the statistics file.
usesDomainbooleantrueIndicates if the group expansion request will use a domain\user format (useful for connectors that does not support domain in the group expander).

Branch Handler Configuration

This component publishes to the onAdd, onDelete and onUpdate, so a branch must be configured for each of these three events.

ElementTypeDescription
branches/branch/@eventstringThe event to configure - onAdd, onDelete or onUpdate.
branches/branch/@pipelineManagerstringThe name of the pipeline manager to publish to. Can be relative.
branches/branch/@pipelinestringThe name of the pipeline to publish to. If missing, publishes to the default pipeline for the pipeline manager.
branches/branch/@allowRemotebooleanIndicates if this pipeline can be found on remote servers (see Distributed Processing for details).
branches/branch/@batchingbooleanIndicates if the jobs processed by this pipeline should be marked for batch processing (useful for publishers or other components that support batch processing).
branches/branch/@batchSizeintThe max size of the batches that the branch handler will created.
branches/branch/@batchTimeoutlongTime to wait before the batch is closed if the batchSize hasn't been reached.
branches/branch/@simultaneousBatchesintThe max number of simultanous batches that will be handled by the branch handler.

Configuration Example

  <component name="Scanner" subType="default" factoryName="aspire-cifs-connector">
    <debug>true</debug>
    <snapshotDir>${aspire.home}/data/snapshots</snapshotDir>
    <branches>
      <branch event="onAdd" pipelineManager="../ProcessPipelineManager" pipeline="addUpdatePipeline" allowRemote="true" batching="true"
        batchSize="50" batchTimeout="60000" simultaneousBatches="2" />
      <branch event="onUpdate" pipelineManager="../ProcessPipelineManager" pipeline="addUpdatePipeline" allowRemote="true" batching="true"
        batchSize="50" batchTimeout="60000" simultaneousBatches="2" />
      <branch event="onDelete" pipelineManager="../ProcessPipelineManager" pipeline="deletePipeline" allowRemote="true" batching="true"
        batchSize="50" batchTimeout="60000" simultaneousBatches="2" />
    </branches>
  </component>

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.

ElementTypeOptionsDescription
@actionstringstart, stop, pause, resume, abortControl command to tell the scanner which operation to perform. Use start option to launch a new crawl.
@actionPropertiesstringfull, incrementalWhen a start @action is received, it will tell the scanner to either run a full or an incremental crawl.
@normalizedCSNamestring Unique identifier name for the content source that will be crawled.
displayNamestring 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.

ElementTypeDefaultDescription
urlstring The smb URL to crawl (smb:// format).
partialScanbooleanfalseTo run a partial scan – i.e. to only scan a portion of the larger directory. This is useful to re-process portions of your system without having to process the entire content source.
subDirUrlstring Configurable when partialScan is set to true. The sub-directory which contains the documents to be processed for this partial scan. This directory must be a relative path to the parent directory. Only the documents in this sub-directory will be scanned. This is useful to re-process portions of your system without having to process the entire content source.
domainstring The domain where the username, connecting to the shared folder, belongs to.
usernamestring The username to connect with.
passwordstring The password of the username to connect with.
indexContainersbooleanfalsetrue if folders (as well as files) should be indexed.
scanRecursivelybooleanfalsetrue if subfolders of the given URL should be scanned.
fileNamePatterns/include/@patternstring 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/@patternstring 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.

Scanner Configuration Example

  <doc action="start" actionProperties="full" normalizedCSName="cifsTest">
    <connectorSource>
      <url>smb://localhost/AspireTesting/</url>
      <partialScan>true</partialScan>
      <subDirUrl>LSA</subDirUrl>
      <domain>search</domain>
      <username>ralfaro</username>
      <password>encrypted:6A2B871F3F30D3B5BF8D406B9C185FAF</password>
      <indexContainers>true</indexContainers>
      <scanRecursively>true</scanRecursively>
      <fileNamePatterns>
        <include pattern=".*LSA.*"/>
        <exclude pattern=".*tmp.*"/>
      </fileNamePatterns>
    </connectorSource>
    <displayName>cifsTest</displayName>
  </doc>

Output

<doc>
  <url>smb://localhost/AspireTesting/LSA/Videos youtube.txt</url>
  <snapshotUrl>003 smb://localhost/AspireTesting/LSA/Videos youtube.txt</snapshotUrl>
  <docType>item</docType>
  <repItemType>aspire/file</repItemType>
  <fetchUrl>smb://localhost/AspireTesting/LSA/Videos youtube.txt</fetchUrl>
  <displayUrl>smb://localhost/AspireTesting/LSA/Videos youtube.txt</displayUrl>
  <id>smb://localhost/AspireTesting/LSA/Videos youtube.txt</id>
  <connectorSpecific type="fileshare">
    <field name="smbUrl">smb://localhost/AspireTesting/LSA/Videos youtube.txt</field>
  </connectorSpecific>
  <lastModified>2012-07-25T05:57:30Z</lastModified>
  <dataSize>111</dataSize>
  <acls>
    <acl access="allow" domain="NT AUTHORITY" entity="group" fullname="NT AUTHORITY\SYSTEM" inherited="true" name="SYSTEM" scope="machine" sid="S-1-5-18" sidType="windowsGroup"/>
    <acl access="allow" domain="SEARCH" entity="user" fullname="SEARCH\ralfaro" inherited="true" name="ralfaro" scope="global" sid="S-1-5-21-4065858124-1791371549-2540926932-1286" sidType="user"/>
    <acl access="allow" domain="BUILTIN" entity="group" fullname="BUILTIN\Administrators" inherited="true" name="Administrators" scope="machine" sid="S-1-5-32-544" sidType="localGroup"/>
    <acl access="allow" domain="" entity="group" fullname="\Everyone" inherited="true" name="Everyone" scope="machine" sid="S-1-1-0" sidType="localGroup"/>
    <acl access="allow" domain="S-1-5-21-4065858124-1791371549-2540926932" entity="group" fullname="S-1-5-21-4065858124-1791371549-2540926932\2687" inherited="true" name="2687" scope="machine" sid="S-1-5-21-4065858124-1791371549-2540926932-2687" sidType="windowsGroup"/>
  </acls>
  <owner>BUILTIN\Administrators</owner>
  <sourceName>cifsTest</sourceName>
  <sourceType>fileshare</sourceType>
  <connectorSource>
    <url>smb://localhost/AspireTesting/</url>
    <partialScan>true</partialScan>
    <subDirUrl>LSA</subDirUrl>
    <domain>search</domain>
    <username>ralfaro</username>
    <password>encrypted:6A2B871F3F30D3B5BF8D406B9C185FAF</password>
    <indexContainers>true</indexContainers>
    <scanRecursively>true</scanRecursively>
    <fileNamePatterns>
      <include pattern=".*LSA.*"/>
      <exclude pattern=".*tmp.*"/>
    </fileNamePatterns>
    <displayName>cifsTest</displayName>
    <partialScanUrl>LSA</partialScanUrl>
  </connectorSource>
  <action>add</action>
  <hierarchy>
    <item id="16C82BC703B3D0BD1A11CBCB9136FCE7" level="3" name="Videos youtube.txt" url="smb://localhost/AspireTesting/LSA/Videos youtube.txt">
      <ancestors>
        <ancestor id="4646C909DA9EE32E5C36C8D5843DCEE3" level="2" name="LSA" parent="true" type="aspire/folder" url="smb://localhost/AspireTesting/LSA/"/>
        <ancestor id="D2B7229CA1C9BCC12AA27BB354BC2DD4" level="1" name="cifsTest" type="aspire/fileshare" url="smb://localhost/AspireTesting/"/>
      </ancestors>
    </item>
  </hierarchy>
</doc>

 

  • No labels