Google Search Appliance Feeds Protocol Developers Guide - Manual (Page 24)

Google Search Appliance: Feeds Protocol Developer’s Guide 24
Groups Feed Document Type Definition
scope (USER|GROUP) #REQUIRED
namespace CDATA "Default"
case-sensitivity-type (EVERYTHING_CASE_SENSITIVE|EVERYTHING_CASE_INSENSITIVE)
"EVERYTHING_CASE_SENSITIVE"
principal-type (unqualified) #IMPLIED>
Creating a Groups Feed Client
A feed client is required for pushing groups information.
You upload an XML feed using an HTTP POST to the feedergate server located on port 19900 of your
search appliance. An XML feed must be less than 1 GB in size. If your feed is larger than 1GB, consider
breaking the feed into smaller feeds that can be pushed more efficiently.
On the search appliance, a feedergate handler, feedergate_groupsfeed, accepts the POST request,
parses the XML into serialized data and stores it in the recordio file. The recordio file cannot exceed 1GB.
If the data size in the request plus the existing recordio file size is greater than 1GB, the request will be
rejected with “error: group db at capacity.”
The feedergate server requires two input parameters from the POST operation:
• groupsource: The name of the data source. Must be one of the following values: sharepoint, ggg,
ldap, and others.
• groupsfilename: The groups XML file you want to push to the search appliance.
• feedtype: Specifies whether a feed is full or incremental. A full feed overwrites onboard groups. An
incremental feed appends groups.
The URL that you should use for the groups feed is:
http://:19900/xmlgroups
The following example shows the command to push a groups feed:
pushgroups_client.py --groupsource=others --feedtype=full
--url="http://:19900/xmlgroups"
--groupsfilename="groups_feed.xml"
Note: To clear the groups database, use the empty content XML file as shown in “Example Feed with
Empty Groups” on page 23 and perform a full push (feedtype=full).