Tuesday, March 20, 2012

New Features in Oracle Data Integrator 11gR1 PS1 (11.1.1.5)

New Features in Oracle Data Integrator 11gR1 PS1 (11.1.1.5)

The first Oracle Data Integrator 11gR1 Patch Set introduces the following enhancements:
  • Load Plans
  • OBIEE Lineage
  • Commands on Connect/Disconnect
  • Complex File Technology
  • Groovy Technology
  • Web Services Enhancements
  • Built-in Technology Additions and Updates
  • Support for Technologies with Ordered and Non-Ordered Join Syntax
  • New Method for Setting Task Names
  • Shared Library for WLS Agent
  • Performance Optimization

Load Plans

Load Plans are new objects introduced in this release to organize at a high level the execution of packages and scenarios. Load Plans provide features for parallel, sequential, and conditional scenario execution, restartability, and exception handling. Load Plans can be created and modified in production environments.

OBIEE Lineage

Oracle Business Intelligence Enterprise Edition (OBIEE) users need to know the origin of the data displayed on their reports. When this data is loaded from source systems into the data warehouse using Oracle Data Integrator, it is possible to use the Oracle Data Integrator Lineage for Oracle Business Intelligence feature to consolidate ODI metadata with OBIEE and expose this metadata in a report-to-source data lineage dashboard in OBIEE.

Commands on Connect/Disconnect

It is possible to define for a data server commands that will be automatically executed when connections to this data server are created or closed by ODI components or by a session.

Complex File Technology

Complex file formats (multiple record files) can now be integrated using the new Complex File technology. This technology leverages a new built-in driver that converts transparently complex file formats into a relational structure using a Native Schema (nXSD) description file.

Groovy Technology

Groovy is added to the list of scripting engines supported by Oracle Data Integrator for use in knowledge modules and procedures.

Web Services Enhancements

Web service support in Oracle Data Integrator has been enhanced with the following features:
  • Support for Container Based Authentication: When external authentication and container based authentication with Oracle Platform Security Services (OPSS) are configured, authentication can be passed to the ODI Run-Time Web Services using HTTP basic authentication, WS-Security headers, SAML tokens and so forth and not in the SOAP request.
  • Support for Asynchronous calls and Callback: A scenario or session can be started using the Run-Time Web Services on a one-way operation. When the session completes, the result of the execution can trigger an operation on a callback address. This pattern can be used for handling long running sessions started, for example, from Oracle BPEL.
  • Full SOAP edition for outbound web services calls: The OdiInvokeWebService tool now supports full-formed SOAP messages including the SOAP header and body.

Built-in Technology Additions and Updates

The following technologies used in Oracle Data Integrator have been added and updated:
  • Embedded HSQL engine is upgraded to version 2.0. This embedded engine is used for the Memory Engine as well as the XML and LDAP Drivers' built-in storage
  • Jython BSF engine is updated to version 2.1
  • JAX-WS/JRF is now used as a standard stack for web service calls and processing. Axis is no longer used

Support for Technologies with Ordered and Non-Ordered Join Syntax

Technologies can now support both the ordered or non-ordered (database-specific) syntax for joins. The Oracle DB technology was modified to support both join syntaxes.

New Method for Setting Task Names

A new setTaskName method is available to update at run-time the name of a task.

Shared Library for WLS Agent

A new template called Oracle Data Integrator - Agent Libraries includes libraries shared by all the deployed JEE agent in a domain, and must be deployed before the Oracle Data Integrator - Agent default template or a generate template.

Performance Optimization

The following optimizations have been made in the design-time and run-time components to improve their performance:
  • Long texts storage modified to use CLOBs
  • Agent-Repository network communications reduced at run-time
  • Agent JDBC to JDBC loading mechanism reviewed and optimized

New Features in Oracle Data Integrator 11gR1 PS2 (11.1.1.6)

New Features in Oracle Data Integrator 11gR1 PS2 (11.1.1.6)

 

The second Oracle Data Integrator 11gR1 Patch Set introduces the following enhancements:
  • Shortcuts
  • Tracking Variables and Sequences
  • Global Knowledge Modules
  • Enhanced Session Logging
  • Handling Failed Load Plan Enhancements
  • Enhanced Variable Handling in Load Plans
  • Smart Export and Import
  • Enterprise Data Quality Integration
  • Groovy Editor
  • Support of Undo and Redo Operations
  • Autocomplete for Text Fields and Lists
  • Version Numbering for Knowledge Modules
