Housekeeping
This section deals with various housekeeping activities.
OpenVPMS Logs
The openvpms log files (in <TOMCAT-HOME>/logs) are kept under control by the settings in <TOMCAT-HOME>/webapps/openvpms/WEB-INF/classes/log4j.properties file. The standard setup is to 'rotate' these when they get to 1024KB and keep only 1 backup. Thus in a mature system you will see an openvpms.log.1 of size 1MB and a smaller openvpms.log (and similarly for the openvpms-full.log).
You can keep more data by increasing the log4j.appender.fileout.MaxBackupIndex parameter from 1 to something greater.
Note that the openvpms.log and openvps-full.log backups are not in sync (ie openvpms-full.log.1 does not contain the full data for the events in openvpms.log.1). This is because the full log grows significantly faster than the standard log.
If you wish to keep older synchronised versions then you need to implement a system for renaming the log files on a regular basis before they grow to 1MB in size. In unix systems this can be done using the logrotate facility. In windows systems you can have a bat file containing commands like the following and run it via the task scheduler.
set DSTAMP=%date:~6,4%-%date:~3,2%-%date:~0,2%
net stop "Apache Tomcat 6.0 Tomcat6"
net stop "MySQL55"
sleep 10
ren C:\openvpms\data\mysql-slow.log %DSTAMP%-mysql-slow.log
ren C:\openvpms\data\mysql-slow.log %DSTAMP%-mysql-error.log
ren "C:\Program Files\Apache Software Foundation\Tomcat 6.0\logs\openvpms.log" %DSTAMP%-openvpms.log
ren "C:\Program Files\Apache Software Foundation\Tomcat 6.0\logs\openvpms-full.log" %DSTAMP%-openvpms-full.log
..... other stuff to backup database etc
net start "MySQL55"
net start "Apache Tomcat 6.0 Tomcat6"
exit
docload Destination Directory
The document loader destination directory receives the files that have been loaded. Since the documents are now in the database, these files can either be deleted or archived elsewhere.
Note that regularly sweeping this directory allows the document loader to load updated copies of documents when the overwrite option is set. Otherwise if the document 3214567_xray.jpg was previously loaded, then when an attempt is made to load an updated copy, this will fail because the file 3214567_xray.jpg is already present in the destination directory.