Cisco Cisco Workload Automation 6.3 User Guide

Page of 42
20
Initial Configuration Recommendations
Performance Tuning
4.
On the Logging tab, set these parameters:
Audits—The number of days to keep audits. Affects the audit log of Job Activity jobs, or the Operations->Logs. This 
corresponds to the msglog table in the database.
Errors—The number of days to keep the messages that show up as the "error" type, in Operations->logs. Also the 
msglog table.
5.
On the Defaults tab, set this parameter:
Job History Retention—The number of days to keep the job history retention for each of the job instances in the job 
activity. Every job instance that runs is assigned a date on which it is to be purged based off of it's job definition's 
Options tab -> History Retention value. So if a job ran when that number was 100, it won't expire until 100 days from 
now, even if the job's definition is edited, since the job instance information has already been written. Mass edits on 
the backend would compromise the stability of the database, so to avoid that, edits to the job retention values in the 
job definition do not affect job instances that have already run.
Performance Tuning
See the Cisco Workload Automation Performance and Tuning Guide for details about performance and tuning. This guide 
describes:
How to optimize CWA performance.
How to monitor CWA scheduling, connections, the cache, and performance.
How to tune CWA.
Best practices for Transporter performance.