Upgrade from DSF 1.9.0
DSF 2.0 Release Candidate
This is a pre-release version of the Data Sharing Framework (DSF) 2.0.
Please do not use this version in production environments.
We kindly invite experienced DSF administrators to test this release on their staging or test instances and share their feedback with us through the usual communication channels.
Thank you for helping us improve the DSF!
Upgrading the DSF from 1.9.0 to 2.0.0-RC2 involves modifying the docker-compose.yml files and recreating the containers.
Update to DSF 1.9.0 first
When upgrading from DSF version < 1.9.0 it is important to migrate to DSF 1.9.0 first.
Modify DSF FHIR Server Setup
Preparation / Backup
- We recommend to create a backup of the
/opt/fhirdirectory before proceeding with the upgrade.
For example using:sudo cp -rp /opt/fhir /opt/fhir_backup_pre_2.0.0-RC2_upgrade
- We recommend to create a backup of the
Modify the DSF FHIR docker-compose.yml file, replace the version number with 2.0.0-RC2.
version: '3.8'
services:
proxy:
- image: ghcr.io/datasharingframework/fhir_proxy:1.9.0
+ image: ghcr.io/datasharingframework/fhir_proxy:2.0.0-RC2
restart: on-failure
...
app:
- image: ghcr.io/datasharingframework/fhir:1.9.0
+ image: ghcr.io/datasharingframework/fhir:2.0.0-RC2
restart: on-failure
...
environment:
- DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT: f4344032fe77bffb...
...The environment variable DEV_DSF_FHIR_SERVER_ORGANIZATION_THUMBPRINT does not need to be specified starting version 2.0.0-RC2. The thumbprint is now calculated based on the client certificate specified via DEV_DSF_FHIR_CLIENT_CERTIFICATE.
- Upgrade the DSF FHIR containers
From/opt/fhirexecutedocker compose up -d && docker compose logs -f
Modify DSF BPE Server Setup
Preparation / Backup
- We recommend to create a backup of the
/opt/bpedirectory before proceeding with the upgrade.
For example using:sudo cp -rp /opt/bpe /opt/bpe_backup_pre_2.0.0-RC2_upgrade
- We recommend to create a backup of the
Modify the DSF BPE docker-compose.yml file, replace the version number with 2.0.0-RC2.
version: '3.8'
services:
app:
- image: ghcr.io/datasharingframework/bpe:1.9.0
+ image: ghcr.io/datasharingframework/bpe:2.0.0-RC2
restart: on-failure
...
environment:
- DEV_DSF_BPE_DB_USER_CAMUNDA_PASSWORD_FILE: /run/secrets/db_user_camunda.password
+ DEV_DSF_BPE_DB_USER_ENGINE_PASSWORD_FILE: /run/secrets/db_user_camunda.password
...Upgrade the DSF BPE containers
From/opt/bpeexecutedocker compose up -d && docker compose logs -fVerify your upgrade:
- Verify the DSF FHIR server is running in version 2.0.0-RC2. The log should contain a message:
INFO main - BuildInfoReaderImpl.logBuildInfo(137) | Artifact: dsf-fhir-server-jetty, version: 2.0.0-RC2, [...] - Verify the DSF FHIR server started without errors
- Verify the DSF FHIR server is accessible via https, for example by browsing to https://your-dsf-endpoint.de/fhir/ (authentication with your client-certificate)
- Verify the DSF BPE server is running in version 2.0.0-RC2. The log should contain a message:
INFO main - BuildInfoReaderImpl.logBuildInfo(137) | Artifact: dsf-bpe-server-jetty, version: 2.0.0-RC2, [...] - Verify the DSF BPE server started without errors
- Verify your install with a ping/pong test
- Verify the DSF FHIR server is running in version 2.0.0-RC2. The log should contain a message: