Cisco Cisco Workload Automation 6.3 User Guide

Using the Oracle Applications Adapter

Working with Oracle Applications Jobs

Deleting Oracle Applications Jobs from the CWA Database

Oracle Applications jobs are deleted like other CWA jobs but the jobs are deleted from the CWA database only. They 
must be deleted from the Oracle database as a separate task. 

The default job history retention period for jobs in general is configured on the Defaults tab of the System Configuration 
dialog. You can set job history retention for an individual job on the Options tab of its job definition. CWA will 
automatically delete job history from its own logs when the job history retention limit is reached. The default retention 
period is 30 days. To delete the job history from Oracle database is a separate procedure. 

Deleting Oracle Applications Jobs from the Oracle Database

You must periodically delete jobs from the Oracle database as a matter of database maintenance. You can do this 
maintenance as a scheduled job in CWA. 

Concurrent request records are created each time an Oracle Applications job is submitted by the CWA. As these records 
accumulate and become obsolete, they must be deleted as a routine maintenance task. 

Oracle Applications provides a concurrent program, called Purge Concurrent Request and/or Manager Data Program, to 
purge the datatables of these old request records. You can schedule this program in CWA to purge request records on 
a regular basis. 

Managing User-Submitted Oracle Applications Jobs

A dynamic production environment requires a way to manage jobs that are submitted outside of the CWA. While end 
users may run unscheduled jobs, high volumes of these jobs will impact the timely completion of the day’s production 
schedule. On the other hand, the production manager must ensure enough flexibility exists in the system to 
accommodate the inevitable unscheduled jobs that occur during a production day. The need for balancing system 
resources between scheduled and unscheduled jobs is heightened by the limitations on the number of available 
background work processes in Oracle.

To improve manageability, CWA’s queue management facility supports a queue filter that can be configured to monitor 
an Oracle Applications instance for ad hoc jobs submitted by users or programs and assign them to a designated queue 
where they can be managed. By intercepting the ad hoc jobs and directing them to designated queues, the launching of 
unscheduled jobs can be regulated with priorities and limits of both jobs and queues, to manage resources better. 

This queue filter, called 

, can be created to designate a queue or queues that will capture 

any submitted Oracle jobs that do not belong to the day’s production schedule. 

With this interception filter monitoring for Oracle jobs, you can separate unscheduled Applications jobs generated 
outside of CWA from other scheduled jobs and direct those unscheduled Oracle Applications jobs to different queues 
where the jobs are controlled by the Queue Manager using the same limits on jobs, priorities and hierarchies typically 
assigned to a queue. You can add as many Oracle queue filters as needed to cover any combination of users, jobs and 
instances. By intercepting these ad hoc Oracle jobs before they are launched, CWA manages system resources by 
controlling when the jobs are launched based on queuing rules.