Google Search Appliance Getting the Most from Your Google Search Appliance - Manual (Page 69)

Google Search Appliance: Getting the Most from Your Google Search Appliance Essentials 69
Learn More about the Search Protocol
For complete information about the Search Protocol and the XML results format, refer to the Search
Protocol Reference.
Writing Applications with the Feeds Protocol
The Feeds Protocol enables you to write a custom application to feed a data source into the Google
Search Appliance for processing, indexing, and serving. You can also use a feed to remove content from
the index.
Use the publicly available GSA Feed Manager ( http://code.google.com/p/gsafeedmanager/ ) to help you
feed data to the GSA and to alleviate potential issues with creating a feed client.
Useful Knowledge for Writing a Feed Client
To write your own feed client, you need knowledge of the following technologies:
• HTTP—Hypertext Transfer Protocol
• XML—Extensible Markup Language
• A scripting language, such as Python
Learn More about the Feeds Protocol
For complete documentation on feeds, refer to the Feeds Protocol Developer’s Guide.
Integrating with an Existing Access-Control Infrastructure
You can enable a Google Search appliance to communicate with an existing access control infrastructure
by using the following Service Provider Interfaces (SPIs):
• SAML Authentication SPI (see “Authentication SPI” on page 70)
• SAML Authorization SPI (see “Authorization SPI” on page 70)
These interfaces communicate by way of standard Security Assertion Markup Language (SAML)
messages.
Before using the Authentication and Authorization SPI, you must configure the appliance to crawl and
index some secure controlled-access content. The SPI is only used when a user queries for secure
results.