Date: Thu, 28 Mar 2024 13:41:14 +0000 (UTC) Message-ID: <620194423.5.1711633274909@4d2df846cd86> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_599109745.1711633274908" ------=_Part_4_599109745.1711633274908 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The dcm4chee-wizard is a web-application that provides a graphical user = interface for configuration of DICOM devices compliant to the DICOM App= lication Configuration Management Profile, specified in DICOM 2011, Part 15, Annex H.
In addition to the configuration of basic DICOM devices, the application= has been extended to allow for the configuration of dcm4che specific DICOM= implementations, such as the DICOM proxy (dcm4chee-proxy) and XDS.b applic= ations (dcm4chee-xds, included in version 1.1.0).
Supported configuration backends include LDAP and Java Pref= erences.
Building the dcm4chee-wizard and dependencies requires Maven 3.
Before building dcm4chee-wizard, check out and build the following proje= cts:
> mv= n install -P {standalone|proxy|jdbc|jdbc-proxy}
standalone: basic web-app with configuration options for suppor=
ted devices
proxy: in addition to standalone includes =
dcm4chee-proxy web-application (bundle)
jdbc: in addition to
dcm4che-jdbc-prefs, a wrapper for storage of Java Prefe=
rences data in a SQL backend.
jdbc-proxy: combination of pr=
oxy and jdbc profiles
To run dcm4chee-wizard within JBoss AS7 requires dcm4che-jboss-modules t= o be installed, which can be found in the dcm4che-3.x DICOM Toolkit (https://github.com/dcm4che/dcm4che).
Unpack dcm4che-jboss-modules-<version>.zip
into the J=
Boss AS7 folder.
Create a directory dcm4chee-wizard
inside the container con=
figuration directory (e.g. <jbossDir>/standalone/configuration/=
dcm4chee-wizard
) and copy all files from dcm4chee-wizard/dcm4c=
hee-wizard-war/src/main/etc/
into it.
Alternatively, specify the directory path with the 'dcm4chee-wizard.cfg.=
path' system property.
Strings specified with
${property.name}
will be evaluated accordingly.
If planned to use Java Preferences as configuration backend, delete the =
file ldap.properties
from <jbossDir>/standalone/co=
nfiguration/dcm4chee-wizard/
.
If planned to use a LDAP configuration backend, edit the file <=
jbossDir>/standalone/configuration/dcm4chee-wizard/ldap.properties
and set the connection and authentication parameters according to the LDA=
P server configuration.
To run dcm4chee-wizard in a JBoss AS7 instance, deploy dcm4chee-wi=
zard/dcm4chee-wizard-war/target/dcm4chee-wizard-war-<version>.war via the JBoss command line interface or by copying it into e.g.
&=
lt;jbossDir>/standalone/deployments/
.
Example:
i) make sure the JBoss instance is running
ii) start the command line interface: <jbossDir>/bin/jboss-c=
li.sh -c
iii) call the deploy procedure: deploy <buildPath>/dcm4chee-=
wizard-war-<version>.war
For each device with network services supported by the wizard (currently=
dcm4chee-proxy and dcm4chee-xds), configure the following system property =
in the container configuration (e.g. <jbossDir>/standalone/conf=
iguration/standalone.xml
):
<sys= tem-properties> <property name=3D"org.dcm4chee.device.<device-name= >" value=3D"http://<device-url>"/> </system-properties>
Example:
In case the wizard was compiled with the profile 'proxy', the bundled pr= oxy application can be configured as followed:
<sys= tem-properties> <property name=3D"org.dcm4chee.device.dcm4chee-proxy"= value=3D"http://${jboss.bind.address}:${jboss.bind.port}/dcm4chee-wizard/p= roxy-application"/> </system-properties>
Use the 'New Device' button to create a configuration for a network enti= ty. Supported configuration types are described below.
A basic device can be used to describe network entities such as modaliti= es or workstation. The available configuration options are based on the DIC= OM standard and include DICOM device parameters, network connection paramet= ers, DICOM network application entity parameters including transfer capabil= ities supported by the AET, as well as HL7 application parameters.
A proxy device extends the basic device with support for dcm4chee-proxy spe= cific configuration options.
Allows configuration of filter rules to be applied on incoming data
Attributes:
Allows configuration of sending options for destination AET
Attributes:
Allows configuration of retry conditions
Attributes:
Definition of coercion templates
Attributes:
Provides a network entity for audit loggers to send data to.