Run with .jar file


In order to run the application, the host needs to have the following installed:

  • Java JDK 11 or higher. The version can be checked with java --version.

Run with .jar file

One of the deployment options is to run jar file manually

java -jar app-[version].jar

After running the above command, the service with in-memory H2 database is running.

For production case it’s recommended to use a separate database instead of in-memory one. It can be done via environmental variables DB.URL, DB.USER, DB.PASSWORD, SQL.DIALECT.

java \
-DDB.URL=[jdbc url] \
-DDB.USER=[database user] \
-DDB.PASSWORD=[database password] \
-DSQL.DIALECT=Postgres \
-jar app-[version].jar

The default port is 8081. To change the port you can set the SERVER.PORT variable.

java -DSERVER.PORT=[port] -jar app-[version].jar

After running the above command, the terminal should show logging messages confirming the service is up:

01-04-2022 15:55:27.095 [main] INFO - Successfully released change log lock
01-04-2022 15:55:27.870 [main] INFO  o.s.b.a.e.web.EndpointLinksResolver.<init> - Exposing 1 endpoint(s) beneath base path '/actuator'
01-04-2022 15:55:27.907 [main] INFO  o.a.coyote.http11.Http11NioProtocol.log - Starting ProtocolHandler ["http-nio-8081"]
01-04-2022 15:55:27.914 [main] INFO  o.s.b.w.e.tomcat.TomcatWebServer.start - Tomcat started on port(s): 8081 (http) with context path ''
01-04-2022 15:55:27.923 [main] INFO - Started TestingSuiteEngineApiKt in 3.574 seconds (JVM running for 4.486)

Once the REST HTTP service is up and running, you can visit a Swagger UI by the following link:


You can find a list of supported Application Properties.