Difference between revisions of "Publish to GSA Application Bundle (Aspire 2)"

From wiki.searchtechnologies.com
Jump to: navigation, search

For Information on Aspire 3.1 Click Here

Line 7: Line 7:
|appBundleName=Publish To GSA
|appBundleName=Publish To GSA
|versions= 2.0
|typeFlags= job-input
|typeFlags= job-input

Latest revision as of 00:16, 9 December 2015

Publish to GSA Application Bundle (Aspire 2)
AppBundle Name  Publish To GSA
Maven Coordinates  com.searchtechnologies.aspire:app-publish-to-gsa
Versions  2.2.2
Type Flags  job-input
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.

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.


This section lists all configuration parameters available to install the GSA Application Bundle.

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 (2.1 Release)   int 1000000 (Index dump) How many documents can be fetched by the search engine for the same query
dumpSlices (2.1 Release)   int 10000 (Index dump) How many documents to fetch per page
urlField (2.1 Release)   string displayUrl (Index dump) Field used to store the url in the search engine
idField (2.1 Release)   string id (Index dump) Field used to store the id in the search engine.

Configuration Example

  <application config="com.searchtechnologies.aspire:app-publish-to-gsa">
      <property name="GSANoUrl">true</property>
      <property name="GSAPort">19900</property>
      <property name="GSAHost">localhost</property>
      <property name="makePublic">true</property>
      <property name="debug">true</property>
      <property name="aspireToGSAXsl">${appbundle.home}/config/xsl/aspireToGSA.xsl</property>

Note: Any optional properties can be removed from the configuration to use the default value described on the table above.

Edit Xsl

The default XSL transformation file can be found in File:AspireToGSA.xsl.

The default transformation XSL file provided by the publisher expects metadata as described in Connector AspireObject Metadata.

Add metadata field

To add a new metadata field extracted by an Aspire Connector add an xsl element under the <metadata> tag.

<meta name="metafieldNameInGSA">
  <xsl:attribute name="content">
    <xsl:value-of select="metafieldNameFromAspireObject" />

Change the id URL

The id URL is the URL the GSA uses to uniquely identify a file in the index. To change the Aspire metadata field being used as the id, change the value of the record's attribute: url to the desired field.

<xsl:attribute name="url">

Change the display URL

The display URL is the URL the GSA uses as the result's file location display in the results page. Change the google:displayurl meta field content attribute to change this value.

<meta name="google:displayurl">
  <xsl:attribute name="content">
    <xsl:value-of select="displayUrlFromAspireObject" />

Advanced Edit

More advanced changes can be accomplished following the Feeds Protocol Developer's Guide instructions.


The output of the component will be a GSA Feed formatted XML that will be sent through the /xmlfeed URL of the GSA. The output XML of the XSL transformation needs to follow the definition established by the gsafeed_dtd