Search
Clear search
Close search
Google apps
Main menu

Legacy Google Search Appliance Releases

Here's a summary of the new and updated features for legacy Google Search Appliance releases 5.2 through 7.2. Please note that these releases are no longer supported by Google; we're providing this information for software version comparison.

Release 7.2

The following sections describe new and changed features in software release 7.2:

New GSA Version Manager

Release 7.2 introduces a new version manager and changes to the software update process. The new version manager is web-based and provides a series of pages designed to make future software updates easier to perform.

Admin Console 2.0

Release 7.2 presents a complete visual redesign of the Google Search Appliance Admin Console. It now has the clear and usable design that you might be familiar with from other Google products, including G Suite.

As part of the redesign, the sidebar navigation has been reorganized to provide intuitive access to Admin Console pages. The new sidebar presents the following options:

  • Content Sources—Lists pages used for web crawl as well as other methods for ingesting content into the search appliance. Also lists diagnostics pages related to content sources.
  • Index—Lists pages used for manipulating the search index, including entity recognition and collections. Also lists diagnostics pages related to the index.
  • Search—Lists pages used for creating the public and secure search experience, including front ends, dynamic navigation, and Universal Login. Also lists diagnostics pages related to search.
  • Reports—Lists pages used for generating logs and reports.
  • GSA Unification—Used for configuring GSA Unification (no change from prior releases).
  • GSA^n—Used for configuring GSA^n (no change from prior releases).
  • Administration—Lists pages used for administering the search appliance (minor changes from prior releases).

Also some of the Admin Console pages have been moved to new locations in the sidebar. If you have used prior releases of Google Search Appliance software, consult the 7.0 to 7.2 GSA Admin Console mapping table.

Onboard Group Resolution

With release 7.2, you can dramatically reduce the latency for group resolution by periodically feeding groups information to the search appliance. When the groups information is on the search appliance, it is available in the security manager for resolving groups at authentication time.

For more information about this feature, see Feeding Groups to the Search Appliance in the Feeds Protocol Developer’s Guide.

Sort Results by Metadata

Starting in release 7.2, the Google Search Appliance provides to ability to sort results by metadata and entities associated with individual documents. This can be used to sort documents by values like prices, dates, authors, etc.

There is no configuration required to enable this feature; the sorting option is activated through a URL parameter on a per-query basis.

To learn more, see Sort by Metadata in the Search Protocol Reference.

Support for HTTP POST Requests

In some instances, a query strings might exceed the 2KB body limit of GET requests and be truncated. This might happen when you submit dynamic navigation queries containing a large number of metadata filters. Starting with release 7.2, you can avoid this limitation by submitting POST requests instead, which have a much larger body limit (10KB).

POST support is only available for:

  • Requests for search service (/search)
  • Public search
  • Secure search, but only when the Trusted Applications feature is used

POST support is not available for Universal Login Auth Mechanisms. You must use the GET command for these.

For detailed information about submitting POST requests, see Using the POST Command in the Search Protocol Reference.

Wildcard Search

Wildcard search is a new feature that enables your users to search by entering a word pattern rather than the exact spelling of a term. The search appliance supports two wildcard operators:

  • *—Matches zero or more characters
  • ?—Matches exactly 1 character

    Using wildcards can simplify queries for long names, technical data, pharmaceutical information, or strings where the exact spelling varies or is unknown. A user can search for all words starting with a particular pattern, ending with a particular pattern, or having a particular substring pattern.

By default, wildcard indexing is disabled for your search appliance. You can enable or disable wildcard indexing by using the Index > Index Settings page. For information about wildcard indexing, click Admin Console Help > Index > Index Settings. See also Wildcard Indexing in Administering Crawl.

By default, wildcard search is enabled for each front end of the search appliance. You can disable or enable wildcard search for one or more front ends by using the Filters tab of the Search > Search Features > Front Ends page. For more information about wildcard search, click Admin Console Help > Search > Search Features > Front Ends > Filters. See also Enabling Wildcard Search in Creating the Search Experience.

Language Improvements

Release 7.2 includes quality improvements to the supported languages and stemming files for additional languages. The additional languages are:

  • Danish (DA)
  • Greek (EL)
  • Finnish (FI)
  • Hungarian (HU)
  • Norwegian (NO)
  • Romanian (RO)
  • Turkish (TR)

Trusted Applications

Release 7.2 introduces the concept of “trusted applications.” The search appliance enables trusted applications to send end-user's search requests along with pre-validated ids when performing a secure search. The search appliance returns secure results without requiring more validation of the user.

Before using this feature, you enable trusted applications and register your application as a “trusted application” on the search appliance. After that, the trusted application can interact with the search appliance.

To register a trusted application with the search appliance, use the Search > Secure Search >Trusted Applications page. For information about using this page, click Admin Console Help > Search > Secure Search >Trusted Applications. See also Using Trusted Applications in Managing Search for Controlled-Access Content.

New Entity Recognition Features

Entity recognition enables the Google Search Appliance to discover interesting entities in documents with missing or poor metadata and store these entities in the search index. Release 7.2 introduces new entity recognition features on the Index > Entity Recognition page, including entity diagnostics and adjustments.

Entity diagnostics enables you to test your entity recognition configuration for a specific HTML document. For this document, you can see highlighted entities that the search appliance has extracted from it. If there are issues with extracted entities, you can modify your entity recognition configuration and retest. By testing, you can gain an understanding of your dictionaries and use this understanding to develop the best ones for your corpus.

The new Adjustments tab enables expert users to fine-tune entity recognition parameters.

To learn more, click Admin Console Help > Index > Entity Recognition. See also Discovering and Indexing Entities in Administering Crawl.

New Crawl Configuration Features

Release 7.2 introduces new features for configuring crawl on the Content Sources > Web Crawl > Start and Block URLs page. This page gives you the option of working with URLs and patterns in one of two views:

  • Action view—provides several features for working with individual URLs and patterns. Use Action view when you want to configure crawl or validate, troubleshoot, recrawl, or test a URL or pattern.
  • Batch Edit view—enables you to work with multiple URLs. Use Batch Edit view when you want to add, edit, or delete multiple URLs and patterns at once.

For more information, click Admin Console Help > Content Sources > Web Crawl > Start and Block URLs. See also Configuring a Crawl in Administering Crawl.

Connectors 4.0 (Beta)

Beta versions of the following connectors are available with release 7.2:

  • SharePoint Connector 4.0
  • SharePoint User Profile Connector 4.0
  • Active Directory Connector 4.0
  • File System Connector 4.0

For information about using 4.0 Beta connectors with release 7.2, see the Connector documentation page in the GSA help center.

Connectors 3.2

Google Search Appliance Connectors Release 3.2 are available for use with release 7.2. For more information about using the 3.2 connectors with release 7.2, see the Connector documentation page in the GSA help center.

Deprecated Legacy Security

Beginning with release 7.2, the Google Search Appliance no longer supports legacy authentication and authorization.

Legacy authentication was superseded in release 6.2 by the Security Manager and Universal Login, but the search appliance continued to support legacy authentication configurations. In release 7.2, the search appliance no longer supports it.

Legacy authorization was superseded in release 6.14, but the search appliance continued to support it through release 7.0. In that release, you had the choice of enabling it or not, and continuing to use legacy authentication. In release 7.2, Flexible Authorization is automatically enabled for the search appliance.

If you have been using legacy authentication, migrate to security manager-based authentication (Universal Login) before migrating to 7.2. If you have been using legacy authorization, migrate to flexible authorization before migrating to 7.2.

In release 7.2, the security manager's headrequestor does not support using a proxy server. If you are considering migrating from 7.0 to 7.2 and you require a proxy server to handle headrequests, you should not update to release 7.2 at this time.

Supported Browsers and Third-Party Software

Google has certified the browsers and third-party products in the following table for use with software release 7.2.

Category Product Name and Version
Browsers Google Chrome (which automatically updates whenever it detects that a new version of the browser is available)
  Microsoft Internet Explorer (IE) 8 and above in standard mode
  Mozilla Firefox current and previous major releases
  The Admin Console supports Safari 5 only; search supports Safari 5.1 and later
Databases IBM DB2
  MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
  MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
  Sybase Adaptive Server Enterprise (ASE) 15 Express
  Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
  MySQL Connector/J 3.1.13
  Microsoft SQL Server 2008, JDBC Driver 2.0
  Sybase jConnect for JDBC 5.5, build 25137
  Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
  HTTPS
  Network Time Protocol (NTP) servers 3.0 and higher
  SMB
