Cisco Cisco Workload Automation 6.3 User Guide
59
Getting Started
System Configuration
System Configuration - Master Tab
The Master tab configures actions managed by the master. This tab contains the following elements:
Future Days to Include in Schedule – Controls the number of future days to include in the production schedule when
the master does its daily compilation. Larger values let you schedule jobs farther into the future. Lower values reduce
compilation time.
the master does its daily compilation. Larger values let you schedule jobs farther into the future. Lower values reduce
compilation time.
Note: When you change the Future Days to Include in Schedule value, the new value will not take effect until the
production schedule is compiled. Compilation will take place at midnight, by default.
production schedule is compiled. Compilation will take place at midnight, by default.
Operator Alert Retention (in days) – The number of days to keep operator alert information in the Job Activity pane.
Note: By default, alerts are kept for seven days. Alerts that are older than the Operator Alert Retention value are
purged daily.
purged daily.
Trigger History Retention (in days) – Sets the default number of days to maintain event trigger history on the Trigger
History tab of the Event Details dialogs. The maximum length of time to keep trigger history information is 9,999
days but this length of time requires very large amounts of hardware and resources and hampers performance.
The default setting is for 30 days.
History tab of the Event Details dialogs. The maximum length of time to keep trigger history information is 9,999
days but this length of time requires very large amounts of hardware and resources and hampers performance.
The default setting is for 30 days.
Use Passwords to Run Windows Jobs – Enables (if checked) Windows agents to use Windows passwords.
Windows agents can be configured to use a per-job password. Each scheduled job can be configured to run under
a specific username and password (runtime users). The job inherits the permissions and resources of the assigned
user account. This means that all runtime users require valid passwords. Any jobs that log on as users with invalid
or missing passwords will fail with a status of Error Occurred.
Windows agents can be configured to use a per-job password. Each scheduled job can be configured to run under
a specific username and password (runtime users). The job inherits the permissions and resources of the assigned
user account. This means that all runtime users require valid passwords. Any jobs that log on as users with invalid
or missing passwords will fail with a status of Error Occurred.
CWA stores the passwords in encrypted form within its own database. At no time is an unencrypted password
echoed to the screen or made otherwise accessible to any user. Passwords are also encrypted when passed from
a master to an agent.
echoed to the screen or made otherwise accessible to any user. Passwords are also encrypted when passed from
a master to an agent.
Caution: Checking the passwords of multiple users when running jobs restricts the Windows agent to only
processing 30 jobs concurrently. If passwords are not used when running Windows jobs, the Windows agent can
handle up to 80 concurrent jobs.
processing 30 jobs concurrently. If passwords are not used when running Windows jobs, the Windows agent can
handle up to 80 concurrent jobs.
CWA stores the passwords using 64-bit block cipher encryption within its own database. At no time is an
unencrypted password echoed to the screen or made otherwi se accessible to any user. Passwords are also
encrypted when passed from a master to an agent.
unencrypted password echoed to the screen or made otherwi se accessible to any user. Passwords are also
encrypted when passed from a master to an agent.
Automatic Daily History Cleanup – When this option is selected, CWA automatically purges the database everyday.
By default, the purge is executed at the beginning of the new production day.
By default, the purge is executed at the beginning of the new production day.
Note: The master will log any errors when purge is performed automatically.
When this option is not selected, CWA will not automatically purge your database of old information history.
FTP Local User Mandatory – Requires that a local (or runtime) user be selected on the Run tab of FTP job definitions.
Using a runtime user adds additional security to FTP jobs. The default is to not use a runtime user (unselected). If
this option is selected, any previous FTP jobs that were defined without assigning a local user, will error out until a
local user is assigned to the job.
Using a runtime user adds additional security to FTP jobs. The default is to not use a runtime user (unselected). If
this option is selected, any previous FTP jobs that were defined without assigning a local user, will error out until a
local user is assigned to the job.
None (except Launched/Active Jobs) – Do not transfer any jobs from the current production schedule to the next
production schedule unless the jobs have already launched or are in active status. (On an individual basis, jobs can
be prevented from carrying forward by selecting the Disable carryover option from the Options tab of the Job
Definition dialog.)
production schedule unless the jobs have already launched or are in active status. (On an individual basis, jobs can
be prevented from carrying forward by selecting the Disable carryover option from the Options tab of the Job
Definition dialog.)
Successors only (unless disabled for job) – Transfers to the following production schedule any successor jobs from
active jobs in the current production schedule unless the Disable carryover option was selected in a job’s definition.
active jobs in the current production schedule unless the Disable carryover option was selected in a job’s definition.