Installation Dcm4che - Dcm4chee-Arc-Light Wiki GitHub

1/19/2020 Installation · dcm4che/dcm4chee-arc-light Wiki · GitHub
Document your code Dismiss
Every project on GitHub comes with a version-controlled wiki to give your documentation the high level of care it deserves. It’s easy to
create well-maintained, Markdown or rich text documentation alongside your code.
Sign up for free See pricing for teams and enterprises
Installation
Jump to bottom
Vrinda edited this page 4 days ago · 78 revisions
Install DCM4CHEE Archive light 5.x

Content
Requirements
Download and extract binary distribution package
Initialize Database
H2
PostgreSQL
MySQL and MariaDB
Firebird
DB2
Oracle
https://github.com/dcm4che/dcm4chee-arc-light/wiki/Installation 1/24
MS SQL Server
Setup LDAP Server
OpenLDAP
OpenLDAP with slapd.conf configuration file
OpenLDAP with dynamic runtime configuration
OpenDJ
Apache DS 2.0.0
Import default configuration into LDAP Server
Setup WildFly
Requirements
Java SE 8 or later - tested with OpenJDK and Oracle JDK
Wildfly 18.0.0 - archive version (5.16.1 or higher) can be run with Wildfly version 14 onwards!
Supported SQL Database:
H2 embedded in Wildfly (Not for production use!)
PostgreSQL 10.4
MariaDB 10.0
MySQL 5.7.9
Firebird 2.5.4
Oracle 11g
DB2 10.5
MS SQL Server (not yet tested!)
Supported LDAP Servers:
OpenLDAP 2.4.45
OpenDJ 2.6.0
Apache DS 2.0.0-M20
LDAP Browser: Apache Directory Studio 2.0.0-M9
Download and extract binary distribution package

DCM4CHEE Archive 5.x binary distributions for different databases can be obtained from Sourceforge. Extract (unzip) one's
chosen download to the directory of one's choice.
For PostgreSQL, MySQL and Oracle, there are also versions provided, with Secure Archive UI and RESTful Services using
Keycloak.
Initialize Database
Note: DCM4CHEE Archive 5.x does not provide SQL scripts and utilities to migrate DCM4CHEE Archive 2.x data base schema to
DCM4CHEE Archive 5.x.
H2
There is no need to initialize the database before starting Wildfly. But one will need to create tables and indexes using H2
Console before deploying the archive.
PostgreSQL
1. Create user with permission to create databases:
> sudo -u postgres createuser -U postgres -P -d <user-name>

Enter password for new role: <user-password>
Enter it again: <user-password>
2. Create database:
> createdb -h localhost -U <user-name> <database-name>

3. Create tables and indexes:
> psql -h localhost <database-name> <user-name> < $DCM4CHEE_ARC/sql/create-psql.sql

> psql -h localhost <database-name> <user-name> < $DCM4CHEE_ARC/sql/create-fk-index.sql
> psql -h localhost <database-name> <user-name> < $DCM4CHEE_ARC/sql/create-case-insensitive-index.sql
MySQL and MariaDB

1. Create database and grant access to user::
> mysql -u root -p<root-password>

mysql> create database <database-name>;
mysql> grant all on <database-name>.* to '<user-name>' identified by '<user-password>';
mysql> quit
2. Create tables and indexes::
> mysql -u <user-name> -p<user-password> <database-name> < $DCM4CHEE_ARC/sql/create-mysql.sql
Firebird
1. Create user
> gsec -user sysdba -password <sysdba-password>

GSEC> add <user-name> -pw <user-password>
GSEC> quit
2. Define database name in configuration file aliases.conf :
<database-name> = <database-file-path>
3. Create database, tables and indexes
> isql-fb
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'localhost:<database-name>' pagesize 16384
CON> user '<user-name>' password '<user-password>';
SQL> in DCM4CHEE_ARC/sql/create-firebird.sql;
SQL> exit;
DB2
1. Create database and grant authority to create tables to user (must match existing OS user)
> sudo su db2inst1

