DevSetup.md

Local Development Setup

Docker Containers

1. mssql - Restored MSSQL Server database pre-configured to work with RTR. Notable configurations 2. RTR User creation scripts applied 3. Change Data Capture (CDC) enabled for relevant databases and tables
2. kafka - Message broker
3. kafka-connect - Reads from the nrt_* topics and inserts into rdb_modern tables. The MSSQL JDBC sink connector is registered automatically by reporting-pipeline-service on startup from mssql-connector.json.
4. debezium - Reads Change Data Capture logs and posts messages to Kafka. Source connectors are registered automatically by reporting-pipeline-service on startup from connectors/debezium.
5. reporting-pipeline-service - Process Kafka messages for investigation, ldf, observation, organization, and person data (also handles key-uid mappings)

Prerequisites:

• Docker GHCR Authentication

Build and run the RTR services

docker compose up -d

Verifying functionality

1. Log into NBS 6 using the user: superuser. No password is required
2. Create a new patient
3. Add an investigation to the patient
4. View RDB_MODERN.D_PATIENT and RDB_MODERN.INVESTIGATION tables and verify the newly created patient and investigation are present.

Running SAS

A SAS container is present in the docker compose witht the sas profile. This means it will not start by default.

To start only the SAS container and its dependencies

docker compose up sas -d

To start all containers including SAS

docker compose --profile sas up -d

To execute the MasterETL script the following 1 liner can be used

# Executes the MasterEtl script from outside the SAS container
docker compose exec -u SAS -it sas sh -c '/opt/wildfly-10.0.0.Final/nedssdomain/Nedss/BatchFiles/MasterEtl.sh'

To log into the SAS container and run it from within the following steps can be taken:

# Connect to SAS container as the SAS user
docker compose exec -u SAS -it sas bash

# Run MasterEtl script
/opt/wildfly-10.0.0.Final/nedssdomain/Nedss/BatchFiles/MasterEtl.sh