...
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:
- Download the dcm4chee Audit Record Repository 3.0.7 (dcm4chee-arr-3.0.7) available at
http://sourceforge.net/projects/dcm4che. Be sure to download the distribution package of dcm4chee-arr-3.0.7 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). - Move to the dcm4chee-xxx-2.14.2/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 installation directory as
parameter.- If you want the Audit Record Repository shall to use a different database instance than the archive to store received Audit Records (this is recommended), create the audit record repository database instance: arrdb, and grant sufficient privileges to the DB user , configured in (see the datasource descriptor deploy/arr-xxx-ds.xml . Optionally, you may also initialize the database using create DDL script dcm4chee-arr-xxx-3.0.7/sql/dcm4chee-arr-xxx.ddl. Otherwise, the database will be initialized automatically at first startup of the application.If the Audit Record Repository shall share the database instance already used by the archive, you have to modify database name - but NOT the JNDI name! -, user and password in the datasource descriptor for user information).
- 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 with the values specified in the main datasource descriptor file deploy/pacs-xxx-ds.xml for the
archive database. OptionallyThe ARR schema will automatically be created upon startup, but if you want to tweak the SQL or do it manually, you may update also initialize the database with dcm4chee-arr specific tables using modified create using the provided DDL script dcm4chee-arr-xxx-3.0.7/sql/dcm4chee-arr-xxx.ddl: . Note that you will have to remove or comment out the creation of already exisiting existing 'code' table. But missing tables will be also initialized automatically at first startup of the application.
6. Set environment variable JAVA_HOME to JDK location.
...