Minimum System Requirements and Supporting Software

dcm4chee is a Java-based application for the management of digital clinical objects. As such, it should be run under the best hardware available for production systems. The minimal system configuration is as follows:

...

DCM4CHEE 2.17.1 Installation Instructions

Version 2.17.1 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.

You will find similar (but not as detailed) installation documentation in the doc directory of your dcm4chee distribution.

Minimum System Requirements

JDK 5 or higher
512 MB RAM
200 MB hard disk space (

...

additional to archive storage disk space

...

)
400 MHz CPU

...

Supported Databases

Need to install separately.

PostgreSQL 8.1

...

+
MySQL 4.1+
Oracle 9i

...

+
SQL Server 2000+
DB2 8.1+

...

dcm4chee is a Java-based application. It requires the installation of the JDK version 1.4.2 or higher. JDK version 5 is recommended for the best performance and stability. Firebird 2.1+
Hypersonic SQL (Embedded in JBoss AS) - not suitable for production use!

Security Notes

See how to limit the server access.

Compression Notes

For image compression/decompression, dcm4chee 2.8.x utilizes Sun's Java Advanced Imaging (JAI) Image Image I/O Tools 1.0_011.

• The binary distribution packages of dcm4chee

...

• already includes

...

• necessary JARs and native libraries for Windows and Linux i586.

• For

...

