If you are trying to upgrade your DocCare to a newer version, or you trying to move DocCare to a different physical machine, then you probably will do data migration.
DocCare data migration is to migrate DocCare documents, database schema data and user logs from an existed DocCare instance to a different DocCare instance.
First, Backup DocCare data online.
Second, install a new DocCare instance.
Third, if you do not plan to use the embedded HSQLDB database server, you should create a schema for DocCare manually. Detail to seeCreate Database Schema and User
Forth, check conf/database.properties to make sure that the JDBC configuration is correct.
Fifth, copy the right version of database migration SQL script from ${BURGEONSOFT_HOME}/upgrade to ${BURGEONSOFT_HOME}/install/schema.
Sixth, check DOCUMENT_REPOSITORY parameter in deploy/04resourcemanager.sar/services.xml. Make sure the document repository is empty. Detail to see Configure Document Repository
At last, execute the following commands:
On Windows platform, execute:
${BURGEONSOFT_HOME}\bin\restore.bat <absolute_path_of_backup_archive>
For example:
On Unix/Linux platform, execute:
${BURGEONSOFT_HOME}/bin/doccare.sh restore <absolute_path_of_backup_archive
For example:
DocCare will re-build the document index during the migration.
If the size of the backup archive is very large, the migration may cost a long time. Currently, DocCare does not know when the migration will complete. If you see ‘Closed Resource Index’ from console output, then it means the migration is completed. You can press Ctrl+C to exit the migration.
After migration is done, you can start DocCare as normal.
Relate topics: