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, Oracle recommends using the
runcommand of the Deployment Template.
Before running the Dgidx binary at the command prompt, do the following prerequisite tasks:
To run the Dgidx binary at the command prompt:
Go to the
%ENDECA_MDEX_ROOT%\bindirectory on Windows, or to$ENDECA_MDEX_ROOT/binon UNIX.Enter the Dgidx command, such as
dgidx(on Windows) ordgidxon 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\endecaUNIX $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/endecaThis command points to the location of the Dgidx log, its DTD directory, and the Dgidx output file.