SSO (Single sign‑on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
  Oracle Access Manager 7.0.4 (formerly Oblix)
  Cams by Cafesoft, version 3.0
Web servers Apache
  Netscape Enterprise
  Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
  XML Path Language: XPath 1.0
Release 7.0

The following sections describe new and changed features in software release 7.0:

Entity Recognition

Release 7.0 introduces entity recognition, which enables the Google Search Appliance to discover interesting entities in documents with missing or poor metadata and store these entities in the search index. Once the entities are indexed, you can enhance keyword search by adding the entities in dynamic navigation, which uses metadata in documents and entities discovered by entity recognition to enable users to browse search results by using specific attributes.

To configure entity recognition, use the new Crawl and Index > Entity Recognition page in the Admin Console. To learn more, click Help Center > Crawl and Index > Entity Recognition.

Expert Search

New in release 7.0 is expert search, which enables your users find experts in your organization by searching on keywords. For example, suppose a user needs to find an expert on network security. When the user searches on this term, a list of network security experts appears in a sidebar next to the search results. The list might include photos, names, and phone numbers. There might also be a more detailed list of experts on a separate page that is linked to the search results page.

Experts in your organization are identified by metadata that resides in a collection that contains only profile information. Data sources for this collection can include Microsoft SharePoint, LDAP, or any other profile content with metadata that can be crawled or fed into the search index.

You can determine the profile elements and their layout in both the sidebar and on the detail page when you configure expert search. Because expert search is configured by front end, you can create different configurations for that address the needs and levels of different end users.

To configure expert search, use the new Social Connect > Expert Search page in the Admin Console. To learn more, click Help Center > Social Connect > Expert Search.

Take note that people search is deprecated in release 7.0. However, for compatibility with previous releases, people search options are available from the Social Connect > Expert Search page.

User Results

In previous releases, the Google Search Appliance supported basic user-added results, which gave your users the capability of creating unmoderated search results. Starting with release 7.0, the enhanced user results feature replaces basic user-added results.

The new feature enables you to add user results configurations, where you can specify whether user results are moderated, that is, they require administrator approval before appearing in search results, and which front ends use the configuration. Because a user result configuration can be associated with one or more front ends, you can create multiple configurations with different settings and associate them with separate front ends.

To add user results configurations, use the new Social Connect > User Results page in the Admin Console. To learn more, click Help Center > Social Connect > User Results.

Document Previews in Search Results

In release 7.0 the Google Search Appliance provides document previews, which enable users to view a preview image of a document without leaving the search results. The search appliance supports document previews for Microsoft Word (doc, docx), Microsoft PowerPoint (ppt, pptx), and Adobe Portable Document Format (pdf) documents.

The new document preview module prepares document preview images. When you enable the document preview module and configure a front end to show document previews, a user can view document previews, as well as page through and enlarge them.

To enable the document preview module, use the new Serving > Document Preview Module page in the Admin Console. To learn more, click Help Center > Serving > Document Preview Module.

Translation of Search Results

Starting with release 7.0, the Google Search Appliance can translate titles and snippets in search results, as well as cached documents into the user’s language in real time. The user’s language is determined by the default language set in the user’s browser. When translation is enabled, translation links appear in search results. The user can translate everything on a results page or just individual titles, snippets, or cached documents. You can enable or disable translation for any front end. Take note that translate does not work for the Document Preview feature.

To enable translation, use the Page Layout Helper on the Serving > Front Ends > Output Format page in the Admin Console. To learn more, click Help Center > Serving > Front Ends > Output Format - Page Layout Helper.

Index Limit Settings

By default, the Google Search Appliance indexes up to 2.5MB of each text or HTML document, including documents that have been truncated or converted to HTML. Starting with release 7.0, you can change the default index limit by entering an new amount of up to 10MB.

To change the index limit, use the new Crawl and Index > Index Settings page in the Admin Console. To learn more, click Help Center > Crawl and Index > Index Settings.

Metadata Indexing Configurations

With release 7.0, you can customize configurations for metadata indexing. The Google Search Appliance has default settings for indexing metadata, including which metadata names are to be indexed, as well as how to handle multivalued metadata and date fields. Now, you can customize the default settings or add an indexing configuration for a specific attribute.

To customize metadata indexing, use the new Crawl and Index > Index Settings page in the Admin Console. To learn more, click Help Center > Crawl and Index > Index Settings.

If you have configured multvalued attributes for dynamic navigation in a pre-7.0 release, the search appliance will automatically add these attributes under Index Settings when it is updated to software version 7.0. After your search appliance is running 7.0, you will only be able to add multivalued attributes by using the Crawl and Index > Index Settings page.

Index Compressed Files

Beginning with release 7.0, the Google Search Appliance supports crawling and indexing compressed files in .zip, .tar, .tar.gz, and .tgz formats.

To enable the search appliance to crawl these types of compressed files, use the Crawl and Index > Crawl URLs page in the Admin Console. To learn more, click Help Center > Crawl and Index > Crawl URLs.

Dynamic Navigation Enhancements

In this release, dynamic navigation has been enhanced to support more date formats and multi-valued attributes. Also, dynamic navigation now supports adding attributes based on entities discovered by Entity Recognition.

To learn more, click Help Center > Serving > Dynamic Navigation in the Admin Console.

Access Control List Enhancements

Content systems allow for ACL information to be applied to groups of documents through inheritance. In release 7.0, the Google Search Appliance is able to model a wide variety of security mechanisms by using ACL inheritance for per-URL ACLs. To specify ACL inheritance, use the new acl element, which also provides attributes that enable you to specify a URL, principal (user or group), access (permit or deny), namespace, and case sensitivity.

To learn more about the new acl element and inheritance, see the Feeds Protocol Developer’s Guide.

Also in release 7.0, you can change the number of principals to add to a per-URL ACL by using the Crawl and Index > Host Load Schedule page in the Admin Console. To learn more, click Help Center > Crawl and Index > Host Load Schedule.

Also new in this release, the search appliance can accept per-URL ACLs, along with documents at crawl time, through the X-GSA-External-Metadata HTTP response header. To learn more, see Managing Search for Controlled-Access Content.

Entity Biasing

In support of Entity Recognition, result biasing has been extended to support entity biasing. This feature enables you to increase or decrease a document's score when it contains an entity that matches a specified name:content pair.

To specify your preferred adjustments for entities, select the entities from the pull-down menu on the Serving > Result Biasing > Edit page in the Admin Console. The menu is populated with entities that are added by using the Crawl and Index > Entity Recognition page.

To learn more, click Help Center > Serving > Result Biasing > Edit.

Configure Multiple LDAP Servers

Starting with release 7.0, you can configure multiple LDAP servers on a Google Search Appliance. There is no limit to the number of LDAP server configurations that you can create.

To configure one or more LDAP servers, use the Administration > LDAP Setup page in the Admin Console. To learn more, click Help Center > Administration > LDAP Setup.

Serving Logs

The Google Search Appliance records detailed information in serving logs about how it serves results for every search query. Information from serving logs can assist you in setting up a new security configuration or debugging an existing configuration.

In this release, the Admin Console provides a new page, Status and Reports > Serving Logs, that enables you to view and filter serving logs. To learn more, click Help Center > Status and Reports > Serving Logs.

IPv6 Support

Beginning with release 7.0, the Google Search Appliance supports IPv6. For more information, see Planning for Search Appliance Installation.

Deprecated Features

In release 7.0, Google has deprecated the following search appliance features:

  • People search
  • Metadata-based per-URL ACLs in feeds

Take note that Google plans to deprecate the following features in release 7.2:

  • Legacy authentication
  • Legacy authorization

Supported Browsers and Third-Party Software

Google has certified the browsers and third-party products in the following table for use with software release 7.0.

Category Product Name and Version
Browsers Google Chrome 22
  Microsoft Internet Explorer (IE) 8 and 9
  Mozilla Firefox 15 and 16
  Safari 5 and 6
Databases IBM DB2
  MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
  MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
  Sybase Adaptive Server Enterprise (ASE) 15 Express
  Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
  MySQL Connector/J 3.1.13
  Microsoft SQL Server 2008, JDBC Driver 2.0
  Sybase jConnect for JDBC 5.5, build 25137
  Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
  HTTPS
  Network Time Protocol (NTP) servers 3.0 and higher
  SMB
SSO (Single sign‑on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
  Oracle Access Manager 7.0.4 (formerly Oblix)
  Cams by Cafesoft, version 3.0
Web servers Apache
  Netscape Enterprise
  Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
  XML Path Language: XPath 1.0

Supported Browsers and Third-Party Software

Google has certified the browsers and third-party products in the following table for use with software release 7.0.

Category Product Name and Version
Browsers Google Chrome 22
  Microsoft Internet Explorer (IE) 8 and 9
  Mozilla Firefox 15 and 16
  Safari 5 and 6
Databases IBM DB2
  MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
  MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
  Sybase Adaptive Server Enterprise (ASE) 15 Express
  Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
  MySQL Connector/J 3.1.13
  Microsoft SQL Server 2008, JDBC Driver 2.0
  Sybase jConnect for JDBC 5.5, build 25137
  Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
  HTTPS
  Network Time Protocol (NTP) servers 3.0 and higher
  SMB
SSO (Single sign‑on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
  Oracle Access Manager 7.0.4 (formerly Oblix)
  Cams by Cafesoft, version 3.0
Web servers Apache
  Netscape Enterprise
  Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
  XML Path Language: XPath 1.0
Release 6.14

The following sections describe new and changed features in software release 6.14:

Flexible Authorization

Beginning with release 6.14, the Google Search Appliance supports flexible authorization, a new model for performing authorization checks. Flexible authorization gives search appliance administrators more control over authorization by enabling them to:

  • Specify authorization mechanisms in the environment
  • Customize which authorization mechanisms handle which URLs
  • Set the precedence of mechanisms for performing authorization checks

As a search appliance administrator, you can choose to enable flexible authorization or continue to use the search appliance's legacy authorization. However, there is one exception: SMB URLs, which are only handled by the search appliance's legacy authorization.

To configure flexible authorization, use the new Serving > Flexible Authorization page. For information about this page, click Help Center > Serving > Flexible Authorization.

Early/Late Binding for Policy ACLs and Per-URL ACLs

Flexible authorization provides an option for enabling late binding for policy ACLs and per-URL ACLs. If you enable late binding for policy ACLs and per-URL ACLs, the search appliance accepts deny decisions only for these mechanisms. For allow and indeterminate decisions, the search appliance applies each subsequent associated mechanism in the authorization mechanisms list in order until one of them returns a decision other than indeterminate.

For information about enabling late binding for policy ACLs and per-URL ACLs, click Help Center > Serving > Flexible Authorization.

Perimeter Security

Release 6.14 provides perimeter security, which ensures that the search appliance doesn't serve any results without user authentication. When perimeter security is enabled, the search appliance prompts the user for credentials when she first submits a search request. The search appliance authenticates the user by using the mechanisms that are configured for Universal Login.

To configure perimeter security, use the Serving > Universal Login page. For instructions for configuring perimeter security, click Help Center > Serving > Universal Login.

Query Suggestions Export

Release 6.14 introduces a new Admin Console page, Serving > Suggestions. This page enables you to see which query suggestions the search appliance is using by exporting them. The search appliance also has a suggestions blacklist, which contains words that are excluded from query suggestions. If you want to change the suggestions blacklist, you can export it, edit it, import it to the search appliance.

For information about exporting query suggestions and the suggestions blacklist, click Help Center > Serving > Suggestions.

Synonyms Support in Dynamic Navigation

In release 6.14, the search appliance enables you to configure query expansion for configured dynamic navigation attributes.

For information about this topic, see Configuring Query Expansion for Dynamic Navigation.

Query Expansion for Meta Tags

Starting with this release, you can set up a query expansion policy for meta tags by using the Serving > Front Ends > Filters page. Use a query expansion policy for meta tags to select the parts of the name/value pair in a meta tag that the search appliance expands with synonyms.

For information about query expansion for meta tags, click Help Center > Serving > Front Ends > Filters.

Click-Jacking Defense

Click-Jacking (sometimes called UI Redress) is a type of web attack where an attacker modifies the user interface of a target web site so that a victim does not realize that he is taking an important action. With release 6.14, the search appliance can prevent these types of attacks when Click-Jacking Defense is enabled, which is the default. You can change the setting for Click-Jacking Defense by using the Serving > Query Settings page.

For more information about click-jacking defense, click Help Center > Serving > Query Settings.

Crawl Coverage Tuning

Release 6.14 introduces a new Admin Console page, Crawl and Index > Coverage Tuning. Use this page to control the number of URLs the search appliance crawls for a site. For example, you might want to limit the number of URLs the search appliance crawls in one site and allocate more space for other sites.

For information about crawl coverage tuning, click Help Center > Crawl and Index > Coverage Tuning.

Infinite Space Detection

In "infinite space," the search appliance repeatedly crawls similar URLs with the same content while useful content goes uncrawled. Starting with release 6.14, you can prevent crawling of duplicate content to avoid infinite space indexing by using the Crawl and Index > Duplicate Hosts page.

For information about configuring infinite space detection, click Help Center > Crawl and Index > Duplicate Hosts.

Lock on Database Crawling

In this release, you can prevent the Google Search Appliance from deleting database content from the index when its PageRank™ is low and the index has reached its license limit by using the Lock documents checkbox on the Crawl and Index > Databases page.

For more information, click Help Center > Crawl and Index > Databases.

External Metadata at Crawl Time

Release 6.14 supports adding external metadata at crawl time. This process is useful for indexing metadata for non-HTML documents where it is not possible to include metadata in the document itself. To use this method of indexing external metadata, the web service that stores the content needs to be designed to generate the optional X-GSA-External-Metadata HTTP response header.

For more information, see External Metadata Sent in an HTTP Header in the External Metadata Indexing Guide.

Document Date Configuration

New options on the Crawl and Index > Document Dates page enable you to define the date format that's used for documents in a specified URL pattern.

For information about configuring document dates, click Help Center > Crawl and Index > Document Dates.

Connector Manager Log Levels

In this release, the Connector Administration > Connector Managers page includes new options for controlling the connector log level and feed log level.

For information about changing log levels, click Help Center > Connector Administration > Connector Managers.

Connector Advanced Properties

With release 6.14, the Connector Administration > Add Connector page provides a new Advanced Properties option, which enables you to change any advanced properties of a connector type while configuring a connector instance of that type.

For information about the Advanced Properties option, click Help Center > Connector Administration > Add Connector.

Mirroring for GSA Unification

In release 6.14, the search appliance enables you to set up mirroring for a node in a unification configuration by designating it as a "Replica" node.

For information about how to set this up, see Configuring GSA Unification.

Multinode Support for G Suite Personal Content

In previous releases, GSA mirroring and GSA distributed crawling and serving could not integrate personal content from the Cloud Connect > G Suite Content into search results. In release 6.14, this limitation is removed and they can integrate personal content into search results.

Password Complexity Enforcement

Release 6.14 introduces password complexity enforcement through strict password checking options on the Administration > User Accounts page. When Use strict password checking is enabled, certain policies apply to administrator and manager accounts for the Admin Console. For example, passwords changes are checked for appropriate password length, password character mix, and password reuse, as well as other policies.

For information about strict password checking, click Help Center > Administration > User Accounts.

Cookie Domain Configuration

By default, the cookie domain is set to the search appliance's host name, which means that a browser can send a cookie only to one search appliance. In this release, you can use the Administration > System Settings page to configure the cookie domain to enable a cookie to be sent to more than one search appliance in the configured cookie domain, such as in GSAn and Unification configurations.

For information about configuring the cookie domain, click Help Center > Administration > System Settings.

Login Terms

If you have additional terms or conditions for using the Admin Console, you can force the administrator to agree to this set of terms before she is able to access the Admin Console. To do this, use the new Administration > Login Terms page in the Admin Console.

For more information, click Help Center > Administration > Login Terms.

Query Prefix Changes

Starting with release 6.14, the prefix filetype filters search results to include only documents with the specified MIME content type. The prefix ext filters search results to include only documents with the specified file extension. 

For more information, see Special Query Terms in the Search Protocol Reference.

Support Scripts Menu Option

In this release, the Administration menu contains a new option, Support Scripts. The Administration > Support Scripts page enables you to run pre-defined or Google-provided scripts that are designed to assist with customer support. Please only use this feature as directed by customer support.

For more information, click Help Center > Administration > Support Scripts.

Export URLs with Pattern Filters

In this release, the Status and Reports >Export URLs page includes a new option, Include Only URLs with the Following Patterns. This option enables you to export only specific URLs to a file.

For more information, click Help Center > Status and Reports > Export URLs.

JustSystems Ichitaro jtd Format Support

Beginning with release 6.14, the Google Search Appliance supports indexing of the JustSystems Ichitaro .jtd word processing format, ver5, 6, 8 to 13, 2004, and 2010.

Deprecation of Indexing Public Content in Cloud Connect > G Suite

With this release, the indexing public content feature of Cloud Connect > G Suite is deprecated.

Supported Third-Party Software in Software Release 6.14

Google has certified the following third-party products for use with software release 6.14.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 6.0, 7.0, and 8.0 on Windows 7, Windows XP, and Vista
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (Secure Serving with Kerberos is not supported)
Netscape 7 on Linux (Secure Serving with Kerberos is not supported)
Databases IBM DB2
MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2008, JDBC Driver 2.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.14 supports the Google Chrome browser for Windows.

Release 6.12

The following sections describe new and changed features in software release 6.12:

Dynamic Navigation for Secure Search

Dynamic navigation helps user explore search results by presenting navigation options based on metadata attribute values. Starting with release 6.12, you can enable dynamic navigation for secure search. If you enable it, the search appliance only uses documents that the user is authorized to see to generate navigation options. To configure dynamic navigation for secure search, use the Serving > Dynamic Navigation page.

For information about dynamic navigation for secure search, click Help Center > Serving > Dynamic Navigation in the Admin Console.

Nested Metadata Queries

In previous search appliance releases there were restrictions for nesting meta tags in search queries. In this release many of those restrictions are lifted. For information about nested metadata queries, see Nested Boolean Filtering Using Meta Tags in the Search Protocol Reference.

LDAP Authentication with Universal Login

In release 6.12, you can configure a Universal Login credential group for LDAP authentication by using the new LDAP tab on the Serving > Universal Login Auth Mechanisms page in the Admin Console. Also on this tab are options for enabling LDAP for a search appliance, as well as group lookup (both formerly on the Administration > LDAP Setup page).

For information about using this tab, click Help Center > Serving > Universal Login Auth Mechanisms > LDAP.

Index Removal and Backoff Intervals

When the search appliance encounters a temporary error while trying to fetch a document during crawl, it retains the document in the crawl queue and the index, and schedules a series of retries after certain time intervals, known as "backoff" intervals, before removing the URL from the index. In release 6.12, you have the option of using the search appliance default settings for index removal and backoff intervals, or configuring them.

To configure settings, use the options in the Configure Backoff Retries and Remove Index Information section of the Crawl and Index > Crawl Schedule page in the Admin Console. For more information about configuring settings, click Help Center > Crawl and Index > Crawl Schedule in the Admin Console.

Specify URLs to Crawl Immediately in Feeds

Release 6.12 provides the ability to specify URLs to crawl immediately in a feed by using the crawl-immediately attribute. For information about the crawl-immediately attribute, see the Feeds Protocol Developer's Guide.

X-Robots-Tag Support

The search appliance supports the X-Robots-Tag directive in an HTTP header response. Use this directive to prevent the search appliance crawler (as well as other crawlers) from indexing or following links in a specific non-HTML document.

For information about the X-Robots-Tag directive, see Using X-Robots-Tag to Control Access to Non-HTML Documents in Administering Crawl: Preparing for a Crawl.

Supported Third-Party Software in Release 6.12

Google has certified the following third-party products for use with software release 6.12.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 6.0, 7.0, and 8.0 on Windows 7, Windows XP, and Vista
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (Secure Serving with Kerberos is not supported)
Netscape 7 on Linux (Secure Serving with Kerberos is not supported)
Databases IBM DB2
MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2008, JDBC Driver 2.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.12 supports the Google Chrome browser for Windows.

Release 6.10

The following sections describe new and changed features in software release 6.10:

Kerberos Crawling

In release 6.10, the Google Search Appliance supports Kerberos-based access for crawling. Before enabling Kerberos-based crawling, configure Kerberos for serving on the Kerberos Based tab of the Serving > Universal Login Auth Mechanisms page. After you configure Kerberos for serving, you can enable Kerberos crawling on the Crawl and Index > Crawler Access page.

For more information about enabling Kerberos crawling, click Help Center > Crawl and Index > Crawler Access in the Admin Console.

Query Settings Page

In previous search appliance releases, you configured query expansion by using the Serving > Query Expansion page in the Admin Console. Starting with release 6.10, this page has a new name: Serving > Query Settings. In addition to supporting query expansion, this page now also provides the following new features:

  • Support for stopwords files. A stopword is a search term that is ignored by the search appliance.
  • An option for increasing the maximum number of terms in a search query.
  • An option for restoring missing snippets in search results.

For information about these new features, click Help Center > Serving > Query Settings in the Admin Console.

Apply Different Dynamic Navigation Configurations to Different Front Ends

In the previous search appliance release, you could create one dynamic navigation configuration and apply it to different front ends. In release 6.10, by using the Serving > Dynamic Navigation page, you can configure different dynamic navigation configurations and apply the configurations to different front ends.

For information about creating dynamic navigation configurations and applying them to front ends, click Help Center > Serving > Dynamic Navigation in the Admin Console.

Increase the Maximum Number of KeyMatches

By default, the Google Search Appliance only returns a maximum of three KeyMatches for a search. In release 6.10, you can increase the maximum number of KeyMatches returned up to 50 by using the numgm parameter, which is described in the Search Protocol Reference.

Add Standard Email Headers and Footers to Alerts

In release 6.10, you can include a standard email header and footer in alert emails sent from the search appliance by using options on the Serving > Alerts page. For information about adding email headers and footers, click Help Center > Serving > Alerts in the Admin Console.

Set the Maximum File Size for the Crawler to Download

In release 6.10, the Google Search Appliance provides an option for changing the file size limits for downloading when crawling documents.

For information about changing the maximum files sizes to download, click Help Center > Crawl and Index > Host Load Schedule in the Admin Console.

Support for Secure Feeds

In release 6.10, the search appliance supports HTTPS access to the Feedergate server, enabling you to upload an XML feed file by using a secure connection with or without client certificate authentication. By default, the search appliance supports HTTP (non-SSL) access to the Feedergate server. You can disable or re-enable HTTP (non-SSL) access to Feedergate by using the Administration > SSL Settings page.

For information about disabling or re-enabling HTTP (non-SSL) access to Feedergate, click Help Center > Administration > SSL Settings in the Admin Console.

Specify PageRank in Feeds

Release 6.10 provides the ability to specify PageRank in a feed for either a single URL or group of URLs. For information about specifying PageRank, see the Feeds Protocol Developer's Guide.

Troubleshoot Feeds

In this release the Serving > Feeds page includes includes statistical information about feeds in several sections to help you troubleshoot feeds, including feeds recieved for the current day, records processed for the current day, total backlog count. Also for all data sources, the page shows the feed size and download feed. For more information, click Help Center > Crawl and Index > Feeds in the Admin Console.

Centralized GSAn and Mirroring Configuration

In previous software releases, it was necessary to configure distributed crawling and serving separately on the master search appliance (shard) and each of the non-master primary shards. In release 6.10, you can configure distributed crawling and serving centrally by using the GSAn > Configuration page.

For information about configuring distributed crawling and serving, click Help Center > GSAn > Configuration in the Admin Console.

Default Certificate Authorities Options

By default, the search appliance uses its own store of preloaded certificate authorities. Additionally, you can upload your own certificate authorities. In release 6.10, the Administration > Certificate Authorities page provides options for selecting one of the following scenarios:

  • Using the default certificate authorities without uploading any of your own certificate authorities
  • Using only your uploaded certificate authorities without using the default ones
  • Using both the default and uploaded certificate authorities

For information about selecting one of these options, click Help Center > Administration > Certificate Authorities.

Supported Third-Party Software in Release 6.10

Google has certified the following third-party products for use with software release 6.10.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 6.0, 7.0, and 8.0 on Windows 7, Windows XP, and Vista
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (Secure Serving with Kerberos is not supported)
Netscape 7 on Linux (Secure Serving with Kerberos is not supported)
Databases IBM DB2
MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2008, JDBC Driver 2.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.10 supports the Google Chrome browser for Windows.

Release 6.8

The following sections describe new and changed features in software release 6.8:

About Preview Features

To accelerate innovation and deployment of new technology, Google encourages early feature development and feedback. Software release 6.8 includes several new Google Search Appliance features in early stages of development, including people search, cloud connect, and dynamic navigation. Each of these features is labeled "Preview" and is likely to be enhanced in future releases. A preview feature might have specific constraints in the current release. For information about constraints for a preview feature, see the Admin Console Help Center page for the feature.

People SearchPreview

Release 6.8 provides new search capabilities with the Social Connect > People Search page. People search is a release 6.8 preview feature that helps your users find people in your organization. When a user submits a search query, the search appliance searches any people search source collection that you specify, as well as the search index, and displays people search profile information in a sidebar element next to ranked search results.

To configure people search, use the Social Connect > People Search page. For information about configuring people search, click Help Center > Social Connect > People Search.

Google Search Appliance Connector for LDAPPreview

Many organizations use LDAP for storing employee profile information. With release 6.8, the Google Search Appliance provides an LDAP connector that enables you to add LDAP information to the search index. After you have added LDAP information in the index, you can easily configure a people search source collection that contains the LDAP information, so that people search can retrieve profile information from LDAP.

For information about the LDAP connector, see Configuring the Connector for LDAP.

Google Search Appliance Connector for File SystemsPreview

With release 6.8, the Google Search Appliance provides a connector for traversing and indexing content found on file systems.

For information about the file system connector, see Configuring the Connector for File Systems.

Google Search Appliance Connector for Databases

With release 6.8, you can index content and metadata in a relational database management system using a connector installed on a stand-alone host.

For information about the database connector, see Configuring the Connector for Databases.

Cloud ConnectPreview

With release 6.8, in addition to serving up the most relevant documents, the Google Search Appliance can also serve results from G Suite, Google Site Search, and Twitter.

G Suite

In previous search appliance releases, you enabled integration of G Suite content by selecting G Suite > Indexing G Suite Content in the Admin Console. Starting with release 6.8, enable integration of G Suite content by selecting Cloud Connect > G Suite. The Cloud Connect > G Suite page provides the following two features:

These two features offer different coverage of G Suite services. Google recommends that you do not use these two features simultaneously. Choose and configure the feature that best suits your needs and ensure that the other feature is disabled.

Indexing Public Content

The Indexing public content tab on the Cloud Connect > G Suite page provides the same functionality that was provided by G Suite > Indexing G Suite Content in previous search appliance releases. That is, it enables the search appliance to crawl, index, and serve results from a G Suite domain's public Google Docs and Google Sites content.

For information about indexing public G Suite content, click Help Center > Cloud Connect > G Suite and see Integrating with G Suite.

Integrating Personal ContentPreview

Integrating personal content is a preview feature that enables the Google Search Appliance to serve both private and public content directly from your G Suite domain. Search results are displayed in the sidebar element on the search results page and are restricted to only the ones that the user has privileges to view. Integrating personal content supports G Suite services such as Google Docs, Google Sites, and Gmail and covers G Suite Premier domains only.

To enable this feature, use the Integrating personal content tab on the Cloud Connect > G Suite page. For information about integrating personal content, click Help Center > Cloud Connect > G Suite and see Integrating with G Suite.

Google Site SearchPreview

Google Site Search is a hosted search solution for publicly available content. You can configure search across your external web site, your partner sites, or other sites that are relevant to your organization. In release 6.8, you can enable the search appliance to serve results from Google Site Search in the sidebar element on the search results page by specifying your custom search engine identifier.

For information about serving results from Google Site Search in the sidebar element, click Help Center > Serving > Front Ends > Output Format - Page Layout Helper.

TwitterPreview

With release 6.8, your users can see what's being said about the topic of a search query on Twitter when you enable the search appliance to serve results from Twitter in the sidebar element. You can further customize queries by using Twitter search operators.

For more information about serving results from Twitter in the sidebar element, click Help Center > Serving > Front Ends > Output Format - Page Layout Helper.

Dynamic NavigationPreview

With release 6.8, the Google Search Appliance supports dynamic navigation, a preview feature that helps users explore search results by using specific metadata attributes. When a user clicks on an attribute value, the search results are filtered to contain results from the original search query that also have that specific attribute value.

To enable or disable dynamic navigation and manage the metadata attributes that appear as navigation options, use the new Serving > Dynamic Navigation page in the Admin Console. For information about dynamic navigation, click Help Center > Serving > Dynamic Navigation.

To use dynamic navigation on a search appliance that has been updated to release 6.8, you do not need to reset the index, but a recrawl of the content (or resending of the content feeds) is required to index the metadata used by dynamic navigation.

Search Results Page Sidebar Elements

Release 6.8 provides options that enable you to show or hide search results from People Search, G Suite, Google Site Search, or Twitter as sidebar elements on the search results page. You can find these new options in the Search Results section on the Page Layout Helper tab of the Serving > Front Ends > Output Format page in the Admin Console. For information about enabling sidebar elements, click Help Center > Serving > Front Ends > Output Format - Page Layout Helper.

Configurable Search Results Title Length

With release 6.8, you can configure the title length of search results by using the Search Results section of the Page Layout Helper tab of the Serving > Front Ends > Output Format page in the Admin Console. For information about configuring search results title length, click Help Center > Serving > Front Ends > Output Format - Page Layout Helper.

Authentication for User-Added Results

Google Search Appliance release 6.8 supports authentication for user-added results. When you enable authentication for user-added results, a user must be properly authenticated with a verified identity before the user can add, edit, or remove user-added results.

If authentication for user-added results is enabled, and the user is not logged in with a proper verified identity, the user cannot add, edit, or delete user-added results. If authentication for user-added results is not enabled, the user is not required to be properly authenticated before adding, editing, or removing them.

To enable authentication for user-added results, use the Serving > Access Control page in the Admin Console. For more information about authentication for user-added results, click Help Center > Serving > Access Control.

Client Certificate-Based Authentication

In previous software releases, you configured client certificates for user authentication by using the Administration > SSL Settings page in the Admin Console. In Google Search Appliance release 6.8, configure client certificate user authentication by using the new Client Based Authentication tab on the Serving > Universal Login Auth Mechanisms page.

For information about universal login and configuring a credential group rule for client certificate user authentication, click Help Center > Serving > Universal Login Auth Mechanisms > Client Certificate Based and see Managing Search for Controlled-Access Content: Crawl, Index, and Serve.

Kerberos Validation Tool

Google Search Appliance release 6.8 provides a link to a diagnostics utility that helps identify Kerberos-related configuration and serving issues. You can find the link, Kerberos Setup Validation Utility, on the Serving > Universal Login Auth Mechanisms > Kerberos Based page.

Domain Checking for Cookies

By default, the Google Search Appliance enforces strict domain checking of cookies that the crawler sends to servers, typically for access to protected resources. In release 6.8, you can relax strict domain checking of cookies, so that the crawler sends a cookie to a server even though there isn't an exact domain match.

To relax strict domain checking of cookies, use the Crawl and Index > HTTP Headers page. For more information about this topic, click Help Center > Crawl and Index > HTTP Headers.

Scale Policy ACLs and Policy ACL Precedence

In release 6.8, it is possible to scale Access Controls Lists (ACLs) with the number of documents on the Google Search Appliance. In addition to the policy ACL feature, which has pattern-matching semantics and can affect multiple URLs, the search appliance now supports per-URL ACLs, by which ACLs can be associated with each document during crawling or feeding. In particular, documents fed through connectors, such as the SharePoint connector, can do fast authorization, without contacting the SharePoint server at serve time.

Occasionally, a URL can be associated with both a per-URL ACL or a policy ACL. By default, per-URL ACLs take precedence when a URL is associated with both types. However, you can specify that policy ACLs can take precedence over per-URL ACLs by using the new Set Policy ACL Precedence options on the Serving > Policy ACLs page. For information about using these options, click Help Center >Serving > Policy ACLs.

GSA Mirroring Active/Active Configuration

GSA mirroring now supports serving from the primary search appliance and the replica appliances. Use this configuration for higher capacity at serve time. For more information, see Configuring GSA Mirroring.

License Limit Notification

With release 6.8, if your search appliance license limit has been reached, the daily status report includes a notification, along with the number of URLs that are not being served. For more information about the daily status report and this notification, click Help Center > Administration > System Settings.

Export URL Options

Starting with release 6.8, the Status and Report > Export URLs page gives you more control over defining a set of URLs to be exported. By using the options on this page, you can export all URLs, all indexed URLs, or all unindexed URLs. For information about using these options, click Help Center > Status and Reports > Export URLs.

Removed getfields 320 Character Limit

The getfields search parameter is used to specify meta tag values to return with the search results. In this release, the size limit for number of characters returned for each meta tag has been increased as follows:

  • For Latin characters: name + value = 1500 characters; chars_AND_name <= 1500/2
  • For characters in multibyte languages (Japanese, Chinese, and Korean): 500 characters

IPSec

The IPsec protocol suite secures inter-node GSA communication in multinode configurations, improving speed and latency over the previous methods of securing communications.

Enable Logging of User IDs

With release 6.8, the search appliance can record the user identity for a secure query and display user identities in search logs. To enable the search appliance to record user identities, use the new Record user identity in search logs option on the Serving > Access Control page. For information about using this option, click Help Center > Serving > Access Control.

Google Chrome Browser Support

Google Search Appliance software release 6.8 supports the Google Chrome browser for Windows.

Release 6.4

The following sections describe new and changed features in software release 6.4:

JavaScript Crawling

With release 6.4, the Google Search Appliance supports crawling JavaScript. The search appliance can detect links and content generated dynamically through JavaScript execution. The search appliance only executes scripts embedded inside a document and does not execute external scripts or AJAX.

For information about JavaScript crawling, see Administering Crawl: Advanced Topics.

Serve-Time Authentication

With release 6.4, the default behavior of the search appliance is to centralize serve-time authentication for the following mechanisms:

  • Cookie-based authentication (single sign-on, forms)
  • HTTP-based authentication (HTTP Basic, NTLM)
  • Kerberos-based authentication
  • SAML
  • Connectors

You do not need to enable the security manager or disable legacy authentication, as was required in release 6.2.

For more information about serve-time authentication, see Managing Search for Controlled-Access Content: Crawl, Index, and Serve.

Kerberos Configuration

In previous search appliance releases, you configured Kerberos support by using the Crawl and Index > Crawler Access page. Google Search Appliance Release 6.4 provides a new Kerberos tab for configuring Kerberos support on the Serving > Universal Login Auth Mechanisms page in the Admin Console.

For information about using this tab, click Help Center > Serving > Universal Login Auth Mechanisms > Kerberos Based.

SAML Authentication SPI Configuration

In previous search appliance releases, you configured SAML Authentication SPI by using the Serving > Access Control page. In release 6.4, you can find options for configuring SAML authentication SPI on the SAML tab of the Serving > Universal Login Auth Mechanisms page in the Admin Console.

For information about using this tab, click Help Center > Serving > Universal Login Auth Mechanisms > SAML.

Challenge Users with HTTP Basic Authentication

The Serving > Access Control page in release 6.4 provides new Challenge users with HTTP Basic Authentication options. Use these options to define when the search appliance challenges a user for a user name and password when HTTP Basic authentication is used: Never, Automatic--only if prompt needed, and Always.

For information about these challenge options, click Help Center > Serving > Access Control in the Admin Console.

Cookie-Based Authentication that Uses NTLM or HTTP Basic as Credentials Gatherer

In release 6.4, the Google Search Appliance supports cookie-based authentication that uses NTLM or HTTP Basic as a credentials gatherer. To implement this feature, configure crawl of the content protected by NTLM or HTTP Basic by using both the Crawl and Index > Forms Authentication and the Crawl and Index > Crawler Access pages in the Admin Console. Then, configure a cookie authentication rule by using the Cookie Based tab of Serving > Universal Login Auth Mechanisms page.

For more information about this configuration, see Managing Search for Controlled-Access Content: Cookie-Based Authentication Scenarios.

Authentication Trust Duration

Release 6.4 provides a new Trust Duration option on the Universal Login Auth Mechanisms page tabs for Cookie Based, HTTP Based, and Connectors. Use the Trust Duration option to specify how long the authentication mechanisms's verification of user credentials will be trusted, in seconds.

For information about Trust Duration, click Help Center > Serving > Universal Login Auth Mechanisms > Cookie Based, Help Center > Serving > Universal Login Auth Mechanisms > HTTP Based, or Help Center > Serving > Universal Login Auth Mechanisms > Connectors.

Return URL Parameter

The Serving > Universal Login Auth Mechanisms > Cookie Based page in release 6.4 provides a new option, Return URL Parameter. Use this option to specify a return URL parameter, which gives the server for a redirect URL information about the quickest path back to the search appliance.

For information about the Return URL parameter, click Help Center > Universal Login Auth Mechanisms > Cookie Based.

LDAP Setup

In release 6.4, the Administration > LDAP Setup page provides two new options:

  • Use LDAP for User Authentication during serve-time--After setting up a valid LDAP configuration, select this option to enable LDAP on the search appliance. You can also use this option to disable LDAP on a search appliance without deleting the LDAP configuration.
  • Lookup a user's group information during Authentication whenever possible--Select this option to enable a search appliance to automatically look up group information for a user during authentication.

For information about using these options, click Help Center > Administration > LDAP Setup in the Admin Console.

Timeout for Authorization Requests

Google Search Appliance Release 6.4 provides a new option for configuring overall timeout for authorization requests on the Serving > Access Control page. The Overall timeout for authorization requests option enables you to specify how long the search appliances waits before fully processing multiple batches of authorization requests.

For information about using this option, click Help Center > Serving > Access Control in the Admin Console.

Head Requestor Deny Rules

Release 6.4 includes a new Admin Console page, Serving > Head Requestor Deny Rules. This page enables you to identify URLs where content servers deny users access with codes other than HTTP code 401 and define for the search appliance the access-denied responses to expect from the content server. For example, a content server might send an HTTP code 200 instead of a 401 code, or the access-denied response might be in the body of content returned by the content server.

For more information about using this page, click Help Center > Serving > Head Requestor Deny Rules in the Admin Console.

No Upper Limit for OneBox Response Timeout

With Release 6.4, there is no upper limit on the OneBox response timeout option. This option specifies how long the search appliance should wait for a response from the OneBox provider. If the OneBox provider does not respond in the specified time, the search appliance assumes that there are no results for the provider.

For information about using this option, click Help Center > Serving > OneBox Modules in the Admin Console.

Serve-Time Data Profile

In release 6.4, you can create a serve-time data profile by using the Status and Reports > Real-time Diagnostics page. A serve-time data profile captures information about serving and the speed of external content servers. You capture data for an arbitrary period of time that you determine, then export a file containing the data profile.

For information about creating a serve-time data profile, click Help Center > Status and Reports > Real-time Diagnostics in the Admin Console.

Static Routes

Google Search Appliance release 6.4 provides a new field for setting static routes on the Administration > Network Settings page. A static route is a route you define to a host or network that is not on the default route the search appliance follows to the hosts that it crawls. You can enter as many static routes as you need in the Static Route field.

For information about using the Static Route field, click Help Center > Administration > Network Settings in the Admin Console.

Ability to Configure a Dedicated Administrative Port on the Search Appliance

Administrators can now configure the search appliance so that a specific network interface card is used for administrative communications. This simplifies administration in load-balanced environments.

For complete information, see Installing a Search Appliance and Planning for Search Appliance Installation.

Supported Third-Party Software in Release 6.4

Google has certified the following third-party products for use with software release 6.4.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 6.0, 7.0, and 8.0 on Windows 7, Windows XP, and Vista
(Secure Serving with Kerberos is not supported with Windows 7)
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (Secure Serving with Kerberos is not supported)
Netscape 7 on Linux (Secure Serving with Kerberos is not supported)
Databases IBM DB2
MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2008, JDBC Driver 2.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 2.0
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.4 supports the Google Chrome browser for Windows.

Release 6.2

The following sections describe new and changed features in software release 6.2:

Universal Login

Release 6.2 introduces Universal Login, a new feature that enables users to search across multiple systems with multiple credentials, securely and seamlessly. Universal Login dynamically generates a single login page, the Universal Login Form, for the user, and securely passes the login information to back-end systems, even if using heterogeneous authentication protocols.

Universal Login is handled by the security manager, a new release 6.2 search appliance component. To configure Universal Login, enable the security manager, disable legacy authentication, and define credential groups to support multiple credentials across multiple systems.

For comprehensive information about Universal Login, the security manager, and credential groups, see Managing Search for Controlled-Access Content.

SSO Experience Across Multiple Cookie Domains

With release 6.2 beta, the Google Search Appliance includes support for multiple cookie domains, enabling typical single sign-on system's multiple domain configurations.

When a user performs a search against the Google Search Appliance, she provides her username and password to get access to the protected content. After the user is authenticated, the SSO system issues a set of session cookies that includes a cookie for each domain. In other words, the user logs in once and gains access to all cookie domains.

For more information about support for multiple cookie domains, see Managing Search for Controlled-Access Content.

Composite Collections

Building on the collections feature, the Google Search Appliance release 6.2 can create virtual collections, collections of collections, or collections that combine collections from remote search appliances. This capability provides both administrators and users with an easy way to group content for many different deployment scenarios.

For information about composite collections, click Help Center > Crawl and Index > Composite Collections.

Automatic Self-Learning Scorer

Release 6.2 introduces the automatic self-learning scorer, a new feature that automatically analyzes user behavior and the specific links that users click on to fine tune relevance and scoring.

The search appliance uses advanced statistical regression to determine the statistical significance of user behavior, and adjusts for trust bias (that is, users clicking on the first result solely because its first). Thus, over time, results become more and more precise without the need of administrator intervention.

To use the automatic self-learning scorer, you must enable advanced search reporting by using the Serving > Front Ends > Output Format page in the Admin Console.

For detailed information, see Using the Automatic Self-Learning Scorer in Creating the Search Experience: Best Practices.

Advanced Language Phrase Segmenting

Google Search Appliance release 6.2 offers phrase segmentation across any language to improve search quality (most applicable to Chinese, Japanese, Korean and Thai scripts).

Age Option for Date Biasing

Release 6.2 provides a new age option for date biasing on the Serving > Result Biasing > Edit page. This option enables you to specify how quickly documents' scores are decreased as they age, by selecting an age at which a document is considered to be moderately old. This setting indicates that a document of the specified age should get a moderate decrease in score from date biasing.

For information about using the age option, see Using Date Biasing in Creating the Search Experience: Best Practices.

Google Search Appliance SharePoint Connector

Connectivity to MicroSoft SharePoint is now built into the Google Search Appliance, with no need to download a separate connector, and crawling content in SharePoint is now 10X faster.

For information about configuring a SharePoint connector instance, see the Connector documentation.

Case-Insensitive URL Patterns

In release 6.2, you can specify URL patterns to be treated case-insensitively by using the new Crawl and Index > Case-Insensitive Patterns page in the Admin Console. All URLs that match the patterns entered on this page are converted to lowercase before crawling or feeding.

For more information about specifying case-insensitive patterns, click Help Center > Crawl and Index > Case-Insensitive Patterns in the Admin Console.

Real-Time Diagnostics

With release 6.2, you can retrieve and view real-time information for the search appliance by using the new Status and Reports > Real-time Diagnostics page in the Admin Console. Information that you can view includes HTTP headers for a specific URL and traffic on the network layer. This information promotes greater transparency for debugging and troubleshooting purposes.

For information about real-time diagnostics, click Help Center > Status and Reports > Real-Time Diagnostics in the Admin Console.

Remote Support Page

In Release 6.2, the remote support option that was on the Administration > System Settings page has been moved to a new Admin Console page, Administration > Remote Support. Use this page to enable Enterprise Technical Support to log in to a search appliance.

For information about using this page, click Help Center > Administration > Remote Support in the Admin Console.

Google Search Appliance Connector for File SystemsBeta Feature

Connectivity to file shares is now significantly more extensible with our open source connector, which administrators can customize to search file shares, including DFS, CIFS/SMB, and more.

Google Search Appliance Connector for DatabasesBeta Feature

Connectivity to databases is now significantly more extensible with our open source connector, which administrators can customize to search any database.

GSA Unification

In release 6.2, the feature that had been called "Dynamic Scalability" has been renamed "GSA Unification." GSA Unification enables multiple Google Search Appliances to work together to scale up as high as you want go - even up to billions of documents and provide unified search results. GSA Unification is based on an environment in which multiple search appliances are configured to work together.

For detailed information about GSA Unification, see Configuring GSA Unification.

Features Now Generally Available and Supported

In release 6.2, the following features that were beta in release 6.0 are now generally available and supported:

GSAn

In release 6.2, the beta feature that had been called "Distributed Crawling and Index Replication" has been renamed "GSAn." Also, with release 6.2, GSAn becomes a fully-supported search appliance feature.

GSAn offers both distributed crawling and serving and mirroring capabilities. With distributed crawling and serving, several search appliances are configured to act as though they are a single search appliance, which greatly increases the number of documents that can be crawled. After distributed crawling and serving is enabled, all crawling, indexing, and serving are configured on one search appliance, called the primary search appliance or primary node.

With mirroring, the search appliance can automatically clone itself. Mirrored search appliances can be used to handle additional query load or can be used as hot backup units that can take over at any point. The mirrored search appliance receives index updates in real time from the primary search appliance, ensuring that the search appliances are always in sync, and that crawling only needs to occur once.

For information about GSAn, see Configuring Distributed Crawling and Serving and Configuring GSA Mirroring.

GSAn Diagnostics Page

Release 6.2 includes a new Admin Console page, GSAn > GSAn Diagnostics. Use this page to review diagnostic information about connections within distributed crawling and serving and GSA mirroring environments.

Query Suggestions

With release 6.2, query suggestions becomes a fully-supported search appliance feature. Query suggestions help users improve their searches when using a given front end. When query suggestions are enabled, search queries auto-complete and query suggestions appear as a user types in the search box.

To enable query suggestions, use the Serving > Front Ends > Page Layout Helper page in the Admin Console.

For information about query suggestions, see Providing Query Suggestions in Creating the Search Experience: Best Practices.

You can also create and upload a blacklist of terms to prevent them from appearing in query suggestions. For information about blacklisting terms, see Query Suggestion Service /suggest Protocol in the Search Protocol Reference.

User-Added Results

With release 6.2, user-added results becomes a fully-supported search appliance feature. With user-added results, you can give users the capability to add search results for certain keywords in a specific front end. User-added results cause designated documents always to appear on the results pages for specified keyword searches performed in the front end.

The Google Search Appliance includes a built-in OneBox provider for implementing user-added results. You can implement user-added results by performing the following tasks:

  1. Creating a OneBox module definition for user-added results on the Serving > OneBox Modules page in the Admin Console.
  2. Enabling the OneBox module for a front end on the Serving > Front Ends > OneBox Modules page.

For information about user-added results, see Creating the Search Experience: Best Practices.

DNS Override

With release 6.2, DNS Override becomes a fully-supported search appliance feature. Use the new Administration > DNS override page in the Admin Console to resolve hostnames that override the response from the DNS server.

For information about DNS Override, click Help Center > Administration >DNS Override in the Admin Console.

Supported Third-Party Software in Release 6.2

Google has certified the following third-party products for use with software release 6.2.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 6.0 and 7.0 on Windows XP
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (except for secure serving with Kerberos)
Netscape 7 on Linux (except for secure serving with Kerberos)
Databases IBM DB2
MS SQL Server 2000, MS SQL Server 2005, and MS SQL Server 2008
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2008, JDBC Driver 2.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 1.1.1.6
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.2 supports the Google Chrome browser for Windows.

Release 6.0

The following sections describe new and changed features in software release 6.0:

Dynamic Scalability

Release 6.0 introduces dynamic scalability, which enables multiple Google Search Appliances to work together to scale up as high as you want go - even up to billions of documents and provide unified search results. Dynamic scalability is based on a federated environment, in which multiple search appliances are configured to work together.

In a dynamic scalability configuration, one search appliance is the primary node and the others are secondary nodes. The primary search appliance aggregates results from all of the search appliances in the configuration and serves them to the search user. The primary search appliance's front end is used for searching all document corpora in the dynamic scalability configuration.

The new Federation pages in the Admin Console enable you to configure dynamic scalability.

Do not create both dynamic scalability and distributed crawling or index replication configurations for a set of search appliances.

As part of the introduction of dynamic scalability, the algorithm for calculating relevance was changed. There may be some changes in ranking in search results. In most cases, the quality of search results ranking will be improved.

Distributed Crawling Beta Feature

Distributed crawling is release 6.0 beta scalability feature in which several search appliances are configured to act as though they are a single search appliance, which greatly increases the number of documents that can be crawled. After distributed crawling is enabled, all crawling, indexing, and serving are configured on one search appliance, called the primary search appliance or primary node.

The new Multibox page in the Admin Console enables you to configure distributed crawling.

Distributed crawling and index replication can be used together. However, do not create distributed crawling and dynamic scalability configurations for a set of search appliances.

For detailed information about distributed crawling, see Configuring Distributed Crawling and Serving.

Index Replication Beta Feature

Index replication is a release 6.0 beta feature enabling the index on one search appliance to be replicated to another search appliance, providing easily-enabled high-availability in an automatic active/passive configuration.

The new Multibox page in the Admin Console enables you to configure index replication.

Index replication and distributed crawling can be used together. However, do not create index replication and dynamic scalability configurations for a set of search appliances.

Policy ACLs

In release 6.0, the Google Search Appliance introduces policy Access Control Lists (ACLs), which enable caching permissions to increase the performance and scalability of the authorization processes. A policy ACL provides information to the Google Search Appliance about which users or groups have access to a specific URL.

Policy ACLs work with all the existing authentication mechanisms supported by the Google Search Appliance. These mechanisms include Kerberos, HTTP-Basic, NTLM, Forms Based Authentication, Certificates and SAML AuthN SPI. 

The new Serving > Policy ACLs page in the Admin Console enables you to add, edit, or delete a policy ACL for a specific URL pattern.

For information about policy ACLs, see Policy Access Control Lists.

Policy ACL API

The Google Search Appliance Policy ACL API enables developers to programmatically manage policy ACL rules on the Admin Console by specifying allowed users or groups, and by specifying rules for which URL patterns that can be accessed.

For information about the Policy ACL API, see the Policy ACL API Developer's Guide.

Batched SAML Authorization Requests

Release 6.0 provides a new option for improving performance, which is sending multiple URLs in a single, batched Security Assertion Markup Language (SAML) authorization request. You can use batched SAML authorization requests only if your SAML provider supports the Google SAML batch authorization extension.

To submit batched SAML authorization requests, use the Serving > Access Control page in the Admin Console.

For information about batched SAML authorization requests, click Help Center > Serving > Access Control.

Multiple Forms Authentication Rules

In release 6.0, the Crawl and Index > Forms Authentication page enables creating multiple rules to provide the crawler access to content secured by forms. In previous releases, the Forms Authentication page enabled you to create only one such rule while the Crawl and Index > Cookie Sites page enabled you to create multiple rules but forced these into public search. The Make Public function is now built into the Forms Authentication page.

With these enhancements, the Crawl and Index > Cookie Sites page has been removed.

For information about creating multiple forms authentication rules, click Help Center > Crawl and Index > Forms Authentication.

Language Bundles

Release 6.0 introduces language bundles, which are collections of files that the search appliance uses for query expansion and spelling in several languages. You can add language bundles to a Google Search Appliance between software releases or anytime you need them.

The Google Search Appliance provides a built-in language bundle for the following languages:

  • English
  • Portuguese
  • French
  • Italian
  • German
  • Spanish
  • Dutch

Google occasionally provides new language bundles that offer support for different sets of languages.

You can install multiple language bundles on a Google Search Appliance, but only one language bundle can be active at any time. The currently active language bundle provides query expansion and spelling support for the languages in the bundle. By default, the built-in language bundle is active.

The new Serving > Language Bundles page in the Admin Console enables you to install, activate, and delete language bundles.

For information about language bundles, see Changing Languages for Query Expansion and Spelling Suggestions.

Result Biasing by Collection

In release 6.0, source biasing has been enhanced with result biasing by collection (a subset of the complete index). Result biasing by collection enables you to influence the order of documents based on their memberships in collections. To specify your preferred adjustments for documents in collections, identify the collections that you want to affect with source biasing.

To increase or decrease a document's score when it belongs to a collection, use the Serving > Result Biasing > Edit page in the Admin Console.

Query Suggestions Beta Feature

Release 6.0 includes a beta feature, query suggestions, that help users improve their searches when using a given front end. When query suggestions are enabled, search queries auto-complete and query suggestions appear as a user types in the search box.

To enable query suggestions, use the Serving > Front Ends > Page Layout Helper page in the Admin Console.

For information about query suggestions, see Providing Query Suggestions.

User-Added Results Beta Feature

With user-added results, a release 6.0 beta feature, you can give users the capability to add search results for certain keywords in a specific front end. User-added results cause designated documents always to appear on the results pages for specified keyword searches performed in the front end.

The Google Search Appliance includes a built-in OneBox provider for implementing user-added results. You can implement user-added results by performing the following tasks:

  1. Creating a OneBox module definition for user-added results on the Serving > OneBox Modules page in the Admin Console.
  2. Enabling the OneBox module for a front end on the Serving > Front Ends > OneBox Modules page.

For information about user-added results, see Providing User Results.

Ranking Framework Beta Feature

The ranking framework is a release 6.0 beta feature that enables you to influence results rankings programmatically for an unlimited number of URL prefixes.

The input to the ranking framework is a configuration file that contains URL prefixes and their rescoring weights. Input by file enables you to input batch customizations for just a few to millions of URLs.

For information about the ranking framework, see Using Result Biasing to Influence Result Ranking.

Export All URLs

Release 6.0 introduces the capability of generating and downloading a file containing the current status of all the URLs that been found by the search appliance including uncrawled and indexed URLs. The file is in compressed (zip) format. After you download and uncompress the file, you can use a text editor to open it.

To generate and download a file of all URLs, use the Status and Reports > Export All URLs page in the Admin Console. For information about using this page, click Help Center > Status and Reports > Export All URLs in the Admin Console.

Serving Status Latency Graph

The Status and Reports > Serving Status page now displays a global summary of recent search latency. The information is displayed in two ways:

  • As a number in the Recent Search Latency in milliseconds field.
  • As a graph displaying the number of queries per minute over the last 24 hours. The x-axis represents time and the y-axis represents search latency in milliseconds.

New Network Diagnostics Options

Release 6.0 introduces new options in the Network Diagnostics section of the Administration > Network Settings page in the Admin Console:

  • Host to ping
  • Host to tracepath

Use the Host to ping field to test whether the specified host is reachable across the network. Use the Host to tracepath field to determine the route taken to the specified host across the network.

Destroy Feeds

In release 6.0, the Crawl and Index > Feeds page provides an option for destroying data sources. Once you have deleted a data source, you can destroy it by clicking the Destroy link. Destroying a data source removes the feed data source from this page.

Index Migration

Release 6.0 provides capabilities for migrating an index and avoiding having to recrawl content during Google Search Appliance software updates.

For detailed information about index migration, see the update instructions for the Google Search Appliance.

Error Logs for Authentication/Authorization SPI

In release 6.0, error logs generated by the Authentication and Authorization SPI are visible in the Google Search Appliance Admin Console.

Authentication with an LDAP Server

With release 6.0, access to the Admin Console can now be granted via an external LDAP server; a user is authenticated to the Admin Console if she has valid LDAP credentials and belongs to a specified LDAP group.

During search appliance installation, the Admin Console login page can be configured to use only the LDAP authentication, the local GSA authentication, or both.  After the authentication mode is selected, configure it by using the Administration > LDAP Setup page in the Admin Console.

Crawling Secure File Shares

With release 6.0, the Google Search Appliance now crawls file shares protected by NTLM v2 security.

Administrative APIs Google Cloud Labs Feature

Release 6.0 introduces Administrative APIs, a Google Cloud Labs feature. You can use the Administrative APIs to code applications that programmatically set administrative functions for the Admin Console of a Google Search Appliance.

For information about the Administrative APIs, see Google Search Appliance Documentation.

DNS Override Experimental Feature

Administrators can configure the search appliance to resolve hostnames which overrides the response from the DNS server. The Administration > DNS Override page in the Admin Console for configuring this is at http://<appliance>:8000/EnterpriseController?actionType=dns.

Supported Third-Party Software in Release 6.0

Google has certified the following third-party products for use with software release 6.0.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 5.5, 6.0, 7.0 on Windows XP
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux (except for secure serving with Kerberos)
Netscape 7 on Linux (except for secure serving with Kerberos)
Databases IBM DB2
MS SQL Server 2000 and MS SQL Server 2005
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2005, JDBC Driver 1.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) Computer Associates SiteMinder 6.0, Policy Server and Web Agent
Note: There is no support for installations with multiple domains.
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache
Netscape Enterprise
Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 1.1.1.6
XML Path Language: XPath 1.0

Google Chrome Browser Support

Google Search Appliance software release 6.0 supports the Google Chrome browser for Windows. 

Release 5.2

New and Changed Features in Software Release 5.2

The following sections describe new and changed features in Software Release 5.2:

Personalized Search Experience

Release 5.2 introduces features that let you, as a search appliance administrator, personalize the search experience for your users. Rather than providing one centralized experience for everyone, you can provide different search experiences for different groups of users. Each personalized search experience is based on the interests, roles, departments, locations, or languages of the user group. Features that support the personalized search experience are:

For an overview of personalization, refer to Personalizing the Search Experience.

Result Biasing by Front End

Result biasing by front end lets you create different result biasing configurations, or policies, for a front end. This means you can personalize different result biasing policies for different sets of end users. A result biasing policy determines the source biasing, date biasing, and metadata biasing settings that are used with a front end.

To create a result biasing policy for a front end, use the Serving > Result Biasing page in the Admin Console.

For detailed information about result biasing by front end, refer to Using Result Biasing to Influence Result Ranking.

Metadata Biasing

A new metadata biasing feature lets you boost or weaken the relevancy score of a document based on metadata associated with a document.

To configure metadata biasing for a result biasing policy, use the Serving > Result Biasing > Edit page in the Admin Console.

For detailed information about metadata biasing, refer to Using Metadata Biasing.

User Alerts

Release 5.2 introduces user alerts, which enable users to subscribe to topics of interest and receive email notifications when new documents appear on a topic of interest or when documents on a topic of interest have changed. Users can create as many alerts as they like and choose to have them delivered via email hourly, daily, or weekly.

To enable user alerts for a search appliance, use the Serving > Alerts page in the Admin Console. To show the My Alerts link in the user interface, use the Page Layout Help or the XSLT Stylesheet Editor on the Serving > Front Ends > Output Format page in the Admin Console.

For detailed information about enabling user alerts, refer to Providing Alerts for End Users.

If you are updating a search appliance from a previous software version and wish to keep an existing configuration or customized XSLT stylesheet, you must edit your existing XSLT stylesheet to enable alerts.

Advanced Search Reporting

In release 5.2, the Google Search Appliance introduces advanced search reporting, which provides rich search behavior reporting for a front end. Advanced search reports list every query and click made by every user.

Using advanced search reports, you, as an administrator, can gain insights about search behavior, such as:

  • Whether your users are finding everything they want within the first 3 results
  • Which queries result in no clicks by the user
  • How often users are clicking on parts of the user interface, for example the sponsored links on top, search results, or a OneBox module

To enable advanced search reporting for a front end, use the Serving > Front Ends > Output Format page in the Admin Console. To export an advanced search report, use the Status and Reports > Search Log page in the Admin Console.

For detailed information about advanced search reporting, refer to Gathering Information About the Search Experience.

If you are updating a search appliance from a previous software version and wish to keep a customized XSLT stylesheet, you must edit your existing XSLT stylesheet to enable advanced search reporting.

Integrated Windows Authentication/Kerberos Authentication

Release 5.2 provides Integrated Windows Authentication (IWA)/Kerberos Authentication. This feature provides silent authentication experience with various content systems. This makes the search experience seamless for end-users as they need to provide their credentials only once when a user logs to his/her computer. Integrated Windows Authentication (IWA)/Kerberos Authentication supports Sharepoint and File Shares.

To use IWA/Kerberos Integrated Windows Authentication, use the Crawl and Index> Crawler Access page in the Admin Console.

For detailed information about using IWA/Kerberos authentication, refer to Managing Search for Controlled-Access Content.

Integration with G Suite

Release 5.2 introduces integration with G Suite. With G Suite Integration, you can enable your Google Search Appliance to crawl, index, and serve results from a G Suite domain's public Google Docs and Google Sites content.

To enable G Suite Integration, use the G Suite > G Suite Integration page in the Admin Console.

For detailed information about using this feature, refer to Integrating with G Suite.

International Expansion

In this release, the Google Search Appliance expands its international support by introducing:

  • Support for administrative functions in 5 new languages (Czech, English-UK, Portuguese-Portugal, Turkish, Vietnamese),
  • Contextual spell checking for all end users in Portuguese, French, Italian, German, Spanish, and Dutch
  • Contextual query expansion for all end users in Dutch

Scheduled Crawl

In release 5.2, scheduled crawl mode replaces full crawl. Scheduled crawl enables you to designate a day, time, and/or duration for crawling your corpus.

To select scheduled crawl, use the Crawl and Index > Crawl Schedule page in the Admin Console.

Supported Third-Party Software in Release 5.2

Google has certified the following third-party products for use with version 5.2.

Category Product Name and Version
Browsers Microsoft Internet Explorer (IE) 5.5, 6.0, 7.0 on Windows XP
Mozilla Firefox 1.5 and 2 on Windows XP
Mozilla Firefox 2 on Linux
Netscape 7 on Linux
Databases IBM DB2
MS SQL Server 2000 and MS SQL Server 2005
MySQL 4.1.13 and 5.0.37. Note: Version 5.0 requires a JDBC upgrade.
Sybase Adaptive Server Enterprise (ASE) 15 Express
Oracle Database 10g Express Edition on Linux x86 and Windows platforms
JDBC enablers DB2 Universal Database (UDB) 8.1.0.64
MySQL Connector/J 3.1.13
Microsoft SQL Server 2005, JDBC Driver 1.0
Sybase jConnect for JDBC 5.5, build 25137
Oracle Database 10g Release 2, 10.1.0.2.0 driver
Network infrastructure HTTP 1.1
HTTPS
Network Time Protocol (NTP) servers 3.0 and higher
SMB
SSO (Single sign-on) eTrust SiteMinder 6.0, Policy Server and Web Agent
Note: There is no support for installations with multiple domains.
Oracle Access Manager 7.0.4 (formerly Oblix)
Cams by Cafesoft, version 3.0
Web servers Apache, Netscape Enterprise, Microsoft Internet Information Server
XSLT EXtensible Stylesheet Language Transformations: XSLT 1.1.1.6
XML Path Language: XPath 1.0
Was this article helpful?
How can we improve it?