dcm4chee depends heavily on the JBoss (http://www.jboss.org) application server for its infrastructure. It is not necessary to download JBoss (as dcm4chee is pre-packaged within JBoss), but viewing the online (or downloaded) JBoss documentation will assist a great deal in learning the dcm4chee directory structure, and how the product operates under the covers. JBoss services such as XMBeans, JBossMQ (JMS), and EJB (Session and Entity beans) are utilized by dcm4chee.

Installation Steps

Installing dcm4chee is fairly easy:

1. Download the binary distribution of dcm4chee for the database of your choice from the Files page of the dcm4che project page on SourceForge (http://sourceforge.net/projects/dcm4che/). If you do not see a distribution for your database, you will have to Building dcm4chee from Source\ from the source code.
2. Once downloaded, extract the distribution package into your desired destination directory. Avoid using a directory path that contains spaces though, as that may cause problems when running the application from the command line.
3. Install the database software of your choice (keeping in mind the supported database systems) if you have not already done so. Keep in mind that the database software that you install (or have installed) must match the version of dcm4chee that you downloaded. For example, if you want to use PostgreSQL with dcm4chee then you should download the dcm4chee-standalone-psql-2.8.2.zip file from SourceForge.
4. If using a database other than MySQL or PostgreSQL you will need to copy an apropriate JDBC Driver for the database to DCM4CHEE_DIST/server/default/lib/. This is not necessary for MySQL or PostgreSQL because the binary distribution of dcm4chee already contains the correct JDBC drivers for these database systems.
5. Verify that your database installation has TCP/IP socket access available.

   For example, with PostgreSQL you can check the pg_hba.conf file for your database:

   No Format
   $PGDATA/pg_hba.conf: # IPv4 local connections: host all all 127.0.0.1/32 trust

   With Oracle, you can verify that the TNS Listener is enabled:

   No Format
   C:\>netstat -b -p TCP Active Connections TCP localhost:1284 host.domain.com:1521 ESTABLISHED 1788 [ORACLE.EXE] TCP localhost:1521 host.domain.com:1284 ESTABLISHED 1816 [TNSLSNR.exe]

6. Initiate the archive database instance (named pacsdb) using the create DDL script located in DCM4CHEE_DIST/sql/create.xxx.

   For example, with PostgreSQL on a Unix-based system:

   No Format
   > export PGUSER=postgres > createdb pacsdb > psql pacsdb \-f DCM4CHEE_DIST/sql/create.psql

   To initialize a MySQL database on a Unix-based system:

   No Format
   > mysql \-uroot mysql> create database pacsdb; mysql> grant all on pacsdb.\* to 'pacs'@'localhost' identified by 'pacs'; mysql> \q > mysql \-upacs \-ppacs < DCM4CHEE_DIST/sql/create.mysql

...

<\!\--example of how to specify class that determines if exception means connection should be destroyed-\->
<\!\--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-\->

<\!-\- this will be run before a managed connection is removed from the pool for use by a client-->
<\!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> \-->

<\!-\- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use \-->
<min-pool-size>5</min-pool-size>

<\!-\- The maximum connections in a pool/sub-pool \-->
<max-pool-size>20</max-pool-size>

<\!-\- The time before an unused connection is destroyed \-->
<\!-\- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use \-->
<idle-timeout-minutes>0</idle-timeout-minutes>

<\!-\- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
 \-->

<\!-\- sql to call on an existing pooled connection when it is obtained from pool
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
\-->

<\!-\- example of how to specify a class that determines a connection is valid before it is handed out from the pool
<valid-connection-checker-class-name>fully qualified name of class to use</valid-connection-checker-class-name>
\-->

<\!-\- Whether to check all statements are closed when the connection is returned to the pool,
 this is a debugging feature that should be turned off in production
<track-statements/>
\-->

...

Windows: DCM4CHEE_DIST/bin/run.bat:

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

Linux/Unix: DCM4CHEE_DIST/bin/run.conf
# Specify options to pass to the Java VM.
JAVA_OPTS="-server -Xms64m -Xmx200m -Djava.awt.headless=true ..

...

Keep in mind the available RAM and memory requirements of other processes running on the hardware. For example, iif only 512 MB RAM is available on the machine, you should decrease the default value from -Xmx512m (on Windows to) -Xmx300.

1. Optional: Upon installation, all DICOM services are pre-configured with DCM4CHEE as the Application Entity Title (AE Title, or AET). Although it is possible to modify this default configuration at a later date through the Web-based administrative console, it is more efficient to replace DCM4CHEE with YOUR_AET in DCM4CHEE_DIST/server/default/conf/xmdesc/*.xml using utilities provided by your platform.

...

> find DCM4CHEE_DIST/server/default/conf/xmdesc \-exec \ sed \-i s/DCM4CHEE_DIST/YOUR_AET/g '{}' ';'}}

...

1. Stop the application (type ctrl-c in the console window).
2. Windows: install dcm4chee as a Windows service executing DCM4CHEE_DIST/bin/install_service.bat.
3. Redhat Linux: copy the init script DCM4CHEE_DIST/bin/dcm4chee_init_redhat.sh to /etc/init.d/ and adjust it according to the dcm4chee installation location, the JDK installation location, and which user the dcm4chee should run under.

Verify the Installation

Navigate to the DCM4CHEE_DIST/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:

...

• Linux-amd64, here is the latest Linux binaries (download it and rename to libclib_jiio.so) and replace the old libclib_jiio.so in dcm4chee/bin/native.

• If you have already installed (or are installing) the JAI Image IO distribution from http://download.java.net/media/jai-imageio/builds/release/1.1/ separate from dcm4chee in a standalone or classpath fashion, you should remove the following files, or potentially suffer from version conflicts:
  • $DCM4CHEE_HOME/server/default/lib/jai_imageio.jar
  • $DCM4CHEE_HOME/server/default/lib/clibwrapper_jiio.jar
  • $DCM4CHEE_HOME/bin/native/clib_jiio.dll
  • $DCM4CHEE_HOME/bin/native/clib_jiio_sse2.dll
  • $DCM4CHEE_HOME/bin/native/clib_jiio_util.dll
  • $DCM4CHEE_HOME/bin/native/libclib_jiio.so

• For Mac OSX and 64 bit Java on Windows there is no free, native Image I/O implementation available. Because of the missing implementations you have to change a file in dcm4chee if you want to have the WADO service running. Please have a look at step 8 to see how to change the file (or modify the settings via the JMX console). See also:
  • http://java.net/jira/browse/JAI_IMAGEIO_CORE-103
  • http://java.net/jira/browse/JAI_IMAGEIO_CORE-62
• FYI - You can run on 64-bit Windows, you just need to use the 32-bit JDK! In that case you do not need to do the above steps of changing the WADO service.

Additional notes from Nicolas Roduit:

I want to clarify the big misunderstanding about the Java imageio library included in dcm4chee and Weasis. I understand that the compression issue with imageio is confusing.

The imageio lib is used for reading and writing the different image formats (image compression). It contains a pure java part (jai_imageio.jar) and a native part (set in $DCM4CHEE_HOME/bin/native/). The native part only exist for the following operating systems:

• Windows 32-bit
• Linux x86 32 and 64-bit
• Solaris (all processors)

Thanks to Sun and Oracle for this limitation, but that's not all, some encoders and decoders are exclusively available in the native part. That means NOT available in the pure java part. Here are these TSUIDs:

• 1.2.840.10008.1.2.4.51 JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only)
• 1.2.840.10008.1.2.4.57 JPEG Lossless, Non-Hierarchical (Process 14)
• 1.2.840.10008.1.2.4.70 JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 Selection Value 1): Default Transfer Syntax for Lossless JPEG Image Compression
• 1.2.840.10008.1.2.4.80 JPEG-LS Lossless Image Compression
• 1.2.840.10008.1.2.4.81 JPEG-LS Lossy (Near-Lossless) Image Compression

And some codecs exist in the pure Java library but have a different implementation in the native library (the native implementation is used by default when available):

• 1.2.840.10008.1.2.4.50 JPEG Baseline (Process 1): Default Transfer Syntax for Lossy JPEG 8 Bit Image Compression
• 1.2.840.10008.1.2.4.90 JPEG 2000 Image Compression (Lossless Only)
• 1.2.840.10008.1.2.4.91 JPEG 2000 Image Compression

About dcm4chee
That's why it is recommended to install dcm4chee on Linux, Solaris or Windows (also with windows 64-bit but only with a 32-bit Java Runtime). Otherwise, the dcm4chee services won't be able to compress or uncompress some DICOM files. One of the mandatory requirement (WADO spec) of a WADO service is to uncompress any DICOM file. The latter requirement cannot be totally fulfilled if you install dcm4chee on OS X.
We provide on the Osirix website this document which recommends to install dcm4chee on Linux and to use the jpeg2000 compression (if you want to compress all the images stored in dcm4chee).

About Weasis
In the table of Platform Compatibility of DICOM Transfer Syntax you can see the compatibility related to the list above. This compatibility is true ONLY when Weasis loads files from a local storage (not WADO). When downloading images with the WADO service of dcm4chee that contain native imageio library, ALL the images can be read on ALL operating systems, because Weasis (in recent version) is able to request the WADO server for an uncompressed syntax (see WEA-73) when the syntax is not supported by the operating system running Weasis.

Installation Procedure:

1. Download and extract the binary distribution package of dcm4chee:

Download the latest version of dcm4chee that is relevant to the database of your choice from the dcm4che Sourceforge site . Extract the package (e.g. dcm4chee-2.17.1-psql.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.

2. Download the binary distribution package of JBoss Application Server 4.2.3.GA:

Download the binary distribution of JBoss 4.2.3.GA from their website and extract it into a different directory.

Use neither JBoss 5 nor JBoss 6, 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!

dcm4chee requires Java Development Kit (JDK) and not just the Java Runtime Environment (JRE).

3. Copy files from JBoss to dcm4chee:

Dcm4chee consists of components that run within the JBoss application server platform. This step will copy the JBoss runtime files to the dcm4chee directory.

Go to the dcm4chee-2.17.1-xxx/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.

For example:

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

4. Install the Database Software and create the DCM4CHEE Database:

If you do not already have database software running, install it now. Please follow the vendor's installation instructions to do so. Some operating systems already come with database software installed (e.g. Mac OSX and MySQL). Even in those cases though, it is helpful for you to review the database vendor's documentation. After all, the database is an extremely important part of the dcm4chee solution.

See below for links to database-specific installation notes:

• PostgreSQL
• MySQL
• Oracle
• Microsoft SQL Server
• DB2
• Firebird
• Hypersonic SQL

5. Deploy the Audit Record Repository (ARR)

Starting with dcm4chee-2.12.0, the binary distribution package of the archive application does NOT include the dcm4chee Audit Record Repository (ARR) anymore. The ARR maintains an audit log of all transactions within the archive. This is necessary for HIPAA and IHE. Some dcm4chee deployment scenarios call for the deployment of the ARR in a standalone fashion because it acts as an ARR for more than one dcm4chee instance, or multiple applications which can take advantage of an external ARR. Commonly though it is deployed within the dcm4chee archive itself. If you are not running the ARR in a standalone fashion, you must do the following:

1. Download the dcm4chee Audit Record Repository 3.0.11 (dcm4chee-arr-3.0.11) available at
   http://sourceforge.net/projects/dcm4che/files/dcm4chee-arr/3.0.11/. Be sure to download the distribution package of dcm4chee-arr-3.0.11 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. Go to the dcm4chee-2.17.1-xxx/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.11 installation directory as
   parameter.
   • Because of the growth factor of the audit database, it is recommended to store the records in it's own database. 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, typically arr with pw of arr). Also see above links to DB-specific pages for tips.

6. Set environment variable JAVA_HOME to JDK location.

The dcm4chee startup/shutdown scripts depend on the JAVA_HOME environment variable in order to find the Java executables and libraries. For example, if your JDK is installed at "C:\Program Files\Java\jdk1.5.0_22" then that is the path to JAVA_HOME

If you're not sure what an environment variable is, check with your IT staff or review this wikipedia page and/or consult the documentation for your operating system.

7. Optional: Adjust maximum allocation of heap memory:

Java programs run with a finite amount of memory allocated to them. If you anticipate high volumes of storage and retrievals, or very large datasets, you may want to increase the max (-Xmx) heap size of the Java process.

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

rem Sun JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=128m

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

# Specify options to pass to the Java VM.
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=128m ..
fi

according available RAM and memory requirements of other processes on this node.
E.g.: if only 512 MB RAM are available, you should decrease the default value -Xmx512m to (e.g.) -Xmx300.

8. Mac OSX and Windows x64 specific changes for the WADO service:

Because there are no native codecs (compression/decompression) for these platforms, it is necessary to edit configuration to disable the loading of the native codecs. These platforms are not able to take advantage of compression/decompression. The only default loading of the codecs is in the WADO service. You can either edit the property within the JMX Console web user interface (see step 11), or edit the configuration files directly:

Change com.sun.media.imageioimpl.plugins.jpeg.CLibJPEGImageWriter to
com.sun.image.codec.jpeg.JPEGImageEncoder for the ImageWriterClass:

$DCM4CHEE_HOME/server/default/conf/xmdesc/dcm4chee-wado-xmbean.xml:
@@ -122,7 +122,7 @@
<name>ImageWriterClass</name>
<type>java.lang.String</type>
<descriptors>
- <value value="com.sun.media.imageioimpl.plugins.jpeg.CLibJPEGImageWriter" />
+ <value value="com.sun.image.codec.jpeg.JPEGImageEncoder" />
</descriptors>
</attribute>

9. Test the installation:

To test your installation, go to the dcm4chee-2.17.1-xxx/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:

=========================================================
.
14:46:16,046 INFO [Server] Starting JBoss (MX MicroKernel)...
14:46:16,046 INFO [Server] Release ID: JBoss [Zion] 4.0.3SP1 (build:
 CVSTag=JBoss_4_0_3_SP1 date=200510231054)
...
...
...
14:46:50,626 INFO  \-> [JkMain] Jk running ID=0 time=0/60  config=null
14:46:50,636 INFO  \-> [Server] JBoss (MX MicroKernel) \[4.0.3SP1 (build:
 CVSTag=JBoss_4_0_3_SP1 date=200510231054)\] Started in 34s:580ms

1. Connect to the Web-based User Interface (default URL is http://localhost:8080/dcm4chee-web/) of the archive using any Web Browser (most tested are Mozilla Firefox and Microsoft Internet Explorer v6.x). You should get the User Login Screen. Login in using the default Administrator account admin, with password admin.
2. Connect to the JBoss JMX Console (default URL is http://localhost:8080/jmx-console/) and login in using the default Administrator account admin, with password admin.
   Follow the link service=FileSystemMgt to the File System Management service configuration page under the dcm4chee.archive heading.
   Invoke the operation addOnlineFileSystem(), with a directory path argument specifying where the archive shall store received objects/images.
   

   Tip
   title Default Storage
   If no Storage File System is configured, the archive will auto-configure DCM4CHEE_DIST/server/default/archive as the Storage File System when the the first object/image is received.

3. Optional: In the default configuration, received images are stored 'as is' - meaning that no compression is performed. Lossless (or other types of) compression of received uncompressed images can be activated by the CompressionRules attribute in the Storage SCP Service (service=StoreScp) configuration page. For example, set it to JLSL, to compress all types of images received from any Storage SCU with JPEG-LS Lossless codec.
4. Optional: The directory used for caching generated JPEG representations of archived images requested by Web Access to DICOM Persistent Objects (WADO)can be specified by the CacheRoot attribute in the the WADO Service (service=WADOService) configuration page. Default: DCM4CHEE_DIST/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 with the CacheRoot attribute in the RID Service (service=RIDService) configuration page. Default: DCM4CHEE_DIST/server/default/ihe_rid_cache.
5. Send some objects/images to the archive's Storage SCP, using the send utility of the dcm4che14 package, the dcm4che2 package, or another Storage SCU of your choice.
   Refresh the Web Interface (http://localhost:8080/dcm4chee-web/), which should now show the the list of received studies.
   Expand a study row to show contained series. Expand one of these series to show contained instances. In the case of images, you can follow the image icon on the right to invoke an HTTP WADO request for a JPEG presentation of this image which will be displayed in a separate browser window.
6. To test object retrieval, you will need an external Storage SCP acting as the Destination using the DICOM Receiver utility of the dcm4che14 package, the dcm4che2 package, or another Storage SCP of your choice.
   Before initiating the retrieve, you will need to configure an additional Application Entity (AE) Title identifying your Move Destination using the "AE Management" function of the Web User Interface. For example:

   No Format
   AE Title: DCMRCV Hostname: localhost Port: 11112

7. Switch back to the Study List (the Folder view) and mark studies to retrieve using the check box on the right. Select "DCMRCV" as the send destination in the combo box above and click on the send button left from it.
   Alternatively, you could initiate a C-MOVE with the utility of your choice with DCMRCV as the destination AE Title.

...

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

JBoss Bootstrap Environment

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

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-2.17.1-psql/bin/native

CLASSPATH: /home/gunter/dcm4chee-2.17.1-psql/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

10. Login into web interface:

Connect to the Web Interface at http://localhost:8080/dcm4chee-web3/ of the archive using any Web Browser (most tested are Mozilla-Firefox and Microsoft Internet Explorer v6.x). You should get the User Login Screen. Login in using default Administrator account 'admin', with password 'admin'.

11. Login to JMX Console:

Connect to JBoss's JMX Console at http://localhost:8080/jmx-console/ and login using also the Administrator account 'admin', with password 'admin'.
Follow the link "group=ONLINE_STORAGE,service=FileSystemMgt" to the configuration page for File System Management service under the "dcm4chee.archive" heading.
Invoke the operation addRWFileSystem(), with argument dirPath specifying the directory, where the archive shall store received objects/images.

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

12. Optional: Change the default AE Title

Connect to JBoss's JMX Console at http://localhost:8080/jmx-console/ and login using also the Administrator account 'admin', with password 'admin'.
Follow the link "service=AE" to the configuration page for AE (Application Entity - a DICOM term for a DICOM node on the network) service under the "dcm4chee.archive" heading.
Invoke the operation updateAETitle with the old AE Title (DCM4CHEE if unchanged from the default), and new AE Title as parameters.
This will update the following configurations:

• update the retrieve AET of file systems, associated to the current retrieve AET of this node
• update retrieveAETs of all instances, series and studies that have files on these filesystems
• update the entry for the retrieve AE in the AE Configuration
• update the AE Title of all services listed by attribute OtherServiceAETitleAttributesToUpdate

13. Optional: Configure image compression:

As noted above, this is not applicable for Mac OSX or 64 bit Windows.

At default configuration, received images are stored as received - in particular, no compression is performed. Lossless compression of received uncompressed images can be activated by attribute "CompressionRules" in the configuration page for the Storage SCP Service (service=StoreScp). E.g. set it to "JLSL", to compress all type of images received from any Storage SCU using JPEG-LS Lossless codec.

14. Optional: Modify web image cache directories:

The directories used for caching generated JPEG representations of archived images requested by Web Access to DICOM Persistent Objects (WADO) can be specified by attributes "CacheDataRootDirectory" and "CacheJournalRootDirectory" in the configuration page for the WADO Service (service=WADOService).
Defaults: dcm4chee-2.17.1-xxx/server/default/wadocachedata and dcm4chee-2.17.1-xxx/server/default/wadocachejournal.

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 modifying BASE_DIR=docstore/rid/store in file conf/dcm4chee-docstore/dcm4chee-docstore-cfg.xml (this file will not exists before processing the first RID request).

15. Optional: Allow remote access:

Not necessary with versions 2.13.6 and newer!

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

16. Test DICOM storage:

Send some object/images to the archive's Storage SCP, e.g. by using the send utility of the dcm4che 2.x (dicom toolkit) core package available at Sourceforge here. E.g:

> dcm4che-2.0.23/bin/dcmsnd DCM4CHEE@localhost:11112 ~/mesa/storage/modality/MR

Refresh the Web Interface (http://localhost:8080/dcm4chee-web3/), which shall now show the the list of received studies. You may need to click the 'binocular' icon to initiate a search.

Expand one study row to show contained series. Expand one of these series to show contained instances. In the case of images, you can follow the image icon on the right, to invoke a http WADO request for a JPEG presentation of this image, which will be displayed in a separate browser window.

17. Test object retrieval:

To test object retrieval, you need an external Storage SCP acting as Move Destination, e.g. by using the receiver utility of the dcm4che 2.x DICOM toolkit:

> dcm4che-2.0.23/bin/dcmrcv 11113
13:55:14,782 INFO - Start listening on 0.0.0.0/0.0.0.0:11113
Start Server listening on port 11113

You also need to configure an additional Application Entity Title identifying this Move Destination. Do so in the "AE Management" tab within the Web user interface.
E.g. new AET
AE Title: DCMRCV
Hostname: localhost
Port: 11113

Switch back to the Study List ("Folder"), mark studies to retrieve using the check box on the right, select "DCMRCV" as send destination in the combo box above and click on the send button left from it.

18. Install as a service:

After verifying that the archive works, you may want to run it as a service so that it stays running even when you log out. If still running in the console window, you may stop the archive by Ctrl+C, and

Windows:

• install it as Windows service executing install_service.bat (see Running dcm4chee PACS as a Windows service or daemon)
• aditional notes:
  • to adjust maximum allocation of heap memory - you need to edit install_service.bat (not run.bat)
  • for 64-bit Windows download JavaService version 2.0.7.64 from http://javaservice.objectweb.org and replace file bin/JavaService.exe
  • if your service fails while starting ("Service could not be started") and you are using JDK 6:
    1. check your your Windows Event Log - if there are messages like "The specified module could not be found.", "Failed creating java ...\jvm.dll" - continue with next step
    2. try to add %JAVA_HOME%\bin to the system PATH environment variable, so java could find file mscvr71.dll (for details see https://issues.apache.org/bugzilla/show_bug.cgi?id=41538 and http://www.duckware.com/tech/java6msvcr71.html)
  • many versions of Windows need to be restarted after modifying environment variables (like JAVA_HOME and PATH)

Redhat and Ubuntu Linux:

• copy the init script dcm4chee_init_redhat.sh to /etc/init.d/ and adjust it according your installation location of the archive and the JDK and under which user the archive application shall run.

Mac OSX

• See this forum post (and others) for suggestions and startup item/plist scripts: http://forums.dcm4che.org/jiveforums/thread.jspa?threadID=593&tstart=0