1. 8-1 3 Oracle Data Integrator Topology: Connecting to the World

2. 8-2 Objectives Understand the basic concepts behind the Topology interface. Understand logical and physical architecture. Know how to plan a Topology. Have learnt current best practices for setting up a Topology. After completing this course, you will:

3. 8-3 What is the Topology? Topology – The representation of the information system in ODI: Technologies: Oracle, DB2, File, etc. Datatypes for the given technology Data Servers for each technologies Physical Schemas under each data server ODI Agents (run-time modules) Definition of Languages and Actions

4. 8-4 Properties of Physical Schemas An ODI physical schema always consists of 2 data server schemas: The Data Schema, which contains the datastores The Work Schema, which stores temporary objects A data server schema is technology-dependant. Catalog Name and/or Schema Name Example: Database and Owner, Schema A data server has: One or more physical schemas One default physical schema for server-level temporary objects

5. 8-5 Concepts in Reality TechnologyData serverSchema OracleInstanceSchema Microsoft SQL ServerServerDatabase/Owner Sybase ASEServerDatabase/Owner DB2/400ServerLibrary TeradataServerSchema Microsoft AccessDatabase(N/A) JMS TopicRouterTopic FileFile ServerDirectory

6. 8-6 Important Notes It is strongly recommended that for each data server you create a dedicated area for ODI‘s temporary objects and use it as the Work Schema. Under each data server, define a physical schema for each sub-division of the server that will be used.

7. 8-7 Oracle 10g Linux Oracle 9i Example Infrastructure Windows Linux ACCOUNTING SALES Windows Production site: Tokyo Production site: Boston MS SQL Server db_dwh db_purchase MS SQL Server A db_dwh MS SQL Server B db_purchase Oracle ACCT SAL

8. 8-8 The Physical Architecture in ODI Data server Physical schema Legend Oracle-Boston9 ACCOUNTING Oracle-Boston10 SALES MSSQL-Boston db_dwh db_purchase MSSQL-TokyoB purchase Oracle-Tokyo ACCT SAL MSSQL-TokyoA dwh

9. 8-9 Prerequisites to Connect to a Server Drivers (JDBC, JMS) Drivers must be installed in /oracledi/drivers This should be done on all machines connecting to the data server. Connection settings (server dependant) Machine name (IP Address), port User/Password Instance/Database Name, …

10. 8-10 Important Note The user name is used to access all underlying schemas, databases or libraries in the data server. Make sure this user account has sufficient privileges.

11. 8-11 1.Right-click the technology of your data server 2.Select Insert Data Server 3.Fill in the Name 4.Fill in the connection settings: Data Server User and Password (Optional) JNDI Connection Creating a Data Server

12. 8-12 Creating a Data Server - JDBC 1.Select the JDBC tab 2.Fill in the JDBC driver 3.Fill in the JDBC URL 4.Test the connection 5.Click OK Select driver Select URL

13. 8-13 The JDBC URL The JDBC driver uses a URL to connect to a database system. The URL describes how to connect to the database system. The URL may also contain driver-specific parameters Use the select button to choose the driver class name and URL template.

14. 8-14 1.Click the Test button 2.Select the Agent to test this Connection Local (No Agent) performs the test with the Topology Manager GUI. 3.Click Test The driver must be installed Testing a Data Server connection

15. 8-15 Note – test the connection Always test the connection to check that the data server is correctly configured.

16. 8-16 1.Right-click the data server and select Insert Physical Schema 2.Select or fill in: Data Schema Work Schema 3.Select whether this is the Default schema 4.Click OK A warning appears Creating a Physical Schema

17. 8-17 What is a Logical Schema? Developers should not have to worry about the actual location of the data servers, or the updates in user names, IP addresses, passwords, etc. To isolate them from the actual physical layer, the administration will create a Logical Schema that is simply an alias for the physical layer.

18. 8-18 Alias vs. Physical Connection MS SQL Server db_dwh Windows Development site: New York, NY Datawarehouse (Logical Schema) Logical Architecture: the Alias Physical Architecture: the Physical Connection User: Srv_dev Password: 12456 IP:10.1.3.195 Database: db_dwh

