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