> db2
db2 => create database <database-name> pagesize 16 K
db2 => connect to <database-name>
db2 => grant createtab on database to user <user-name>
db2 => terminate
2. Create tables and indexes
> su <user-name>
Password: <user-password>
> db2 connect to <database-name>
> db2 -t < $DCM4CHEE_ARC/sql/create-db2.sql
> db2 -t < $DCM4CHEE_ARC/sql/create-fk-index.sql
> db2 terminate
Oracle
1. Connect to Oracle and create a new tablespace
$ sqlplus / as sysdba
SQL> create bigfile tablespace <tablespace-name> datafile '<data-file-location>' size <size>;
Tablespace created.
2. Create a new user with privileges for the new tablespace
$ sqlplus / as sysdba
SQL> create user <user-name>
2 identified by <user-password>
3 default tabelspace <tablespace-name>
4 quota unlimited on <tablespace-name>
5 quota 50M on system;
User created.
SQL> grant create session to <user-name>;

SQL> grant create table to <user-name>;
SQL> grant create any index to <user-name>;
SQL> grant create sequence to <user-name>;
SQL> exit
3. Create tables and indexes
$ sqlplus <user-name>/<user-password>
SQL> @$DCM4CHEE_ARC/sql/create-oracle.sql
SQL> @$DCM4CHEE_ARC/sql/create-fk-index.sql
SQL> @$DCM4CHEE_ARC/sql/create-case-insensitive-index.sql
MS SQL Server
Not yet tested
Setup LDAP Server
OpenLDAP
OpenLDAP binary distributions are available for most Linux distributions and for Windows.
OpenLDAP can be alternatively configured by
slapd.conf configuration file

