Before you begin working on your ODI projects, you need to describe your ODIinfrastructure in the topology. As a starting point of this practice, you will use the environment provided with the ODI installation. The infrastructure includes several servers. You need to define the following new data server and its attached physical schemas.
Data Server: ORACLE_ORCL_LOCAL
SALES_DEV Schema storing the target tables for development purposes
SALES_PROD Schema storing the production target tables
STAGING Schema used to store ODI temporary
objects (not used in this practice) Both the SALES_DEV and SALES_PROD physical schemas contain identical table structures
and correspond to the same logical schema called ORACLE_ORCL_LOCAL_SALES. The
mapping for this logical schema depends on the context.
Note: Completing these tasks is critical for all subsequent practice sessions.
This practice consists of the following six steps:
1. Define the Production context.
2. Define the Development context (a third context, Global, is pre-seeded).
3. Define the ORACLE_ORCL_LOCAL data server.
4. Define the ODI physical schemas for data server: SALES_DEV,SALES_PROD.
5. Define the ORACLE_ORCL_LOCAL_SALES ODI logical schema.
6. Map the logical schema to the two physical schemas, in terms of the three contexts.
Your Tasks:
1. If not started, start Oracle Data Integrator and open the DEV_ODI_REPO connection.
Note: The username and password are case-sensitive.
a. Select Start > Programs > Oracle ODI11g-Home > Oracle Data Integrator > ODI Studio. Click Connect To Repository.
b. Log in with the following details. Click OK
2. Create a new context:
a. Click the Topology navigator tab, and then click the Context tab.
b. Click the New Context icon
on the toolbar, and then select New Context.
c. Enter your context parameters as shown below. The context window should appear as follows. Click the Save button
d. To create another new context , repeat the operations:
The contexts should appear as follows:
3. Create an ORACLE_ORCL_LOCAL data server:
a. Click the Physical Architecture tab. Expand the Technologies node, select the Oracle node, and then right-click and select New Data Server.
b. Enter the following information on the Definition tab
c. Click the JDBC tab. Click the
button at the right of the JDBC Driver field. In the window that appears, select Oracle JDBC Driver, and then click OK.
d. Click the button to the right of the JDBC URL field. In the window that appears,select the first URL, and then click OK.
e. Edit the JDBC URL to have the following:
URL: jdbc:oracle:thin:@localhost:1521:ORCL
The JDBC tab should now appear as follows:
4. Test this data server:
a. Click the Test Connection button. Click Yes to confirm saving your data before testing the connection. In the Information window, click OK.
b. In the dialog box that appears, click the Test button. Click OK.
5. Create a physical schema for this data server: ORACLE_ORCL_LOCAL.SALES_DEV with
the following parameters:
b. In the new window that appears, select SALES_DEV from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) dropdown
list. Verify that the Default check box is selected, and leave all the other fields unchanged. Click the Save button
. Click OK in the Information window that appears.
c.Expand: Oracle > ORACLE_ORCL_LOCAL. The Physical schema ORACLE_ORCL_LOCAL.SALES_DEV appears in the tree view:
6. Create a physical schema ORACLE_ORCL_LOCAL.SALES_PROD for the
ORACLE_ORCL_LOCAL data server:
b. In the new window that appears, select SALES_PROD from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) drop-down list. Check that the Default check box is not selected, and leave all the other
fields unchanged. Click the Save button
. In the Information window, click OK.
Data Server: ORACLE_ORCL_LOCAL
SALES_DEV Schema storing the target tables for development purposes
SALES_PROD Schema storing the production target tables
STAGING Schema used to store ODI temporary
objects (not used in this practice) Both the SALES_DEV and SALES_PROD physical schemas contain identical table structures
and correspond to the same logical schema called ORACLE_ORCL_LOCAL_SALES. The
mapping for this logical schema depends on the context.
Note: Completing these tasks is critical for all subsequent practice sessions.
This practice consists of the following six steps:
1. Define the Production context.
2. Define the Development context (a third context, Global, is pre-seeded).
3. Define the ORACLE_ORCL_LOCAL data server.
4. Define the ODI physical schemas for data server: SALES_DEV,SALES_PROD.
5. Define the ORACLE_ORCL_LOCAL_SALES ODI logical schema.
6. Map the logical schema to the two physical schemas, in terms of the three contexts.
Your Tasks:
1. If not started, start Oracle Data Integrator and open the DEV_ODI_REPO connection.
Note: The username and password are case-sensitive.
a. Select Start > Programs > Oracle ODI11g-Home > Oracle Data Integrator > ODI Studio. Click Connect To Repository.
b. Log in with the following details. Click OK
- .Login name: DEV_ODI_REPO
- User: SUPERVISOR
- Password: SUNOPSIS
2. Create a new context:
a. Click the Topology navigator tab, and then click the Context tab.
b. Click the New Context icon
on the toolbar, and then select New Context.c. Enter your context parameters as shown below. The context window should appear as follows. Click the Save button
- . Name: Production
- Code: PRODUCTION
- Password: Leave this field empty.
- Default: Select this check box, and click Yes to confirm in the pop-up window.
c.
d. To create another new context , repeat the operations:
- Name: Development
- Code: DEVELOPMENT
- Password: Leave this field empty.
- Default: Leave the check box deselected.
The contexts should appear as follows:
3. Create an ORACLE_ORCL_LOCAL data server:
a. Click the Physical Architecture tab. Expand the Technologies node, select the Oracle node, and then right-click and select New Data Server.
b. Enter the following information on the Definition tab
- Name: ORACLE_ORCL_LOCAL
- Instance Name: ORCL
- User: ODI
- Password: ODI
c. Click the JDBC tab. Click the
button at the right of the JDBC Driver field. In the window that appears, select Oracle JDBC Driver, and then click OK.d. Click the
button to the right of the JDBC URL field. In the window that appears,select the first URL, and then click OK.e. Edit the JDBC URL to have the following:
URL: jdbc:oracle:thin:@localhost:1521:ORCL
The JDBC tab should now appear as follows:
4. Test this data server:
a. Click the Test Connection button. Click Yes to confirm saving your data before testing the connection. In the Information window, click OK.
b. In the dialog box that appears, click the Test button. Click OK.
5. Create a physical schema for this data server: ORACLE_ORCL_LOCAL.SALES_DEV with
the following parameters:
- Data Schema: SALES_DEVWork
- Schema: STAGING
- Default check box: Selected
a. Expand the Oracle node. Right-click the newly created data server,ORACLE_ORCL_LOCAL, and then select New Physical Schema.
b. In the new window that appears, select SALES_DEV from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) dropdown
list. Verify that the Default check box is selected, and leave all the other fields unchanged. Click the Save button
. Click OK in the Information window that appears.c.Expand: Oracle > ORACLE_ORCL_LOCAL. The Physical schema ORACLE_ORCL_LOCAL.SALES_DEV appears in the tree view:
6. Create a physical schema ORACLE_ORCL_LOCAL.SALES_PROD for the
ORACLE_ORCL_LOCAL data server:
- Data Schema: SALES_PROD
- Work Schema: STAGING
- Default Schema: Not selected
a. Select the ORACLE_ORCL_LOCAL data server in the tree view, and then right-click
and select New Physical Schema.
and select New Physical Schema.
b. In the new window that appears, select SALES_PROD from the Schema (Schema)
drop-down list, and then select STAGING from the Schema (Work Schema) drop-down list. Check that the Default check box is not selected, and leave all the other
fields unchanged. Click the Save button
. In the Information window, click OK.
No comments:
Post a Comment