1. 3 Copyright © 2009, Oracle. All rights reserved. Understanding the Warehouse Builder Architecture

2. Copyright © 2009, Oracle. All rights reserved. 3 - 2 Objectives After completing this lesson, you should be able to do the following: Define the OWB architecture components Explain how locations, control centers, and default configuration relate to each other Create target schemas or users and modules –Use the Security Node in the Globals Navigator panel –Examine roles and privileges –Register an Oracle Workflow user

3. Copyright © 2009, Oracle. All rights reserved. 3 - 3 Lesson Agenda Overview of the OWB Architecture Locations and Connectors: Concepts and Usage –Control centers and locations –Configurations and control centers Target schemas –Register OWB Users

4. Copyright © 2009, Oracle. All rights reserved. 3 - 4 Warehouse Builder Development Cycle Design Client  Metadata locations  Modules Design Data Flows Design TimeRuntime Reverse Engineering Test Data Flows Promote in Production Design Client  Dimensional modeling  Mappings  Process Flows  Create locations  Create Modules  Import metadata  Sample Flat files  Create relational and dimensional objects  Create Mappings  Create Process Flows Control Center Manager  Database Objects  Mappings  Process Flows Control Center Manager  Configurations  Configuration Templates  Deploy all objects  Deploy mappings and process flows  Execute mappings and process flows  Re-deploy all objects, and re-run Mappings, process flows Tool Actions

5. Copyright © 2009, Oracle. All rights reserved. 3 - 5 OWBSYS (Repository) Configuration Template Architecture for Design, Deployment, Execution Design ServerRun-time Server Design Center Control Center Manager Configuration 1 Data to be loaded Configuration 2 1. Design source and target metadata, ETL mappings, process flows. Design metadata (tables, dimensions, cubes, ETL mappings) Design Workspace 2. Deploy PL/SQL packages to target schema. 3. Execute process flows or individual mappings to load tables in target schemas. Configuration points to a control center Control Center Service “ execution agent ” outside of DB Audit Tables OWBSYS (Repository) Audit Tables Control center Target schema Deployed tables, dimensions, PL/SQL packages Workspace Deploy Execute

6. Copyright © 2009, Oracle. All rights reserved. 3 - 6 Architecture for Design, Deployment, Execution OWBSYS (Repository) Configuration Template Design ServerRun-time Server Design Center Control Center Manager Configuration 1 Data to be loaded Configuration 2 1. Design source and target metadata, ETL mappings, process flows. Design metadata (tables, dimensions, cubes, ETL mappings) Design Workspace 2. Deploy PL/SQL packages to target schema. 3. Execute process flows or individual mappings to load tables in target schemas. Configuration points to a control center Control Center Service “ execution agent ” outside of DB Audit Tables OWBSYS (Repository) Audit Tables Control center Target schema Deployed tables, dimensions, PL/SQL packages Workspace Deploy Execute 1 2 2 1

7. Copyright © 2009, Oracle. All rights reserved. 3 - 7

8. Copyright © 2009, Oracle. All rights reserved. 3 - 8 Architecture for Design, Deployment, Execution OWBSYS (Repository) Configuration Template Design ServerRun-time Server Design Center Control Center Manager Configuration 1 Data to be loaded Configuration 2 1. Design source and target metadata, ETL mappings, process flows. Design metadata (tables, dimensions, cubes, ETL mappings) Design Workspace 2. Deploy PL/SQL packages to target schema. 3. Execute process flows or individual mappings to load tables in target schemas. Configuration points to a control center Control Center Service “ execution agent ” outside of DB Audit Tables OWBSYS (Repository) Audit Tables Control center Target schema Deployed tables, dimensions, PL/SQL packages Workspace Deploy Execute 3 4 5

9. Copyright © 2009, Oracle. All rights reserved. 3 - 9

10. Copyright © 2009, Oracle. All rights reserved. 3 - 10 OWBSYS (Repository) Configuration Template Design ServerRun-time Server Design Center Control Center Manager Configuration 1 Data to be loaded Configuration 2 1. Design source and target metadata, ETL mappings, process flows. Design metadata (tables, dimensions, cubes, ETL mappings) Design Workspace 2. Deploy PL/SQL packages to target schema. 3. Execute process flows or individual mappings to load tables in target schemas. Configuration points to a control center Control Center Service “ execution agent ” outside of DB Audit Tables OWBSYS (Repository) Audit Tables Control center Target schema Deployed tables, dimensions, PL/SQL packages Workspace Deploy Execute Architecture for Design, Deployment, Execution 6 Design Reports Audit Reports Repository Browser

