Use to configure and execute scenarios.
A scenario is designed to put a source component (mapping, package, procedure, variable) into production. A scenario results from the generation of code (SQL, shell, and so forth) for this component.
The Scenario Editor has the following tabs:
| Properties | Description |
|---|---|
| Package/Mapping/Variable/Procedure | Name of the component used to create the scenario. |
| Name | Name of the scenario. |
| Version | Version of the scenario. |
| Deployment | Deployment plan used for generating the scenario. |
| Description | Detailed description of the scenario. |
Concurrent Execution Controller
| Properties | Description |
|---|---|
| Limit Concurrent Executions | If checked, enables the Concurrent Execution Controller for the Scenario. |
| Violation Behavior | Specifies the violation behavior action. Default is Raise Error and End Execution. |
| Wait Polling Interval | Specifies the polling frequency (in seconds) for the wait behavior to check for its turn to run. This field accepts only a positive integer, and it is enabled only when Violation Behavior is selected as Wait.
Note: A newly generated scenario or a newly created load plan has blank as the default value, meaning that the runtime agent determines the actual value used for the polling (currently the default is 30 seconds in the runtime agent). |
Click Execute to launch the scenario. The editor for selecting the execution options opens.
This tab allows you to select the scenario variables. They are displayed as parameters when starting the scenario or when creating a schedule. Selecting parameter variables enables you to hide the user variables that cannot be considered as parameters.
If the Use All value is selected, then all variables are considered as parameters. If the Use Selected value is selected, you can select the variables to use as parameters.
"Introduction to Scenarios" in the "Using Scenarios" chapter in Oracle Fusion Middleware Developing Integration Projects with Oracle Data Integrator