Cisco Cisco Workload Automation 6.3 User Guide

Using the Oracle Applications Adapter

Working with Oracle Applications Jobs

Intercepting Oracle Applications Jobs

The filter to intercept Oracle jobs can be created by clicking the 

 button on the 

 tab of the 

dialog and selecting the 

option. Job interception will not work unless 

table has been properly configured as described on 

This 

 dialog contains the following options that can be used as needed to fine-tune filter criteria:



– Specifies the Oracle instance that should be monitored for jobs scheduled outside of CWA.



– Specifies that jobs that originate from the specified application will be intercepted.



– Specifies that jobs that originate from the specified responsibility will be intercepted.



– Designates that the queue filter monitor for jobs submitted by the specified user (or creator) of the Oracle 

jobs. A mask using the asterisk (*) wildcard character can be used here.



– Creates a mask with the asterisk (*) wildcard character (though wildcards do not need to be used) 

to intercept particular jobs that originating from programs that meet the specified criteria.



– Creates a mask using the asterisk (*) wildcard character (though wildcards do not need to be 

used) to intercept jobs originating from requests that meet the specified criteria.

You can use as much of the criteria as needed to create a broad based or specific filter. Only the Oracle jobs that match 
all of the specified criteria will be filtered out for controlled release. These intercepted jobs are placed on hold and can 
be viewed from the 

 dialog.

The 

 tab of the 

 dialog for the queue defined to accept the intercepted Oracle jobs 

displays all jobs that are active or waiting to run. You can double-click on any of the jobs listed on the 

 tab 

to see basic information about the Oracle job in the 

 dialog. 

The

 queue filter manages the launching of ad hoc Oracle jobs. Here are a few scenarios to 

demonstrate how the queue filter works.

For the scenarios, let us assume that an Oracle Applications parent queue contains two child queues–one for externally 
submitted jobs and one for production jobs created by CWA. The externally scheduled jobs queue (called EB Queue for 
External Jobs in this example) also has an Oracle interception filter defined, with a limit of one, and the production queue 
(called EB Queue for Cisco Workload Automation Jobs) has a Production Oracle Connection filter and a queue limit of 3. 

Release a scheduled job from CWA. It will go to the EB Queue for Cisco Workload Automation jobs, launch and go into 
an Active status since an execution slot is available.

From Oracle, release a job (using the same user defined in the Oracle Applications interception filter). Since there is a 
queue with a defined Oracle Applications job interception filter, the unscheduled job goes to the EB Queue for External 
Jobs. There is an execution slot available so the job is launched and the EB queue for externally scheduled jobs shows 
the job is active.