Page Comparison

...

1. Download the dcm4chee Audit Record Repository 3.0.5 (dcm4chee-arr-3.0.5) available at http://sourceforge.net/projects/dcm4che. Be sure to download the distribution package of dcm4chee-arr-3.0.5
   for the database of your choice. - It may differ from the database used for dcm4chee archive if you wish.
2. Move to the dcm4chee-xxx-2.13.56/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.5 installation directory as
   parameter.
   1. If the Audit Record Repository shall use a different database instance than the archive to store received Audit Records, create the audit record repository database instance: arrdb, and grant sufficient privileges to the DB user, configured in the datasource descriptor arr-xxx-ds.xml. Optionally, you may also initialize the database using create DDL script dcm4chee-arr-xxx-3.0.5/sql/dcm4chee-arr-xxx.ddl. Otherwise, the database will be initialized automatically at first startup of the application.
   2. 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 arr-xxx-ds.xml, to match with the values specified in the datasource descriptor pacs-xxx-ds.xml for the
      archive database. Optionally, you may update the database with dcm4chee-arr specific tables using modified create DDL script dcm4chee-arr-xxx-3.0.5/sql/dcm4chee-arr-xxx.ddl: you have to remove or comment out the creation of already exisiting 'code' table. But missing tables will be also initialized automatically at first startup of the application.

...

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

Migrate Audit Records received by DCM4CHEE Audit Record Repository 2.x to 3.x:

Audit Records received by dcm4chee-arr-2.x and stored in database table 'audit_record_old' can be migrated to dcm4chee-arr-3.x by re-emission to the new Audit Record Repository by service 'MigrateOldARR':

1. Connect to JBoss's JMX Console

at http://localhost:8080/jmx-console/ and login using the Administrator account 'admin', with password 'admin'.
Follow the link "service=MigrateOldARR" under the "dcm4chee.archive" heading.

Invoke the operation emitAuditRecords(), with argument num=1, to test the
migration on the first Audit Record in table audit_record_old.

Check in the Audit Record Repository Web Application (http://localhost:8080/dcm4chee-arr) if the record is now stored by dcm4chee-arr-3.x.

2. Determine the number of Audit Records to migrate by (e.g.) executing

SELECT count ( * ) FROM audit_record_old

using any SQL client of your database.
Estimate the migration time for all Audit Records by configured

EmissionInterval x count.

If the estimated time exeeds several hours, you may consider - to split the migration in chunks of records, and/or - decrease the configured EmissionInterval from default 100 ms (but which will increase the load for the Database during the task is running)

3. Invoke the operation emitAuditRecords():

...