ODI12C Installation guide (standalone)

Before starting the installation, JDK (Java Development Kit) is required.

It is important to use JDK because

•  OUI requires a JDK which provides the JRE (Java Run-Time Environment) and tools for compiling and debugging java applications. 
•  Moreover installation process assigns values to JAVA_HOME and related variables points to JDK directory. 

Step for installation:-

Step 1:-Navigate to Java directory like (cd /usr/java/jdk1.7/jdk1.7.0_79/bin/) and run below mention command:

            java –jar D:\oracle\odi\fmw_12.1.3.0.0_odi.jar

Step 2:- Click Next

Step 3:- Specify the location where you want to install ODI. 

Step 4:- Select standalone installation. Click on next.

Step 5:- Click on next.

Step 6:- Unchecked the security updates. Click on next.

Step 7:- Click on Install. 

Step 8:- Click next then finish.

ODI ARCHITECTURE

                                                      
Oracle Data Integrator is an ETL tool (Extract, Load and Transform). It provides a graphical interface for user to build, manage and maintain data integration processes.

ODI follow 4 tier architecture. It consists of:-

• Desktop
• WebLogic Server
• Repositories
• Sources and Targets  

ODI consist of following components:-

Repositories

Repository is the primary component in the ODI architecture. Basically repository contains design time objects (packages, interface or mapping), run time objects (scenarios) plus sessions.

There are two types of Repositories

• Master Repository
• Work Repository

Master Repository

It contains information related to topology and security navigator.

1. Topology:- It includes information like technologies, physical and logical schema, context, agents, languages, JDBC URLs, username etc.
2. Security:- All the information handled by security navigator is also part of master repository like users, profiles, access privileges.
3. Versions:- Whenever new version of object is create, master repository maintains its a record.

This repository comprise of sensitive information.

Work Repository

1. It manages information regarding designer and operator navigator.
2. Information corresponding to developer activities like:- Projects i.e. packages, procedures, variables, sequences, mapping.
3. Scenarios, load plan, schedules, source and target metadata.
4.  And one master repository can have multiple work repositories, but work repository can only have one and only one master repository.
5. Work repository cannot exist alone. Work repository depends upon master repository for its existences.

ODI Studio is the medium through which we can access the master and work repository.

Four navigators are provided through which we can manage different aspect and steps of odi project. 

• Design

Design navigator manages model and projects. Project Development tasks are done in this navigator. In this we develop, maintain tasks graphically. Moreover metadata about the projects is defined in this navigator. Codes generated in this can be customized.

• Operator

This navigator is used for production management and monitoring. In this we can monitor step by step execution of scenario i.e. mapping, packages and procedure or of load plan.

• Topology Manager

Topology navigator describes the logical and physical architecture of the information system. This navigator contains information about technologies, physical and logical schema, context, agents and languages.

• Security Manager

As the name suggest security manager, its helps to manage the security of ODI.  Creation of user profiles, roles takes place in this navigator and it also assign privileges to profiles and roles.

Run Time Agents

Agents are required for the execution of the scenarios. Agent don not contain all the information regarding session, but only have basic information.  Other detail information about session is stored in the repository.

So whenever scenario is executed on an agent, the agent will create session on the repository.  Agent will read task to done on this session from the repository, then it will process it and then write the result in the repository.

There are 2 types of agents

Standalone Agent:-  

• Standalone agent is light weighted because it does not require application server.  Due to this installation on already active or running server is easy.
• For standalone agent to work it requires java virtual machine.

Java EE agent:-

Since on agent whole execution process depends, so it is important that it should be up all the time, because if agent is down and some schedule job tries to run it will fail and create issue. So it was the main drawback of standalone agent.

Whereas in Java EE is web application and can be deploy on several nodes. And all the schedule jobs are stored in coherence cache and if any nod is down another one can perform its job. It makes use of the benefits provided by application server.

ODI Console

It is a web based user interface where you can view and edit topology objects, manage scenarios, monitor sessions.

http://ithelpdeskinc.com/