How to Handle DEV&TEST&PROD for Oracle Data Integrator
•
15 gostaram•13,338 visualizações
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.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a How to Handle DEV&TEST&PROD for Oracle Data Integrator
Semelhante a How to Handle DEV&TEST&PROD for Oracle Data Integrator (20)
Último
Último (20)
How to Handle DEV&TEST&PROD for Oracle Data Integrator
- 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. #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. 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
- 5. #Harmony17 18 MAY 2017 Overview
- 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. #Harmony17 18 MAY 2017 AGENDA
- 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. #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. #Harmony17 18 MAY 2017 ODI REPOSITORY ARCHITECTURE WORK REPOSITORY (EXECUTION) Scenarios Load Plans Schedules Execution Logs
- 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. #Harmony17 18 MAY 2017 AGENDA
- 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. #Harmony17 18 MAY 2017 START-UP PROJECT : MANUAL EXPORT-IMPORT
- 15. #Harmony17 18 MAY 2017 AGENDA
- 16. #Harmony17 18 MAY 2017 WE’RE ON PRODUCTION We need to make some changes…
- 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. #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. #Harmony17 18 MAY 2017 AGENDA
- 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. #Harmony17 18 MAY 2017 EXPORT-IMPORT WITH A PACKAGE http://sonra.io/odi-automating-deployment-of-scenarios-in-oracle-data-integrator/
- 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. #Harmony17 18 MAY 2017 AGENDA
- 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. #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. #Harmony17 18 MAY 2017 http://gurcanorhan.wordpress.com gurcan_orhan http://tr.linkedin.com/in/gurcanorhan
Notas do Editor
- JDBC URLs, user names and passwords used to connect to the different systems, LDAP connectivity information, and schemas where data can be found. In fact, all the information that is managed with the Topology navigator. Security, authentication management : ODI users names and passwords, ODI users privileges and profiles, profiles definition. When a new version of an object is created in the ODI studio.
- There are also Work Repositories that are labeled “Execution” Work Repositories. These can be used in production environments to make sure that source code will not be modified hastily in a live environment.
- Contexts are the keys which merges Logical Architecture with Physical Architecture depending on the defined contexts. Each Logical entity has physical connections related to each context.
- Simple architecture when starting up a project. Limited developers (1-5) with limited testers (1-3) with an admin or none. Up to 50 business users with limited power users (for UAT). Initial state
- Developers count increased to 10 Testers wants to make tests on production environment with live data. Simple UAT with power users on the production environment. *** PROD Context has encrypted password, which only supervisor can change.
- Admins don’t want developers and testers to have access to production systems. UAT activity is still made on production environment by business power users. PROD Context has encrypted password, which only supervisor can change.
- More admins, more testers and more developers hired. Changes need to be in a simple architecture from DEV to TEST and TEST to PROD. UAT is still in production with more business power users.
- More admins, more testers and more developers hired. Changes need to be in a simple architecture from DEV to TEST and TEST to PROD. UAT is still in production with more business power users. Uli Bethke
- More admins, more testers and more developers hired. Changes need to be in a simple architecture from DEV to TEST and TEST to PROD. UAT is still in production with more business power users.
- External source control for the hotfix environment.