Customizing Archive/Load Scripts
Four script templates are provided under the installation directory of QAD Enterprise Applications, two for UNIX (or Linux) and two for Windows:
UNIX:
aud_archive.tpl — Audit archive data
aud_load.tpl — Audit data load
Windows:
aud_archive.wtp — Audit data archive
aud_load.wtp — Audit data load
The basic approach is to allow the user to have the customized archive script running on the applications database server, and the load script running on the archive database server. Users can configure the scripts as batch tasks to automate the process as needed.
To use the templates, first choose the right templates according to the operating system type. Change the file extension to .bat for Windows scripts or .sh for UNIX (or Linux) scripts.
Next, modify the related settings:
• Set the database name, database directory, and DLC.
• Make sure the Progress database user has a non-blank password and proper privileges (Audit Data Archiver).
Run the archive script. The archive file named DBNAME.abd is generated in the directory ARCHDIR/DBNAME/DATEDIR, where DATEDIR is named based on the archive date and time. The related information is recorded in the log file in the LOG directory. The user is informed of the result. Check the log file if there are any issues.
Run the load script. In some circumstances, before loading the data, you might need to manually move the file to a location that the load script can access.
The UNIX (or Linux) scripts can also send e-mail to the mail address USER_TO_NOTIFY to report the result.