Before you start installing Search, consider the following questions:
What ATG products do you plan to use along with Search? It’s a good idea to review all of the applicable documentation before beginning any ATG installation.
How will you apportion your hardware? Indexing and searching are resource-intensive functions that benefit strongly from dedicated hardware with robust specifications.
How will your applications be distributed? Some ATG applications can share an ATG server instance, while others cannot. Will your system include clusters? See the ATG Multiple Application Integration Guide for architectural information.
How will administrative functions such as lock management be handled? With a dedicated ATG server instance, or as part of some other function?
What database software will you use? Where will the ATG platform and application schemas live? How will they be accessed?
Where will your ATG Search deployment share be located? The deployment share is a single, scalable, shared directory where master copies of indexes are stored. Your installation can have only one deployment share, which should be located on a dedicated high-performance disk, separate from the Search Administration installation. The Search Administration installation and all Search engines must have access to this directory.
Note: The size of the index that is deployed does not bear any direct relationship to the size of the raw information being indexed—dictionaries, topics, and other customization data can all add to the size of the index, as can the nature of the content itself. For example, content consisting mostly of pictures with some metadata might form a very small index relative to the raw content size, while a product catalog with many small, unique pieces of information might be relatively large.
Review this guide thoroughly before beginning your installation. This chapter includes the following sections:
