ODI - Type1- Installation of ODI 12c

Installation needs following 2 components:

• Search ODI in google and download the software disk1. The latest version is now Oracle Data Integrator 12c (12.2.1.4.0).
• JDK version 1.8

Simple steps:

Step1: Open CMD in admin mode.

Step2: Go to the Java bin path like "C:\Program Files\Java\jdk1.8.0_51\bin"

Step3: java - jar  <ODI file path>

ODI file path like C:\Users\Srinanda\Desktop\fmw_12.2.1.4.0_odi_Disk1_1of1\fmw*.jar

Step4: Installer will start. Choose Standard or Enterprise

Next

Install

Step5: Once Installation done, connect to repository.

ODI - Creating the Master and Work Repository Schemas

Creating the Master and Work Repository Schemas

Before you can configure an Oracle Data Integrator domain, you must create the Master and Work Repository (ODI_REPO) schemas on a certified database for use with this release of Oracle Fusion Middleware.

Configuring a Certified Database

Before you begin, make sure you have installed and configured a certified database

Starting the Repository Creation Utility

Navigate to the ORACLE_HOME/oracle_common/bin directory:

Start RCU.

On UNIX operating systems:

./rcu

On Microsoft Windows operating systems:

rcu.bat

Navigating the Repository Creation Utility Screens to Create the Schema

Start RCU - Click Next.

Select a Repository Creation Method.

If you have permission to perform DBA activities on your database, select System Load and Product Load Concurrently.

Provide the database connection details for RCU to connect to your database. Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.

Select Create a new prefix, specify a custom prefix, then select the Oracle Data Integrator schema.

If you are running RCU from a Standalone installation, you will see the following:

Select Oracle Data Integrator and click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.

Specify the custom variables for the Master and Work Repository

Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.

Steps with screenshots:

For  more details: https://docs.oracle.com/middleware/1221/core/ODING/GUID-25AC5AEE-D46D-4E4B-8835-4C1FE32207CC.htm#ODING860

ODI - How to add Data servers and schemas in the Topology

Physical Topology:

Add Data Server:

First choose one technology for example oracle and right click and add new data server

Provide data server details like

• Definitions: Name, User , Password
• JDBC: JDBC driver and URL

and test connection.

Add Physical schema:

Suppose you have created data server name as Test and then right click on test and create new physical schema and add the schema name and save. 

Logical Topology:

Create a new logical schema and provide context values with the required physical schemas

4 context environments are available:

• development
• Global
• Production
• Test

Now go  to the Physical schema of Oracle technology, you will see that all the context values are mapped with the logical schemas.

With screenshots:

Designer Tab = Model:

Go to the designer tab and create new object and new  model

provide definition , reverse engineering details

selective reverse engineering etc. to import all the tables.

ODI - Overview of Oracle Data Integrator Topology

 This section contains these topics:

• Physical Architecture
• Contexts
• Logical Architecture
• Agents

Physical Architecture

The physical architecture defines the different elements of the information system, as well as their characteristics taken into account by Oracle Data Integrator. Each type of database (Oracle, DB2, etc.), Big Data source (Hive, HBase), file format (XML, Flat File), or application software is represented in Oracle Data Integrator by a technology.

A technology handles formatted data. Therefore, each technology is associated with one or more data types that allow Oracle Data Integrator to generate data handling scripts.

The physical components that store and expose structured data are defined as data servers. A data server is always linked to a single technology. A data server stores information according to a specific technical logic which is declared into physical schemas attached to this data server. Every database server, JMS message file, group of flat files, and so forth, that is used in Oracle Data Integrator, must be declared as a data server. Every schema, database, JMS Topic, etc., used in Oracle Data Integrator, must be declared as a physical schema.

Finally, the physical architecture includes the definition of the Physical Agents. These are the Java software components that run Oracle Data Integrator jobs.

Contexts:

Contexts bring together components of the physical architecture (the real Architecture) of the information system with components of the Oracle Data Integrator logical architecture (the Architecture on which the user works).

For example, contexts may correspond to different execution environments (Development, Test and Production) or different execution locations (Boston Site, New-York Site, and so forth.) where similar physical resource exist.

Note that during installation the default GLOBAL context is created.

Logical Architecture:

The logical architecture allows you to identify as a single Logical Schema a group of similar physical schemas (that contain datastores that are structurally identical) that are located in different physical locations. Logical Schemas, like their physical counterparts, are attached to a technology.

Contexts allow logical schemas to resolve to physical schemas. In a given context, a logical schema resolves to a single physical schema.

For example, the Oracle logical schema Accounting may correspond to two Oracle physical schemas:

Accounting Sample used in the Development context

Accounting Corporate used in the Production context

These two physical schemas are structurally identical (they contain accounting data), but are located in different physical locations. These locations are two different Oracle schemas (Physical Schemas), possibly located on two different Oracle instances (Data Servers).

All the components developed in Oracle Data Integrator are designed on top of the logical architecture. For example, a data model is always attached to logical schema, and data flows are defined with this model. By specifying a context at run-time (either Development or Production), the model's logical schema (Accounting) resolves to a single physical schema (either Accounting Sample or Accounting Corporate), and the data contained in this schema in the data server can be accessed by the integration processes

Agents:

Oracle Data Integrator run-time Agents orchestrate the execution of jobs. These agents are Java components.

The run-time agent functions as a listener and a scheduler agent. The agent executes jobs on demand (model reverses, packages, scenarios, mappings, and so forth), for example when the job is manually launched from a user interface or from a command line. The agent is also used to start the execution of scenarios according to a schedule defined in Oracle Data Integrator.