When it comes to supervising data in your DOCUMENTS system, consider implementing the following key routines:
Monitor the flow of data in your system on a regular basis.
Analyze how long the data should be directly accessible in the production environment.
Include the setting when you define production tasks including the Output activity.
If you have problems uploading output files to a target system, consider deselecting this setting. Be aware that if you do not manually delete these documents later, then they will accumulate in the database.
Decide which routine you will use for reprocessing documents that become corrupt.
Configure and regularly run a maintenance plan for your runtime system.
Aim at storing one only month of operation statistics at any one time, and reduce this to a two-week maximum for a high-volume installation.
Specify where log files are stored and, more importantly, the which level of logging best fits your needs.
Checking locks older than one hour for automatic production tasks running as services.
Checking locks older than 12 hours for manual production tasks and activities.
Checking service logs.
Access production data on the Administration module's tab.
The document status tells you where documents are in the production flow.
Specify what information to include in audit trails and view the system-wide and document-specific data to learn who did what and when.
Use the log files for troubleshooting and checking DOCUMENTS and operating system events.
Create routines for dealing with common problems related to data integrity and the data flow.