19. 8-19 Modifications of the Physical Connection MS SQL Server db_dwh Windows Production Server: Houston, TX Datawarehouse (Logical Schema) Logical Architecture: the Alias Physical Architecture: the Physical Connection User: Srv_prod Password: 654321 IP:10.1.2.221 Database: db_dwh Changes in the actual physical information have no impact on the developers who always refers to the same logical alias

20. 8-20 Mapping Logical and Physical Resources MS SQL Server db_dwh Windows Development site: New York, NY Windows MS SQL Server db_dwh db_purchase Production site: Houston, TX Windows MS SQL Server A dwh QA: New York Datawarehouse (Logical Schema) Logical Architecture Physical Architecture But changing the connectivity from one server to the other can become painful…

21. 8-21 Mapping Logical and Physical Resources MS SQL Server db_dwh Windows Development site: New York Windows MS SQL Server db_dwh db_purchase Production site: Boston Windows MS SQL Server A dwh Production site: Tokyo Datawarehouse (Logical Schema) Development Production QA Logical Architecture Contexts Physical Architecture For that purpose, the definition of Contexts will allow you to attach more than one physical definition to a Logical Schema

22. 8-22 Mapping Logical and Physical Resources Windows MS SQL Server db_dwh db_purchase Production site: Boston Datawarehouse (Logical Schema) Production Logical Architecture Contexts Physical Architecture Purchase (Logical Schema) Of course, a given context will map all physical connections Unix MS SQL Server CRM (Logical Schema) Production

23. 8-23 Note – Design-Time vs. Run-Time In ODI, the design or data integration processes is done with logical resources. At run-time, execution is started in a particular context, and ODI will select the associated physical resources for that context.

24. 8-24 Notes Logical resources may remain unmapped to any physical resource in a given contexts. Unmapped resource cannot be used in the context. A single physical resource may be mapped in several contexts. In a given context, a logical resource is mapped at most to one physical resource.

25. 8-25 Logical Architecture/Context views Logical Schema Technology Logical Agent The same technologies are displayed in Physical and Logical Architecture views. You can reduce the number of technologies displayed Windows > Hide Unused Technologies Context

26. 8-26 1.Double-click the context 2.Go to the Agents tab 3.For each logical agent, select the corresponding physical agent in the context. 4.Go to the Schemas tab 5.For each logical schema, select the corresponding physical schema in the context. 6.Click OK. Linking Logical and Physical Architecture

27. 8-27 Planning the Topology 1.Identify the physical architecture All data servers All physical schemas Required physical agents 2.Identify the contexts 3.Define the logical architecture Name the logical schemas Name the logical agents 4.On paper, write out a matrix of logical/physical mappings This matrix helps you plan your topology

28. 8-28 Matrix of Logical/Physical Mappings Logical Schemas ContextsAccountingSales… Development ACCOUNTING in Oracle on Windows SALES in Oracle on Windows … Tokyo ACCT in Oracle on Linux … … ………… 1 2 3

29. 8-29 JDBC Driver A JDBC driver is a Java driver that provides access to a type of database. Type 4: Direct access via TCP/IP Type 3: Three- tier architecture Type 2: Requires the database client layer Type 1: Generic driver to connect ODBC data sources. Drivers are identified by a Java class name. Class must be in present on the classpath. Drivers are distributed as.jar or.zip files Should be copied to the /oracledi/drivers directory.

30. 8-30 Some Examples of Drivers and URLs TechnologyDriverURL Oracleoracle.jdbc.driver.OracleDriverjdbc:oracle:thin:@ : : Microsoft SQL Servercom.inet.tds.TdsDriverjdbc:inetdae7: : Sybase (ASE, ASA, IQ)com.sybase.jdbc2.jdbc.SybDriverjdbc:sybase:Tds: : /[ ] DB2/UDB (type 2)COM.ibm.db2.jdbc.app.DB2Driverjdbc:db2: DB2/400 com.ibm.as400.access.AS400JDBCDriver jdbc:as400:// [;libraries= ] Teradatacom.ncr.teradata.TeraDriverjdbc:teradata:// : / Microsoft Access (type 1)sun.jdbc.odbc.JdbcOdbcDriverjdbc:odbc: File (Sunopsis driver)com.sunopsis.jdbc.driver.file.FileDriverjdbc:snps:dbfile