Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Upgrade could be complex task, depending on changes in configuration files of basic dcm4chee installation.

There is root folder name change between versions 2.14.7 and 2.14.8 - i was dcm4chee-xxx-2.yy.y and now it is dcm4chee-2.yy.y-xxx.

Upgrade Procedure:
  1. Shutdown dcm4chee
  2. Extract the new version to a different folder dcm4chee-2.yy.y-xxx
  3. Copy files from JBoss to dcm4chee (see points 2. and 3. of Instalation Instructions)
  4. If you have installed Audit Record Repository, then install it (see point 5. of Instalation Instructions)
  5. Copy all following directories/files from old to new installation directory:
    • dcm4chee-xxx-2.xx.x/server/default/archive (if there are your DICOM archive files)
    • dcm4chee-xxx-2.xx.x/server/default/data/xmbean-attrs (there are MBean settings)
    • dcm4chee-xxx-2.xx.x/server/default/deploy/pacs-*-ds.xml (if you have older version, its name may be *-ds.xml - then rename it)
    • if you have installed Audit Record Repository, then copy dcm4chee-xxx-2.xx.x/server/default/deploy/arr-xxx-ds.xml
    • if you replaced JAI Image IO files in dcm4chee-xxx-2.xx.x/bin/native then copy them
    • if you changed or added any other files manually, then you should merge them to their new dcm4chee versions (it may be complex task), i.e. run.bat, run.conf (changing heap memory), JavaService.exe, dcm4chee-xxx-2.xx.x/server/default/conf/*
  6. Execute every upgrade script in the dcm4chee-2.yy.y-xxx/sql directory higher then your current version (means if you have 2.11.x execute update-2.12.xxsql, update-2.13.xxsql and update-2.14.xxsql upgrade scripts)
  7. Start dcm4chee
  • No labels