You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exercises/exercise-1.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -103,7 +103,7 @@ To verify the `dsfdev_dicProcess` can be executed successfully, we need to deplo
103
103
```
104
104
docker-compose up dic-fhir
105
105
```
106
-
Verify the DSF FHIR server started successfully. You can access the webservice of the DSF FHIR server at https://dic/fhir.
106
+
Verify the DSF FHIR server started successfullyat https://dic/fhir.
107
107
The DSF FHIR server uses a server certificate that was generated during the first maven install build.
108
108
To authenticate yourself to the server you can use the client certificate located at `.../dsf-process-tutorial/test-data-generator/cert/dic-client/dic-client_certificate.p12` (Password: `password`).
109
109
Add the certificate and the generated Root CA located at `.../dsf-process-tutorial/test-data-generator/cert/ca/testca_certificate.pem` to your browser certificate store.
# Exercise 2 - Environment Variables and Input Parameters
@@ -82,7 +82,7 @@ To verify the `dsfdev_dicProcess` can be executed successfully, we need to deplo
82
82
```
83
83
docker-compose up dic-fhir
84
84
```
85
-
Verify the DSF FHIR server started successfully.
85
+
Verify the DSF FHIR server started successfully at https://dic/fhir.
86
86
87
87
2. Start the DSF BPE server for the `dic.dsf.test` organization in second console at location `.../dsf-process-tutorial/dev-setup`:
88
88
```
@@ -104,4 +104,4 @@ To verify the `dsfdev_dicProcess` can be executed successfully, we need to deplo
104
104
Also check that modification to the [Task](../learning/concepts/fhir/task.md) input parameter specified in the `TutorialExampleStarter` class, have the appropriate effect on your log message.
@@ -54,14 +54,14 @@ Verify that the build was successful and no test failures occurred.
54
54
### Process Execution and Manual Tests
55
55
To verify the `dsfdev_dicProcess` and `dsfdev_cosProcess`es can be executed successfully, we need to deploy them into DSF instances and execute the `dsfdev_dicProcess`. The maven `install` build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker dev setup.
56
56
Don't forget that you will have to add the client certificate for the `COS` instance to your browser the same way you added it for the `DIC` instance
57
-
in [exercise 1](exercise-1.md) or use the Keycloak user you created in [exercise 3](exercise-3.md) for the `cos` realm. Otherwise, you won't be able to access [https://cos/fhir](https://cos/fhir). You can find the client certificate
57
+
in [exercise 1](exercise-1.md) or use the Keycloak user `Tyler Tester` with username `test` and password `test`. Otherwise, you won't be able to access [https://cos/fhir](https://cos/fhir). You can find the client certificate
58
58
in `.../dsf-process-tutorial/test-data-generator/cert/cos-client/cos-client_certificate.p12` (password: password).
59
59
60
60
1. Start the DSF FHIR server for the `dic.dsf.test` organization in a console at location `.../dsf-process-tutorial/dev-setup`:
61
61
```
62
62
docker-compose up dic-fhir
63
63
```
64
-
Verify the DSF FHIR server started successfully.
64
+
Verify the DSF FHIR server started successfully at https://dic/fhir.
65
65
66
66
2. Start the DSF BPE server for the `dic.dsf.test` organization in another console at location `.../dsf-process-tutorial/dev-setup`:
67
67
```
@@ -73,7 +73,7 @@ in `.../dsf-process-tutorial/test-data-generator/cert/cos-client/cos-client_cert
73
73
```
74
74
docker-compose up cos-fhir
75
75
```
76
-
Verify the DSF FHIR server started successfully. You can access the webservice of the DSF FHIR server at https://cos/fhir. To authenticate yourself to the server you can use the client certificate located at `.../dsf-process-tutorial/test-data-generator/cert/cos-client/cos-client_certificate.p12` (Password: `password`).
76
+
Verify the DSF FHIR server started successfullyat https://cos/fhir.
77
77
78
78
4. Start the DSF BPE server for the `cos.dsf.test` organization in another console at location `.../dsf-process-tutorial/dev-setup`:
79
79
```
@@ -87,4 +87,4 @@ in `.../dsf-process-tutorial/test-data-generator/cert/cos-client/cos-client_cert
87
87
Verify that a FHIR [Task](../learning/concepts/fhir/task.md) resource was created at the DSF FHIR server of the `cos.dsf.test` organization and the `dsfdev_cosProcess` was then executed by the DSF BPE server of the `cos.dsf.test` organization.
@@ -34,7 +34,7 @@ To verify the `dsfdev_dicProcess` and `dsfdev_cosProcess`es can be executed succ
34
34
```
35
35
docker-compose up dic-fhir
36
36
```
37
-
Verify the DSF FHIR server started successfully.
37
+
Verify the DSF FHIR server started successfully at https://dic/fhir.
38
38
39
39
2. Start the DSF BPE server for the `dic.dsf.test` organization in a second console at location `.../dsf-process-tutorial/dev-setup`:
40
40
```
@@ -46,7 +46,7 @@ To verify the `dsfdev_dicProcess` and `dsfdev_cosProcess`es can be executed succ
46
46
```
47
47
docker-compose up cos-fhir
48
48
```
49
-
Verify the DSF FHIR server started successfully.
49
+
Verify the DSF FHIR server started successfully at https://cos/fhir.
50
50
51
51
4. Start the DSF BPE server for the `cos.dsf.test` organization in a fourth console at location `.../dsf-process-tutorial/dev-setup`:
52
52
```
@@ -59,4 +59,4 @@ To verify the `dsfdev_dicProcess` and `dsfdev_cosProcess`es can be executed succ
59
59
Verify that the `dsfdev_dicProcess` was executed successfully by the `dic.dsf.test` DSF BPE server and possibly the `dsfdev_cosProcess` by the `cos.dsf.test` DSF BPE server, depending on whether decision of your algorithm based on the input parameter allowed to start the `dsfdev_dicProcess`.
# Exercise 6 - Event Based Gateways and Intermediate Events
@@ -47,14 +47,14 @@ Verify that the build was successful and no test failures occurred.
47
47
### Process Execution and Manual Tests
48
48
To verify the `dsfdev_dicProcess`, `dsfdev_cosProcess` and `dsfdev_hrpProcess`es can be executed successfully, we need to deploy them into DSF instances and execute the `dsfdev_dicProcess`. The maven `install` build is configured to create a process jar file with all necessary resources and copy the jar to the appropriate locations of the docker dev setup.
49
49
Don't forget that you will have to add the client certificate for the `HRP` instance to your browser the same way you added it for the `DIC` and `COS` instances
50
-
in [exercise 1](exercise-1.md) and [exercise 4](exercise-5.md) or use the Keycloak user you created in [exercise 3](exercise-3.md) for the `hrp` realm. Otherwise, you won't be able to access [https://hrp/fhir](https://hrp/fhir). You can find the client certificate
50
+
in [exercise 1](exercise-1.md) and [exercise 4](exercise-5.md) or use the Keycloak user `Tyler Tester` with username `test` and password `test`. Otherwise, you won't be able to access [https://hrp/fhir](https://hrp/fhir). You can find the client certificate
51
51
in `.../dsf-process-tutorial/test-data-generator/cert/hrp-client/hrp-client_certificate.p12` (password: password).
52
52
53
53
1. Start the DSF FHIR server for the `dic.dsf.test` organization in a console at location `.../dsf-process-tutorial/dev-setup`:
54
54
```
55
55
docker-compose up dic-fhir
56
56
```
57
-
Verify the DSF FHIR server started successfully.
57
+
Verify the DSF FHIR server started successfully at https://dic/fhir.
58
58
59
59
2. Start the DSF BPE server for the `dic.dsf.test` organization in a second console at location `.../dsf-process-tutorial/dev-setup`:
60
60
```
@@ -66,7 +66,7 @@ in `.../dsf-process-tutorial/test-data-generator/cert/hrp-client/hrp-client_cert
66
66
```
67
67
docker-compose up cos-fhir
68
68
```
69
-
Verify the DSF FHIR server started successfully.
69
+
Verify the DSF FHIR server started successfully at https://cos/fhir.
70
70
71
71
4. Start the DSF BPE server for the `cos.dsf.test` organization in a fourth console at location `.../dsf-process-tutorial/dev-setup`:
72
72
```
@@ -79,7 +79,7 @@ in `.../dsf-process-tutorial/test-data-generator/cert/hrp-client/hrp-client_cert
79
79
```
80
80
docker-compose up hrp-fhir
81
81
```
82
-
Verify the DSF FHIR server started successfully. You can access the webservice of the DSF FHIR server at https://hrp/fhir. To authenticate yourself to the server you can use the client certificate located at `.../dsf-process-tutorial/test-data-generator/cert/hrp-client/hrp-client_certificate.p12` (Password: `password`).
82
+
Verify the DSF FHIR server started successfullyat https://hrp/fhir.
83
83
84
84
6. Start the DSF BPE server for the `hrp.dsf.test` organization in a sixth console at location `.../dsf-process-tutorial/dev-setup`:
85
85
```
@@ -99,4 +99,4 @@ in `.../dsf-process-tutorial/test-data-generator/cert/hrp-client/hrp-client_cert
99
99
Verify that the `dsfdev_dicProcess` either finishes with the arrival of the `goodbyeDic` message or after waiting for two minutes.
0 commit comments