Module Owb Lifecycle

1,388 views
1,294 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,388
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
71
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Module Owb Lifecycle

    1. 1. OWB Lifecycle Export, Import, MDL
    2. 2. OWB Lifecycle New Feature or Functionality Planned Built in Development Area Tested in QA And/or staging environment Deployed To production
    3. 3. Change Management <ul><li>Our definition </li></ul><ul><ul><li>The methods, procedures, and technology used to incrementally introduce changes into our Data Warehouse that lowers risk and increases system stability </li></ul></ul><ul><li>Know changes introduced! </li></ul>
    4. 4. Topics <ul><li>Deployment Scenarios </li></ul><ul><ul><li>Scripts </li></ul></ul><ul><ul><li>Deployment Manager </li></ul></ul><ul><li>Multiple “environments” </li></ul><ul><ul><li>Development/QA/Production </li></ul></ul><ul><ul><li>MDL / Snapshot </li></ul></ul><ul><li>One of “many” </li></ul><ul><ul><li>Source Control </li></ul></ul><ul><ul><li>Coordinated Release </li></ul></ul><ul><li>Data Migration </li></ul><ul><li>Impact Analysis </li></ul>
    5. 5. Deployment Scenarios <ul><li>Generated Code </li></ul><ul><ul><li>Create/Drop/Replace/Upgrade </li></ul></ul><ul><li>“ Deploy to File” </li></ul><ul><li>Deployment Manager </li></ul>
    6. 6. Development/QA/Product <ul><li>Development </li></ul><ul><ul><li>Multiple “dev” instances </li></ul></ul><ul><ul><li>Zero impact to production users </li></ul></ul><ul><ul><li>Small Volumes </li></ul></ul><ul><li>QA </li></ul><ul><ul><li>One or two instances </li></ul></ul><ul><ul><li>Used by QA team to test changes (users allowed to “acceptance” test) </li></ul></ul><ul><ul><li>Medium or Full Volumes </li></ul></ul><ul><li>Production </li></ul><ul><ul><li>One or two instances (not RAC term, our term) </li></ul></ul><ul><ul><li>Used by users to access data, changes impact users and systems </li></ul></ul><ul><ul><li>Full data volume with significant “window” </li></ul></ul>
    7. 7. Option 1: Separate Design Reps
    8. 8. Option 1: Propagation
    9. 9. Option 2 : One Design Rep
    10. 10. Option 2 : One Design Rep <ul><li>Advantages </li></ul><ul><ul><li>OWB provided comparisons </li></ul></ul><ul><ul><li>Saves space </li></ul></ul><ul><ul><li>OWB preferred </li></ul></ul><ul><li>Disadvantages </li></ul><ul><ul><li>Not truly “separated” </li></ul></ul><ul><ul><li>Design Browser for versions </li></ul></ul><ul><ul><li>Source Control integration </li></ul></ul>
    11. 11. Impact Analysis <ul><li>VERY USEFUL </li></ul><ul><li>Establish “depth” of impact </li></ul>
    12. 12. Source Code Control <ul><li>OWB is not the only part of the “stack” </li></ul><ul><li>Are there BO or MS reporting configs? </li></ul><ul><li>shell/ftp scripts for remote retrieval </li></ul><ul><li>Solution </li></ul><ul><ul><li>Export objects INDIVIDUALLY and use CVS </li></ul></ul><ul><ul><li>Separate Design Reps </li></ul></ul><ul><ul><li>TAG/BRANCH as part of “whole release” </li></ul></ul><ul><ul><li>Use OMB, etc for build </li></ul></ul>
    13. 13. Coordinated Release <ul><li>Source systems change </li></ul><ul><ul><li>GASP! </li></ul></ul><ul><li>Source X changes Table Y in dev </li></ul><ul><ul><li>OWB changes Table Y in Source X in dev </li></ul></ul><ul><li>Source X changes Table Y in QA </li></ul><ul><ul><li>OWB changes Table Y in Source X in QA </li></ul></ul><ul><li>Source X changes Table Y in prod </li></ul><ul><ul><li>OWB changes Table Y in Source X in prod </li></ul></ul>
    14. 14. Data Migration <ul><li>Situation </li></ul><ul><ul><li>3 measures and a new Dimension added to Data Mart </li></ul></ul><ul><ul><li>Processing 1 day = 1 hour, horizon = 2 years </li></ul></ul><ul><li>Migration Mappings </li></ul><ul><ul><li>Consider a custom “upgrade process” </li></ul></ul><ul><ul><li>update cube set profit = revenue/cost </li></ul></ul><ul><ul><li>Only used for “releasing” </li></ul></ul>
    15. 15. Upgrading OWB/Oracle versions <ul><li>Depends on OWB/Oracle prescribed upgrade procedures </li></ul><ul><li>Consider fresh installations </li></ul><ul><ul><li>Install new Oracle/OWB </li></ul></ul><ul><ul><li>Upgrade MDL using utility </li></ul></ul><ul><ul><li>Import MDL </li></ul></ul><ul><ul><li>Deploy fresh “warehouse” </li></ul></ul><ul><ul><li>Process/Copy historical data </li></ul></ul>
    16. 16. Questions <ul><li>QA hardware purchasing: If one day = 30 minutes to process. </li></ul><ul><li>T/F : Single Rep can be used with CVS </li></ul><ul><li>Manually exporting seems tough; how does one automate the build process? </li></ul>
    17. 17. STUDENT lifecycle <ul><li>select </li></ul><ul><li>change_info, env_info, good_info </li></ul><ul><li>from </li></ul><ul><li>student </li></ul><ul><li>where </li></ul><ul><li>present = true and awake = true; </li></ul>

    ×