Configuring Live Indexing for Search

Important: When configuring a live indexing server, please note that it must run on a separate dedicated server. Live indexing cannot run on your Knowledge servers or customer-facing servers, which use simple caching mode for the Profile Adapter Repository. Indexing servers must disable caching. If the indexing server does not disable caching, updates to profiles will not be indexed.

For every server that creates, updates, or deletes profiles, you must perform the following:

  1. Add the DPS.Search.Index module to the EAR file on the servers, if not already present. Add this module to the EAR file for your customer-facing and management servers also.

  2. During your CIM installation, you identified an internal server that is your live indexing server. To create a full index, the indexing engine requires a clean partition. The clean partition is a file from which all indexes are created. As such, you need to identify the location of the clean partition by creating a /localconfig/atg/search/routing/
    Configuration.properties     file. Use the cleanPhysicalPartitionPath property to identify the full path to the clean partition.

    There is a copy of the clean partition located at <ATGSearchdir>/SearchEngine/
    operatingsystem/data/initial.index. To resolve the path correctly, use a relative path to identify the clean partition location as a local copy. For example:

    cleanPhysicalPartitionPath =../data/initial.index

  3. Configure the processing of live indexing requests. Set the following property in the /localconfig directory of the customer-facing server. 1:

    /atg/userprofiling/search/ProfileOutputConfig
    incrementalUpdateSeconds=-1

    Set the following property in the /localconfig directory of the management server:

    /atg/userprofiling/search/ProfileOutputConfig
    incrementalUpdateSeconds=5

    By setting incrementalUpdateSeconds to a positive value, you enable incremental indexing of profiles on the management server. The value you enter is the frequency to check for profiles to index. The value you set depends on how often you need the profile indexed.

  4. Set the following /localconfig /atg/search/routing/
    LaunchingService     values on your indexing and agent-facing servers. The deployment share directory is a single shared directory where master copies of indexes are stored. For additional information, refer to the     ATG Search Installation and Configuration Guide:

    deployShare=drive:/yourSharedDirectory/yourDeployShareMainDirectory
    engineDir=drive:/pathtoSearchEngine

    For example:

    deployShare=C:\ATG\DeployShareMain
    engineDir=C:\ATG\ATG10.1\Search10.1\SearchEngine

Copyright © 1997, 2012 Oracle and/or its affiliates. All rights reserved. Legal Notices