With the new ODI version 12c (Oracle Data Integrator), Oracle provides us an enhanced ELT (Extract Load Transform) and more opened with all other applications.
Find here a short summary of those new features for the 12c (release 18.104.22.168.0 and 22.214.171.124.0):
|Control for Scenario and Load Plan Concurrent Execution
|Improved control allows the ability to limit concurrent executions in a scenario or load plan and force a concurrent execution to either wait or raise an execution error.
|The ODI Studio client is entirely redesigned in this release to enhance user experience and productivity. The new user interface blends the previous declarative design model approach with a flow-based methodology. Now the business user or the developer can focus on describing what to do, not how to do it. Mappings (the successor of the Interface concept in Oracle Data Integrator 11g) connect sources to targets through a flow of components such as: Join, Filter, Aggregate, Set, Split, etc. Oracle Data Integrator Enterprise Edition generates, deploys and manages the code required to implement those processes across the various source and target systems.
|The information that was previously available in the Oracle Data Integrator Developer’s Guide is now reorganized. Three new guides have been added to meet this requirement (Understanding ODI, Administering ODI and ODI Tool Reference).
|Federal Information Processing Standard (FIPS) Compliance
|ODI leverages Advanced Encryption Standard (AES) as the standard encryption algorithm for encrypting Knowledge Modules, procedures, scenarios, actions, and passwords. Passwords and other sensitive information included in repository exports are now encrypted and secured by a password.
|ODI supports Apache HBase through a new technology and related Knowledge Modules
|Hive Append Optimization
|Knowledge Modules writing to Hive support the Hive 0.8+ capability and can append data to the existing data files rather than copying existing data into a new appended file.
|The Oracle Data Integrator Complex File Driver introduces the ability to read and write files in JSON format. The JSON structure is defined through an nXSD schema.
|Knowledge Module Architecture
|ODI has introduced a new style of Knowledge Module, called Component-Style Knowledge Module. This new style of Knowledge Module provides an extensible component framework that improves the overall mapping design, where for example users are able to declare the transformation order. These also improve reusability as they can be plugged together; in addition to helping avoid code and data duplication as well as providing improved Oracle connectivity with database links.
|Lower Session Overhead and Enhanced Parallelism
|ODI 12c introduces improved runtime execution to enhance performance. Various changes have been made to reduce overhead of session execution, including the introduction of blueprints, which are cached execution plans for sessions. The improvement comes from loading sources in parallel into the staging area. Parallelism of loads can be customized in the physical view of a map. Users also have the option to use unique names for temporary database objects, allowing parallel execution of the same mapping.
|Model and Topology Objects Wizard
|The Create New Model and Topology Objects dialog in the Designer Navigator provides the ability to create a new model and associate it with new or existing topology objects, if connected to a work repository. This dialog enables you to create topology objects without having to use Topology editors unless more advanced options are required.
|Multiple Target Support
|ODI’s flow-based declarative user interface allows for a mapping to load multiple targets as part of a single flow. Whether one or multiple targets, the order of target loading can be specified, and the Split component can be optionally used to route rows into different targets, based on one or several conditions.
|Multi-threaded Target Table Load
|ODI provides the functionality to load a target table using multiple parallel connections. This capability is controlled through the Degree of Parallelism for Target property available at the data server level in Topology Navigator.
|Oracle Platform Security Services Integration
|Oracle Data Integrator is able to use the authorization model in Oracle Platform Security Services (OPSS) to control access to resources. Enterprise roles can be mapped into Oracle Data Integrator roles to authorize enterprise users across different tools.
|Oracle Warehouse Builder Integration
|ODI provides improved interoperability with Oracle Warehouse Builder, providing the foundation for customers to start migrating to Oracle’s strategic Oracle Data Integrator platform. Oracle Warehouse Builder (OWB) jobs can now be executed in Oracle Data Integrator through the OdiStartOwbJob tool. The Oracle Warehouse Builder repository is configured as a data server in Topology. Users will thus also find all the Oracle Warehouse Builder job execution details displayed as a session in Operator, Oracle Data Integrator Console, and Enterprise Manager.
|Reusable mappings can be used to encapsulate flow sections that can then be reused in multiple mappings. A reusable mapping can have input and output signatures to connect to an enclosing flow, and it can also contain sources and targets that are encapsulated inside the reusable mapping.
|ODI introduces loading of sources and targets using Apache Sqoop.
Sqoop enables load and unload mechanisms using parallel JDBC connections in Hadoop Map-Reduce processes.
|Standalone Agent and WebLogic
|Standalone agents are managed through the WebLogic Management Framework. The following advantages comes as a result of user-interface driven configuration through the Configuration Wizard, multiple configurations can be maintained in separate domains then Node Manager can be used to control and automatically restart agents.
|ODI has introduced a step-by-step debugger. Mappings, Packages, Procedures, and Scenarios can be debugged in a step-by-step manner. Users are able to manually traverse task execution within these objects and set breakpoints to interrupt execution at pre-defined locations. Values of variables can be introspected and changed during a debugging session, and data of underlying sources and targets can be queried, including the content of uncommitted transactions for better insight.
|Studio and Repository Performance
|Studio/Repository performance improvements have been made, reducing the chattiness for remote repository access, and optimizing database access.
|Superior Oracle GoldenGate Integration
|High performance E-LT capabilities integrated with Oracle GoldenGate enable faster and more efficient loading and transformation of real-time data into a data warehouse. Customers can now easily configure and deploy real-time data warehousing solutions without impacting source systems or batch window dependencies.
Oracle GoldenGate Gate source and target systems are now configured as data servers in Oracle Data Integrator’s Topology, most Oracle GoldenGate parameters can be added to extract and replicate processes in the physical schema configuration, a single Oracle Data Integrator mapping can be used for journalized Change Data Capture load and bulk load of a target then Oracle GoldenGate parameter files can now be automatically deployed and started to source and target Oracle GoldenGate instances through the JAgent technology.
|Unified Administration and Monitoring
|Oracle introduces Management Pack for Oracle Data Integrator, which leverages Oracle Enterprise Manager Cloud Control’s advanced management capabilities, to provide an integrated and top-down solution for your Oracle Data Integrator environments. Management Pack for Oracle Data Integrator provides a consolidated view of your entire Oracle Data Integrator infrastructure enabling users to monitor and manage all their components centrally from Oracle Enterprise Manager Cloud Control. Management Pack for Oracle Data Integrator supports both 11g (126.96.36.199.0 and higher) and 12c versions of Oracle Data Integrator.
|Unique Repository IDs
|Master and Work Repositories now use unique IDs following the GUID convention. This avoids collisions during import of artifacts and allows simpler management and consolidation of multiple repositories in any given project or organization.
|The XML Schema support enhancements have been added. Now ODI supports recursion inside XML Schemas. The types named any, anyType, and anyAttribute have been added, data defined by these types is stored in string type columns with XML markup from the original document. Metadata annotations can be added inside an XML Schema to instruct the ODI XML Driver which table name, column name, type, length, and precision should be used.