Generating Project Documentation


Any Jedox Integrator project can generate documentation that contains an alphabetical list of all components with type, descriptions, and references. A graphic flow chart of a user-specified list of jobs for this project can be included in the documentation. It is possible to navigate within the generated documentation to the referenced components.

Project documentation generation is currently available via the Jedox Integrator Command Line Client (CLI). In a forthcoming release, it will also be integrated in the Jedox Integrator.


etlclient -pd <projectname> -j <jobname1> <jobname2> …. -o <directory>


  1. Create project documentation for project sampleBiker without flow graphs in directory C:\EtlDoku1:
    etlclient -pd sampleBiker -o C:\EtlDoku1
  2. Create project documentation for project sampleBiker with flow graphs of job Masterdata and Cubedata:
    etlclient -pd sampleBiker -j Masterdata Cubedata -o C:\EtlDoku2
  3. Create documentation for job Cubedata in project sampleBiker. It only contains the referenced components of this job and the flow graph of job Cubedata:
    etlclient -pd -o C:\EtlDoku3

The documentation can be displayed by opening file etldocumentation.html with a browser. Note that Internet Explorer 9 doesn’t display the graphical flow graph due to insufficient support for the SVG format.

The following files are generated in the output directory:

etldoc.xml Contains all project- and component-related information, SVG flow graphs, references, and all component fields (references etldoc.xslt).
etldoc.xslt The XSTL transformation of etldoc.xml. By adapting this file, the layout and content of the documentation can be modified (references etldoc.css).
etldoc.css A style sheet (references etldoc_bg.png).
etldoc_bg.png A background image.
etldocumentation.html The documentation file to be displayed in the browser. Technically, it is etldoc.xslt transformation applied to etldoc.xml (requires only files etldoc.css and etldoc_bg.png).
Was this post helpful?
NoYes (+1 rating, 1 votes)