How to use job definitions?

Scheduled processes are based on jobs that process data and, in some cases, provide output. Each job requires a job definition. A job definition can also include parameters and user properties that the user defines while submitting the scheduled process.

You are encouraged to use predefined scheduled processes as is, so usually you don't need to do anything with job definitions. But if you do need something specific to your needs, you can create Oracle Analytics Publisher reports as the basis for custom jobs, and create job definitions for those custom jobs. You can also duplicate predefined job definitions and edit your copy, mainly to update the parameters. But, usually you wouldn't duplicate predefined job definitions. Some of them can't be duplicated anyway, and there are many limitations to consider with the duplicate.

To view, create, edit, or duplicate job definitions, use the Manage Job Definitions tab on the Manage Enterprise Scheduler Job Definitions and Job Sets page. In the Setup and Maintenance work area, here's where you go to open that page:

• Functional Area: Application Extensions a product-specific functional area

• Task: Manage Enterprise Scheduler Job Definitions and Job Sets

Viewing Job Definitions

Use the table on the Manage Job Definitions tab to view the job definitions created for the application. An asterisk in the name column indicates a predefined job definition. Not all job definitions are shown. You always see only the ones you have access to, and only the first 100 are shown when you open the tab.

Note:

Use Query by Example to find the job definition you're looking for, even those not shown in the table by default.

Table

Column Name	Description
Name	Name of the job definition.
Display Name	Name of the job definition as available to users while submitting scheduled processes.
Description	Description for the job definition.
Path	The full directory path where the job definition is saved.
Execution Type	The type of job request for the given job definition, such as a Java, C, PL/SQL, Perl, or hosted script job.
Job Type	The name of the job type that the job definition is based on. BIPJobType: Jobs that run as Oracle Analytics Publisher reports CJobType: Jobs that are implemented in C and run in the container HostJobType: Jobs that run as host scripts executed from the command line JavaJobType: Jobs that are implemented in Java and run in the container PerlJobType: Jobs that are implemented in Perl and run in the container PlsqlJobType: Jobs that run as PL/SQL procedures stored in a database server SqlLdrJobType: Jobs that are implemented in SQL*Loader and run in the container SqlPlusJobType: Jobs that are implemented in SQL*Plus and run in the container Note: If you create a brand new job definition (not by duplicating an existing one), the only job type you can use is BIPJobType.

Parameters

A parameter controls which records are included or how they are affected when the job runs. Parameters are available to users when they submit scheduled processes based on your job definitions. For example, a job updates only the records that are effective after the date that users enter in a Start Date parameter. You can create, edit and delete parameters for job definitions that are not predefined.

User Property

A user property is set in the job definition to attain some specific results.