Page History

Step 1. Launch Aspire and

Open the Content Source Management

page.

Anchor
Step1 Step1

1.

Launch Aspire (if it's not already running).

 
See Launch Control

For details on using the Aspire Content Source Management page, please refer to Admin UI.

Step 2. Add a

New StageR Content Source.

Anchor
Step2 Step2

To specify exactly what shared folder to crawl, we will need to create a new "Content Source".

1. From the Content Source, click

1. Add Source

1. .
2. Click

1. StageR Connector.

Step 2a. Specify

basic information

In the

General

tab in the Content Source Configuration window, specify basic information for the content source:

1. Enter a content source name in the "Name" field. 
   1. This is any useful name which you decide is a good name for the source. It will be displayed in the content source page, in error messages, etc.
2. Click on the Scheduled

1. pull-down list and select one of the following: Manually, Periodically, Daily, Weekly or Advanced.
   1. Aspire can automatically schedule content sources to be crawled on a set schedule, such as once a day, several times a week, or periodically (every N minutes or hours).For the purposes of this tutorial, you may want to

1. 1. select Manually and then set up a regular crawling schedule later.
2. Click on the Action

1. pull-down list to select one of the following: Start, Stop, Pause, or Resume.
   1. This is the action that will be performed for that specific schedule.
2. Click on the Crawl

1. pull-down list and select one of the following: Incremental, Full, Real Time, or Cache Groups.
   1. This will be the type of crawl to execute for that specific schedule.
      
2. After selecting a Scheduled, specify the details, if applicable:

• • Manually: No additional options.
  • Periodically: Specify the "Run every:" options by entering the number of "hours" and "minutes."
  • Daily: Specify the "Start time:" by clicking on the hours and minutes drop-down lists and selecting options.
  • Weekly: Specify the "Start time:" by clicking on the hours and minutes drop-down lists and selecting options, then clicking on the day checkboxes to specify days of the week to run the crawl.
  • Advanced: Enter a custom CRON Expression (e.g. 0 0 0 ? * *)

Step 2b. Specify the

connector information

In the

Connector

tab, specify the connection information

to crawl the StageR.

1. 1. Server: The host and port of the server the STageR is running on. The STageR's default port is 3000
   2. Use https: Check this box if your STageR requires an https connection
   3. Storage Unit: The name of the STageR storage unit you wish to crawl
   4. Scope: The scope with in the STageR's storage unit you wish to crawl
   5. Page size: The number of transactions to retrieve from the STageR in a single call

If required, you can also configure the connection to the STageR. Check the configure connection check box to allow you to configure:

1. 1. Connection timeout:Period to attempt to connect to the STageR for before timing out
   2. Read timeout :Period to attempt to read from the STageR for before timing out
   3. Retries:The number of retries that will be attempted when a connection or read timeout occurs before the STageR reports an error
   4. Retry delay: The period to wait after a failure before retrying the operation
   5. Retry policy: The policy to use for the retries
      1. Fixed: The same delay will apply on each retry
      2. Increasing: The delay will be the attempt number multiplied by a fixed value. Eg for a value of 2, the delay would be 2, 4, 6, 8 etc
         1. Maximum retry delay: The maximum time to wait before retrying a REST call
      3. Cumulative: The delay will be increased by a multiple on each attempt. Eg for a delay of 3 and a multiplier of 2, the delay would be 3, 3x2, 3x2x2, 3x2x2x2 (3, 6, 12, 24) etc
         1. Retry delay multipler: The factor by which to increase the retry delay for every failed REST crawl
            
         2. Maximum retry delay: The maximum time to wait before retrying a REST call
            

Step 2c. Specify workflow information.

In the Workflow tab, specify the workflow steps for the jobs that come out of the crawl. Drag and drop rules to determine which steps should an item follow after being crawled.

These rules could be where to publish the document or transformations needed on the data before sending it to a search engine. See Workflow for more information.

1. 1. For the purpose of this tutorial, drag and drop the Publish To File rule found under the Publishers tab to the onPublish Workflow tree.
      1. Specify a 

1. 1. 1. Name and Description for the Publisher.
      2. Click Add.

1. 1. Click Save and Done and you'll be sent back to the Home

1. 1. page.
      
      

Step 3: Initiate a

full crawl.

Anchor
Step3 Step3

Now that the content source is set up, the crawl can be initiated.

1. Click on the full crawl

1. icon to start a crawl (if you start an incremental crawl the first time, it'll work like a full crawl

1. as all content will be seen as new)
2. Click Start

1. .

During the

crawl

• • Click

• • Refresh

• • on the Content Sources page to view the latest status of the crawl.
    The status will show RUNNING while the crawl is going, and CRAWLED when it is finished.
  • Click

• • Complete

• • to view the number of documents crawled so far, the number of documents submitted, and the number of documents with errors.

If there are errors, you will get a clickable "Error" flag that will take you to a detailed error message page.

Step 4: Initiate an

incremental crawl.

Anchor
Step4 Step4

If you only want to process content updates from the STageR (documents which are added, modified, or removed), then click

Incremental

instead of

Full

. The STageR connector will automatically identify only changes which have occurred since the last crawl, using the transactions returned from the STageR.

If this is the first time that the connector has crawled, the action of the "Incremental"

crawl will be the same as a "

full" crawl. Thereafter, the Incremental

option will only crawl updates.