11. Copyright © 2009, Oracle. All rights reserved. 3 - 11 OWB Topology with CCA on Oracle Target Server Oracle DB Repository OWB Code Data Schema Source Tables OWB Browser Local OC4J Workspace1 Audit Tables Design Deploy Execute Design Reports Audit Reports Client DB2 SQL Server Execute DS1 DS2 DS3 ExU1ExU2 Control Center Agent Local OC4J Stage Loads data from staging to target Remote SQL ExU3 TGT1 TGT2 C$EXU1 C$EXU2 Integrate CT Load CT C$ = prefix for load table for staging DS = data source credentials (location details) ExU = execution unit Design Client OWB Control Center Service Map1 Browser Server Source Tables

12. Copyright © 2009, Oracle. All rights reserved. 3 - 12 One “active” configuration Modules point to metadata and data locations. Configuration points to one control center. A control center manages a set of source and target locations. A location can be a target for only one control center, but a source for many control centers. 12 3  Design Center is for designing the logical model of your data warehouse.  Configurations, control centers, and locations are definitions for implementing the objects physically in the run-time environment. Configurations, Control Centers, Locations

13. Copyright © 2009, Oracle. All rights reserved. 3 - 13

14. Copyright © 2009, Oracle. All rights reserved. 3 - 14 Lesson Agenda Overview of the OWB Architecture Locations and Connectors: Concepts and Usage –Control centers and locations –Configurations and control centers Target schemas –Register OWB Users

15. Copyright © 2009, Oracle. All rights reserved. 3 - 15 Locations Different types of locations Databases Files Applications Process flow and schedules Business Intelligence Locations contain credentials and connect information for a single physical place.

16. Copyright © 2009, Oracle. All rights reserved. 3 - 16 Creating Locations Locations are created: –For the OWBSYS repository by default –When you define source or target modules from within Design Center –When you register a user (optional) Default name for the OWBSYS repository location is OWB_REPOSITORY_LOCATION.

17. Copyright © 2009, Oracle. All rights reserved. 3 - 17 Metadata and Data Locations Each object has both a data location and a metadata location.

18. Copyright © 2009, Oracle. All rights reserved. 3 - 18 Registering Locations After you have deployed the objects for a location or explicitly registered the location, you cannot edit or delete it. You can only update its password. You must unregister the location if you want to edit or delete it.

19. Copyright © 2009, Oracle. All rights reserved. 3 - 19 Unregistering Locations

20. Copyright © 2009, Oracle. All rights reserved. 3 - 20 Alternatives for Unregistering Locations Use the OMBUNREGISTER LOCATION command to unregister locations. Or Run the [ORACLE_HOME]/owb/misc/unregister_location. sql script. –Use this script when the control center becomes inaccessible for some reason.

21. Copyright © 2009, Oracle. All rights reserved. 3 - 21 Connectors Logical links between source and target location Physically implemented as: –Database links –Directories A location may have multiple connectors. Location Connector 1 n

22. Copyright © 2009, Oracle. All rights reserved. 3 - 22

23. Copyright © 2009, Oracle. All rights reserved. 3 - 23 Quiz Connectors link the source and the target locations and are implemented as database links or directories. a.True b.False

24. Copyright © 2009, Oracle. All rights reserved. 3 - 24 Control Centers You cannot edit the DEFAULT_CONTROL_CENTER control center. You can create additional control centers to deploy to different systems. Only one control center can be used from Design Center at any one time. A Control Center Service is a Java program running outside of the database as an “execution agent.”

25. Copyright © 2009, Oracle. All rights reserved. 3 - 25

26. Copyright © 2009, Oracle. All rights reserved. 3 - 26 Control Center and Locations A control center manages many locations. A target location can be managed only by a single control center. Source locations, by contrast, can be used by multiple control centers. Control centerLocations 1 n Grey means that the location is registered.

27. Copyright © 2009, Oracle. All rights reserved. 3 - 27 Configurations and Control Centers Each configuration maps to a control center. Each control center maps to a workspace. To work in a particular control center, ensure that the configuration associated with that control center is set to Active. DEFAULT_CONFIGURATIONDEFAULT_CONTROL_CENTER PROD_CONFIGURATIONPROD_CONTROL_CENTER DEV_WORKSPACE PROD_WORKSPACE Active configuration Default configuration

28. Copyright © 2009, Oracle. All rights reserved. 3 - 28 Lesson Agenda Overview of the OWB Architecture Locations and Connectors: Concepts and Usage –Control Centers and Locations Target schemas –Register OWB Users