dynamic runtime configuration
See also Converting old style slapd.conf file to cn=config format
OpenLDAP with slapd.conf configuration file
1. Copy LDAP schema files for OpenLDAP from DCM4CHEE Archive distribution to OpenLDAP schema configuration directory:
> cp $DCM4CHEE_ARC/ldap/schema/* /etc/openldap/schema/ [UNIX]

> copy %DCM4CHEE_ARC%\ldap\schema\* \Program Files\OpenLDAP\schema\ [Windows]
2. Add references to schema files in slapd.conf , e.g.:
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/dicom.schema
include /etc/openldap/schema/dcm4che.schema
include /etc/openldap/schema/dcm4chee-archive.schema
include /etc/openldap/schema/dcm4chee-archive-ui.schema
3. Directory Base DN and Root User DN are specified in slapd.conf by
suffix "dc=nodomain"
rootdn "cn=admin,dc=nodomain"
rootpw secret
and may be modfied to
suffix "dc=dcm4che,dc=org"
rootdn "cn=admin,dc=dcm4che,dc=org"
rootpw secret
OpenLDAP with dynamic runtime configuration
1. Import LDAP schema files for OpenLDAP runtime configuration, using OpenLDAP CL utility ldapadd, e.g.:
> sudo ldapadd -Y EXTERNAL -H ldapi:/// -f $DCM4CHEE_ARC/ldap/slapd/dicom.ldif

> sudo ldapadd -Y EXTERNAL -H ldapi:/// -f $DCM4CHEE_ARC/ldap/slapd/dcm4che.ldif
> sudo ldapadd -Y EXTERNAL -H ldapi:/// -f $DCM4CHEE_ARC/ldap/slapd/dcm4chee-archive.ldif
> sudo ldapadd -Y EXTERNAL -H ldapi:/// -f $DCM4CHEE_ARC/ldap/slapd/dcm4chee-archive-ui.ldif
2. Directory Base DN and Root User DN can be modified by changing the values of attributes
olcSuffix: dc=nodomain
olcRootDN: cn=admin,dc=nodomain
olcRootPW
of object olcDatabase={1}hdb,cn=config by specifying the new values in a LDIF file (e.g. modify-baseDN.ldif )
dn: olcDatabase={1}hdb,cn=config
changetype: modify
replace: olcSuffix
olcSuffix: dc=dcm4che,dc=org
-
replace: olcRootDN
olcRootDN: cn=admin,dc=dcm4che,dc=org
-
replace: olcRootPW
olcRootPW: <{SSHA}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
-
Note: In order to execute the commands on CentOS7 use dn: olcDatabase={2}hdb,cn=config instead of dn: olcDatabase=
{1}hdb,cn=config.
Note: Replace <{SSHA}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> by the hash generated by the command :
> sudo slappasswd
and applying it using OpenLDAP CL utility ldapmodify, e.g.:
> sudo ldapmodify -Y EXTERNAL -H ldapi:/// -f modify-baseDN.ldif
After that you have to create the top element of the directory tree (dc=dcm4che,dc=org) and the object for the LDAP
administrator account (cn=admin,dc=dcm4che,dc=org).
LDIF file slapd_setup_basic.ldif :
dn: dc=dcm4che,dc=org
changetype: add
objectClass: top
objectClass: dcObject
objectClass: organization
o: Example Organisation name
dc: dcm4che
dn: cn=admin,dc=dcm4che,dc=org
changetype: add
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
userPassword:
To create these objects, you have to use the databases root account and to enter your LDAP admin password as specified
during installation
> ldapmodify -x -W -D cn=admin,dc=dcm4che,dc=org -H ldapi:/// -f slapd_setup_basic.ldif
OpenDJ
1. Copy LDAP schema files for OpenDJ from DCM4CHEE Archive distribution to OpenDJ schema configuration directory:
> cp $DCM4CHEE_ARC/ldap/opendj/* $OPENDJ_HOME/config/schema/ [UNIX]

> copy %DCM4CHEE_ARC%\ldap\opendj\* %OPENDJ_HOME%\config\schema\ [Windows]
2. Run OpenDJ GUI based setup utility
> $OPENDJ_HOME/setup
Log the values choosen for
LDAP Listener port (1389)

Root User DN (cn=Directory Manager)
Root User Password (secret)
Directory Base DN (dc=dcm4che,dc=org)
needed for the LDAP connection configuration of DCM4CHEE Archive.
3. After initial setup, one may start and stop OpenDJ by
> $OPENDJ_HOME/bin/start-ds
> $OPENDJ_HOME/bin/stopt-ds
Apache DS 2.0.0
1. Install Apache DS 2.0.0-M20 on the system and start Apache DS.
2. Install Apache Directory Studio 2.0.0-M9 and create a new LDAP Connection with:
Network Parameter:
Hostname: localhost
Port: 10389
Authentication Parameter:
Bind DN or user: uid=admin,ou=system
Bind password: secret
3. Import LDAP schema files for Apache DS:
$DCM4CHEE_ARC/ldap/apacheds/dicom.ldif
$DCM4CHEE_ARC/ldap/apacheds/dcm4che.ldif
$DCM4CHEE_ARC/ldap/apacheds/dcm4chee-archive.ldif
$DCM4CHEE_ARC/ldap/apacheds/dcm4chee-archive-ui.ldif
using the LDIF import function of Apache Directory Studio LDAP Browser.
4. One may modify the default Directory Base DN dc=example,dc=com by changing the value of attribute
ads-partitionsuffix: dc=dcm4che,dc=org`
of object
ou=config
+ ads-directoryServiceId=default
+ ou=partitions
ads-partitionId=example
to ads-partitionId=dcm4che
using Apache Directory Studio LDAP Browser.
Note : One may need to restart the Apache DS service to effect the above changes.
Alternatively, one may also run ApacheDS using docker
Import default configuration into LDAP Server

1. If not already done, install Apache Directory Studio 2.0.0-M9 and create a new LDAP Connection corresponding to one's
LDAP Server configuration, e.g:
Network Parameter:
Hostname: localhost
Port: 389
Authentication Parameter:
Bind DN or user: cn=admin,dc=dcm4che,dc=org
Bind password: secret
Browser Options:
Base DN: dc=dcm4che,dc=org
2. If one configured a different Directory Base DN than dc=dcm4che,dc=org , one has to replace all occurrences of
dc=dcm4che,dc=org in LDIF files
$DCM4CHEE_ARC/ldap/init-baseDN.ldif
$DCM4CHEE_ARC/ldap/init-config.ldif
$DCM4CHEE_ARC/ldap/default-config.ldif
$DCM4CHEE_ARC/ldap/default-ui-config.ldif
$DCM4CHEE_ARC/ldap/add-vendor-data.ldif
by one's Directory Base DN, e.g.:
> cd $DCM4CHEE_ARC/ldap
> sed -i s/dc=dcm4che,dc=org/dc=my-domain,dc=com/ init-baseDN.ldif
> sed -i s/dc=dcm4che,dc=org/dc=my-domain,dc=com/ init-config.ldif
> sed -i s/dc=dcm4che,dc=org/dc=my-domain,dc=com/ default-config.ldif
> sed -i s/dc=dcm4che,dc=org/dc=my-domain,dc=com/ default-ui-config.ldif
> sed -i s/dc=dcm4che,dc=org/dc=my-domain,dc=com/ add-vendor-data.ldif
3. If there is not already a base entry in the directory data base, import $DCM4CHEE_ARC/ldap/init-baseDN.ldif using the LDIF
import function of Apache Directory Studio LDAP Browser.
4. If there are not already DICOM configuration root entries in the directory data base, import $DCM4CHEE_ARC/ldap/init-
config.ldif using the LDIF import function of Apache Directory Studio LDAP Browser.
5. Import
$DCM4CHEE_ARC/ldap/default-config.ldif
$DCM4CHEE_ARC/ldap/default-ui-config.ldif
using the LDIF import function of Apache Directory Studio LDAP Browser.
6. On dcm4chee-arc device level, one may add new attribute dicomVendorData using the New Attribute function (or
Ctrl+Shift++) of Apache Directory Studio and in its value one can load the data - $DCM4CHEE_ARC/ldap/add-vendor-
data.ldif which imports $DCM4CHEE_ARC/ldap/dcm4chee-arc-conf-data-<version>.zip . This zip file contains XSLT
stylesheets specifing attribute coercion in incoming or outgoing DICOM messages and mapping of HL7 fields in incoming
HL7 messages.
7. One may change the default AE Title(s) of the Archive: AS_RECEIVED , DCM4CHEE , IOCM_REGULAR_USE , IOCM_EXPIRED ,
IOCM_QUALITY , IOCM_PAT_SAFETY and IOCM_WRONG_MWL .
8. One may change the default Storage Directory: /var/local/dcm4chee-arc/fs1 .
9. One may configure AE Title(s) of external DICOM Applications to which the Archive shall be able to connect.
10. One may change the default Web Application(s): 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 .
11. Version 5.19.1 onwards, the new Study page uses Web Applications also for querying the own archive. In default
configuration, the Web Applications uses http and https connection references which are configured with hostname as
localhost by default. If one is accessing the archive UI from a browser which is not on the same host as that of archive,
then one needs to change the hostname of these connections from localhost to actual hostname or IP address where the
archive is running.
Setup WildFly
NOTE : Below configurations for Widlfy can be done only with archive versions 5.16.1 onwards. QueryDSL JBoss module is no
longer supported.
For secured version of archive, refer here
1. Copy configuration files into the WildFly installation:
> cp -r $DCM4CHEE_ARC/configuration/dcm4chee-arc $WILDFLY_HOME/standalone/configuration [UNIX]

> xcopy %DCM4CHEE_ARC%\configuration\dcm4chee-arc %WILDFLY_HOME%\standalone\configuration\dcm4chee-arc
[Windows]
(Select D = directory)
Note: Beside LDAP Connection configuration dcm4chee-arc/ldap.properties , the private key dcm4chee-arc/key.jks used
in TLS connections are not stored in LDAP. Ensure that one's LDAP specific values are present in the file dcm4chee-
arc/ldap.properties .
2. The Jakarta Full Platform certified configuration can be used as base configuration. To preserve the original WildFly
configuration one may copy the original configuration file for Jakarta Full Platform Profile:
> cd $WILDFLY_HOME/standalone/configuration/
> cp standalone-full.xml dcm4chee-arc.xml
3. Install DCM4CHE libraries as JBoss modules:
> cd $WILDFLY_HOME
> unzip $DCM4CHEE_ARC/jboss-modules/dcm4che-jboss-modules-5.x.x.zip
4. Install JAI Image IO 1.2 libraries as JBoss module (needed for compression/decompression, does not work on Windows 64
bit and Mac OS X caused by missing native components for these platforms):
> cd $WILDFLY_HOME
> unzip $DCM4CHEE_ARC/jboss-modules/jai_imageio-jboss-modules-1.2-pre-dr-b04.zip
5. Install jclouds 2.2.0 libraries as JBoss modules:
> cd $WILDFLY_HOME
> unzip $DCM4CHEE_ARC/jboss-modules/jclouds-jboss-modules-2.2.0-noguava.zip
6. Install ecs-object-client 3.0.0 libraries as JBoss modules:
> cd $WILDFLY_HOME
> unzip $DCM4CHEE_ARC/jboss-modules/ecs-object-client-jboss-modules-3.0.0.zip
7. Except for H2, one has to install the JDBC Driver for the database.
The JDBC driver can be installed either as a deployment or as a core module.
For installation as a core module extract the corresponding ZIP file into $WILDFLY_HOME, e.g.:
> cd $WILDFLY_HOME
> unzip $DCM4CHEE_ARC/jboss-modules/jdbc-jboss-modules-mysql-8.0.18.zip
Installation as deployment is limited to JDBC 4-compliant driver consisting of one JAR. You may either take the JDBC driver
JAR from included core module ZIP, or download it from:
MySQL
PostgreSQL
Firebird
DB2
Oracle
Microsoft SQL Server
8. Start WildFly in standalone mode with the correct configuration file:
> $WILDFLY_HOME/bin/standalone.sh -c dcm4chee-arc.xml [UNIX]

> %WILDFLY_HOME%\bin\standalone.bat -c dcm4chee-arc.xml [Windows]
Verify, that JBoss started successfully, e.g.:
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /home/work/wildfly-18.0.0.Final
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -

Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -
agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n --add-exports=java.base/sun.nio.ch=ALL-
UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-
UNNAMED
=========================================================================
08:30:44,540 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final

08:30:44,766 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
08:30:44,774 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
:
08:30:47,562 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 18.0.0.Final (WildFly Core
10.0.0.Final) started in 3313ms - Started 330 of 552 services (324 services are lazy, passive or on-demand)
Running JBoss in domain mode should work, but was not yet tested.
9. If you installed the JDBC Driver as a core module in step 7, you have to add it into the server configuration using JBoss CLI
in a new console window:
> $WILDFLY_HOME/bin/jboss-cli.sh -c [UNIX]

> %WILDFLY_HOME%\bin\jboss-cli.bat -c [Windows]
[standalone@localhost:9990 /] /subsystem=datasources/jdbc-driver=<driver-name>:add(driver-name=<driver-
name>,driver-module-name=<module-name>)
One may choose any <driver-name> for the JDBC Driver, <module-name> must match the name defined in the module
definition file module.xml of the JDBC driver, e.g.:
[standalone@localhost:9990 /] /subsystem=datasources/jdbc-driver=mysql:add(driver-name=mysql,driver-module-
name=com.mysql)
10. Create and enable a new Data Source bound to JNDI name java:/PacsDS using JBoss CLI:
[standalone@localhost:9990 /] data-source add --name=PacsDS \

> --driver-name=<driver-name> \
> --connection-url=<jdbc-url> \
> --jndi-name=java:/PacsDS \
> --user-name=<user-name> \
> --password=<user-password>
The format of <jdbc-url> is JDBC Driver specific, e.g.:
H2: jdbc:h2:<directory-path>/<database-name>
MySQL: jdbc:mysql://<host>:3306/<database-name>
PostgreSQL: jdbc:postgresql://<host>:5432/<database-name>
Firebird: jdbc:firebirdsql:<host>/3050:<database-name>
DB2: jdbc:db2://<host>:50000/<database-name>
Oracle: jdbc:oracle:thin:@<host>:1521:<database-name>
Microsoft SQL Server: jdbc:sqlserver://<host>:1433;databaseName=<database-name>
There is also a CLI script $DCM4CHEE_ARC/cli/add-data-source-<db>.cli provided, which just applies the command to add
the JDBC driver and creating the Data Source. Replace <host> , <database-name> , <user-name> and <user-password> by
their actual values before executing it:
> $WILDFLY_HOME/bin/jboss-cli.sh -c --file=$DCM4CHEE_ARC/cli/add-data-source-<db>.cli
11. If one is using H2 as database, create tables and indexes using the H2 Console:
i. Download the H2 Console WAR file from https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.1.0.GA/h2-

console
ii. Deploy it using JBoss CLI, e.g.:
[standalone@localhost:9990 /] deploy ~/Downloads/h2-console.war
iii. Access the console at http://localhost:8080/h2console and login with JDBC URL , User name und Password matching
the values passed to above data-source add --name=PacsDS .
iv. Create tables and indexes:
RUNSCRIPT FROM '$DCM4CHEE_ARC/sql/create-h2.sql'
12. Create JMS Queues using JBoss CLI:
[standalone@localhost:9990 /] jms-queue add --queue-address=StgCmtSCP --entries=java:/jms/queue/StgCmtSCP

[standalone@localhost:9990 /] jms-queue add --queue-address=StgCmtSCU --entries=java:/jms/queue/StgCmtSCU
[standalone@localhost:9990 /] jms-queue add --queue-address=MPPSSCU --entries=java:/jms/queue/MPPSSCU
[standalone@localhost:9990 /] jms-queue add --queue-address=IANSCU --entries=java:/jms/queue/IANSCU
[standalone@localhost:9990 /] jms-queue add --queue-address=Export1 --entries=java:/jms/queue/Export1
[standalone@localhost:9990 /] jms-queue add --queue-address=HL7Send --entries=java:/jms/queue/HL7Send
[standalone@localhost:9990 /] jms-queue add --queue-address=RSClient --entries=java:/jms/queue/RSClient
[standalone@localhost:9990 /] jms-queue add --queue-address=DiffTasks --entries=java:/jms/queue/DiffTasks

[standalone@localhost:9990 /] jms-queue add --queue-address=StgVerTasks --entries=java:/jms/queue/StgVerTasks
[standalone@localhost:9990 /] jms-queue add --queue-address=Rejection --entries=java:/jms/queue/Rejection
[standalone@localhost:9890 /] jms-queue add --queue-address=Retrieve1 --entries=java:/jms/queue/Retrieve1
There is also a CLI script $DCM4CHEE_ARC/cli/add-jms-queues.cli provided, containing these commands, which one may
just execute:
> $WILDFLY_HOME/bin/jboss-cli.sh -c --file=$DCM4CHEE_ARC/cli/add-jms-queues.cli
13. Enable property replacement in deployment descriptors by setting attribute spec-descriptor-property-replacement of the
ee subsystem to true , and adjust the managed-executor-services and the managed-scheduled-executor-service
configuration of the ee subsystem to avoid thread-pool related issues on long running tasks or heavy load using JBoss
CLI - you may configure a larger maximal number of threads than 100 according your needs:
[standalone@localhost:9990 /] /subsystem=ee:write-attribute(name=spec-descriptor-property-
replacement,value=true)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:undefine-attribute(name=hung-task-
threshold)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=long-running-
tasks,value=true)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=core-
threads,value=2)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=max-
threads,value=100)
[standalone@localhost:9990 /] /subsystem=ee/managed-executor-service=default:write-attribute(name=queue-
length,value=0)
[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=default:undefine-
attribute(name=hung-task-threshold)
[standalone@localhost:9990 /] /subsystem=ee/managed-scheduled-executor-service=default:write-
attribute(name=long-running-tasks,value=true)
There is also a CLI script $DCM4CHEE_ARC/cli/adjust-managed-executor.cli provided, containing these commands, which
one may execute:
> $WILDFLY_HOME/bin/jboss-cli.sh -c --file=$DCM4CHEE_ARC/cli/adjust-managed-executor.cli
You have to reload the configuration - or restart Wildfly - to make the changes effective:
[standalone@localhost:9990 /] :reload
14. At default, DCM4CHEE Archive 5.x will assume dcm4chee-arc as its Device Name, used to find its configuration in the LDAP
Server. One may specify a different Device Name by system property dcm4chee-arc.DeviceName using JBoss CLI:
[standalone@localhost:9990 /] /system-property=dcm4chee-arc.DeviceName:add(value=<device-name>)
15. At default, the Wildfly supports maximum size of POST requests only as 10MB, one may change this to a higher value as
shown below
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/http-listener=default:write-
attribute(name=max-post-size,value=10000000000)
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/https-listener=https:write-
attribute(name=max-post-size,value=10000000000)
You have to reload the configuration - or restart Wildfly - to make the changes effective:
[standalone@localhost:9990 /] :reload
16. Deploy DCM4CHEE Archive 5.x using JBoss CLI, e.g.:
[standalone@localhost:9990 /] deploy $DCM4CHEE_ARC/deploy/dcm4chee-arc-ear-5.x-psql.ear
Verify that DCM4CHEE Archive was deployed and started successfully, e.g.:
11:00:38,511 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment
of "dcm4chee-arc-ear-5.x-psql.ear" (runtime-name: "dcm4chee-arc-ear-5.x-psql.ear")
:
11:00:42,742 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Start TCP
Listener on /0.0.0.0:11112
Listener on /0.0.0.0:2762
Listener on /0.0.0.0:2575
Listener on /0.0.0.0:12575
11:00:43,095 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0021: Registered
web context: /dcm4chee-arc/xdsi
web context: /dcm4chee-arc
web context: /dcm4chee-arc/ui2
11:00:43,157 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "dcm4chee-arc-
ear-5.x-SNAPSHOT-psql.ear" (runtime-name : "dcm4chee-arc-ear-5.x-SNAPSHOT-psql.ear")
Verify that the Web UI is accessible at http://localhost:8080/dcm4chee-arc/ui2.
One may undeploy DCM4CHEE Archive at any time using JBoss CLI, e.g.:
[standalone@localhost:9990 /] undeploy dcm4chee-arc-ear-5.x-psql.ear
11:05:23,905 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0022: Unregistered

web context: /dcm4chee-arc
11:05:23,906 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 80) WFLYUT0022: Unregistered
web context: /dcm4chee-arc/ui
11:05:23,912 INFO [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Stop TCP Listener
on /0.0.0.0:11112
on /0.0.0.0:2762
on /0.0.0.0:12575
on /0.0.0.0:2575
:
11:05:24,023 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0009: Undeployed "dcm4chee-arc-
ear-5.x-psql.ear" (runtime-name: "dcm4chee-arc-ear-5.x-psql.ear")
Pages 172
Find a Page…
Home
Access Control
Access control based on Archive AEs
Accessing external archive
Accessing external archive PAM Services

Accessing external archive Web Services
Accessing own archive
AE Title(s) of the Archive
Anonymize objects on Retrieve
Apply Retention Policy
Archive as SCP
Archive UI Testplan
Attribute Coercion
Attribute Update Policy
Audit Logger
Show 157 more pages…
Clone this wiki locally
https://github.com/dcm4che/dcm4chee-arc-light.wiki.git

Installation Dcm4che - Dcm4chee-Arc-Light Wiki GitHub

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Installation Dcm4che - Dcm4chee-Arc-Light Wiki GitHub

Hochgeladen von

Copyright:

Verfügbare Formate

1/19/2020 Installation · dcm4che/dcm4chee-arc-light Wiki · GitHub

Document your code Dismiss

Sign up for free See pricing for teams and enterprises

Vrinda edited this page 4 days ago · 78 revisions

Install DCM4CHEE Archive light 5.x

LDAP Browser: Apache Directory Studio 2.0.0-M9

Download and extract binary distribution package

> sudo -u postgres createuser -U postgres -P -d <user-name>

> createdb -h localhost -U <user-name> <database-name>

3. Create tables and indexes:

> psql -h localhost <database-name> <user-name> < $DCM4CHEE_ARC/sql/create-psql.sql

MySQL and MariaDB

> mysql -u root -p<root-password>

2. Create tables and indexes::

> mysql -u <user-name> -p<user-password> <database-name> < $DCM4CHEE_ARC/sql/create-mysql.sql

> gsec -user sysdba -password <sysdba-password>

2. Define database name in configuration file aliases.conf :

3. Create database, tables and indexes

> sudo su db2inst1

2. Create tables and indexes

2. Create a new user with privileges for the new tablespace

SQL> grant create session to <user-name>;

3. Create tables and indexes

Setup LDAP Server

OpenLDAP can be alternatively configured by

slapd.conf configuration file

See also Converting old style slapd.conf file to cn=config format

OpenLDAP with slapd.conf configuration file

> cp $DCM4CHEE_ARC/ldap/schema/* /etc/openldap/schema/ [UNIX]

2. Add references to schema files in slapd.conf , e.g.:

3. Directory Base DN and Root User DN are specified in slapd.conf by

and may be modfied to

OpenLDAP with dynamic runtime configuration

> sudo ldapadd -Y EXTERNAL -H ldapi:/// -f $DCM4CHEE_ARC/ldap/slapd/dicom.ldif

Note: Replace <{SSHA}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> by the hash generated by the command :

> sudo slappasswd

and applying it using OpenLDAP CL utility ldapmodify, e.g.:

> sudo ldapmodify -Y EXTERNAL -H ldapi:/// -f modify-baseDN.ldif

LDIF file slapd_setup_basic.ldif :

> ldapmodify -x -W -D cn=admin,dc=dcm4che,dc=org -H ldapi:/// -f slapd_setup_basic.ldif

> cp $DCM4CHEE_ARC/ldap/opendj/* $OPENDJ_HOME/config/schema/ [UNIX]

2. Run OpenDJ GUI based setup utility

Log the values choosen for

LDAP Listener port (1389)

Directory Base DN (dc=dcm4che,dc=org)

needed for the LDAP connection configuration of DCM4CHEE Archive.

3. After initial setup, one may start and stop OpenDJ by

3. Import LDAP schema files for Apache DS:

using Apache Directory Studio LDAP Browser.

Alternatively, one may also run ApacheDS using docker

Import default configuration into LDAP Server

by one's Directory Base DN, e.g.:

8. One may change the default Storage Directory: /var/local/dcm4chee-arc/fs1 .

For secured version of archive, refer here

1. Copy configuration files into the WildFly installation:

> cp -r $DCM4CHEE_ARC/configuration/dcm4chee-arc $WILDFLY_HOME/standalone/configuration [UNIX]

3. Install DCM4CHE libraries as JBoss modules:

5. Install jclouds 2.2.0 libraries as JBoss modules:

6. Install ecs-object-client 3.0.0 libraries as JBoss modules:

The JDBC driver can be installed either as a deployment or as a core module.

8. Start WildFly in standalone mode with the correct configuration file:

> $WILDFLY_HOME/bin/standalone.sh -c dcm4chee-arc.xml [UNIX]

Verify, that JBoss started successfully, e.g.: