1 / 30

Oracle Data Integrator Topology: Connecting to the World

Oracle Data Integrator Topology: Connecting to the World. 3. Objectives. After completing this course, you will:. Understand the basic concepts behind the Topology interface. Understand logical and physical architecture. Know how to plan a Topology.

britanney-williams
Download Presentation

Oracle Data Integrator Topology: Connecting to the World

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Objectives After completing this course, you will: • 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. 8-2

  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 8-3

  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 8-4

  5. Concepts in Reality 8-5

  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. 8-6

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

  8. Legend MSSQL-Boston Data server Oracle-Boston9 Oracle-Boston10 The Physical Architecture in ODI ACCOUNTING db_dwh db_purchase SALES Oracle-Tokyo MSSQL-TokyoA MSSQL-TokyoB ACCT dwh Physical schema SAL purchase 8-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, … 8-9

  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. 8-10

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

  12. Creating a Data Server - JDBC Select URL Select driver • Select the JDBC tab • Fill in the JDBC driver • Fill in the JDBC URL • Test the connection • Click OK 8-12

  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. 8-13

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

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

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

  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 Schemathat is simply an alias for the physical layer. 8-17

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

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

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

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

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

  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. 8-23

  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. 8-24

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

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

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

  28. Matrix of Logical/Physical Mappings 2 1 3 8-28

  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. 8-29

  30. Some Examples of Drivers and URLs 8-30

More Related