The Background Queue Connector is new in Aspire 4.0 and allows processing of items that have been published to an Aspire queue for later processing. Background processing uses the same distributed queues (held in NoSQL) as used in the connector framework. The Background Processing Connector is, in fact, a cut down version of connector framework, with no “scan” method, since the scanning is done elsewhere. The interaction of the connector framework and background processing can be seen below:

Features

• Read from a named queue in an Aspire cluster
• Publishes the queued document supplemented with information about the queue entry
  • So the document sent to the workflow has the same id etc as the original
• Optionally deletes queue entries once processed
  • Or leave for debugging
• Optionally ends the crawl when the queue is empty
  • Or runs indefinitely