Installation dcm4chee 2.18.3

Instructions

write me to WhatsApp for the installation instructions

https://api.whatsapp.com/send?phone=573166182057

Version 2.18.3 is the latest version of the file. It is recommended that you install this version

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

Minimum system requirements

JDK 5 or higher
512 MB of RAM
200 MB of hard disk space (additional to file storage disk space)
400 MHz CPU

Supported Databases

Need to install separately.

PostgreSQL 8.1+
MySQL 4.1+
Oracle 9i+
SQL Server 2012+

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.18.3-mysql.zip for the MySQL 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. Copie los archivos de JBoss a dcm4chee:

C:\pacs\dcm4chee-2.18.3-xx\bin> install_jboss.bat c:\pacs\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

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.18.3-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.18.3-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. Test the installation:

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

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

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

9. 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'.