Oracle ODI Use __oracle

Prerequisites:
1) Install Oracle ODI
2 Install Oracle XE database
3 CREATE DATABASE user Odi/apps, Odi_work/apps, Odi_ess/apps, Odi_obj/apps
4 CREATE database tables in Odi_ess and odi_obj (source data and destination data storage locations) Cux_users/cux_sites
The table script is:
CREATE TABLE Cux_users
(user_id number,
Username VARCHAR2 (20),
Email VARCHAR2 (20),
Phone VARCHAR2 (20));

CREATE TABLE Cux_sites
(site_id number,
USER_ID number,
Site_use_code VARCHAR2 (20),
Address1 VARCHAR2 (100));
5) Add data to the Cux_users/cux_sites under Odi_ess

1, create the main repository (Start menu – All Programs –oracle data integrator–oracle data integrator–repository management–master Repository creation, Create primary repository)

ODI information for all modules is stored in a central repository called Master Repository . Master Repository is created through the Master Repository Creation Wizard, which is the first task you should do after you install ODI.
In addition to master Repository, you need to create Work Repositoryfor different tasks. The information in Work repository includes module information, project information, and run-time information.

2. Connect the main repository (Start menu – All Programs –oracle data integrator–oracle data integrator–topology Manager)
1) Select New

2 Login name can be arbitrary, the user and password must be: supervisor/sunopsis, master repository Select the primary repository created in step 1th

Click Test to test the success of the connection and, if successful, be sure to log in to topology Manager.

3. Create context (Login to topology Manager.) Switch to Context tab, right-new context)
Modification of physical schema information does not affect references to logical schemas, but is cumbersome if the connection information of the physical schema database server changes. The appearance of the context is to allow the logical mode to connect multiple physical modes through the context, and to avoid redefining the connection information changes. Of course, the context matches all physical patterns.

Enter the name, password (optional, after entering a password each time use this context will require the password, the case strictly match), click "OK" directly

4. Create a working repository (login to Topology Manager.) Switch to Repository tab, right-new insert work repository


The user here chooses Odi_work, the working storage inventory is in the table Odi.snp_rem_rep, ODI is the user of the primary repository.

5, create the database server (login to topology Manager.) Switch to Physical Architecture tab, select Oracle in Technology, right-click "Insert Data Server"
In the Definition and JDBC tab page, fill in the appropriate information, where the odi_ess is the source data storage place, the test connection is normal after the direct point "OK

6. Create the physical schema (database service created in step 5th, right-click Insert Item schema)
Fill out the information in the "Definition" tab and click "OK" directly

7, create the logical schema (login to Topology Manager.) Switch to Logical Architecture tab, select Oracle in the technique, right-click Insert Logical Schema
Select the corresponding item schema for each context

Note: Follow the steps above to create a new database service Odi.odi_obj, and the material schema is odi.odi_obj. Odi. OBJ, the logical schema is Odi.obj_logicalschema (this database service was created for the target data user)

8. Log in to the working repository (login to the Working repository via designer)
First Login Select "New", Login name arbitrary, username/password must be supervisor/sunopsis, master repository Select the primary repository created above

9, create the project (through the 8th Step login designer, the Project tab to create a new project)

10, Import knowledge module (in the odi_demo/Knowledge module to import the required knowledge module)
ODI's knowledge modules are divided into several major categories (RKM,CKM,LKM,IKM,SKM), the most important of which are LKM (load KM) and ikm (integration km) RKM:
RKM completes the function of reverse engineering of data structure from source system and target system to form model.
CKM:CKM completes the data quality check.
LKM:LKM completes loading from source database data to temporary table.
IKM:IKM completes loading the data from the temporary table to the target table.
SKM:SKM completes the functionality of the ODI and Web service interfaces.
SKM (Service KM): Web Services Knowledge module, which can be used to generate Web service calls

Note: This will import some of the Knowledge module content in lkm/ckm/ikm
Select Lkm, right-click "Import Knowledge Module", select <odi_home>/oracledi/impexp in File path, select in import file
ikm File to SQL
IKM SQL to SQL

Select CKM, right-click "Import Knowledge Module", select <odi_home>/oracledi/impexp in File path, select in import file
CKM Oracle

Select ikm, right-click "Import Knowledge Module", select <odi_home>/oracledi/impexp in File path, select in import file
IKM Oracle Incremental Update

11. Create a model (create a new model in the Model tab page)

Select reverse to load the data table with the odi_ess user under "Cux_" (select "Cux_users", right-click "View Data", and display the loaded data)

Note: Load the "cux_" database under the Odi_obj user into the Odi.odi_obj model in the same way

12. Add constraint (add key constraint for cux_users/cux_sites)
In Odi.odi_ess/odi. Odi_obj Select Cux_users/cux_sites, expand, select Constraints, right-click Insert Key

13. Create interface (select Odi_demo, expand, select "Interface", right-click "Insert Interface")

Note: In the pop-up window "whether to automatically map" select "OK"

Note the contents of the Flow and Controls tab (if no "LKM" and "CKM" options are blank, check that the Project knowledge module is imported correctly)

14, the implementation of "interface" to observe the implementation of the results

Select "Operator" on toolbar to view session execution results

For a session that is performing an error, right-click the cause of the error

15, check the import data
As shown in the "8007" session above, after successful execution, return to "Designer" to view the cux_users under the Odi.odi_obj model, right-click "View Data" and see the data imported successfully