How to debug the DITA-OT Server

The DITA-OT Server is easily debugged by a local DITA-OT implementation, for example working on a oXygen plateform. For a server debugging, all intermediate steps are located in differents temporary directories.

• Debugging with a local oXygen implementation:

  No specific requirements: the DITA-OT tree structure needs to be the same onto the server and locally.

  Note: As soon as you add a new plugin to your local implementation, remember to also run the dita --install command on the DITA-OT Server.

  Attention: If you debug on Windows and have your server on linux, you may face "carriage return" encoding problems. So, if you change any ant build file of any plugin of the local implementation, be sure to also run the dita --install command on the DITA-OT Server when you deploy your modifications. This is not needed for XSLT or CSS modifications.
• Debugging the Componize process:
  • First look at the log file detecting any specific problem.

  • It may be useful to look at the files that Componize server will make available to the DITA-OT Server.

    All the source files, the ditamap and anything referenced directly or indirectly by the ditamap, are copied to a temporary folder on disk. The temp directory of the Componize server, contains folders named like XProcPipelineService1518958057983166493.

  • It may also be usefull to look at the temp and output directories of the DITA-OT Server.

    The DITA-OT Server uses it's own temp directory in foders such as : /home/componize-temp/dita-ot/jobs/704/builds/1/temp. The result is stored in folder such as or /home/componize-temp/dita-ot/jobs/704/builds/1/out.