Google Search Appliance Planning for Search Appliance Installation - Manual (Page 8)

Google Search Appliance: Planning for Search Appliance Installation 8
Serving
Users submit search requests to the Google Search Appliance a web page similar to the search page at
Google.com. A user types a search term into the search box and the request is transmitted to the
serving software. The search appliance locates results in the index. The search appliance then returns
the results to the user’s browser as a series of links. When the user clicks a link in the results, the
content file is displayed.
You can customize the behavior and appearance of the search page from the Admin Console, which you
use to administer and configure the search appliance. For complete information on customizing the
search page and other aspects of the user experience, see Creating the Search Experience.
About the End User License Agreement
During the initial search appliance configuration process, you must accept an End User License
Agreement. Google recommends that you copy the license agreement when you view it. After the
configuration process is complete, you cannot view the End User License Agreement again.
How Do I Plan My Installation?
Before you install the Google Search Appliance, follow one of the high-level preinstallation workflows
below to ensure that the installation goes smoothly.
For Sites or Locations with New Content
1. Determine the physical location of the search appliance.
• Will the search appliance be installed in a data center or in your office?
If you install the search appliance in an office, place it in an area where any noise produced by
the cooling fan in the search appliance will not be disturbing.
• Does the location meet the electrical and temperature requirements described in “Electrical
and Other Technical Requirements” on page 21.
2. Analyze your business’s content and decide which files you want indexed.
3. Decide whether to use a database feed.
Use a database feed to associate metadata with a corresponding content file and include the
metadata in the index. If you are indexing a content management system, the connector
automatically associates metadata from the repository with the appropriate content file.
4. Determine which files are public and can be viewed by any person performing a search of the
content.
5. Determine how to provide the appropriate security for files that are not fully public. For example,
store confidential files in locations that are not crawled or use a security model that requires
authorization to view content that you want to protect from public view. For more information, see
Managing Search for Controlled-Access Content.
6. Design a directory structure for the web site or intranet that supports the desired security model.