4 Copyright © 2009, Oracle. All rights reserved. Designing Mappings with the Oracle Data Integration Enterprise Edition License

Copyright © 2009, Oracle. All rights reserved Objectives After completing this lesson, you should be able to: Explain how to define new code templates for heterogeneous connectivity to non-Oracle sources Work with execution units –Use the execution view and logical view of the mapping Deploy CT mappings –Manage the privileges required of Java 2, Enterprise Edition users and agents for placing agents in sources

Copyright © 2009, Oracle. All rights reserved Lesson Agenda Comparing traditional OWB mappings with CT mappings Using code templates in mappings Combining traditional OWB mapping functionality with CT functionality Deploying CT mappings –Privileges for J2EE users and agents –Starting the default agent –Setting up credentials for the default agent –Mapping modules and agent locations

Copyright © 2009, Oracle. All rights reserved Traditional Versus CT Mappings When creating new mappings, you first need to consider whether you will be using code templates. This determines under which node to create the mapping. Code template mappings Traditional mappings

Copyright © 2009, Oracle. All rights reserved Integrate CTs into an OWB Mapping Framework OWB OWB UI OWB Repository Maps CTs Add OWB xforms Deploy map to J2EE Start map Apply CT to map Deploy map to J2EE Start map Import some CTs Code templates

Copyright © 2009, Oracle. All rights reserved Additional Tasks for Using CTs in Mappings 1. Create project. 2. Define a platform. 3. Import code templates (CTs) that you will be using. 4. Construct mapping. 4.a. Create execution units, assign code template to each execution unit. 5. Validate mapping. 6. Generate mapping. 7. Deploy mapping. 8. Execute mapping. Use code templates for direct, native access to non-Oracle systems. Minimum set of metadata necessary to connect to a source or target system

Copyright © 2009, Oracle. All rights reserved Lesson Agenda Comparing traditional OWB mappings with CT mappings Using code templates in mappings Combining traditional OWB mapping functionality with CT functionality Deploying CT mappings –Privileges for J2EE users and agents –Starting the default agent –Setting up credentials for the default agent –Mapping modules and agent locations

Copyright © 2009, Oracle. All rights reserved Execution Units in a CT Mapping Unit Oracle target execution unit SQL Server source execution unit DB2 source execution unit Code template Code Template

Copyright © 2009, Oracle. All rights reserved Execution View Versus Logical View Code template mapping Execution Unit Execution Unit Execution Unit Source execution unit Target execution unit Execution view (physical design) Alternate Code template Oracle target Code template SQL to Oracle Default configuration (active) - SQL to Oracle - Oracle target - Parallel Code template SQL to SQL Code template Data Pump Logical view Assign each execution unit a code template. The active configuration brings into play its execution view.

Copyright © 2009, Oracle. All rights reserved Default Configuration and Its Execution View Execution unitAssigned code template Stage CustomersLCT_SQL_TO_ORACLE Stage DetailsLCT_SQL_TO_SQL MergeDEFAULT_ORACLE_TARGET_CT Default configuration Execution unit LCT_SQL_TO_ORACLE LCT_SQL_TO_SQL DEFAULT_ORACLE_TARGET_CT

Copyright © 2009, Oracle. All rights reserved Alternate Configuration and Its Execution View Execution unitAssigned code template Stage CustomersLCT_ORACLE_TO_ORACLE_DBLINK Stage DetailsLCT_SQL_TO_SQL MergeDEFAULT_ORACLE_TARGET_CT Alternate configuration Execution unit LCT_ORACLE_TO_ORACLE_DBLINK LCT_SQL_TO_SQL DEFAULT_ORACLE_TARGET_CT

Copyright © 2009, Oracle. All rights reserved Customers GIS Details Cust Info Staging Target Load Integrate Mechanics of Template-Based Mappings LCT_SQL_TO_ORACLE LCT_SQL_TO_SQL DEFAULT_ORACLE_TARGET_CT

Copyright © 2009, Oracle. All rights reserved New Properties in the Location Dialog Box Support Code Template Mappings OWB 11g Release 2 offers many location properties, logically grouped among six tabs: Details Registration Advanced Prefix Mask Connection Pool

Copyright © 2009, Oracle. All rights reserved Customers GIS Details Cust Info Staging Target Location Information for CT-Based Mappings

Copyright © 2009, Oracle. All rights reserved Staging Table Prefixes

Copyright © 2009, Oracle. All rights reserved Create a List of Favorite Operators Operators used in execution units that have code templates assigned for loading or integration