Shortcuts
This ODI release introduces new objects called shortcuts. Shortcuts greatly improve productivity by allowing end users to express the large commonality that often exists between two different versions of the same source application, such as same tables and columns, same constraints, and same transformations.
Shortcuts are links to common Oracle Data Integrator objects stored in separate locations and can be created for datastores, integration interfaces, packages, and procedures. In addition, release tags have been introduced to manage the materialization of shortcuts based on specific tags.

Tracking Variables and Sequences
Variables and sequences are often used in Oracle Data Integrator processes. Oracle Data Integrator 11.1.1.6 introduces a new feature allowing end users to determine the actual values of variables and sequences that were used during an executed session. Tracking variables and sequences is extremely useful for debugging purposes.
With the variable tracking feature you can also easily determine whether the variable was used in a mapping or an internal operation such as an Evaluate Variable step.

Global Knowledge Modules
ODI 11.1.1.6 introduces Global Knowledge Modules (KMs) allowing specific KMs to be shared across multiple projects. In previous versions of ODI, Knowledge Modules were always specific to a Project and could only be used within the project into which they were imported. Global KMs are listed in the Designer Navigator in the Global Objects accordion.

Enhanced Session Logging
The readability of the execution logs has been improved in this release for Knowledge Modules and Procedure commands. The final code for source and target commands is now available in the Operator Navigator, making it easier to review executions containing several runtime parameters.

Handling Failed Load Plan Enhancements
It is now possible to change the execution status of a failed Load Plan step from Error to Done on the Steps tab of the Load Plan run Editor. This allows this particular Load Plan step to be ignored the next time the Load Plan run is restarted. This is useful, for example, when the error causing this Load Plan step to fail is not possible to fix at the moment. However, you want to execute the rest of the Load Plan regardless of this Load Plan step status. By changing the status to Done, the step will be ignored on the next execution.

Enhanced Variable Handling in Load Plans
Load Plan variables that are not used in a Load Plan can now be hidden to improve the readability of Load Plans.

Smart Export and Import
Exporting and importing Oracle Data Integrator objects between repositories is a common practice when working with multiple environments such as Development, Quality Assurance and Production. The new Smart Export and Import feature guides you through this task and provides advanced code management features.
Smart Export automatically exports an object with all its object dependencies. It is particularly useful when you want to move a consistent lightweight set of objects from one repository to another including only a set of modified objects.
The Smart Export and Import feature is a lightweight and consistent export and import mechanism providing several key features such as:
  • Automatic and customizable object matching rules between the objects to import and the objects already present in the repository
  • A set of actions that can be applied to the object to import when a matching object has been found in the repository
  • Proactive issue detection and resolution that suggests a default working solution for every broken link or conflict detected during the Smart Import
Enterprise Data Quality Integration
With the EnterpriseDataQuality Open Tool it is now possible to invoke an Oracle Enterprise Data Quality (Datanomic) Job in a Package. Developers can design a Data Quality process in Oracle Enterprise Data Quality and invoke it in a Package in ODI along with the ETL steps.
The EnterpriseDataQuality Open Tool is installed using the standard procedure for Open Tools and can be used in a Package or a Procedure, similarly to the tools provided out of the box in Oracle Data Integrator.

Groovy Editor
This release introduces the Groovy editor. The Groovy editor provides a single environment for creating, editing, and executing Groovy scripts within the ODI Studio context. It provides all standard features of a code editor such as syntax highlighting and common code editor commands.

Support of Undo and Redo Operations
It is now possible to undo or redo changes in editors, dialogs, wizards, and in the Property Inspector using the following keyboard shortcuts: CTRL+Z and CTRL+Y.

Autocomplete for Text Fields and Lists
Certain text components and drop down lists in the ODI Studio now support the autocomplete feature, making end users more productive.

Version Numbering for Knowledge Modules
The version numbering of Knowledge Modules improves the information provided to identify the used environment:
  • It is now possible to determine when a KM has been modified and when it is not the original Knowledge Module as released by Oracle.
  • The KM modifications can be tracked by a version number.
  • It is now possible to find out when a KM has been released with an external component such as a jar file or a dll file (This is the case for example for the SAP and Hyperion KMs.)
  • It is posssible to indicate whether a given ODI version is compatible with the KM version.