Step 1. Launch Aspire and Open the Content Source Management Page

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

Step 2. Add a new Content Source

  • For this step please follow the step from the Configuration Tutorial of the connector of you choice, please refer to Connector list


Step 3. Add a new Parquet Extractor to the Workflow

To add a Parquet Extractor application drag from the Parquet Extractor rule from the Workflow Library and drop to the Workflow Tree where you want to add it. This will automatically open the Parquet Extractor window for the configuration of the application.


Step 3a. Specify Application Information

 In the Parquet Extractor window, specify the configuration information of the application.

  1. General configuration
    1. Do not store ids - Check if you do not want to store ids in NoSql. Warning! Aspire will not be able to delete items in the index in future crawls.
    2. Sub Job timeout - Time out for secondary jobs in milliseconds..
      1. Example: 60000
    3. No info messages - Check if you want info messages disabled
    4. Batch Size - Sub job batch size.
    5. Batch Timeout - Sub job batch timeout in milliseconds.
    6. Debug:
      1. Enable debug messages.
  2. Routing
    1. Workflow for add/update jobs:
      1. Workflow to send the generated add or update jobs.
    2. Workflow for delete jobs:
      1. Workflow to send the generated delete jobs.
    3. Workflow for error jobs:
      1. Workflow to send the generated error jobs.


Step 3b. Share rule to a library

Once the application is set, it must be shared to a (new or existing) library.

Note: This is a required step. 

Step 3c. Copy the rule from the shared library

Add the shared application from the library to the Delete workflow.

Note: This is a required step. 


In order to work, the application requires Extract Text to be disabled in the connector configuration.

image2020-1-7_15-22-48.png

Once you've clicked on the Add button, it will take a moment for Aspire to download all of the necessary components (the Jar files) from the Maven repository and load them into Aspire. Once that's done, the application will appear in the Workflow Tree.

For details on using the Workflow section, please refer to Workflow introduction.