...
To run dcm4chee-wizard within JBoss AS7 requires dcm4che-jboss-modules to 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 JBoss AS7 folder.
...
Create a directory dcm4chee-wizard inside the container configuration directory
(e.g. <jbossDir>/standalone/configuration/dcm4chee-wizard)
and copy all files from dcm4chee-wizard/dcm4chee-wizard-war/src/main/etc/ into it.
Alternatively, specify the directory path with the 'dcm4chee-wizard.cfg.path' system property.
Strings specified with
...
will be evaluated accordingly.
If planned to use Java Preferences as configuration backend, delete the file
ldap.properties from <jbossDir>/standalone/configuration/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 LDAP server configuration.
...
To run dcm4chee-wizard in a JBoss AS7 instance, deploy dcm4chee-wizard/dcm4chee-wizard-war/target/dcm4chee-wizard-war-<version>.war
via the JBoss command line interface or by copying it into e.g. <jbossDir>/standalone/deployments/.
...
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/configuration/standalone.xml):
| Code Block |
|---|
<system-properties>
<property name="org.dcm4chee.device.<device-name>" value="http://<device-url>"/>
</system-properties>
|
Example:
In case the wizard was compiled with the profile 'proxy', the bundled proxy application
can be configured as followed:
| Code Block |
|---|
<system-properties>
<property name="org.dcm4chee.device.dcm4chee-proxy" value="http://${jboss.bind.address}:${jboss.bind.port}/dcm4chee-wizard/proxy-application"/>
</system-properties>
|
Configuration
Use the 'New Device' button to create a configuration for a network entity.
Supported configuration types are described below.
...
A basic device can be used to describe network entities such as modalities or workstation.
The available configuration options are based on the DICOM standard and include
DICOM device parameters, network connection parameters,
DICOM network application entity parameters including transfer capabilities supported by the AET,
as well as HL7 application parameters.
...