External Execution run_my_owb_stuff.sql, sqlplus, Enterprise Manager

Why run externally? Scheduling system OWB is “fat” Part of a “whole” GUI HTMLDB Forms JDeveloper

Scheduling system

OWB is “fat”

Part of a “whole”

GUI

HTMLDB

Forms

JDeveloper

OWB External Execution run_my_owb_stuff.sql Accesses Runtime Repository Blocking Provides “easy” interface Runs FLOWS and MAPPINGS

run_my_owb_stuff.sql

Accesses Runtime Repository

Blocking

Provides “easy” interface

Runs FLOWS and MAPPINGS

“ Clients” of run_my_owb_stuff

Using run_my_owb_stuff Note “paramaters” are comma delimited key=value pairs

Note “paramaters” are comma delimited key=value pairs

SQLPlus / Shell Scripts / PLSQL Use run_my_owb_stuff Build map.sql script sqlplus owb_rt/pw@sid @map.sql Wrap with a “shell script”

Use run_my_owb_stuff

Build map.sql script

sqlplus owb_rt/pw@sid @map.sql

Wrap with a “shell script”

Enterprise Manager Enter PL/SQL block Schedule, periodic, resource groups, etc

Enter PL/SQL block

Schedule, periodic, resource groups, etc

Questions for Discussion T/F: Any person or system that runs an OWB mapping or process requires a license. What is missing from external runs with run_my_owb_stuff? How can we overcome this?

T/F: Any person or system that runs an OWB mapping or process requires a license.

What is missing from external runs with run_my_owb_stuff?

How can we overcome this?