The Publish to GSA application performs content feeds to a GSA of metadata and content of files extracted by Aspire connectors. The feed to the GSA can be customized by editing the XSL transformation file provided by the user.
| Publish to GSA Application Bundle | |
|---|---|
| Factory Name | com.searchtechnologies.aspire:app-publish-to-gsa |
| subType | default |
| Inputs | AspireObject from a connector's subjob with metadata and content extracted from a specific file/folder. |
| Outputs | An XML transformation of the AspireObject sent to the GSA's xmlfeed URL. |
Configuration
This section lists all configuration parameters available to configure the Publish to GSA Application Bundle component.
| Property | Type | Default | Description |
|---|---|---|---|
| GSANoUrl | boolean | true | Indicates if the publisher must use a Url or build one from the host and port entered. |
| GSAPort | interger | 19900 | GSA port where to send the feeds |
| GSAHost | string | none | GSA hostname or IP adress. e.g. gsa.domain.com |
| GSAUrl | string | none | Complete Url where the feeds are going to be send. e.g.http://localhost:19900/xmlfeed |
| makePublic | boolean | false | Makes public all content published to the GSA. |
| aspireToGSAXsl | string | ${appbundle.home}/config/xsl/aspireToGSA.xsl | Location of the XSL to transform the job data to a GSA feed. See Edit Xsl. |
| maxResults | int | 1000000 | (Index dump) How many documents can be fetched by the search engine for the same query |
| dumpSlices | int | 10000 | (Index dump) How many documents to fetch per page |
| urlField | string | displayUrl | (Index dump) Field used to store the url in the search engine |
| idField | string | id | (Index dump) Field used to store the id in the search engine. |
Example Configuration
Simple
Complex
Overview
Content Tools