Friday, March 18, 2016
Dgidx is the indexing program that reads the tagged records that were prepared by Forge or CAS and creates the proprietary indexes for the MDEX Engine.
Find out steps if Dgidx process needs to be run from command prompt against forge_output.
1. Go to <<Endeca_Install_Path>>\MDEX\<version>
2. Run mdex_setup script.
3. Run dgidx using the following command.
Windows:
dgidx -v --out [specify output log directory] [forge_output_directory]\[appliation configuration prefix] (dgidx_output_directory)\(appliation configuration prefix)
Unix:
.\dgidx -v --out [specify output log directory] [forge_output_directory]/[appliation configuration prefix] (dgidx_output_directory)/(appliation configuration prefix)
Find out steps if Dgidx process needs to be run from command prompt against forge_output.
1. Go to <<Endeca_Install_Path>>\MDEX\<version>
2. Run mdex_setup script.
3. Run dgidx using the following command.
Windows:
dgidx -v --out [specify output log directory] [forge_output_directory]\[appliation configuration prefix] (dgidx_output_directory)\(appliation configuration prefix)
Unix:
.\dgidx -v --out [specify output log directory] [forge_output_directory]/[appliation configuration prefix] (dgidx_output_directory)/(appliation configuration prefix)
Example:
dgidx -v --out C:\test\log\Dgidx.log C:\test\forge_output\CRS C:\test\dgidx_output\CRS
Note:- This would helpful for debugging/performance tuning purpose.
No comments
Post a Comment
Note: Only a member of this blog may post a comment.