Professional Documents
Culture Documents
Agenda
<Insert Picture Here>
ODI Architecture Overview ODI Components Agents Console Repositories Data Flow Q&A
ODI Architecture
ODI Architecture
Open Web Services for decoupled invocation of any ODI jobs
WebLogic 11g / Application Server FMW Console Servlet Container Web Service Container
Runtime WS Java EE Agent Public WS Data Services
JVM
Java EE Application
ODI SDK
Repositories
ODI Work Repository Legacy
Files / XML
DBMS
Applications ERP/CRM/PLM/SCM
DW / BI / EPM
ODI Components
Graphical Modules
ODI Designer
Operator Operate production Monitor sessions Topology Manager Define the infrastructure of the IS
Access Data
Repository
Any ISO-92 RDBMS Public Web Services Manage sessions Access Data Java EE Agent Handles schedules Orchestrate sessions
Return Code
Execute Jobs
Information System
Submit Jobs
Repository
Execute Jobs
Information System
Repository
Any ISO-92 RDBMS Enterprise Manager Fusion Middleware Console Java EE Agent Handles schedules Orchestrate sessions
Submit Executions
Return Code
Information System
Access Data
Repository
Data Services Access Data and Changed Data Public Web Services Manage sessions Access Data Java EE Agent Handles schedules Orchestrate sessions
Other components
SOA Suite, WLS Servers, Web apps.
ODI Studio
Designer Navigator Operator Navigator Topology Navigator Define the infrastructure of the IS. Operate production. Monitor sessions.
Reverse engineer.
Develop projects.
Release scenarios.
Repository
Designer Navigator
Toolbar
Object tree
In ODI Designer, you can create, configure, and execute various ODI objects. Workspace to define ODI objects and design EL-T transformations
Operator Navigator
Toolbar
Topology Navigator
Toolbar
Technologies tree Workspace to define ODI Topology objects In ODI Topology Manager, you set the architecture of your information system, the technologies, servers, schemas, and repositories.
Security Navigator
Object tree
Agents
What Is an Agent?
An agent is a run-time component of ODI that orchestrates the integration process. At design time, developers generate scenarios from the business rules that they have designed. The code of these scenarios is then retrieved from the repository by the agent at run-time. This agent then connects to the data servers and orchestrates the code execution on these servers.
ODI Agents
Agents are lightweight Java processes that orchestrate the execution of objects at run time. Agents can: Execute objects on demand, or Execute according to predefined schedules
Standalone agent
JDeveloper
ODI Studio
Standalone Java
ODI Agent
Designer Security Topology Operator
ODI Agent
Any Application
ODI Public Web Service ODI SDK APIs ODI Data Services
Knowledge Modules ODI Work ODI Work Repository ODI Work Repository Repository
Repository Data Sources Sources Data Sources Repository Data Sources Sources Data Sources Repository Data Sources Sources Data Sources
----------Best-of-Breed Applications
-----------
Legacy
Deploying an agent in a JEE Application Server (Oracle WebLogic Server): 1. Define the JEE Agent in the Topology Navigator 2. Create the WLS template for the JEE Agent 3. Deploy this template directly using the WLS Configuration Wizard Using a standalone agent: 1. Launch an Agent 2. Display Scheduling Information 3. Stop the Agent
Reverse engineer Monitor sessions View Reports Develop projects Submit Release Jobs scenarios
Repository Read sessions Standalone Agent Orchestrates sessions Return Code Execute Jobs Write reports
Information System
Console
ODI Console
Development
Agent
ODI Console
ODI Console
Agent
ODI Repositories
ODI Repositories
There are two types of repositories in ODI: Master repository Work repository Development repository Execution repository Work repositories are always attached to a Master repository.
Models
Execution
Two type of Repositories: Master and Work Work Repositories are always attached to a Master Repository
Master Repository
Import released versions of models, projects and scenarios for testing
Models Models Execution Projects Execution Work Repository (Test & QA) Execution Repository (Production)
Projects
Execution
Security Topology
Projects
Execution
Firewall
Master Repository
Master Repository
Architecture
No Server: only an orchestrator (The Agent) that will send the appropriate SQL statements to the different databases.
Servers and Applications
Execution
CRM
Return Codes
ESB Files / XML
ER P
Developer
Developer
Developers each have the Java GUI on their machine and share a central repository to store the metadata and the transformation processes (no local storage).
Copyright 2010, Oracle. All rights reserved.
Architecture
Execution
CRM
Developer
Developer
Processes are orchestrated (and possibly scheduled) by an ODI Java agent (no graphical component to allow for the largest possible set of platform support).
Architecture
Execution
CRM
Developer
Developer
Multiple agents can co-exist in any given environment. Typical locations for the agents are on the target system and/or on the system that hosts the ODI repository.
Copyright 2010, Oracle. All rights reserved.
1. 2. 3.
Development
CRM
Data Warehouse
CRM
Data Warehouse
Legacy
Legacy
ERP
ESB
Administrators
Designers