Running mappings from OWB Browser
By Jean-Pierre Dijcks on May 18, 2007
It seems that this is a hidden feature in the browser, so lets see how you can actually start mappings (and process flows) from the OWB Browser in 10gR2 (this was not possible in 10gR1).
Create a mapping, and to make it more fun, add a mapping input parameter. The parameter is called ID_FLT_CLAUSE
The map is quite simple and it serves the purpose of being an example. Just as a note, this could be a very good way to do CDC on objects that have last_update_date like columns...
After deploying the mapping (either directly from the design center or from the control center) you can start the mapping. If you do so with parametized mappings make sure that you set the preference to ask OWB to prompt for execution parameters. Also if you have the habit to run mappings directly from the design center, check the preference to Show design center deployment job (this also shows the execution).
Running a mapping from the client will give you this screen, with the entry option for the ID_FLT_CLAUSE:
Notice that you can enter a value here for the input parameter (highlighted).
So far I think people will know how this works. The same functionality is however also available in the Browser. To explore that, log in to the browser on your environment (and start the local OC4J from the client). Go to the runtime reports and find your mapping.
If you had some previous runs, you will get something like this:
Then click on the Start entry (top right of the browser page, under available reports). The screen will show (automatically) the next step, and you can now change or fill in the actual parameters. Note that the parameters are labeled, either Custom or System. In most cases you only want to change the Custom entries (set the System ones as desired in mapping configuration).
After filling in the value again for the custom parameter (see highlighted line) click the Start Execution button on the page.
The page will refresh, make sure to visit the Execution Job Report on the refreshed page. That will give you the status of the current execution. The important part in this example (here already expanded) is the normally collapsed node for execution parameters. The node is collapsed to make room for the actual audit details (not shown here). You can see the parameter results including values for custom.
Some other things to note on the pages. One is that you can actually issue a Stop Execution from the browser. Once the database receives this command it will try to stop the execution. In many cases this will not be instantly done! The other button is Expedite Execution. If you include for example a manual activity in a process flow, this is the button that allows you to say "continue".