Logical and Physical Schema in ODI
Posted by Dylan Wan on November 10, 2015
ODI Topology allows you to isolate the physical connection and the logical data source by defining the physical schema and logical schema.
This object may be seen as redundant during development. However, it is a very useful feature for supporting the Test to Production (T2P) process. The objects in the design tab references only the logical schema and never directly reference to any physical connection. When you are moving to the production system, you can just change the context from the testing to production instance.
This design satisfies the need by the system administrators to name the instances according to their internal deploying company’s system naming while it also satisfies the content developer’s, especially the prepackaged application developer’s need of naming the data source in a generic way.
For example, when we developed the EBS adaptor, we named the data source EBSR12, we do not name it as EBSR12DEV or EBR12TST. However, we may have multiple source databases, and we do need to know which one we are connecting to. We can name the physical connection as EBSR12DEV vs EBSR12TST.
This design takes care of the needs of both a content developer and a system administrator.
How about Informatica?
Informatica Workflow also refers to database connection by name directly. It does not have such isolation from its data model.
However, Informatica treat the connection to a workflow session as a property and the property can be parameterized in a variable. By referencing the variable in the workflow session, and let the deploying companies to set the value for the variable, OBIA accomplishes the isolation between the packaged apps development and the deploying company.
DAC serves the needs in Informatica based ETL
Informatica does not address the T2P needs.
For the deploying companies for OBIA, during Testing to Production process, the variable value is actually set from the Data Warehouse Administration Console (DAC). DAC provides another level of isolation and smooth the T2P process.
DAC fills many gaps of Informatica for prepackaged apps requirements due to the fact that Informatica is not an Oracle product and was not designed for the requirements of prepackaged apps.
DAC is not needed in the ODI based architecture since many of its roles are taken care by ODI.