Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DCM4CHEE 2.14.

...

3 Installation Instructions

Version 2.14.2 3 is the latest version of the archive. It is recommended that you install this version and not an older version because of improvements and bug fixes.

...

  • For image compression/decompression, dcm4chee utilizes Sun's Java Advanced Imaging Image I/O Tools 1.1. The binary distribution packages of dcm4chee already includes necessary JARs and native libraries for Windows and Linux i586. For Linux-amd64, and Solaris, you have to download the SW package from Sun here yourself and replace the Linux version of libclib_jiio.so in dcm4chee-xxx-2.1314.x/bin/native from the JAI Image IO package for Linux-amd64 or Solaris.

...

Download the version of dcm4chee that is relevant to the database of your choice from the dcm4che Sourceforge site. Extract the package (e.g. dcm4chee-psql-2.14.23.zip for the PostgreSQL version). When extracting, avoid using a directory that has a name that contains spaces in order to avoid issues with running command line applications with spaces in the path name.

...

Download the binary distribution of JBoss 4.2.3 from their website and extract it into a different directory.
Don't use JBoss 5, because it is completely re-architected and is significantly different than the 4.2 line of JBoss!
If you want to use JDK 5, don't download JBoss for JDK 6 (jboss-4.2.3.GA-jdk6.zip) - use jboss-4.2.3.GA.zip!

3. Copy files from JBoss to dcm4chee:

...

Move to the dcm4chee-xxx-2.14.23/bin directory and execute the install_jboss.bat or install_jboss.sh script, as appropriate for your operating system, with the path of your JBoss AS installation directory as a parameter.

...

No Format
C:\apps\dcm4chee-psql-2.14.23\bin>install_jboss.bat c:\apps\jboss-4.2.3.GA

...

  1. Download the dcm4chee Audit Record Repository 3.0.7 8 (dcm4chee-arr-3.0.78) available at
    http://sourceforge.net/projects/dcm4che. Be sure to download the distribution package of dcm4chee-arr-3.0.7 8 for the database of your choice (likely the same database that you are using for the archive, but it could differ if you wish to store audit records in a completely different database).
  2. Move to the dcm4chee-xxx-2.14.23/bin directory and execute the install_arr.bat or install_arr.sh script, as appropriate for your operating system, with the path of the dcm4chee-arr-3.0.7 8 installation directory as
    parameter.
    1. If you want the Audit Record Repository to use a different database instance than the archive to store Audit Records (this is recommended), create the audit record repository database instance: arrdb, and grant sufficient privileges to the DB user (see the datasource descriptor deploy/arr-xxx-ds.xml for user information).
    2. If the Audit Record Repository is to share the database instance used by the archive, you will have to modify the database name - but not the JNDI name! -, user and password in the datasource descriptor file deploy/arr-xxx-ds.xml, to match the values specified in the main datasource descriptor file deploy/pacs-xxx-ds.xml for the
      archive database. The ARR schema will automatically be created upon startup, but if you want to tweak the SQL or do it manually, you may also initialize the database using the provided DDL script dcm4chee-arr-xxx-3.0.78/sql/dcm4chee-arr-xxx.ddl. Note that you will have to remove or comment out the creation of already existing 'code' table.

...

For example, in Windows see the file dcm4chee-xxx-2.1314.x/bin/run.bat:

No Format
rem Sun JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m

Linux/Unix/OSX: dcm4chee-xxx-2.1214.x/bin/run.conf

No Format
# Specify options to pass to the Java VM.
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m ..
fi

...

To test your installation, move to the dcm4chee-xxx-2.14.23/bin directory and execute the run.bat or run.sh script, as appropriate for your operating system. Your output should look like the following and contain no error or exception messages:

No Format
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /home/gunter/dcm4chee-psql-2.14.23

JAVA: /usr/lib/j2sdk1.5-sun/bin/java

JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m
-Dsun.rmi.dgc.client.gcInterval=3600000
-Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true
-Dapp.name=dcm4chee -Djava.net.preferIPv4Stack=true
-Djava.library.path=/home/gunter/dcm4chee-psql-2.14.23/bin/native

CLASSPATH: /home/gunter/dcm4chee-psql-2.14.23/bin/run.jar:
/usr/lib/j2sdk1.5-sun/lib/tools.jar

=========================================================================

23:17:52,373 INFO [Server] Starting JBoss (MX MicroKernel)...
23:17:52,374 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build:
SVNTag=JBoss_4_2_3_GA date=200807181439)
:
23:19:49,580 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
23:19:49,632 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build:
SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 1m:57s:103ms

...

If no Storage File System is configured, the archive will auto-configure dcm4chee-xxx-2.1214.x/server/default/archive as Storage File System, when receiving the first object/image.

...

The directory used for caching generated JPEG representations of archived images requested by Web Access to DICOM Persistent Objects (WADO) can be specified by attribute "CacheRoot" in the configuration page for the WADO Service (service=WADOService).
Default: dcm4chee-xxx-2.1214.x/server/default/wadocache.

The directory used for caching generated PDF representations of archived Structured Report Documents requested by IHE Retrieve Information for Display (RID) Services can be specified by attribute "CacheRoot" in the configuration page for the RID Service (service=RIDService).
Default: dcm4chee-xxx-2.1214.x/server/default/ihe_rid_cache.

...

Not necessary with version 2.14.23!

By default, JBoss does not bind to anything except the local address. Use
run -b 0.0.0.0
to allow running generic access.

...