Oracle® Business Intelligence Scheduler Guide > Oracle BI Scheduler Job Manager Menus >

Job Actions in Oracle BI Scheduler Job Manager


Table 14 describes the job action properties available in the Add Job and Modify Job dialog boxes. Use the fields in the Script area of the Add Job or Modify Job dialog box to define the actions a job performs when it executes.

Table 14. Job Manager Job Action Fields
Field
Description

Script Type

Oracle BI Scheduler supports VBScript, JScript, Java, and NQCmd. Set this field according to the type of script referenced by the Script field. The fields that appear depend upon the type of script that you specify.

Script Contains File Name

(VBScript and JScript, only) In the Job Manager, you can enter either a file name or the actual contents of a script in the Script field. Click this option if the Script field contains a file name.

Script

(VBScript and JScript, only) This value is either a reference to a job script file or the contents of a job script itself. If it is a reference, enter a file name in this field, such as TestConnect.js. If no path is given, Oracle BI Scheduler examines the directory referred to in the Default Script Path configuration value in the Scheduler tab of the Job Manager Configuration dialog. If a path is given, the path must be accessible by the Oracle BI Scheduler application.

Parameters

(VBScript, JScript, and Java, only) Field values are passed to the job script through the Parameters array. Enter one parameter per line. For example:

c:\oracleBI\data\scheduler
cli_snowflake
SELECT Lastname FROM Employee

Class Name

(Java, only) The fully qualified implementation class for the Java program action.

Class Path (jar file)

(Java, only) The name of the jar file containing the Java program.

Additional Class Path(s)

(Java, only) Other jar files containing the utility classes and libraries that the Java program needs to run properly. These are coma separated jar files.

DSN (Data Source Name)

(NQCmd, only) The data source name that OBISch uses to connect to OBIS.

NOTE:  Impersonation is used with NQCmd. The value in the User ID is the user that OBISch tries to impersonate when connecting to OBIS.

SQL Input File

(NQCmd, only) The fully qualified path to the SQL file that NQCmd executes. Type the full path or click the ... button to browse to the file's location. This field is typically used for files generated by the aggregate persistence feature.

Additional Command Line Parameters

(NQCmd, only) Parameters that are passed to NQCmd. Enter one parameter per line. For example:

-o
D:\foo\bar.txt

Oracle® Business Intelligence Scheduler Guide Copyright © 2007, Oracle. All rights reserved.