Google Search Appliance Creating the Search Experience - Manual (Page 68)

Google Search Appliance: Creating the Search Experience Best Practices 68
To enable/disable click-jacking defense:
1. Click Serving > Query Settings.
2. Under Click-Jacking Defense Settings, click the Enable Click-Jacking Defense checkbox.
3. Click Apply Click-Jacking Defense Settings.
Using OneBox Modules to Integrate Structured
Results
In some instances, the most relevant result for a search query is real-time, structured data. This
type of data does not usually reside in the search index because it would be obsolete before it could be
indexed.
For example, as a service to its users, mediacompany.com provides information about local movie times.
When a user searches for “movies,” a specially formatted search box appears at the top of the search
results, as illustrated in the following figure.
When a user enters a location in the search box, formatted, real-time data about theater show times
appear, as illustrated in the following figure.
This type of result is served by a OneBox module. A OneBox module sends the user’s query to a back-
end or third party system and retrieves relevant data immediately. A OneBox module is returned when
an end user's search term matches a “trigger” term. In the previous example, the trigger is “movies.”
The search appliance supports two types of OneBox modules:
• Internal—Provides real-time access to data from a collection on the search appliance
• External—Provides real-time access to data from an external source, such as an application or
database
You can develop OneBox modules with the use of simple APIs and a standard XML format. A OneBox
module that has been integrated with the search appliance can be used with any front end on the
search appliance. A front end can use an unlimited number of OneBox modules.
For detailed information about developing OneBox modules, refer to the following documents:
• Google OneBox for Enterprise Developer’s Guide
• Google OneBox for Enterprise Design Principles