The iText DITO Editor is a web application that runs in the browser. It is used to design iText DITO templates. 

Download Location

The iText DITO Editor can be downloaded from JFrog Artifactory: https://repo.itextsupport.com/webapp/#/artifacts/browse/tree/General/dito/com/itextpdf/dito/editor-server

Deployment and Configuration

Video Tutorial

This video explains how to download, install and configure iText DITO Editor, the template design component of the iText DITO framework. This video is aimed at system administrators and/or developers.

Step by Step

After you have downloaded the JAR file from JFrog Artifactory, you’ll need to set up a configuration file such as this one:

    - type: http
      port: 8080
    - type: http
      port: 8081
  level: INFO
  path: D:/DITOWork

As you can see, the editor uses two ports:

  • The first one (8080 in the above example), is used to access the web editor itself. Users of the application will connect through this port.
  • The second port (8081) is used for access to administrative features.

You can configure the ports manually, as long as the editor and the administrator connector use a different one. You should make sure the admin port isn’t accessible from outside the local trusted network. The workDirectory parameter specifies the directory that will be used for temporary storage. This parameter is required for the web editor application to work correctly, make sure the path is valid.

iText DITO uses the Dropwizard webserver in the back-end. If you need documentation detailing how to set up the https connection and how to add https certificates, you can refer to the Dropwizard configuration manual. In order to run the editor application, you need the following command:

java -jar dito-server.jar {server, check} config.yml

The server command starts the web application. As soon as it’s started, it should be available through the specified port. The check command makes sure the configuration file offers valid configuration data. If something is not working properly, you’ll see the errors printed.

As an administrator, you can access the health check feature. Health checks help you identify the cause of problems with the application. The feature is available through the administrator port:


The result of a health check is returned in JSON format.


Assuming everything works well, you’ll see {“healthy”:true} for all checks. If there is a problem, the JSON data will contain a message describing the problem. For example:

"workDirectory":{"healthy":false,"message":"Work directory does not exist"}