module owb external execution
TRANSCRIPT
All information Copyright Bayon Technologies, Inc.
External Execution
run_my_owb_stuff.sql, sqlplus, Enterprise Manager
All information Copyright Bayon Technologies, Inc.
Why run externally?
Scheduling system OWB is “fat” Part of a “whole” GUI
HTMLDBFormsJDeveloper
All information Copyright Bayon Technologies, Inc.
OWB External Execution
run_my_owb_stuff.sqlAccesses Runtime RepositoryBlockingProvides “easy” interface
Runs FLOWS and MAPPINGS
All information Copyright Bayon Technologies, Inc.
“Clients” of run_my_owb_stuff
All information Copyright Bayon Technologies, Inc.
Using run_my_owb_stuff
Note “paramaters” are comma delimited key=value pairs
All information Copyright Bayon Technologies, Inc.
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”
All information Copyright Bayon Technologies, Inc.
Enterprise Manager
Enter PL/SQL block Schedule, periodic, resource groups, etc
All information Copyright Bayon Technologies, Inc.
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?