Oracle ODI usage

Note: At the request of the general public, see the address for the original image:Http://blog.csdn.net/meteorlwj/article/details/6949096

Prerequisites:
1) install Oracle ODI
2) install Oracle Xe Database
3) create database users odi/apps, odi_work/apps, odi_ess/apps, odi_obj/apps
4) Create a database table cux_users/cux_sites in odi_ess and odi_obj (where the source and target data are stored ).
Table creation script:
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 cux_users/cux_sites under odi_ess

1. Create a primary database (Start Menu-all programs-ORACLE data integrator-repository management-master repository creation, and create a primary database)

The information of all ODI modules is stored inMaster Repository. Master repository is created through master repository creation wizard, which is the first task to be done after ODI is installed.
In addition to master repository, you also need to create different tasksWork Repository. The information in work repository includes module information, project information, and runtime information.

2. Connect to the primary database (Start Menu-all programs-ORACLE data integrator-topology manager)
1) Select New

2) the logon name can be used at will. the user name and password must be: Supervisor/sunopsis. Select the primary storage database created in step 1 as the primary storage database.

Click test to test whether the connection is successful. If yes, log on to topology manager.

3. Create a context (log on to topology manager. Switch to the context tab and right-click to create a context)
Modification of the physical mode information does not affect the reference of the logical mode, but it is troublesome if the connection information of the Physical Mode Database Server changes. context allows the logical mode to connect multiple physical modes through context to avoid redefinition due to changes in connection information. Of course, context matches all physical modes.

Enter the name and password (Optional). After the password is entered, the password is required for each use of the context. The password is case-insensitive. Click "OK"

4. Create a working repository (log on to topology manager. Switch to the repository tab, right-click to create and insert a working repository)

Here, the user selects odi_work. The work storage stock is in the table Odi. snp_rem_rep, and ODI is the user of the master storage.

5. Create a database server (log on to topology manager. Switch to the physical architecture tab, select "oracle" in technology, and right-click "insert data server ")
Fill in the corresponding information on the "Definition" and "JDBC" tabs. The odi_ess here is the place where the source data is stored. After the test connection is normal, click "OK ".

6. Create a physical architecture (for the database service created in step 1, right-click "Insert Material architecture ")
On the "Define" tab, enter the information and click "OK"

7. Create a logical architecture (log on to topology manager. Switch to the logical architecture tab, select "oracle" in technology, and right-click "insert logical architecture ")
Select the appropriate material architecture for each context

Note: follow the steps above to create a new database service Odi. odi_obj. The material architecture is Odi. odi_obj.odi.obj, and the logical architecture is Odi. obj_logicalschema (this database service is created for the target data user)

8. log on to the work repository (log on to the work repository through designer)
For the first login, select "new". The logon name is arbitrary. The user name and password must be supervisor/sunopsis. For the master database, select the master database created above.

9. Create a project (log on to designer in step 1 and create a project in the project tab)

10. Import the knowledge module (import the required knowledge module to the odi_demo/knowledge module)
The knowledge modules of Odi are mainly divided into several categories (rkm, CKM, lkm, ikm, and SKM), among which the most important are lkm (load km) and ikm (integration km) rkm:
Rkm completes reverse engineering of the data structure of the source and target systems to form a data model.
CKM: CKM completes data quality check.
Lkm: lkm loads data from the source database to a temporary table.
Ikm: ikm loads data from a temporary table to the target table.
SKM: SKM provides the ODI and web service interfaces.
SKM (Service km): Web Service knowledge module, which can be used to generate Web service calls

Note: Some knowledge modules in lkm, CKM, and ikm will be imported here.
Select lkm, right-click "Import knowledge module", select <odi_home>/oracledi/impexp in the file path, and select
Ikm file to SQL
Ikm SQL to SQL

Select CKM, right-click "Import knowledge module", select <odi_home>/oracledi/impexp in the file path, and select
CKM Oracle

Select ikm, right-click "Import knowledge module", select <odi_home>/oracledi/impexp in the file path, and select
Ikm Oracle incremental update

11. Create a model (create a model on the "model" tab)

Select "reverse" and load the data table with the "cux _" header under the odi_ess user to the model (select "cux_users" and Right-click "View data" to display the loaded data)

Note: In the same way, load the database with the "cux _" header under the odi_obj user into the ODI. odi_obj model.

12. Add constraints (add key constraints for cux_users/cux_sites)
In Odi. odi_ess/odi. odi_obj, select cux_users/cux_sites, expand, select constraints, and right-click Insert key"

13. Create an interface (select odi_demo, expand, select "interface", right-click "insert interface ")

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

Observe the content on the "stream" and "control" tabs (if the "lkm" and "CKM" options are not available, check whether the import of the project knowledge module is correct)

14. Execute the "interface" and observe the execution result.

Select "operator" on the toolbar to view the session execution result.

For sessions with errors, right-click to view the error cause

15. Check the imported data
For example, in the "8007" session, after the execution is successful, return to "designer" to view cux_users under the ODI. odi_obj model, right-click "View data", and the data is successfully imported.