...
- For Mac OSX and 64 bit Windows there is no free, native Image I/O implementation available. Because of the missing implementations you have to change 2 files a file in dcm4chee if you want to have RID and the WADO service running. Please have a look at step 8 to see how to change the files file (or modify the settings via the JMX console). See also:
...
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 and RID servicesservice. You can either edit the properties 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"
...
- />
...
and
...
</descriptors>
...
...
$DCM4CHEE_HOME/server/default/conf/xmdesc/dcm4chee-wado-xmbean.xml:
@@ -128,7 +128,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:
...
- </attribute>
No Format h4. 9. Test the installation: To test your installation, move to the dcm4chee-xxx-2.13.6/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:
...
...
- =========================================================================
...
JBoss
...
Bootstrap Environment
JBOSS_HOME:
...
/home/gunter/dcm4chee-psql-2.13.6
...
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.13.6/bin/native
...
CLASSPATH:
...
/home/gunter/dcm4chee-psql-2.13.6/bin/run.jar:
...
/usr/lib/j2sdk1.5-sun/lib/tools.jar
...
=========================================================================
...
23:17:52,373
...
INFO
...
...
Starting
...
JBoss
...
(MX
...
MicroKernel)...
...
23:17:52,374
...
INFO
...
...
Release
...
ID:
...
JBoss
...
...
4.2.2.GA
...
(build:
...
SVNTag=JBoss_4_2_2_GA
...
date=200710221139)
...
:
...
23:19:49,580
...
INFO
...
...
Starting
...
Coyote
...
AJP/1.3
...
on
...
ajp-127.0.0.1-8009
...
23:19:49,632
...
INFO
...
...
JBoss
...
(MX
...
MicroKernel)
...
[4.2.2.GA
...
(build:
...
SVNTag=JBoss_4_2_2_GA
...
date=200710221139)]
...
Started
...
in
...
1m:57s:
...
103ms
| No Format |
|---|
h4. 10. Login into web interface: |
...
Connect to the Web Interface at [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 default Administrator account 'admin', with password 'admin'. h4. |
...
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 "service=FileSystemMgt" to the configuration page for File System Management service under the "dcm4chee.archive" heading. |
...
Invoke the operation addOnlineFileSystem(), 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-xxx-2.12.x/server/default/archive as Storage File System, when receiving the first object/image. h4. |
...
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=FileSystemMgt" to the configuration page for File System Management service under the "dcm4chee.archive" heading. |
...
Invoke the operation updateRetrieveAETitle with the new AE Title as parameter. |
...
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 all service attributes listed by attribute OtherServiceAETitleAttributesToUpdate |
...
h4. 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. h4. |
...
14. _Optional:_ Modify web image cache directories: |
...
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.12.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.12.x/server/default/ihe_rid_cache. h4. |
...
15. _Optional:_ Allow remote access: |
...
*Not necessary with version 2.13.6\! |
...
* By default, JBoss does not bind to anything except the local address. Use |
...
run \-b 0.0.0.0 |
...
to allow running generic access. h4. |
...
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.0 core package available at Sourceforge [here|http://www.sourceforge.net/projects/dcm4che]. E.g: |
...
>
...
dcm4che-2.0.14/bin/dcmsnd
...
DCM4CHEE@localhost:11112
...
~/mesa/storage/modality/MR
| No Format |
|---|
Refresh the Web Interface ([http://localhost:8080/dcm4chee-web/]), which shall now show the the list of received studies. |
...
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. h4. |
...
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.0 DICOM toolkit: |
...
>
...
dcm4che-2.0.14/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
...
| No Format |
|---|
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
...