Deploying the DQM


The DQM is a web based application hosted on a local server or cloud. 
There a two deployment options:

Docker container

Java WAR file

The minimum requirements for the server or cloud instance hosting the application are as follows:
CPU: 2 core
HDD: A minimum of 10GB of free space

Note: When hosting application from WAR file, Java 11 is required

Deploying/updating the DQM using WAR file

Download the latest version of WAR from
To run WAR application, use command:

java -XX:TieredStopAtLevel=1 -Dspring.jmx.enabled=false -Xmx4g -Dserver.port=8090 -jar LiTech_DQM_2023.3.war

-Xmx4g – Specifies the amount of memory that can be used by Java – in this case 4GB
-Dserver.port=8090 – Defining DQM’s machine port

It is recommended to run the Java file as a service.
Java application as a service on Ubuntu
Java application as a service on Windows

Deploying the DQM using docker image

For hosting your application on your cloud instance, make sure you have a connection to docker hub.

NB! When running in container mode, it is important to run one node per instance. In current state DQM does not support multiple nodes per instance (for example when running in kubernetes cluster)

1. Docker pull LiTech DQM image:

docker pull litech/tester:latest

Note: Please check for available versions

2. Run DQM container:

Note: “-e JAVA_OPTIONS=’-Xmx4g’” is optional. It is recommended to specify maximum heap size (4GB recommended)

docker run -d   
-v {local_path}/logs:/usr/app/logs        
-v {local_path}/database:/usr/app/database
-v {local_path}/drivers:/usr/app/drivers
-v {local_path}/keys:/usr/app/keys                    
-p 8090:8090 
-e –server.port=8090 
-e JAVA_OPTIONS=’-Xmx4g’

-v {local_path}/logs:/usr/app/logs
Mapping of logs folder for DQM user and SQL log files. Needed for persisting logs.

-v {local_path}/database:/usr/app/database
Mapping of database folder for local database files. Needed for persisting local database.

-v {local_path}/drivers:/usr/app/drivers  
Mapping of drivers folder for JDBC driver files. Needed for persisting JDBC drivers uploaded to DQM.

-v {local_path}/keys:/usr/app/keys  
Mapping of keys folder for certificates. Needed for persisting all certificates uploaded to DQM.

-p 8090:8090
Mapping of DQM port 8090 to machine port 8090

-e –server.port=8090
Defining DQM machine port (By default container port will be 8090, this wont be needed)

Image id for “litech/tester” image. You can also directly use image name “litech/tester:2022.10”

3. Validate that DQM container is running:

docker ps

4. If the container is now up and running, you have successfully started the DQM

Deploying the DQM using docker compose

Easiest way is to deploy via docker compose file


version: "3.7"
    container_name: litech-tester
    image: litech/tester:2023.3
      - 8090:8090
      - ./logs:/usr/app/logs
      - ./database:/usr/app/database
      - ./drivers:/usr/app/drivers
      - ./keys:/usr/app/keys
      JAVA_OPTIONS: -Xmx4g

Updating from older image

Please create and download a backup of your database before proceeding. (see chapter Database settings)

1. Pull the new docker image

docker pull litech/tester:latest

2. Kill the older docker container (data is kept because you have already mapped your volumes).

docker kill {container_id}

Note: You can get container id with “docker container ps –all”

3. (Optional) Remove the old container.  You might want to keep it as a backup if the newer version has some unexpected errors.

docker rm {container_id}

4. Run the new pulled container. See chapter Deploying the DQM using docker image

Updating from older image via docker compose

1. Change image in your docker-compose.yml

image: litech/tester:XXXX.XX

2. Pull new image via docker compose

docker compose pull

3. Launch new image via docker compose

docker compose up -d


Logging in for the first time

The DQM is available from your machine address with specified port:

Please use Chrome web browser to access the DQM.

Use default credentials to log in for the first time:

Username: admin
Password: admin
  1. Log in using provided credentials (you will be redirected to the License page. Enter the license key provided)
  2. After logging in, change admin password in Settings -> Users:
  1. Click “Save changes”