FAST Listener Application Bundle (Aspire 2)
For Information on Aspire 3.1 Click Here
The FAST Listener application mimics a FAST content distributor. It receives calls via HTTP turns these requests in to AspireObjects. Some of these requests are for services (sessions, names of servers, callbacks etc) and others contain data (jobs containing documents or batches of documents to be indexed).
All requests are eventually handled by the FAST Content API Listener component which, in the case of data to be indexed, creates AspireObjects and publishes them. They are then routed to the appropriate applications for processing. Clients may then request callback information, detailing if the data has been successfully indexed by the search engine. The application returns information on whether the data has been successfully processed in Aspire, or if the Publish to FAST Application Bundle is being used, then the callbacks from FAST may be passed directly to the client.
In the case of service calls, this application will provide the appropriate response.
|Content tag||String||The tag in the Aspire document that the Fast content should be written to. If specified, each FAST data item will be written as a child of this tag. If omitted, all content will be written as children of the root of the document.|
|Drop on terminate||boolean||false||When set jobs published by the listener and terminated in subsequent pipelines will report error callbacks with a suggested action of "drop" to the FAST client|
|Use external callbacks||boolean||false||If true, use callback information from another component (such as a Post to FAST component). Otherwise, the application will keep track of the success and failures of jobs it publishes and use this to provide call back information.|
|Component||String||The name of the component publishing to Fast (or providing callbacks). This allows the callback information to be transferred from the publisher to this listener and back to the client.|
|Sub-systems||Group||One or more sub-systems that should be reported to the FAST client, made up from the four items below.|
|Name||String||The name of the FAST subsystem. e.g. indexing or processing.|
|ID||String||How the sub-system should be reported to the client. e.g. indexing:1:1 or processing:0:1.|
|Success callbacks||String||The list of callbacks that should be reported to the client upon successful processing. e.g. secured,completed.|
|Error callbacks||String||The list of callbacks that should be reported to the client upon failed processing. e.g. secured,completed.|
|Job Routing||Group||One or more routes, describing where the jobs created in the application should be sent to. These are the processing applications that will process the data sent to this application for indexing. Consists of the two items below.|
|Pipeline||String||The document processing applications to route the jobs from the FAST listener to.|
|Preference||String||LOCAL||The route preference. One of LOCAL, PREFER_LOCAL, PREFER_REMOTE or REMOTE.|