Embedding in dcm4chee

This page describes how installing Weasis to be the default web viewer of dcm4chee web interface. See How to launch Weasis from any environments to integrate Weasis into your own user interface.

Weasis is launched from the dcm4chee administrative web interface with the weasis protocol, as shown in the pictures below.

The documentation where Weasis is launched with Java Webstart is still available here.

For dcm4chee-arc-light

dcm4chee-arc-light

An alternative configuration without weasis-pacs-connector and with dcm4chee DICOMWeb services is possible (No need to consider the following points), it requires only the installation of Weasis 3.5.4 or superior.

  1. Install dcm4chee, if not already done (Installation with Docker is straightforward).

  2. Go here and download these following files:

    Download issue: Some browsers (like Internet Explorer) may rename war files to zip. If so, use the Save As option when downloading and change the name back to war.

    • From weasis-pacs-connector folder:
      • [weasis-pacs-connector.war] Requires at least the version 7.1.1
    • From the folder with the latest version number (Optional if you want to run only the native version installed on the client system):
      • [weasis.war] requires at least Weasis 3.5.3
      • [weasis-i18n.war] Optional for internationalization
      • [weasis-ext.war] Optional package for additional plug-ins (e.g. exporting the images to build an ISO image for CD/DVD)
    • From the folder with the latest version number:
  3. Open the wildfly management console (at http://<your-host>:9990).

    • Select the “Deployments” tab
    • Add the .war files using the “Add” button (Choose Upload a new deployment or select Replace when the file already exists)

      Alternatively one may deploy .war files using JBoss Command Line Interface Console.

  4. Configure weasis-pacs-connector (This step is optional if you just want to keep the default configuration).
    The default configuration is stored in two files inside weasis-pacs-connector.war. To override the default configuration:

    • Download the current weasis-pacs-connector.properties and dicom-dcm4chee-arc.properties (configuration of the dcm4chee archive)
    • Edit the configuration as needed. For example, dcm4chee may be running on a different computer than Weasis, or the AE Title of dcm4chee may have been changed. If so, edit weasis-pacs-connector.properties or dicom-dcm4chee-arc.properties (Change pacs.host, pacs.port, and pacs.aet).
    • Copy weasis-pacs-connector.properties and dicom-dcm4chee-arc.properties into $WILDFLY_HOME/standalone/configuration (where $WILDFLY_HOME is the path of the running Wildfly).
      With the docker installation use the docker copy command ($ docker cp …)

      Instead of copying the files into $WILDFLY_HOME/standalone/configuration, JBoss Command Line Interface Console can be used to override files in the war. Add the two configuration files with the deployment-overlay command:

      deployment-overlay add --name=dcm4chee-arc --deployments=weasis-pacs-connector.war --content=WEB-INF/classes/weasis-connector-default.properties=/tmp/weasis-pacs-connector.properties,WEB-INF/classes/dicom-dcm4chee-arc.properties=/tmp/dicom-dcm4chee-arc.properties --redeploy-affected
    • For applying the new configuration, from the management console “Disable” weasis-pacs-connector.war and then “Enable”
  5. To activate Weasis in dcm4chee-arc-light user interface (see the matrix of the required versions, you need need to changes two attributes in the configuration

    • Go to the configuration or from Configuration > Devices > dcm4chee-arc > Extensions > Archive Device  And fill up the following properties (add &cdb if weasis.war has not been deployed) : 

      • Invoke Image Display Patient URL: ../../weasis-pacs-connector/weasis?&patientID={}&target=_self&access_token={}
      • Invoke Image Display Study URL: ../../weasis-pacs-connector/weasis?&studyUID={}&target=_self&access_token={}

        &access_token={} is necessary in secure mode (secured RESTful services) from dcm4chee-arc-light 5.15.1
        &target=_self avoids to open a new empty window in the web browser
        &cdb cdb parameter to override the URL of the Weasis web context to null (when you want only the native local version or when weasis.war has not be deployed)
        See also Invoke Image Display in dcm4chee

        Absolute path: The values above starting by “../” are the default relative path when weasis-pacs-connector is installed in the same JBoss as dcm4chee. Otherwise replace the relative URL by an absolute value, ex: http://<your-host>:<port>/weasis-pacs-connector/...

    • Optional: add other properties in the URL.

    • Refresh the web page and the view button should appear as in the screenshot above

    • To launch the viewer from the web portal, the client computer must have installed the Weasis package on the operating system.


For dcm4chee-web3

dcm4chee-web3

  1. Install dcm4chee (2.18.3 recommended), if not already done. For security see also how to limit the server access.

  2. Go here and download these following files.

    Download issue: Some browsers (like Internet Explorer) may rename war files to zip. If so, use the Save As option when downloading and change the name back to war.

    • From weasis-pacs-connector folder:
      • [weasis-pacs-connector.war] Requires at least the version 6.1.5, the version 7.x is not supported
      • [dcm4chee-web-weasis.jar]
    • From the folder with the latest version number (Optional if you want to run only the native version installed on the client system):
      • [weasis.war] requires at least Weasis 3.5.3
      • [weasis-i18n.war] Optional for internationalization
      • [weasis-ext.war] Optional package for additional plug-ins (e.g. exporting the images to build an ISO image for CD/DVD)
  3. Place these files in the dcm4chee deploy folder (server/default/deploy/).

  4. To activate Weasis, go to the JMX console (at http://<your-host>:8080/jmx-console)

    • In dcm4chee.web select service=WebConfig and set these two values:
      WebviewerNames = weasis
      WebviewerBaseUrl = weasis:/weasis-pacs-connector/weasis

      This configuration allows launching Weasis with the weasis protocol that requires the installation of the native client..

    • Click the Apply Changes button
  5. Configure Weasis (This step is optional if you just want to keep the default configuration. It is required when the AETitle DCM4CHEE has been changed) The default configuration is stored in two files inside weasis-pacs-connector.war. To override the default configuration:

    •  Download the current weasis-connector-default.properties and rename it weasis-pacs-connector.properties, and download dicom-dcm4chee.properties (configuration of the dcm4chee archive)
    • Copy the files into a folder in the classpath of the servlet container. In JBoss (inferior to version 7), the best location would typically be server/default/conf.
    • Edit the configuration as needed. For example, dcm4chee may be running on a different computer than Weasis, or the AE Title of dcm4chee may have been changed.

      If so, edit weasis-pacs-connector.properties or dicom-dcm4chee.properties (e.g. pacs.host, pacs.port, pacs.aet…)

  6. That’s all, now restart dcm4chee. To launch the viewer from the dcm4chee-web3 portal, the client computer must have installed the Weasis package on the operating system.