Thursday, March 14, 2013

Third-Party Triggering of Oracle BI Scheduler Jobs

Third-party applications and scripts can launch an Oracle BI Scheduler job from the command line. They can also change the Job Parameters for a single instance. This change simulates third-party-triggered iBots. The interface for the command line is:

saschinvoke.exe -u <Admin Name>/<Admin Password> (-j <job id> |
-i <iBot path>) [-m <machine name>[:<port>]] ([-r <replace parameter filename>] | [-a <append parameter filename>])
The required parameters <Admin Name> and <Admin Password> are the same as those configured for Oracle BI Scheduler where you invoke the job. You can invoke the job either by the job ID or by the iBot path. Optionally, you can specify a machine and port for Oracle BI Scheduler server. If this is omitted, the invoker uses localhost and 9705 respectively.
The invoker also takes an optional job parameter file. Depending on the mode you choose, the parameters configured in Oracle BI Scheduler are changed in one of the following ways by the options in the job parameter file:
  • Replace the existing parameters, using the following syntax:
    [-r <replace parameter filename>]
  • Append to the existing parameters, using the following syntax:
    [-a <append parameter filename>]
  • When using a parameter file, employ the following rules:
    • Use only one parameter per line.
    • Do not ignore white space because it may be custom script-dependent.

Using Replace Mode

In replace mode, the file can specify to leave some parameters as they are in Oracle BI Scheduler. To specify this for a specific line, enter $SCH_DEFAULT$ on the line. This text string acts as a variable and replaces the $SCH_DEFAULT$ text with the text from the original Oracle BI Scheduler parameter.
For example, if the original parameter is hello, the line
$SCH_DEFAULT$ world, $SCH_DEFAULT$ again
is changed to
hello world, hello again
If you use the saschinvoke command, make sure the job parameters are correct. The saschinvoke command does not test the parameters for correctness. A job may not properly execute if invalid parameters are passed to it.

Satya Ranki Reddy

No comments:

Post a Comment