dcm4che2 Installation

In order to start using dcm4che, you must first download the distribution from SourceForge. To begin:

1. Download the binary distribution of dcm4che2 from SourceForge. If you plan on writing your own DICOM applications, it is recommended that you download the source distribution as well. The source may then be linked in with your IDE for debugging and browsing purposes.
2. Extract the archive file to the directory of your choice.

After extracting the contents, you should see the following directory structure:

dcm4che-2.0.12
|
|_bin
|
|_dtd
|
|_etc
    |
    |_dcmof
    |
    |_hpsamples
    |
    |_logger
    |
    |_tls
|
|_lib
|
|_xml

This directory listing may be described as follows:

• dcm4che-2.0.12
  • This is the root directory, named by "dcm4che" and the version. It doesn't contain anything other than the following subdirectories.
• bin
  • The bin directory contains Unix and Windows scripts to run the sample applications.
• dtd
  • The dtd directory contains DTD files which define the XML format of the DICOM data dictionary used by dcm4che2, and the XML format of DICOM objects.
• etc
  • The etc directory contains configuration used by the sample applications. There are a couple of subdirectories as well:
    • dcmof - information used by the Order Filler samples, currently only a sample Modality Worklist (MWL) Item (in XML format for submission to dcm4chee) resides here
    • hpsamples - sample hanging protocol data
    • logger - a sample log4j.properties file which defines a syslog appender.
    • tls - sample certificates for secured communications.
• lib
  • The lib directory contains the dcm4che2 libraries, all of the third party libraries that the toolkit depends upon, and individual JAR files for all of the samples.
• xml
  • The xml directory contains the XML definition of the DICOM data dictionary, and the DICOM UIDs that the toolkit will use. These items are inclusive of the DICOM 2006 standard, and are actually generated from the standard documents during the build process.

Installation tip for RedHat/Fedora

On Red Hat based systems (or Unix in general) there are some conventions, that newly installed applications should conform to. A lot of them - especially those not originating from this environment - do not do so. Such is the case with Sun Java, Maven and dcm4che2. It doesn't seem a big issue, however keeping some culture makes maintenance like updating with new versions, reinstalling the system from fresh, etc., makes for less hassle. The installation tips are covered Here

However if you can happily live with the standard way and don't want to do any unnecessary steps, stick with the basics and stop here..

This page has been viewed

times.