29. Copyright © 2009, Oracle. All rights reserved. 3 - 29 Creating Target Schemas The target schema is the target to which you load your data and data objects such as cubes, dimensions, tables, and mappings. Target schema Data to be loaded Deployed tables, dimensions, PL/SQL packages In OWB 11g, any OWB user that you define can serve as either a source or target user.

30. Copyright © 2009, Oracle. All rights reserved. 3 - 30 Creating Target Schemas Implement the logical design as physical database objects by deploying the objects to a target schema. Load target tables by executing deployed mappings. You may have multiple target schemas associated with one Warehouse Builder workspace. Target schema SALES Logical design in Design Center Deploy Test physical implementation Target schema SALES Deploy Production physical implementation

31. Copyright © 2009, Oracle. All rights reserved. 3 - 31 Registering DB User as an OWB User Only a workspace owner or a user with Warehouse Builder administrative privileges can register users. To register a user, use either of the following: –Security > Users node in Design Center – OMBINSTALL OWB_TARGET_USER OMB Plus command You cannot register a user with multiple workspaces –If you want to deploy to a schema from a different workspace, you would first have to unregister the location from the original workspace.

32. Copyright © 2009, Oracle. All rights reserved. 3 - 32 Using the Security Node to Register an OWB User 1 2 3 No automatic creation of the target location 4

33. Copyright © 2009, Oracle. All rights reserved. 3 - 33 Roles and Privileges of Warehouse Builder Users Two default roles: EVERYONE, ADMINISTRATOR EVERYONEADMINISTRATOR Workspace Owner Yes Workspace User YesNo Registered Users YesNo

34. Copyright © 2009, Oracle. All rights reserved. 3 - 34 Registering an Oracle Workflow User To deploy and execute process flows in a control center, you need to register the Oracle Workflow user. The Workflow location points to your workflow user schema.

35. Copyright © 2009, Oracle. All rights reserved. 3 - 35 Channels, Promotions, Products, Addresses, Categories, Cities, Countries, Customers, Regions, Promo- subcategories, Promo- categories, Orders, Order_items ORDERS_SRC (imported by you) Mapping Course: Predefined and New Objects Flat file source module: FILE_SOURCE CUSTOMERS.TXT FILE_GEOGRAPHY_MULTI.CSV DB module: DQ Target module: STAGING_AREA Target user: STAGING_USER External table: CUST_EXT MAP_STG_GEOGRAPHY Target module: SALES Dimensions: CHANNELS, PRODUCTS, TIMES, CUSTOMERS, PROMOTIONS Cube: SALES Tables: CHANNELS_TAB, PRODUCTS_TAB, TIMES_TAB, CUSTOMERS_TAB, PROMOTIONS_TAB, ORDERS_TGT, T_IND_PART, T_PART Mappings: Loading Dimensions and Cube Mappings, DEBUG_TEST_MAPPING, LOAD_ORDERS, PIVOT_SALES, UNPIVOT_SALES DB source module: XSALES Tables: SOURCE, CLEANSED, CROSSREF, TARGET Mappings: MAP_NA, MAP_NA_MM = Items with the check mark are predefined. Staging tables: STG_COUNTRIES STG_REGIONS Mapping MAP_STG_CUSTOMERS Target user: SALES_WH (You create/register this) You also create a mapping: LOAD_CONTACT that uses XSALES source tables

36. Copyright © 2009, Oracle. All rights reserved. 3 - 36 Import the CLASS_PROJECT1.mdl File Select File > Import > Warehouse Builder Metadata Browse to select the class_project1.mdl file from the /home/oracle/labs/etl1/mdl/ folder.

37. Copyright © 2009, Oracle. All rights reserved. 3 - 37 Quiz In OWB 11.2, any OWB user that you define can serve as either a source or target user. a.True b.False

38. Copyright © 2009, Oracle. All rights reserved. 3 - 38 Summary In this lesson, you should have learned how to: Describe the various architectural components of Warehouse Builder Explain how locations, control centers, and configurations relate to each other Describe the process of registering OWB users Describe the process of registering the Oracle Workflow user

39. Copyright © 2009, Oracle. All rights reserved. 3 - 39 Practice 3-1 Overview: Setting Up a Pre-Populated Project This practice covers the following topics: Importing a CLASS_PROJECT1.mdl file Registering target users ( SALES_WH, STAGING_USER ) Registering the Oracle Workflow user

40. Copyright © 2009, Oracle. All rights reserved. 3 - 40