Introduction to Scenarios

1. Generate Scenario After Component Completion:
• Once a component is finished and tested, you can generate the corresponding scenario for its actual state.
• This operation is performed in the Designer Navigator.
2. Scenario Code Freezing:
• The generated scenario code is frozen after creation.
• Any further modifications made to the components involved in creating the scenario will not impact the generated scenario.
3. Types of Scenarios:
• Scenarios can be generated for:
• Packages
• Procedures
• Mappings
• Variables
• Procedure, mapping, or variable scenarios are considered single-step scenarios, meaning they will execute the procedure, mapping, or refresh the variable.
4. Scenario Variables:
• These are variables used within the scenario that should be defined before running the scenario to parameterize its behavior.
5. Scenario Storage and Export:
• Once a scenario is generated, it is stored inside the work repository.
• The scenario can be exported and then imported into another repository (whether remote or local) and used in different contexts.
• Scenarios can only be created in a development work repository but can be imported into both development and execution work repositories.
6. Visibility of Scenarios:
• Scenarios appear in:
• Operator Navigator and Designer Navigator under the Load Plans and Scenarios section.
• Projects section within a project in the Designer Navigator.
7. Versioning:
• Scenarios can be versioned, providing version control for tracking changes over time. (For more information, see Using Version Control (Legacy Mode)).
8. Launching Scenarios:
• Scenarios can be launched in different ways:
• From the command line
• From the Oracle Data Integrator Studio
• They can be scheduled using the built-in scheduler in the run-time agent or through an external scheduler.