Web Application - dcm4che/dcm4chee-arc-light GitHub Wiki

Overview

To access most of the DICOM Web Services and / or proprietary REST service of DCM4CHEE Archive services over UI, it is essential that the necessary web applications are configured. As most of the archive's REST services have an Application Entity Title in the path, it is essential that before configuring a web application a corresponding application entity is configured as well. For some services where there is a HL7 Application name in the path, corresponding HL7 applications need to be created first.

Configuration

Archive is pre-configured with following web applications which can be accessed by going to Devices -> dcm4chee-arc -> Device Extension -> Child Objects -> Web Application

AS_RECEIVED, AS_RECEIVED-WADO, DCM4CHEE, DCM4CHEE-WADO, IOCM_REGULAR_USE, IOCM_REGULAR_USE-WADO, IOCM_EXPIRED, IOCM_EXPIRED-WADO, IOCM_QUALITY, IOCM_QUALITY-WADO, IOCM_PAT_SAFETY, IOCM_PAT_SAFETY-WADO, IOCM_WRONG_MWL, IOCM_WRONG_MWL-WADO and dcm4chee-arc.

One may change the default Web Application(s) configured in the device either by :

Using Archive UI

Go to Menu -> Configuration -> Devices -> dcm4chee-arc -> Device Extension -> Child Objects -> Web Applications.
Select the web application whose Web Application name is to be changed. Change the value and Save.

Using LDAP

One may

create a LDIF file (e.g.):

  version: 1
  # LDIF for modifying the Web Application 
  # Adjust Base DN (dc=dc=dcm4che,dc=org), Device name (dcm4chee-arc), previous Web Application (DCM4CHEE),
  # new Web Application (MY_WEB_APP) before import it into the LDAP server
  dn: dcmWebAppName=DCM4CHEE,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  changetype: modrdn
  newrdn: dcmWebAppName=MY_WEB_APP
  deleteoldrdn: 1
  newsuperior: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org

and import it to the LDAP Server by using the ldapmodify command line utility.

or use the Rename Entry... function of Apache Directory Studio.

One should also rename the corresponding entry in the Unique Web Application Names Registry (e.g.):

    dn: dcmWebAppName=DCM4CHEE,cn=Unique Web Application Names Registry,cn=DICOM Configuration,dc=dcm4che,dc=org
    changetype: modrdn
    newrdn: dcmWebAppName=MY_WEB_APP
    deleteoldrdn: 1
    newsuperior: cn=Unique Web Application Names Registry,cn=DICOM Configuration,dc=dcm4che,dc=org

Go to the Control tab on Configuration page in archive UI and reload the configuration.

If you don't see the changed Web Application Name in other pages, try reloading the page (by pressing F5 in the most browsers).

Web Applications for new AEs of Archive

If one configures / clones an existing Application Entity of archive and intends to use this new AE for RESTful services, then one needs to configure / clone existing pre-configured Web Applications and associate this new Application Entity Title in the Web Service Path and AE Title fields of the newly configured / cloned Web Application.