Read more about the search indexing @ http://tips4ufromsony.blogspot.com/2011/11/atg-search-architectural-flow-search.html
ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step.
1. Initial stage:
a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles.
b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently :
66900009 @ index engine box
66900010 @ search engine box
c. Lets assume that the component SearchEngineService has the "Local Content Path" as following for the search and index environments :
Search environment --> ../indexFiles/66900010
Indexing environment --> ../indexFiles/66900009
2.Preparing Content
a. start an indexing engine @ step "Load latest pre-index customizations"
b. delete the folder "\indexFiles\66900009" and create a new folder "\indexFiles\66900011" @ location "SearchEngine\i686-win32-vc71\indexFiles" @ index engine box
c. copy the files initial.index ( from SearchEngine\i686-win32-vc71\data ) and LUIStore.stg to “indexFiles\66900011” --> done by indexing engine
3.Indexing
a. create a new index and stg files @ "SearchEngine\i686-win32-vc71\buildedIndexFiles". First create the index file and then the stg file.
b. copy the new index and stg files to the folder indexFiles\66900011 --> done by indexing engine
c. update the SearchEngineService.Local Content Path of the indexing environment to ../indexFiles\66900011
d. kill the indexing engine
4.Deploying
a. start a new answer engine
b. create the folder "indexFiles\66900012" @ answer engine box --> done by the new engine
c. copy the new index and stg files to the folder "indexFiles\66900012" --> done be new engine
d. update the SearchEngineService.Local Content Path of the search environment to ..\indexFiles\66900012
e. delete the folder "indexFiles\66900010"
f. shutdown the previous running engine
ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step.
1. Initial stage:
a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles.
b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently :
66900009 @ index engine box
66900010 @ search engine box
c. Lets assume that the component SearchEngineService has the "Local Content Path" as following for the search and index environments :
Search environment --> ../indexFiles/66900010
Indexing environment --> ../indexFiles/66900009
2.Preparing Content
a. start an indexing engine @ step "Load latest pre-index customizations"
b. delete the folder "\indexFiles\66900009" and create a new folder "\indexFiles\66900011" @ location "SearchEngine\i686-win32-vc71\indexFiles" @ index engine box
c. copy the files initial.index ( from SearchEngine\i686-win32-vc71\data ) and LUIStore.stg to “indexFiles\66900011” --> done by indexing engine
3.Indexing
a. create a new index and stg files @ "SearchEngine\i686-win32-vc71\buildedIndexFiles". First create the index file and then the stg file.
b. copy the new index and stg files to the folder indexFiles\66900011 --> done by indexing engine
c. update the SearchEngineService.Local Content Path of the indexing environment to ../indexFiles\66900011
d. kill the indexing engine
4.Deploying
a. start a new answer engine
b. create the folder "indexFiles\66900012" @ answer engine box --> done by the new engine
c. copy the new index and stg files to the folder "indexFiles\66900012" --> done be new engine
d. update the SearchEngineService.Local Content Path of the search environment to ..\indexFiles\66900012
e. delete the folder "indexFiles\66900010"
f. shutdown the previous running engine
Hi Sony, I have a clarification in step 4, It will be great if you can help me understand : Will ATG create a new search engine with a new Port at this phase ? Say we have existing engine running in port 5010, will a new engine be created and assigned 5011 and engine at 5010 will be killed during this deploying step ?
ReplyDeleteYes. A new searhc engine will automatically started @ 4.a @ new port. When we create the search project, we can define the range of port numbers for the search engines amd the new port will be opened with in that range.
ReplyDelete:-)
Hi Sony,
ReplyDeleteFirst of all, thanks for the post....
I have some concerns. Why do we need the deploy share ?
As far as i understood
at step 3.a index and stg files are created in deployeshare folder.
at step 3.b the index and stg from deploy share is copied to ndexFiles\66900011.
at step 4.c the index and stg from deploy share is copied to indexFiles\66900012.
Please correct me
deploy share is the name of the folder we specify @ /atg/search/routing/LaunchingService. This is where the index files are placed for index deployment. Index deployment is the process when the index files are copied to search instances. so the deploy share will come into picture only @ index deployment.
ReplyDeleteHi Sony,
ReplyDeleteI am a newbie to ATG..! I am really excited to learn ATG concepts...! I have a doubt in the above topic...what is the need for two segment (folders) you mentioned in the below step and why they are mentioned as Index engine box and search engine box..!
b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently :
66900009 @ index engine box
66900010 @ search engine box
Also please clarify me why the remote launcher is used..and where en all it should run..?
Hi Sony,
ReplyDeleteI have one query i hope you will be helping me in this,
Is it possible to trigger the index deployment using shell script rather than from administration UI.
Thanks
Amit Kumar
Can you give pointers to below error while searching for custoemr in CSC.(ATGProfile env is running)
ReplyDeleteError copying file null\data\initial.index to file ../indexFiles\500001\initial.index: boost::filesystem::copy_file: The system cannot find the path specified: "null\data\initial.index", "..\indexFiles\500001\initial.index"