Running the Dgidx binary at the command prompt

In rare instances, you may need to run the Dgidx binary from the command prompt outside of your EAC and Deployment Template configuration. This is helpful if the Dgidx process fails, and you need to identify whether a possible cause of the problem is in the Deployment Template scripts, the EAC, or Dgidx itself.

Note: You should only run the Dgidx binary directly at the command prompt in rare instances when you need to replicate a Deployment Template job in a separate testing environment. If you need to re-run a particular process with its normal settings, Endeca recommends using the runcommand of the Deployment Template.

Before running the Dgidx binary at the command prompt, do the following prerequisite tasks:

Copy the necessary files into the locations where the Dgidx process can find them.
Create the dgidx_output directory. It must exist prior to running Dgidx, but is not created automatically as part of running it from the command prompt.

To run the Dgidx binary at the command prompt:

Go to the %ENDECA_MDEX_ROOT%\bin directory on Windows, or to $ENDECA_MDEX_ROOT/bin on UNIX.
Enter the Dgidx command, such as dgidx (on Windows) or dgidx on UNIX. The usage information for the Dgidx binary is displayed. The parameters for Dgidx depend on your specific implementation. Examine the Dgidx command usage to construct the command you will run in the next step.

Run the command, which will be similar to the following example:

Option	Description
Windows	`%ENDECA_MDEX_ROOT%\bin\dgidx --out \localdisk2\endeca\version\dgidx.log --dtddir %ENDECA_ROOT%\conf\dtd \localdisk2\endeca\version\endeca \localdisk2\endeca\version\dgidx_output\endeca`
UNIX	`$ENDECA_MDEX_ROOT/bin/dgidx --out /localdisk2/endeca/version/dgidx.log --dtddir $ENDECA_ROOT/conf/dtd /localdisk2/endeca/version/endeca /localdisk2/endeca/version/dgidx_output/endeca`

This command points to the location of the Dgidx log, its DTD directory, and the Dgidx output file.