This chapter introduces the basic steps to creating an integration project with Oracle Data Integrator (ODI). It will help you get started with ODI by outlining the basic functionalities and the minimum required steps.
This section is not intended to be used for advanced configuration, usage or troubleshooting.
To perform the minimum required steps of an Oracle Data Integrator integration project follow the ODI QuickStart list and go directly to the specified section of this guide.
Before performing the QuickStart procedure ensure that you have Installed Oracle Data Integrator, including setting up and configuring ODI agents, according to the instructions in Installing and Configuring Oracle Data Integrator.
Step 1 of the following "QuickStart" list describes setting up the ODI Studio repository architecture. This means creating repositories to store metadata for the applications involved in transformation and integration processing, developed project versions, and all of the information required for their use (planning, scheduling and execution reports).
Steps 2 through 4 describes setting up the topology of your information system by defining the data servers, the schemas they contain, and the contexts. Refer to Chapter 1, "Introduction to Oracle Data Integrator" if you are not familiar with these concepts.
Step 5 consists of creating a model. A model is a set of datastores corresponding to data structures contained in a physical schema: tables, files, JMS messages, elements from an XML file are represented as datastores.
Steps 6 through 8 describe creating your integration project. In this project you create mappings to load data from source datastores to target datastores.
Steps 9 and 10 consist of executing the mappings you have created in step 8, and viewing and monitoring the execution results.
Step 11 describes how to creating sequential loading operations using packages.
Set up the Oracle Data Integrator repository architecture:
You need to create one master repository containing information about the topology, security, and version management of projects and data models. Refer to "Creating the Master Repository" for more details.
To test your master repository connection, refer to "Connecting to the Master Repository".
You need to create at least one Work Repository containing information about data models, projects, and their operations. Refer to "Creating a Work Repository" for more details.
To test your work repository connection and access this repository through Designer and Operator, refer to the section "Connecting to a Work Repository".
To connect source and target systems you need to declare data servers. A data server can be a database, a MOM, a connector or a file server and is always linked with one specific technology. Creating a data server corresponding to the servers used in Oracle Data Integrator is covered in "Creating a Data Server".
A physical schema is a defining component of a data server. It allows the datastores to be classified and the objects stored in the data server to be accessed. For each data server, create the physical schemas as described in "Creating a Physical Schema". Use the default Global context.
In Oracle Data Integrator, you perform developments on top of a logical topology. Refer to Chapter 1, "Introduction to Oracle Data Integrator," if you are not familiar with the logical architecture. Create logical schemas and associate them with physical schemas in the Global context. See "Creating a Logical Schema" for more information.
Mappings use data models containing the source and target datastores. Data Models are usually reverse-engineered from your data server's metadata into an Oracle Data Integrator repository. Create a model according to "Creating and Reverse-Engineering a Model".
The developed integration components are stored in a project. Creating a new project is covered in "Creating a New Project".
Mappings use Knowledge Modules to generate their code. For more information refer to the E-LT concept in Chapter 1, "Introduction to Oracle Data Integrator." Before creating mappings you need to import the Knowledge Modules corresponding to the technology of your data. Importing Knowledge Modules is described in "Importing Objects". Which Knowledge Modules you need to import is discussed in Connectivity and Knowledge Modules Guide for Oracle Data Integrator.
To load your target datastores with data from source datastores, you need to create an mapping. A mapping consists of a set of rules that define the loading from one or more source datastores to one or more target datastores. Creating a new mapping for your integration project is described in "Creating a Mapping".
Once you have finished creating a mapping, you can run it, as described in "Running Mappings". Select Local (No Agent) to execute the mapping directly by Oracle Data Integrator.
You can view and monitor the execution results in the Operator navigator. Follow a mapping's execution using the Operator navigator is described in Chapter 23, "Monitoring Integration Processes."
An integration workflow may require the loading of several target datastores in a specific sequence. If you want to sequence your mappings, create a package. This is an optional step described in "Creating a new Package".