Presentation is loading. Please wait.

Presentation is loading. Please wait.

3 Copyright © 2009, Oracle. All rights reserved. Accessing Non-Oracle Sources.

Similar presentations


Presentation on theme: "3 Copyright © 2009, Oracle. All rights reserved. Accessing Non-Oracle Sources."— Presentation transcript:

1 3 Copyright © 2009, Oracle. All rights reserved. Accessing Non-Oracle Sources

2 Copyright © 2009, Oracle. All rights reserved. 3 - 2 Objectives After completing this lesson, you should be able to: Explain the concepts behind code templates (CTs) Identify the location of code templates that ship with the product Import code templates Describe how to create new code templates Describe how to define new integration platforms

3 Copyright © 2009, Oracle. All rights reserved. 3 - 3 Lesson Agenda Concepts behind code templates Location of seeded code templates that ship with the product Importing code templates Creating new code templates Creating new integration platforms

4 Copyright © 2009, Oracle. All rights reserved. 3 - 4 Extensible Framework of OWB 11g Release 2 11g R1 11g R2 Mapping design Connectivity: Oracle, Gateway, ODBC, JDBC, Native Extensible platforms Code templates: extensible, pluggable Non-modifiable: PL/SQL SQL ABAP SQL*Loader Non-modifiable: PL/SQL SQL ABAP SQL*Loader plus … Extensible: Code template support Native connectivity takes advantage of the host system services, such as loaders. New operators, plus enhancements to the existing ones Platforms: Oracle or file Code templates: internal, not addressable Mapping design Connectivity: Oracle, Gateway, or ODBC Oracle and file platforms, plus user-defined platforms

5 Copyright © 2009, Oracle. All rights reserved. 3 - 5 What Is a Code Template? Code Templates (CTs) in Oracle Warehouse Builder are components that implement reusable transformation and ETL (extract, transform, and load) strategies across different technologies. Warehouse Builder ships with various predefined CTs. –You can directly use these in your mappings, or –Adapt them to your specific requirements Warehouse Builder implements six types of CTs: –Integration code template (ICT) –Load code template (LCT) –Control code template (CCT) –Change data capture code template (CDCCT) –Oracle target code template (OTCT) –Function code template (FCT) The Integration, Load, Control, and CDC code templates are based on the ODI 10g API Reference.

6 Copyright © 2009, Oracle. All rights reserved. 3 - 6 Custom metadata import CDC CT Load CT Control CT Integration CT Pluggable Code Template Framework CDC Load Integrate/ Oracle Tgt Control Sample seeded code templates Oracle LogMiner SQL Server Triggers Oracle SQL*Loader DB2 UDB Triggers Oracle Target SQL to SQL Oracle DBLink Oracle Control An Open Extensibility Framework

7 Copyright © 2009, Oracle. All rights reserved. 3 - 7 Benefits of Extensible Code Templates Architectural flexibility Alternative data movement strategies Greater integration via Open Connectivity framework Implementations for standard design patterns Integrate new database features outside product release cycles Construct and share modular templates Code templates: extensible, pluggable Non-modifiable: PL/SQL SQL ABAP SQL*Loader Non-modifiable: PL/SQL SQL ABAP SQL*Loader plus … Extensible: Code template support (LCT, ICT, JCT, CCT, OTCT) Code templates: internal, not addressable

8 Copyright © 2009, Oracle. All rights reserved. 3 - 8 What Is a Code Template Mapping? CT-based mapping = Mapping design plus code templates + platform definition Traditional mappings:  Mapping design New CT-based mappings:  Mapping design plus  Code templates  Platform definition

9 Copyright © 2009, Oracle. All rights reserved. 3 - 9 Typical Usage of Code Templates Operational data layer SQL Server Informix Other sources Sybase Data sources Message queue Staging data layer Performance data layer Code templates in OWB Oracle Warehouse Builder

10 Copyright © 2009, Oracle. All rights reserved. 3 - 10 Lesson Agenda Concepts behind code templates Location of seeded code templates that ship with the product Importing code templates Creating new code templates Creating new integration platforms

11 Copyright © 2009, Oracle. All rights reserved. 3 - 11 Location of Seeded Code Templates Types of seeded code templates: Load code templates (LCT) Integration code templates (ICT) Control code templates CCT) Oracle target code templates (TCT, leveraging OWB’s existing engine) Change data capture code templates (CDC)

