Oracle data Integrator Tutorial --- Part 1

Overview :
Oracle Data Integrator is an integration platform. Simply put, it is used to move and transform information across the information system.
Oracle Data Integrator is also a development platform for integration processes. It is unique in two respects:
• It uses an approach driven by business rules. In this approach, you focus your effort on the business side of integration, and not on the technical aspects.
• It uses the E-LT approach. Oracle Data Integrator does not execute the integration processes itself at run time, but orchestrates a process which leverages existing systems.
Oracle Data Integrator is based on metadata. That is, descriptive information about the information system and its contents. This metadata is stored in a centralized metadata repository.
---------------------------------------------------------------------------

Above picture shows the overall Oracle Data Integrator Architecture.
The central component of the architecture is the repository. This stores configuration information about the IT infrastructure, the metadata for all applications, projects, scenarios, and execution logs. Repositories can be installed on an OLTP relational database. The repository also contains information about the Oracle Data Integrator infrastructure, defined by the administrators.
Administrators, developers, and operators use different Oracle Data Integrator Graphical User Interfaces to access the repositories. Security and Topology are used for administering the infrastructure, Designer is used for reverse engineering metadata and developing projects, and Operator is used for scheduling and operating run-time operations.
At design time, developers work in a repository to define metadata and business rules. The resulting processing jobs are executed by the Agent, which orchestrates the execution by leveraging existing systems. It connects to available servers and requests them to execute the code. It then stores all return codes and messages into the repository. It also stores statistics such as the number of records processed, the elapsed time, and so on.
Several different repositories can coexist in a single IT infrastructure. In the graphic in the previous page, two repositories are represented: one for the development environment, and another one for the production environment. The developers release their projects in the form of scenarios that are sent to production.
In production, these scenarios are scheduled and executed on a Scheduler Agent which also stores all its information in the repository. Operators have access to this information and are able to monitor the integration processes in real time.
Business users, as well as developers, administrators and operators, can get Web-based read access to the repository. The Metadata Navigator application server links the Oracle Data Integrator Repository to any Web browser, such as Firefox or Internet Explorer.
------------------------------------------------------------------

The four Oracle Data Integrator GUIs—Designer, Operator, Topology , and Security , are based on Java.
Designer is the GUI for defining metadata, and rules for transformation and data quality. It uses these to generate scenarios for production, and is where all project development takes place. It is the core module for developers and metadata administrators.
Operator is used to manage and monitor Oracle Data Integrator in production. It is designed for production operators and shows the execution logs with errors counts, the number of rows processed, execution statistics, and so on. At design time, developers use Operator for debugging purposes.
Topology manages the physical and logical architecture of the infrastructure. Servers, schemas, and agents are registered here in the Oracle Data Integrator Master Repository. This module is usually used by the administrators of the infrastructure.
Security manages users and their privileges in Oracle Data Integrator. It can be used to give profiles and users access rights to Oracle Data Integrator objects and features. This module is usually used by security administrators
Repository :
First of all you should know how to create the Master and Work repository used in ODI manually.You can create them during before ODI installtion by using Repository creation utility (RCU).
After successful installtion of ODI you create the master as well as work repository manually.To perform this you first creare the tablespace and schema/user dedicated for each repository and give the necessary privileges to those users.
SQL> create tablespace odim_tab add datafile “d:\oracle\dbf\odim01.dbf” size 1G;
SQL> create user odim identified by odim default tablespace odim_tab temporary tablespace temp;
SQL>grant resource,connect to odim;
SQL> create tablespace odiw_tab add datafile “d:\oracle\dbf\odiw01.dbf” size 1G;
SQL> create user odiw identified by odiw default tablespace odiw_tab temporary tablespace temp;
SQL>grant resource,connect to odiw;
Afterwards go to the File menu and select New.In the new gallery select Master Repository Creation Wizard.Press OK.
----------------------------------------------------------------

In Repository Connection  menu Following details would be required to fill it up.
Technology : Technology used for creating the repositories that means the type of database e.g. oracle, sql server etc.
JDBC Driver : JDBC driver used in specified technology. In Oracle technology it is oracle.jdbc.OracleDriver.
JDBC Url: JDBC url to mention the connectivity of that server. In Oracle technology select jdbc:oracle.thin@<host><port><sid> from the dropdown list and change <host>,<port> and <sid> parameters accordingly.
User: user/schema for master repository. [odim]
Password: password for that user. [odim]
Press Test Connection button to check the connectivity. Press OK in Information window. Click Next.
-------------------------------------------------------

In Authentication menu put the password details for ODI supervisor user SUPERVISOR. You cannot change the ODI supervisor user. Click Next.
In Password Storage select ‘Internal Password Storage’ option and click Finish.
-------------------------------------------------------

After creation of master repository in ODI you have to create the ODI repository login id for master repository. You may have more than one ODI repository login id for a single master repository.

To create ODI repository login id again click New under File menu and select Create a New ODI Repository Login. Then click OK.

-------------------------------------------------------------

A Repository Connection Information window is opened.You have to put  the relevant information in each properties.
Oracle Data Integrator Connetion :
Login name:  user defined name as login name.
User: ODI supervisor user SUPERVISOR. (It is case sensitive and you cannot change it).
Password: password of ODI supervisor user.
Database Connection (Master Repository) :
User: database user of master repository.
Password: database password of above user .
Driver List: select Oracel JDBC Driver from drop-down list.
Driver Name: automatically populate according to driver list selected.
Url: select jdbc:oracle.thin@<host><port><sid> from the dropdown list and change <host>,<port> and <sid> parameters accordingly.
Work Repository :
Select Master Repository Only radio button as you create the ODI login id for master repository.
Click Test button to check the connectivity.Press OK afterwards.

------------------------------------------------------------------------

 

 

 Finally we are able to connect to our Master repository.
---------------------------------------------------------------------------------

Please stay in touch for further updates on ODI. For any information in Database visit "Apps DBA Corner" --- akashpramanik.blogspot.com