Creation and configuration of the ODI studio topology (Oracle)

Creation and configuration of the ODI studio topology (Oracle) I. Conceptual interpretation

Topology Manager is primarily used to manage the following 5 categories of tasks and store the information in the master repository for shared use by all modules.

Physical Architecture:

Define various technologies and their data servers, physical architectures, and physical proxies. Data server blind can build multiple physical scenarios, and the essence of each physical scheme is the schema.

Logical Architecture:

Define the various technologies and their associated logical schemas, logical proxies. A logical scenario needs to be based on one or several physical scenarios, essentially a layer of abstraction, and an alias for a physical scheme.

Context:

The main purpose of the context is to implement many-to-many relationships for the logical scheme Multiphysics scenarios, such as the same logical schema that can correspond to different physical scenarios in different contexts.

language :

Language features that can be used by different technologies.

Agent:

The agent is a Java component component, which is also divided into physical agents and logical agents, usually it needs to run on the target library (also can run on the non-target library), the role is to dispatch the data migration job, usually, it simply retrieves the code from the execution repository and requests the database server, The operating system or script engine executes the code.

Data base:

Contains the master repository and its affiliated work repositories. Master Repository, save all the enterprise IT resources topology, save the project and data Model security information, version information for the ODI graphics module and so on. You typically create one. Master repository should be stored as independently as possible, separate instance, or a separate schema. Work Repository, save the project and data model for use with the ODI graphics module. You can create more than one. A work Repository can only connect to one master Repository. A schema can store only one work Repository, but Master Repository can be installed in the same schema.

Ii. Creating a physical architecture 2.1. Creating a source database and a target database scheme

The source and target databases are simulated using ODI_SRC and Odi_tag respectively.

Create User Odi_src,odi_tag

1 /*1th Step: Create a temporary table space*/       2 Create Temporarytablespace odi_temp3Tempfile'C:\app\ORACLE\oradata\orcl\odi_temp.dbf'        4 size 50m5Autoextend on         6 Next50m maxsize 20480m7 extent management Local; 8   9 /*2nd Step: Create a data table space*/        Ten Createtablespace odi_data One Logging ADataFile'C:\app\ORACLE\oradata\orcl\odi_data.dbf'         - size 50m -Autoextend on          the Next50m maxsize 20480m - extent management Local;  -          -  +  /*3rd Step: Create a user and specify a tablespace*/        - Create UserODI_SRC identified byodi_src + defaulttablespace odi_data A Temporarytablespace odi_temp atQuota Unlimited onOdi_data -Profiledefault ;  - Create UserOdi_tag identified byOdi_tag - defaulttablespace odi_data - Temporarytablespace odi_temp -Quota Unlimited onOdi_data inProfiledefault ;  -  to /*4th Step: Grant permissions to the user*/        + GrantConnect,resource toodi_src;  - GrantConnect,resource toOdi_tag;  the Grant Create View  toodi_src;  * Grant Create View  toOdi_tag;

View Code

Create two users odi_src_work and odi_tag_work for the work scheme of the physical scheme odi_src and Odi_tag

1 Create UserOdi_src_work identified byodi_src_work2 defaulttablespace odi_data3 Temporarytablespace odi_temp4Quota Unlimited onOdi_data5Profiledefault ;6 7 Create UserOdi_tag_work identified byodi_tag_work8 defaulttablespace odi_data9 Temporarytablespace odi_tempTenQuota Unlimited onOdi_data OneProfiledefault;

View Code2.2. Create a data server

STEP1: Click Topology, Physical architecture, select oracle-> Right-Select the new database server:

STEP2: Specifies the definition of the database server:

Name: ODI_SRC

Database server: localhost

Connection (user and password for the database, the user's permissions should be greater than or equal to the permissions of the schema in which the data resides)

Users: ODI_SRC

Password: odi_src

STEP3: Specifies the JDBC of the database server:

JDBC Driver: oracle.jdbc.OracleDriver

JDBC URL:jdbc:oracle:thin: @localhost: 1521/PDBORCL

Save, click Test Connection Test successfully.

The same operation establishes the data server Odi_tag

Final effect

2.3. Create a physical scenario

STEP1: On the new data server ODI_SRC, right-click to select New Physical scenario:

STEP2: Create a physical schema of the source database, selecting the odi_src that represents the source data in Oracle,

Directory: ODI_SRC (indicates the source data schema to which the physical scheme should be connected, i.e. where the source data is)

Working directory: odi_src_work (This specifies the storage scheme for temporary tables that need to be created during the data migration process), and if Odi_src is selected, the temporary table is under ODI_SRC scheme

Click Save, ignore the warning below, and then configure the context later

In the same vein, create a physical schema for the target database, choose the odi_tag you just created, select the work plan Odi_tag_work click Save All

The final effect is as follows

2.4. Create a logical scenario

STEP1: Click Topology, Logical Architecture, select Oracle-> Right-select the new logical scheme:

STEP2: Create a logical Scheme ODI_SRC, where you can use the context global that ODI has built, or use the context that you created yourself. The physical scheme corresponds to the source data physics scheme odi_src that you just created. ODI_SRC, click Save All.

At this point, click Physical Scheme odi_src. ODI_SRC, you will find that the context is automatically configured. This actually reflects the direct relationship between the physical scheme-context-logic scheme, which is designed to achieve physical and logical separation. The implementation of a logical scheme can be related to different physical scenarios according to different contexts such as development, build, and the same physical scheme can support the flexible configuration needs of multiple logical schemes.

STEP3: Similarly create the logical scheme Odi_tag, the physical scheme corresponds to the source data physics scheme Odi_tag that you just created. Odi_tag, click Save All, the final effect is as follows

Iii. New Context

There is already a context global in the system, and we can either take this context or create a new one.

Fill in the name and code, here develop represents the development environment, the agent does not fill in, save the effect as follows

Iv. Creating an Agent

Agents also need to create physical and logical proxies, and if they are developed locally, there is no need to create proxies for the time being.

4.1 Creating a physical proxy

Refer to configuring the Domain for the Java EE Agent

4.2 Creating a logical Proxy

Context Select the develop that you just created, or you can use global, the physical proxy scheme to select the oraclediagent you just created

At this point, the topology configuration is complete, the following can create a new project, model, and then design an interface for ETL.

Creation and configuration of the ODI studio topology (Oracle)