Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to Handle DEV&TEST&PROD for Oracle Data Integrator

11,042 views

Published on

Most of us have development teams apart from test and operation teams using the different repository environments. And there are generally 3 different ODI installations and repositories which each of the teams use separately. Chaos is usually expected and happened who will test which development and what to deploy into production.
In this session hear how ODI can handle your development hierarchy with ease of usage and in simplified/synchronized way for successful deployments.
A simple project will be built up and will be enlarged to enterprise level step by step.

Published in: Technology, Business
  • In 27th slide, there we can see different Master Repositories, All the phases will be having same Master repository right.?? please correct me if i am wrong as you mentioned in slide 15.... . :(
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • With ODI11g don't have this problems (import load plans) with smart export/import...but ODI12c yes...
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Thanks Gurcan. We study new solutions to enviroments, thanks! How methodology to import load plans? Now we have problems with import different load plans, we appear meaningless errors
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi Jorge,
    There can be various types of architecture depending on your team's and/or company's strategy. And my answers would mostly be 'it depends'.
    Here are some questions & suggestions that you can choose or think of one, depending your environment or team's or company's decision or strategy, but there are many 'Best Practice' approaches.
    - What if there needs to be a tiny or small bug/hot-fix in your test? You need to start over in DEV and import/export to TEST again. Typically, I would recommend DEV and TEST as 'Development Work Repository' and PROD as 'Execution Work Repository' for DEV&TEST&PROD environments.
    - Unshared Master Repository is a tricky decision, but could be useful, you need to manually insert topology, users/roles and other related information for both TEST and PROD in your architecture. As far as I understand in your architecture, I would share Master Repository to TEST and PROD since both are 'Execution Work Repository', in order to decrease manual insertions related to 'Master Repository'.

    There are several limitations when you are setting up an SDLC architecture. These limitations could be addressed as hardware, strategy, decision, regulations, needs, amount of people involving in project (developers, testers, operators, dbas, admins, business users, etc.), location of teams, and many more.

    Cheers,
    Gurcan.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi, good info. But we have a DEV-TEST-PROD enviroment. Each enviroment have master-work repository. We import to TEST-PROD only load plans and scenarios. It's correct procedure this export-import?

    Before project, we have problems export - import with all odi objects. Now try the procedure export-import only scen and load plan and run ok
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

How to Handle DEV&TEST&PROD for Oracle Data Integrator

  1. 1. HOW TO HANDLE DEV & TEST & PROD IN THE CLOUD FOR ORACLE DATA INTEGRATOR Gürcan Orhan Enterprise Data Warehouse Architect Ekol Logistics - Turkey 18 May 2017 http://gurcanorhan.wordpress.com gurcan_orhan http://tr.linkedin.com/in/gurcanorhan
  2. 2. #Harmony17 18 MAY 2017 WHO AM I?+20 years of IT experience. +14 years of DWH experience. +10 years of Oracle Data Integrator experience. +8 years of Oracle Warehouse Builder experience. Sybase Power Designer, ERwin Data Modeler, SDDM OBIEE, Cognos, Microstrategy, Business Objects, Qlikview, Tableau IBM Data Stage, SAP Data Services, Informatica, etc… Oracle Excellence Awards - Technologist of the Year 2011 : Enterprise Architect DWH & BI Chair : TROUG (Turkish Oracle User Group) Published Customer Snapshot for NODI @Oracle.com Published videos about ODI @Oracle.com Published OTN Podcasts about “Data Warehousing and ODI” “ODI and the Evolution of Data Integration” Lots of “2MTT”s Articles in OTech Magazine, SearchSoftwareQuality.com Annual panelist for ODTUG “Ask the Experts Panel : ODI” Presenter in OOW since 2010 (7 times in a row ⭐ ) Presenter in many OUG conferences in globe Presenter in various universities in Turkey
  3. 3. Ekol Germany Warehousing Solutions begin with the Kardelen Facility 1996 2003 2010 2012 2014 2016 201520132011200820021990 Acquire STS Int. Transport Ekol Bosnia Ekol France Ekol Greece Ekol Ukraine Ekol Spain Ekol Bulgaria Ekol Czech Rep. Ekol Iran Ekol PolandEkol Italy Ekol Romania Ekol HungaryAcquire Unok/Unatsa n Rainbow Replaced by Quadro (software) Intermodal operations Ro-Ro operations Established Ekol Milestones
  4. 4. Headquarters Ekol Locations Current countries 15 80 locations 201723 countries 92 locations 201831 countries 104 locations 201942 countries 122 locations USA CN
  5. 5. #Harmony17 18 MAY 2017 Overview
  6. 6. #Harmony17 18 MAY 2017 MY DEFINITION OF ODI ODI (Oracle Data Integrator) is a tool, that can talk, or learn how to talk, with any database system, or any operating system, in its own language. This is the power of ODI.
  7. 7. #Harmony17 18 MAY 2017 AGENDA
  8. 8. #Harmony17 18 MAY 2017 ODI REPOSITORY ARCHITECTURE MASTER REPOSITORY  Information related to DB/OS connections Contexts, Repositories, Logical Architecture  Information related to ODI internal security  Versions
  9. 9. #Harmony17 18 MAY 2017 ODI REPOSITORY ARCHITECTURE WORK REPOSITORY (DEVELOPMENT)  Source / Staging / Target metadata Models in Designer Navigator  Projects and beneath : Folders, Interfaces, Packages, Procedures, Variables, Sequences, Knowledge Modules, User Functions  Scenarios, Load Plans, Schedules  All the logs related to execution
  10. 10. #Harmony17 18 MAY 2017 ODI REPOSITORY ARCHITECTURE WORK REPOSITORY (EXECUTION)  Scenarios  Load Plans  Schedules  Execution Logs
  11. 11. #Harmony17 18 MAY 2017 CONTEXTS KEY TO JOIN PHYSICAL ARCHITECTURE AND LOGICAL ARCHIT SRC A (dev) SRC A (prod) SRC B (dev) SRC B (prod) SRC C (prod) Source-C Source-B Source-A
  12. 12. #Harmony17 18 MAY 2017 AGENDA
  13. 13. #Harmony17 18 MAY 2017 START-UP PROJECT : INITIAL ARCHITECTURE DEV & TEST PROD MASTER Topology Versionin g Security DEV WORK Models Projects Executio n EXEC WORK Executio n SRC A (dev) SRC B (dev) SRC A (test) SRC B (test) SRC A (prod) SRC B (prod) SRC C (prod) https://cloud.oracle.com/ en_US/data-integrator
  14. 14. #Harmony17 18 MAY 2017 START-UP PROJECT : MANUAL EXPORT-IMPORT
  15. 15. #Harmony17 18 MAY 2017 AGENDA
  16. 16. #Harmony17 18 MAY 2017 WE’RE ON PRODUCTION We need to make some changes…
  17. 17. #Harmony17 18 MAY 2017 ADMINS AT WORK TEST & PROD* ContextDEV Context MASTER Topology Versionin g Security EXEC WORK Executio n DEV WORK Models Projects Executio n EXEC WORK Executio n DEV WORK Models Projects Executio n EXPORT IMPORT MASTER Topology Versionin g Security * New
  18. 18. #Harmony17 18 MAY 2017 ADMINS AT WORK DEV & TEST Context PROD* Context EXEC WORK Executio nEXPORT IMPORT DEV WORK Models Projects Executio n MASTER Topology Versionin g Security MASTER Topology Versionin g Security Insert manually Insert manually
  19. 19. #Harmony17 18 MAY 2017 AGENDA
  20. 20. #Harmony17 18 MAY 2017 MORE TESTERS IN TEAM DEV & TEST Context PROD* ContextDEV Context TEST Context EXEC WORK Executio nEXPORT IMPORT DEV WORK Models Projects Executio n DEV WORK Models Projects Executio n MASTER Topology Versionin g Security MASTER Topology Versionin g Security
  21. 21. #Harmony17 18 MAY 2017 EXPORT-IMPORT WITH A PACKAGE http://sonra.io/odi-automating-deployment-of-scenarios-in-oracle-data-integrator/
  22. 22. #Harmony17 18 MAY 2017 EXPORT-IMPORT WITH THE ODI SDK for (Object scen : scenarioCollection) { OdiScenario odiscen =(OdiScenario)scen ; export.exportToXml(odiscen, ExportPath, OverWrite, RecursiveExport, Encoding); }for (String filename : XMLFiles) { import.importObjectFromXml( import.IMPORT_MODE_SYNONYM_INSERT_UPDATE, filename, true); } For(Object interface : interfaces) { OdiInterface odiInt = (OdiInterface) interface; String scenName = odiInt.getName(); OdiScenario newScen = gene.generateScenario(odiInt, scenName, newVersion); }
  23. 23. #Harmony17 18 MAY 2017 AGENDA
  24. 24. #Harmony17 18 MAY 2017 ENTERPRISE ARCHITECTURE DEV Context TEST Context PRE-PROD* Context PROD* Context DEV WORK Models Projects Executio n EXEC WORK Executio n DEV WORK Models Projects Executio n EXEC WORK Executio n MASTER Topology Versionin g Security MASTER Topology Versionin g Security MASTER Topology Versionin g Security * New
  25. 25. #Harmony17 18 MAY 2017 ENTERPRISE ARCHITECTURE DEV PROD* DEV WORK Models Projects Executio n EXEC WORK Executio n DEV WORK Models Projects Executio n TEST PRE-PROD* EXEC WORK Executio n HOTFIX* DEV WORK Models Projects Executio n SMOKE EXEC WORK Executio n MASTER Topology Versionin g Security MASTER Topology Versionin g Security MASTER Topology Versionin g Security
  26. 26. #Harmony17 18 MAY 2017 http://gurcanorhan.wordpress.com gurcan_orhan http://tr.linkedin.com/in/gurcanorhan

×