The Post FS4SP Stage stage uses a properties mapping file to create a FAST Document mapping AspireObject properties with FS4SP Managed Properties that already exist on the search engine, the FAST Document is then sent to the content distributor service (default on port 13391 of the FS4SP installation) via the contentAPI.
The stage also allows to configure the FS4SP collection to send the documents to and supports job batching, see Branch Handler.
|fastServer||String||localhost:13391||Comma separated list of server:port for the FS4SP Content Distributors.|
|fastCollection||String||The name of the Fast collection the document should be indexed in to.|
|idPath||String||/doc/fetchUrl||The location of the document id in the AspireObject (required for the FAST API).|
|actionPath||String||/doc/action||The action to be performed (one of unknown, noChange, insert, update or delete).|
|Fast API timeout in ms.|
|fastWaitForSecure||boolean||false||Wait for a secured callback from Fast before allowing the job to complete.|
|fastWaitForIdx||boolean||false||Wait for an indexed callback from Fast before allowing the job to complete.|
|maxBatchSize||long||1000||The maximum number of documents to add to a batch before sending to Fast.|
|The maximum time to wait before sending documents in a batch to Fast if the document count has not reached the maxBatchSize.|
|debugFile||String||Debug file to write documents to before sending to Fast.|
|mappingFile||string||Location of the properties mapping file. See Properties Mapping File for more information.|
Properties Mapping File
The properties mapping file specifies an association between AspireObject properties and FS4SP managed properties. The property type is also specified.
How to specify an Aspire property
Use AXPath to specify the location of the AspireObject property
List of available property types
- acl: string with user/group name. Will be encoded as base32 text.
- byte: byte array