1. What is a scenario in ODI?
· A scenario is a production-ready version of a component (mapping, package, procedure, or variable)
· It contains generated code (SQL, shell scripts, etc.) based on the component’s current state
· Once generated, the scenario is frozen — further changes to the component do not affect the scenario
2. When should a scenario be generated?
· After a component is finished and tested
· Ensures a stable, reproducible execution of the component in production
3. What types of components can have scenarios?
· Mappings → Single-step execution of the mapping
· Packages → Multi-step ETL process
· Procedures → Executes the procedure as a single step
· Variables → Refreshes or updates the variable
4. What are scenario variables?
· Variables defined in the scenario to parameterize its behavior
· Values can be set at execution time to control logic and flow
5. Where are scenarios stored?
· Stored in the work repository
· Can be exported and imported across repositories
· Can be imported into development or execution repositories
6. How are scenarios displayed in ODI?
· In Designer Navigator → Under the source component in the Projects tree (development only)
· In Operator Navigator → In the Scenarios tree (visible in both development and production)
7. Can scenarios be versioned?
· Yes, scenarios support versioning for change tracking and deployment
· See Chapter 19, Using Version Control for detailed version management
8. How can scenarios be executed?
· Command line execution → For automated scripts or CI/CD
· ODI Studio → Run interactively from the GUI
· Scheduler → Built-in agent scheduler or external scheduler for automation
9. Why use scenarios instead of direct components in production?
· Provides a stable, frozen version of the code
· Prevents unintended changes in production execution
· Supports reproducibility, scheduling, and deployment across environments
No comments:
Post a Comment