12 Copyright © 2009, Oracle. All rights reserved. 3 - 12 Quiz Which of the following are benefits of using code templates? a.Architectural flexibility b.Built-in graphical debugger c.Integrate new database features outside product release cycles d.Implementations for standard design patterns e.Support for rapid application development f.Construct and share modular templates

13 Copyright © 2009, Oracle. All rights reserved. 3 - 13 Lesson Agenda Concepts behind code templates Location of seeded code templates that ship with the product Importing code templates Creating new code templates Creating new integration platforms

14 Copyright © 2009, Oracle. All rights reserved. 3 - 14 Imported CT Opened in OWB CT Editor CT Editor Task list Task Editor Code templates can be imported from Oracle Data Integrator (ODI) files included in the OWB product. The import process is wizard-driven. In ODI, code templates are called “knowledge modules.”

15 Copyright © 2009, Oracle. All rights reserved. 3 - 15 Practice 3-1 Overview: Examine Built-In and Imported Code Templates This practice covers: Examining the code templates built into Warehouse Builder. Importing some predefined code templates shipped with Warehouse Builder, but not built-in.

16 Copyright © 2009, Oracle. All rights reserved. 3 - 16 Lesson Agenda Concepts behind code templates Location of seeded code templates that ship with the product Importing code templates Creating new code templates Creating new integration platforms

17 Copyright © 2009, Oracle. All rights reserved. 3 - 17 Creating New Code Templates You specify the tasks between the Start and End tasks. Example: Bulk extract from SQL Server CT

18 Copyright © 2009, Oracle. All rights reserved. 3 - 18 Lesson Agenda Concepts behind code templates Location of seeded code templates that ship with the product Importing code templates Creating new code templates Defining new integration platforms –Set up platform properties. –Define data type mapping between heterogeneous source and target. –Add connectivity. –Use code templates in mappings.

19 Copyright © 2009, Oracle. All rights reserved. 3 - 19 What Is an Integration Platform A platform is the minimum set of metadata (data types, locations, and so on) necessary to connect to a source or target system other than Oracle. The platform represents that system. Seeded platforms

20 Copyright © 2009, Oracle. All rights reserved. 3 - 20 Define New Integration Platforms in OWB Warehouse Builder Data type mapping design Code templates in mapping Platform properties Connectivity (JDBC, ODBC, and Native) Metadata infrastructure 1.2.3.4. CT-based mapping = Mapping design + code templates + platform definition

21 Copyright © 2009, Oracle. All rights reserved. 3 - 21 Setting Up Platform Properties Change the user interface. Add module types.

22 Copyright © 2009, Oracle. All rights reserved. 3 - 22 Creating Data Type Mappings Define data types. Map the data types to or from the core. Core types DB2 types SQL Server types Oracle types XML types Teradata types

23 Copyright © 2009, Oracle. All rights reserved. 3 - 23 Adding Connectivity

24 Copyright © 2009, Oracle. All rights reserved. 3 - 24 Using Code Templates in Mappings The data type mapping that you define (from the platform to the generic data type set) will be used by the CT mapping. CT-based mappings are created under the Template Mappings node.

25 Copyright © 2009, Oracle. All rights reserved. 3 - 25 Hybrid Design: Combine Template Extract with PL/SQL Use Oracle Transforms for full Oracle PL/SQL functionality Use code template extract for heterogeneous connectivity OWB provides a hybrid design where execution units in a single mapping can be a mixture of those assigned a Load or Integration code template plus an Oracle Target code template to leverage OWB code generation capabilities. This execution unit uses Oracle Target code template This execution unit uses Load File to External Table code template

26 Copyright © 2009, Oracle. All rights reserved. 3 - 26 Quiz A platform is the minimum set of metadata (data types, locations, and so on) necessary to connect to a source or target system other than Oracle. a.True b.False

27 Copyright © 2009, Oracle. All rights reserved. 3 - 27 Summary In this lesson, you should have learned how to: Explain the concepts behind code templates (CTs) Identify the location of code templates that ship with the product Import code templates Describe how to create new code templates Describe how to define new integration platforms

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


Download ppt "3 Copyright © 2009, Oracle. All rights reserved. Accessing Non-Oracle Sources."

Similar presentations


Ads by Google