If you are running Search engine instances on machines other than the Search Administration machine, and you want to use those instances in an indexing environment, additional configuration is required.
In order to create a full index (see Note below) the indexing engine needs a clean partition, a file from which all indexes are created. If the engine is not local to the Search Administration installation, you must make it available. The clean partition is located in the <Searchdir>\SearchEngine\operatingsystem\data\ directory.
To make a clean partition available:
Either move the clean partition into your deployment share folder, or create a new share with read access for the Search engine (for example,
\\mymachine\sharedData).Create a
RoutingSystemService.propertiesfile in your<ATG9dir>\home\localconfig\atg\search\routingdirectory to point to the partition in the shared directory, using the full network path. The file should contain acleanPhysicalPartitionPathproperty as shown in the following examples.Windows:
cleanPhysicalPartitionPath=\\\\server\\deploymentshared\\initial.indexUNIX:
/mount_location/deploymentshared/initial.index
The Search engines must also be able to access all directories that contain content to be indexed. When indexing a file system, the Search engines receive paths to the files, for example, D:\CustomerDocs\whitepaper.doc. If the Search engine is not on the same machine as Search Administration, then the D drive is not accessible, and the engine cannot open the file to index it. In that case, you should share the content location, for example as \\some_machine\CustomerDocs.
Note: Even if you use incremental indexing, you should recreate the full index every so often; see the ATG Search Administration Guide for indexing suggestions.
