ODI offers a unique design approach through use of Contexts and Logical schemas. Imagine a development TEAM, within the ODI Topology manager a senior developer can define the SYSTEM architecture, connections, databases, data servers (tables ETC) and so forth.

These objects are linked through contexts to ‘logical’ architecture objects that are then used by other developers to simply create interfaces using these logical objects, at run-time, on specification of a context within which to execute the interfaces, ODI will use the CORRECT physical connections, databases + tables (source + target) linked the logical objects being used in those interfaces as DEFINED within the environment Topology.

ODI offers a unique design approach through use of Contexts and Logical schemas. Imagine a development team, within the ODI Topology manager a senior developer can define the system architecture, connections, databases, data servers (tables etc) and so forth.

These objects are linked through contexts to ‘logical’ architecture objects that are then used by other developers to simply create interfaces using these logical objects, at run-time, on specification of a context within which to execute the interfaces, ODI will use the correct physical connections, databases + tables (source + target) linked the logical objects being used in those interfaces as defined within the environment Topology.