Copyright © 2009, Oracle. All rights reserved Quiz Which of the following statements are true? a.Each configuration can have its own unique execution view. b.An execution unit can be assigned multiple, concurrent code templates. c.Each execution unit is assigned a single code template.

Copyright © 2009, Oracle. All rights reserved Lesson Agenda Comparing traditional OWB mappings with CT mappings Using code templates in mappings Combining traditional OWB mapping functionality with CT functionality Deploying CT mappings –Privileges for J2EE users and agents –Starting the default agent –Setting up credentials for the default agent –Mapping modules and agent locations

Copyright © 2009, Oracle. All rights reserved Convert a Classic Mapping to a CT Mapping That Utilizes Data Pump Classic set-based SQL mapping Logical view: Move Oracle table between two Oracle instances Generation results: INSERT statement

Copyright © 2009, Oracle. All rights reserved Copy and Paste a Classic Mapping to a Template Mapping Node From the classic mapping node… … to the template mapping node

Copyright © 2009, Oracle. All rights reserved Execution View of a Code Template Version of the Mapping We can replace this default Oracle target CT with one that uses Data Pump.

Copyright © 2009, Oracle. All rights reserved Assign the USE_DATA_PUMP Code Template Execution unit with Data Pump template assigned

Copyright © 2009, Oracle. All rights reserved Lesson Agenda Comparing traditional OWB mappings with CT mappings Using code templates in mappings Combining traditional OWB mapping functionality with CT functionality Deploying CT mappings –Privileges for J2EE users and agents –Starting the default agent –Setting up credentials for the default agent –Mapping modules and agent locations

Copyright © 2009, Oracle. All rights reserved Reminder of CT-Based Mapping Architecture Warehouse Builder Data type mapping design Code templates in mapping Platform properties Connectivity (JDBC, ODBC, and Native) Metadata infrastructure Code template–based mapping = Mapping design + code templates + platform definition

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

Copyright © 2009, Oracle. All rights reserved Privileges for J2EE Users and Agents CT-driven mappings in heterogeneous environments require agents to which to deploy.

Copyright © 2009, Oracle. All rights reserved

Copyright © 2009, Oracle. All rights reserved Starting the Default Agent In Windows, navigate to \owb\bin\win32 and execute: ccastart.bat In Linux, open a terminal session, navigate to /owb/bin/unix, and perform the following: We will use welcome as the OC4J Administrator’s password

Copyright © 2009, Oracle. All rights reserved Setting Up Credentials for Default Agent welcome

Copyright © 2009, Oracle. All rights reserved Mapping Modules and Agent Locations CT-based heterogeneous mappings must be created in the top-level Template Mappings node.

Copyright © 2009, Oracle. All rights reserved Agents Need Information About Locations

Copyright © 2009, Oracle. All rights reserved Installing the OWB Agent on Another System

Copyright © 2009, Oracle. All rights reserved System A - SQL Server Source OWB Infrastructure with Agent on Oracle Target SQL Server Database System B – Oracle Target Oracle Database OWB design client Execute Local SQL Move data over JDBC to staging table Execute Remote SQL Loads data from staging to target Load CTIntegration CT Audit Agent Deploy EAR file to agent. Contains all SQL

Copyright © 2009, Oracle. All rights reserved System A - SQL Server Source OWB Infrastructure with Agent on Remote Source Agent SQL Server Database System B – IBM DB2 Target Oracle Database OWB design client Deploy EAR file to agent Contains all SQL Execute SQL Move data over via SQL Loader Execute Remote SQL Loads data from staging to target Load CTIntegration CT Audit

Copyright © 2009, Oracle. All rights reserved Monitoring Deployments with HRAB Reports Heterogeneous Repository Audit Browser (HRAB) reports are useful for monitoring deployments to heterogeneous databases. –Scripts are provided for you to audit the deployment and execution of mappings to Oracle, DB2, and SQL Server environments. The HRAB reports are a subset of the Repository Browser reports, with fewer details.

Copyright © 2009, Oracle. All rights reserved Quiz CT-driven mappings in heterogeneous environments require which of the following for successful deployment? a.Pluggable mappings b.Database links c.Agents d.All of the above

Copyright © 2009, Oracle. All rights reserved Summary In this lesson, you should have learned how to: Explain how to define new code templates for heterogeneous connectivity to non-Oracle sources Work with execution units –Use the execution view and logical view of the mapping Deploy CT mappings –Manage the privileges required of Java 2, Enterprise Edition users and agents for placing agents in sources

Copyright © 2009, Oracle. All rights reserved Practice 4-1 Overview: Using Code Templates in Mappings This practice covers the examination and modification of a code template–based mapping. CT-based mapping Source module Source tables MDL-imported project Target module Target table Source flat file