Exercise 1.1 - Process Debugging

Exercise 1.1 - Process Debugging

This exercise looks at how to use the Java debugger of your IDE to remote debug the execution of a process plugin.

Introduction

The DSF FHIR server and the DSF BPE server applications are written in Java and as such are execute on a headless JRE 11 within their docker containers. Command line arguments can be passed to the JVM inside the ghcr.io/highmed/fhiropen in new window and ghcr.io/highmed/bpeopen in new window docker images by specifying the environment variable EXTRA_JVM_ARGS. This can be used for example to configure the minimum and maximum heap of the JVM; but can also be used to specify a remote debugging port, which we will use in this exercise.

An EXTRA_JVM_ARGS environment variable is already configure for all DSF FHIR server and DSF BPE server docker containers in the tutorial docker-compose test setup. Take a look at the docker-compose.yml file to lookup the port numbers specified for the different DSF FHIR and DSF BPE servers.

Exercise Tasks

Start the DSF FHIR server for the Test_DIC organization in a console at location .../dsf-process-tutorial/test-setup:

docker-compose up dic-fhir

Start the DSF BPE server for the Test_DIC organization in second console at location .../dsf-process-tutorial/test-setup:

docker-compose up dic-bpe

Configure your Java IDE for remote debugging

Eclipse:
IntelliJ:

Create a debug breakpoint in the first line of the HelloDic class doExecute method.
Start your previously defined remote Java debugger in your IDE.
Execute the TutorialExampleStarter class to start highmed_helloDic process.
User your IDE's debugger to step thru the code of the HelloDic class doExecute method.

Continue with Exercise 2.