Publish to GSA Tutorial (Aspire 2)

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

For Information on Aspire 3.1 Click Here

Step 1: Launch Aspire and open the Content Source Management Page

Aspire Content Source Management Page

Launch Aspire (if it's not already running). See:

Browse to: http://localhost:50505. For details on using the Aspire Content Source Management page, please refer to UI Introduction.


Step 2: Create a new Content Source

For this step please follow the step from the Configuration Tutorial of the connector of you choice, please refer to Connector list.

Step 3: Add a new Publish to GSA to the Workflow

To add a Publisher to GSA drag from the Publish to GSA rule from the Workflow Library and drop to the Workflow Tree where you want to add it. This will automatically open the Publish to GSA window for the configuration of the publisher.

Step 3a: Specify Publisher Information

Publish to GSA Configuration Aspire 2.0.x
Publish to GSA Configuration Aspire 2.1 +

In the Publish to GSA window, specify the connection information to publish to the GSA.

  1. Enter the name of the publisher. (This name must be unique).
  2. Enter the description of the publisher that will be shown in the Workflow Tree.
  3. Enter the Specify GSA URL
    • Host and port
      • Enter the GSA host.
      • Enter the GSA port (19900 by default)
    • Complete Url
      • Enter the url for the GSA, it must have this format <protocol>://<host>:<port>/xmlfeed
  4.  (2.1 Release)   Max Results per request: The maximun number of documents the search engine can fetch in a single query.
  5.  (2.1 Release)   Slices: How many requests to fetch from GSA, to make sure each request don't have more documents than the max results allowed, the recommended slices size is: (2 * Index_Size) / max_results_per_request
  6.  (2.1 Release)   Url field: Field containing the url indexed
  7.  (2.1 Release)   Id Field: Field containing the id field indexed, used to compare against the content source audit logs
  8. Make public: it will mark all the content published to the GSA as public.
  9. XSL File Path: set to the default parameter to use the default XSL transformation file. To use a custom file, follow the instructions in Edit Xsl
  10. Debug: Check if you want to run the publisher in debug mode.
  11. Click on the Add button.

Once you've clicked on the Add button, it will take a moment for Aspire to download all of the necessary components (the Jar files) from the Maven repository and load them into Aspire. Once that's done, the publisher will appear in the Workflow Tree.

For details on using the Workflow section, please refer to Workflow Introduction.