DCM4CHEE Archive 5.x

DCM4CHEE Archive 5.x is a DICOM Archive Java EE application designed to run in WildFly.

A core architectural feature of version 5.x is the use of LDAP as central configuration, which complies with the DICOM Application Configuration Management Profile (DICOM 2015, Part 15, Annex H). This replaces the configuration methods used in the 2.x series.

To build the Archive, you must have Java 17 (JDK) or newer installed.

If you are building unreleased versions that are not yet in the Maven repository, you must first build the dcm4che 3 Library and dcm4chee-arc-lang from their respective master branches.

Follow these steps to build the Archive for a specific database using Maven.

# 1. Build dcm4che 3 Library (if needed)
git clone https://github.com/dcm4che/dcm4che.git
cd dcm4che
./mvnw install

# 2. Build dcm4chee-arc-lang (if needed)
git clone https://github.com/dcm4che/dcm4chee-arc-lang.git
cd dcm4chee-arc-lang
./mvnw install

# 3. Build the Archive for a specific database
# Replace {db} with: db2, firebird, h2, mysql, oracle, psql, or sqlserver
./mvnw install -D db={db}

To ensure the Angular development server correctly maps requests for /assets/schema to the Apache-served files, update your Angular proxy configuration with the following mapping. This rewrites the path to include the language prefix used by Apache.

"/assets/schema": {
  target: "http://localhost",
  pathRewrite: {
    "^/assets/schema": "/dcm4chee-arc-lang/en/assets/schema"
  }
}

When building the Archive, you can specify security levels for the Web UI and RESTful services using the -D secure flag.

Available options:

• ui: Builds with a secured WEB UI.
• all: Builds with both a secured WEB UI and secured RESTful services.

# Build with secured WEB UI
./mvnw install -D db={db} -D secure=ui

# Build with secured WEB UI and secured RESTful services
./mvnw install -D db={db} -D secure=all

After completing the Apache setup, verify that the schema files are accessible by navigating to a schema JSON file in your browser. Replace the path with a valid schema file from your dcm4chee-arc-lang workspace.

http://localhost/dcm4chee-arc-lang/en/assets/schema/device.schema.json

The project provides a suite of SQL scripts to manage the PostgreSQL database lifecycle for DCM4CHEE Archive. These include scripts for initial creation, index management, and version-specific updates.

Core PostgreSQL Scripts

• create-psql.sql: Used for initial database creation.
• create-fk-index.sql: Used to create foreign key indexes.
• create-case-insensitive-index.sql: Used to create case-insensitive indexes.
• drop-psql.sql: Used to drop the database schema.

Version Update Scripts

When upgrading the archive, use the corresponding update script for your target version (e.g., update-5.34-psql.sql). These scripts are located in the dcm4chee-arc-entity/src/main/resources/sql/ directory of the repository.

### PostgreSQL Script Reference
- create-psql.sql
- create-fk-index.sql
- create-case-insensitive-index.sql
- drop-psql.sql
- update-[VERSION]-psql.sql

DCM4CHEE Archive 5.x provides a set of SQL scripts to manage the MySQL database schema. Use these scripts for initial creation, dropping the schema, or performing version-specific updates.

Available Scripts

• Creation: create-mysql.sql for initial schema setup.
• Deletion: drop-mysql.sql to remove the schema.
• Updates: Version-specific update scripts (e.g., update-5.34-mysql.sql) to migrate the database from one version to another. These are located in the dcm4chee-arc-entity module resources.

DCM4CHEE Archive 5.x provides specialized SQL scripts for Oracle database environments. These include scripts for schema creation, index optimization, and versioned updates.

Available Scripts

• Creation: create-oracle.sql for initial schema setup.
• Optimization:
  • create-fk-index.sql: Creates indexes for foreign keys.
  • create-case-insensitive-index.sql: Creates case-insensitive indexes.
• Deletion: drop-oracle.sql to remove the schema.
• Updates: Version-specific update scripts (e.g., update-5.34-oracle.sql) to migrate the database. These are located in the dcm4chee-arc-entity module resources.