7. Create a logical schema, ORACLE_ORCL_LOCAL_SALES, and map this schema to different
physical schemas, for the different contexts.
b. Enter the name of the logical schema ORACLE_ORCL_LOCAL_SALES. To map this
logical schema to physical schemas in different contexts, select the appropriate
physical schema in front of each context, as shown in the following screen. Click the
Save button.
8. The logical schema FILE_DEMO_SRC is predefined for you and is mapped in the Global
context to a physical schema that represents a subfolder in a file system. Map
FILE_DEMO_SRC to the same physical schemas in the Development and Production
contexts.
a. In the Logical Architecture, expand the File node, and double-click the
FILE_DEMO_SRC logical schema. Ensure that the logical schema FILE_DEMO_SRC
is mapped to the physical schemas in the Development, Global, and Production
contexts, as follows. Click the Save button.
b. Repeat the previous step for the following logical schemas:
Note: Ensure that these mappings are similar in the three contexts. Close all the tabs, as
shown:
9. You set up ODI agent localagent in Practice . Link the Logical agent to the Physical
agent in all three contexts and test the connection.
a. In the Physical Architecture, open the Physical agent localagent. Similarly, open the
Logical agent, localagent, in the Logical Architecture. Ensure that this Logical agent,
localagent, is linked to Physical agent localagent in all three contexts as follows.
Save your changes.
b. In the physical agent’s localagent tab, click Test, and verify successful connection.
Click OK, and then close all the tabs.
physical schemas, for the different contexts.
- Development Context: To the ORACLE_ORCL_LOCAL.SALES_DEV physical schema
- Production Context: To the ORACLE_ORCL_LOCAL.SALES_PROD physical schema
- Global Context: To the ORACLE_ORCL_LOCAL.SALES_DEV physical schema
a. Select the Logical Architecture tab and expand the Technologies node. Select the
Oracle node, and then right-click and select New Logical Schema.
Oracle node, and then right-click and select New Logical Schema.
b. Enter the name of the logical schema ORACLE_ORCL_LOCAL_SALES. To map this
logical schema to physical schemas in different contexts, select the appropriate
physical schema in front of each context, as shown in the following screen. Click the
Save button.
8. The logical schema FILE_DEMO_SRC is predefined for you and is mapped in the Global
context to a physical schema that represents a subfolder in a file system. Map
FILE_DEMO_SRC to the same physical schemas in the Development and Production
contexts.
a. In the Logical Architecture, expand the File node, and double-click the
FILE_DEMO_SRC logical schema. Ensure that the logical schema FILE_DEMO_SRC
is mapped to the physical schemas in the Development, Global, and Production
contexts, as follows. Click the Save button.
b. Repeat the previous step for the following logical schemas:
- In XML technology, the logical schema XML_DEMO_GEO should be mapped to the
- In Hypersonic SQL, the logical schema HSQL_DEMO_SRC should be mapped to the physical schema HSQL_LOCALHOST_20001_Default in all contexts
- Hypersonic SQL, the logical schema HSQL_DEMO_TARG should be mapped to the physical schema HSQL_LOCALHOST_20002_Default, as follows.
Note: Ensure that these mappings are similar in the three contexts. Close all the tabs, as
shown:
9. You set up ODI agent localagent in Practice . Link the Logical agent to the Physical
agent in all three contexts and test the connection.
a. In the Physical Architecture, open the Physical agent localagent. Similarly, open the
Logical agent, localagent, in the Logical Architecture. Ensure that this Logical agent,
localagent, is linked to Physical agent localagent in all three contexts as follows.
Save your changes.
b. In the physical agent’s localagent tab, click Test, and verify successful connection.
Click OK, and then close all the tabs.
No comments:
Post a Comment