This document describes the new and enhanced features introduced with Oracle Data Integrator 11g Release 1 (11.1.1).
This chapter includes the following sections:
Oracle Data Integrator 11gR1 (22.214.171.124) introduces the following enhancements:
A core strategy and a key feature of Oracle Fusion Middleware is hot-pluggability. Built for the heterogeneous enterprise, Oracle Fusion Middleware consists of modular component software that runs on a range of popular platforms and interoperates with middleware technologies and business applications from other software vendors such as IBM, Microsoft, and SAP. The hot-pluggability aims to make components deployable and operational in non-Oracle environments and on multiple application servers.
This ODI release introduces the support of IBM WebSphere Application Server (WAS). ODI Agents and datasources can now be deployed on Oracle WebLogic Server (WLS) and IBM WebSphere Application Server (WAS).
Full support for XML Schema constructs by using standard Oracle parser:
New JDBC driver parameter compat_mode to indicate the compatibility with mapping modes such as the XDK XSD parser.
New JDBC driver command WRITEMAPPINGFILE to help understand the relational structure that has been created for the XSD/DTD file. The mapping file contains the element/attribute name to table/table.column name mapping for each element/attribute.
The JDBC command CREATE SCHEMA includes now the compat_mode parameter.
The Standalone Agent now supports the SSL protocol for secure connectivity. New parameters added to specify the Standalone Agent server side transport protocol and to configure the SSL truststore and keystore:
New environment variables in agent.sh/agent.bat scripts
New configuration variables in odiparams.sh/odiparams.bat scripts
Java system properties in odiparam.sh/odiparams.bat scripts
The EDQ Open Tool introduced in ODI 11gR1 PS2 ( 126.96.36.199) to invoke an Oracle Enterprise Data Quality (Datanomic) Job is now available as a standard ODI tool. The OdiEnterpriseDataQuality tool includes a new, optional parameter to connect MBean domains.
Oracle Data Integrator 11gR1 (188.8.131.52) introduces the following enhancements:
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.
Variables and sequences are often used in Oracle Data Integrator processes. Oracle Data Integrator 184.108.40.206 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.
ODI 220.127.116.11 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.
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.
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.
To improve the readability of Load Plans, the Load Plan variables are grouped into two tables to distinguish between scenario variables and other variables.
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
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.
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.
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.
Certain text components and drop down lists in the ODI Studio now support the autocomplete feature, making end users more productive.
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.
Oracle Data Integrator 11gR1 (18.104.22.168) introduces the following enhancements:
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.
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.
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 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 is added to the list of scripting engines supported by Oracle Data Integrator for use in knowledge modules and procedures.
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.
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
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.
A new setTaskName method is available to update at run-time the name of a task.
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.
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
This first release of Oracle Data Integrator introduces a large number of new features, grouped in this section by release themes.
This section includes the following topics:
Release Themes. This section provides the primary themes of this release and associated features.
New Features. This section provides a complete list of the new features for this release.
While the new features of Oracle Data Integrator for this release cover a number of different areas, the most important changes for new and existing customers are:
Oracle Data Integrator now provides several deployment options for lightweight standalone deployments and enhanced architectures for deployments based on cluster-able and fault tolerant application server frameworks. Features in this area include:
Standalone Agent deployment when agents should be deployed on the same hardware where database software is running
Java EE Agent when agents are used in a clustered Java EE configuration
Oracle Data Integrator now provides a set of core features for increasing development productivity and the performance of the integration flows. Features in this area include:
The Oracle Data Integrator User Interface now uses the JDeveloper-based integrated development environment (IDE), and is renamed Oracle Data Integrator Studio.The user interface has been entirely redesigned in this release to improve developer productivity and make advanced features more accessible. This new IDE provides the following key features:
In addition to the entire redesign of the development interface, features have been added to improve the developer's experience and productivity while working in Oracle Data Integrator. Features in this area include:
Quick-Edit to edit interface in a tabular view
Auto fixing errors from the interface editor
Oracle Data Integrator Java API to programmatically manage design and run-time operations.
Features have been added to improve manageability of the Oracle Data Integrator components and sessions. Features in this area include:
Oracle Data Integrator has been improved with features to facilitate problems troubleshooting and fixing. Features in this area include:
New technologies and knowledge modules planned for this release have been continuously delivered during the 10g lifecycle patch sets. In addition, existing knowledge modules and technologies have been enhanced to support new core product features and diagnostics.
Features added in 10g Release 3 patch sets include:
Features added for this release include:
Release 11.1.1 includes many new features. These features are listed below and grouped in the followings component and functional areas:
Oracle Data Integrator runtime agent has been enhanced with the features listed in this section.
The Runtime Agent can now be deployed as a Java EE component within an application server. It benefits in this configuration from the application server layer features such as clustering and connection pooling for large configurations. This Java EE Agent exposes an MBeans interface enabling lifecycle operations (start/stop) from the application server console and metrics that can be used by the application server console to monitor the agent activity and health.
In addition to the Java EE Agent, a Standalone Agent, similar to the one available in previous Oracle Data Integrator releases, is still available. It runs in a simple Java Virtual Machine and can be deployed where needed to perform the integration flows.
Both agent flavors are now always connected to a master repository, and are started with the built-in scheduler service. This scheduler service takes its schedules from all the Work Repositories attached to the connected Master.
Communications with the run-time agents (for example, when sending an execution request to a remote agent) now use standard HTTP protocol. This feature facilitates network management and security for Oracle Data Integrator components in distributed environments.
Oracle Data Integrator components integrate seamlessly with Oracle's Java EE application server.
Oracle Data Integrator provides a wizard to automatically generate templates for deploying Java EE agents in Oracle WebLogic Server. Such a template includes the Java EE Agent and its configuration, and can optionally include the JDBC datasources definitions required for this agent as well as the drivers and libraries files for these datasources to work.
By using the Oracle WebLogic Configuration Wizard, domain administrators can extend their domains or create a new domain for the Oracle Data Integrator Java EE runtime agents.
Java EE Components use JDBC datasources to connect to the repositories as well as to the source and target data servers, and benefit, when deployed in an application server, from the connection pooling feature of their container.
To facilitate the creation of these datasources in the application server, Oracle Data Integrator Studio provides an option to deploy a datasource into a remote Oracle WebLogic application server.
Oracle Data Integrator Java EE components that can be deployed in an application server are provided now with pre-packaged templates for Oracle WebLogic Server. Oracle Data Integrator provides templates for:
Java EE Runtime Agent
Oracle Data Integrator Console
Public Web Service
These templates are used to create a WLS domain for Oracle Data Integrator or extend an existing domain with Oracle Data Integrator components.
Oracle Data Integrator web services support has been enhanced with the features listed in this section.
Oracle Data Integrator Web Services - including the Public Web Service as well as the generated Data Services - now support the market standard Java API for XML Web Services (JAX-WS 2.0). As a consequence, they can be deployed into any web service container that implements this API. The use of the Axis2 stack for these web services is deprecated.
The web services have been reorganized and the following run-time web operations are now part of the run-time agent application:
getVersion - Retrieve agent version. This operation is new in this version.
getSessionStatus - Retrieve the status of a session.
invokeRestartSess - Restart a session.
invokeStartScen - Start a scenario.
The Public Web Service application retains the following operations:
listScenario - List the scenarios.
listContext- List the contexts.
Security in Oracle Data Integrator can be hardened with the enterprise features listed in this section.
Source and target data server passwords, as well as the context passwords, can optionally be stored in an external credential store instead of storing them in an encrypted form in the master repository. This credential store is accessed via the Java Platform Security (JPS) Credential Store Framework (CSF). The password storage method (internal or external with JPS) is defined at repository creation, and can be switched for existing repositories.
With this password storage approach, administrators can choose to rely on a corporate credential store for securing their data server passwords.
Oracle Data Integrator users can be authenticated using an external authentication service. Using Oracle Platform Security Services (OPSS), Oracle Data Integrator users authenticate against an external Enterprise Identity Store (LDAP, Oracle Internet Directory, Active Directory), which contains in a central place enterprise user and passwords.
With this feature, the master repository retains the Oracle Data Integrator-specific privileges and the user names, but passwords rely in a centralized identity store, and authentication always takes place against this external store. The authentication mode (internal or external) is defined at repository creation, and can be switched for existing repositories.
This feature enables Single Sign-On (SSO) for Oracle Data Integrator Console, and seamless authentication integration between Enterprise Manager and Oracle Data Integrator Console.
Oracle Data Integrator is now installed with a default password policy that prevents from setting passwords with a low security level.
When deploying in Oracle WebLogic Server a Java EE component that requires a bootstrap connection to a repository (Java EE Agent, Oracle Data Integrator Console), the configuration of this component contains a Supervisor user login. To enforce a strong security policy this user's password is not stored within the application configuration, but centralized in the WLS Credential Store. The configuration will refer to this centralized store.
Oracle Data Integrator provides new features for an enhanced experience in production.
Error messages raised by Oracle Data Integrator Components and Sessions have been enhanced to provide administrators and production operators with precise information for troubleshooting and fixing the status of the architecture, and debugging the sessions. Enhanced messages cover:
Component lifecycle (startup, shutdown, schedule refresh, etc.)
Session lifecycle (incorrect scenario version, load balancing issue, agent not available, etc.)
Session Tasks/Steps (source/target not available, interface error). Database errors are enriched with information allowing developers or production operators to quickly identify the location and reason for an error.
These error messages are standardized with Oracle Data Integrator error codes.
Oracle Data Integrator components are now using the Oracle Logging Framework. Logging in any component can be configured to meet the requirements of development, test and production environments.
In addition to this logging capability, agent components can now raise status and session information in the form of Java Management Extension (JMX) notifications that propagate to any administration console.
Error tables can now be managed via Oracle Data Integrator Console. Production operators can review the content of the error tables and purge their content selectively.
The OdiPurgeLog tool has been enhanced to support a purge of the log while retaining only a number of sessions in the log. Purged sessions can be automatically archived by the tool before performing the purge.
The Metadata Navigator UI has been replaced with the Oracle Data Integrator Console. This web interface for production operations has been rewritten using the ADF-Faces Ajax Framework for a rich user experience. Using this console, production users can set up an environment, export/import the repositories, manage run-time operations, monitor the sessions, diagnose the errors, browse through design-time artifacts, and generate lineage reports.
This web interface integrates seamlessly with Oracle Fusion Middleware Control Console and allows Fusion Middleware administrators to drill down into the details of Oracle Data Integrator components and sessions.
Oracle Data Integrator provides an extension integrated into the Oracle Fusion Middleware Control Console. The Oracle Data Integrator components can be monitored as a domain via this console and administrators can have a global view of these components along with other Fusion Middleware components from a single administration console.
This extension discovers Oracle Data Integrator components and allows administrators to:
Monitor the status and view the metrics of the master and work repositories, Java EE and Standalone Agents components, and the Oracle Data Integrator Console
Review from a central location the notifications raised by any of these components
Transparently drill down into Oracle Data Integrator console to browse detailed information stored in the repositories
Start and stop Oracle Data Integrator Console and Java EE Agent applications
Monitor session executions and review session statistics attached to any of those components
Search for specific sessions, view a session status, and drill down into the session details in Oracle Data Integrator Console.
Sessions can now be stopped in an immediate mode. This new mode attempts to abort the current operation (for example, SQL statements launched against a database engine) instead of waiting for its completion.
For an enterprise scale deployment, the features enable high available of the Oracle Data Integrator components.
Oracle Data Integrator is now able to detect sessions pending due to an unexpected shutdown of the agent or repository. Such stale session are now managed and pushed to an error state.
The Agent, when connected to a repository based on Oracle RAC technology, can be configured with connection retry logic. If the one of the Oracle RAC nodes supporting sessions for an agent becomes unavailable, the agent is able to retry and continue its session on another node of the Oracle RAC infrastructure.
Clustering is supported for the Java EE agents deployed on a WebLogic Server. Clustering includes schedule porting on a different cluster node. Unrecoverable running sessions are automatically moved to an error state.
Standalone agent can be now made highly available using Oracle Process Manager and Notification Server (OPMN). Scripts are provided to configure OPMN to protect standalone agents against failure.
Integration interface design and performance are enhanced with the following features.
Oracle Data Integrator now supports partitioning features of the data servers. Partitions can be reverse-engineered using RKMs or manually created in models. When designing an interface, it is possible to define the partition to address on the sources and target datastores. Oracle Data Integrator code generation handles the partition usage syntax for each technology that supports this feature.
A wizard is available in the interface editor to create lookups using a source as the driving table and a model or target datastore as the driving table. These lookups now appear as a compact graphical object in the Sources diagram of the interface. The user can choose how the lookup is generated: as a Left Outer Join in the FROM clause or as an expression in the SELECT clause (in-memory lookup with nested loop). This second syntax is sometimes more efficient on small lookup tables.
This feature simplifies the design and readability of interfaces using lookups, and allows for optimized code for executing lookups.
This major enhancement introduces the notion of dataset in interfaces. A dataset represents the data flow coming from a group of joined and filtered source datastores. Each dataset includes the target mappings for this group of sources. Several datasets can be merged into the interface target datastore using set-based operators such as Union and Intersect.
This feature accelerates the interface design and reduces the number of interfaces needed to merge several data flows into the same target datastore.
When using a temporary interface as a source or a lookup table in another interface, you can choose not to persist the target of the temporary interface, and generate instead a Derived Select (sub-select) statement corresponding to the loading of the temporary datastore. Consequently, the temporary interface no longer needs to be executed to load the temporary datastore. The code generated for the sub-select is either a default generated code, or a customized syntax defined in an IKM.
This feature eliminates the need for complex packages handling temporary interfaces and simplifies the execution of cascades of temporary interfaces.
Oracle Data Integrator now provides support for a new type of sequence that directly maps to database-defined sequences. When created, these can be picked from a list retrieved from the database. Native Sequences are used as regular Oracle Data Integrator sequences, and the code generation automatically handles technology-specific syntax for sequences.
This feature simplifies the use of native sequences in all expressions, and enables cross references when using such sequences.
Oracle Data Integrator now provides support for the Natural join, defined at technology level. This join does not require any join expression to be specified, and is handled by the engine that processes it. This engine matches automatically columns with the same name.
When creating joins or filters on source tables, it is possible to have Oracle Data Integrator automatically generate temporary indexes for optimizing the execution of these joins or filters. The user selects the type of index that needs to be created in the list of index types for the technology. Knowledge modules automatically generate the code for handling indexes creation before executing the join and filters as well as deletion after usage.
This feature provides automated optimization of the joins and filters execution, and enables better performances for integration interfaces.
The interface editor, used to create the integration interfaces, has been entirely redesigned to use the JDeveloper diagramming framework.
The advantages of this new diagram include:
Improved look and feel and better user experience
Support for graphical options on diagram objects. For example, compact and expanded view can be used for better readability.
Thumbnail and zoom in/out is supported on the sources and flow diagram to navigate large diagrams.
Multiple source columns can be dropped directly onto the target datastore for faster mapping.
Target mapping table is improved. Mapping properties (Position, Indicator, Name and Mapping expression) can be displayed selectively and sorted.
Sources, targets, filters, joins can be selected and edited directly in the flow diagram.
The new interface editor includes a new Quick-Edit tab to edit the interface diagram faster. Quick-Edit displays these components in a tabular form, supports mass-updates and intuitive keyboard navigation.
When saving an interface or clicking the error button from the interface editor toolbar, a list of all the design errors in the interface is displayed with meaningful messages and tips. Automated fixes are suggested and can be applied with a single click.
When performing an execution of design-time objects from the Oracle Data Integrator Studio (for example, when running an interface, a procedure, a package or a customized reverse-engineering process), it is possible to make a code simulation instead of a full execution.
Code simulation displays a session simulation report. This report includes complete session, step, and task information and contains the full generated code. The session simulation report can be reviewed and saved in XML or HTML format.
With this features Oracle Data Integrator developers can easily review the generated code for troubleshooting, debugging, optimization purposes, and save this generated code for documentation or archive purposes.
When a model is created the reverse-engineering context is automatically set to the default context, instead of having to select it manually. In addition, when performing a selective reverse-engineering, the system tables are now hidden from the display.
When generating a scenario or a group of scenarios from the Studio or using a tool, the naming convention that is used for naming the scenario can be defined in a pattern (using the object name, folder path or project name) using the Scenario Naming Convention user parameter.
Object names have been extended to support long database object names (128 characters) and repository object labels (400 characters).
Oracle Data Integrator provides a Java API for managing run-time and design time artifacts. Using this API, Java developers can embed Oracle Data Integrator in their product and can drive integration process creation from their own user interface.
Oracle Data Integrator provides a new IDE called the Studio, based on JDeveloper. This component includes the following features:
The new Oracle Data Integrator studio is used as a replacement for all Oracle Data Integrator modules (Designer, Topology, Operator and Security Manager). All the features of these modules now appear as Navigators within the Oracle Data Integrator Studio window.
This new Navigator organization provides the following features:
Navigators can be docked/undocked and displayed/hidden using the View menu. These Navigators allow access to the former module-specific actions from their Navigator toolbar menu (for example, the export/import master repository operations in the Topology Navigator)
Accordions group the tree views that appear in the Navigators (for example the Project and Models accordions in the Designer Navigator). Accordions that are not frequently used can be minimized into the lower section of the Navigator to allow more room for the other tree views. Accordions allow access to the tree view-specific actions from their toolbar menu (for example, import project from the Project Accordion in the Designer Navigator).
Tree Views objects are provided with context menus and markers the same way as in Oracle Data Integrator 10g. Tree view objects can be dragged and dropped within a tree view or across tree views for defining the security policies. Double clicking an object opens by default the corresponding Object Editor.
Context Menus have been reorganized into groups with separators and normalized across the interface.
This feature provides a single user interface from which the user can perform all the tasks in a project lifecycle. It also provides a better productivity for the user.
The look and feel of Oracle Data Integrator has been enhanced with the use of the JDeveloper base IDE. This new look and feel is customizable with the Preferences menu option. Icons are being redesigned in a new, trendy style to enhance the overall visual appeal of Oracle Data Integrator
All object editors in Oracle Data Integrator have been redesigned for better usability.
Main changes include:
Tabs are organized as finger tabs on the left hand-side of the editor. Complex editors (as for example Interface or Package Editors) have also tabs appearing in the bottom of the editor.
Fields have been grouped under headers. These field groups implement an expand/collapse behavior.
Fields and labels have been organized in a standard way for all editors for a better readability of the editors.
Text Buttons in the editors are transformed into hyperlinks, and all buttons appearing in editors have been redesigned.
Knowledge Modules, Actions and Procedure editors have been redesigned in order to edit the Lines directly from the main editor instead of opening a separate editor.
The windows, editors and navigators in the Oracle Data Integrator Studio benefit from the following JDeveloper IDE features:
Full Docking Support: All windows, editors and navigators can now be docked and undocked intuitively. The visual feedback provided when repositioning editor windows and dockable windows has been improved. You now see an outline shape of where the window will be placed when the mouse is released. You can also now reorder the document tabs using drag and drop.
Fast maximize and restore: To quickly maximize a dockable window or the editor area, double-click on the title bar of the window you want to maximize. To restore the window to its previous dimensions, double-click again on the title bar.
Title bars as tabs: The tab for a dockable window (when tabbed with another dockable window) is now also the title bar. This makes more effective use of the space on the screen. Reposition a window by dragging its tab. Some additional related enhancements include a new context menu from the gray background area behind the tab, change in terminology from "auto-hide" and "show" to "minimize" and "restore", ability to minimize a set of tabbed windows with a single click, and toggling the display of a minimized window by clicking on its button.
Object edition has been enhanced in the Oracle Data Integrator Studio with improved document management. This includes:
Save and close multiple editors: You can easily save all your work with a single click using the File > Save All option and close all opened editors similarly. You can also close all the editors but the current one.
Forward and back buttons: Now you can easily return to a previously visited document with the convenient browser-style forward and back buttons on the main toolbar. These buttons maintain a history, so you can drop down the back or forward button to get a list of the documents and edit locations you have visited. Alt+Left and Alt+Right activate the back and forward buttons.
Quick document switching: Switching between editors and navigators is also possible. Now when you press Ctrl+Tab or Ctrl+F6, you can choose which document you want to switch from a list ordered by the most recently used. You can use the same technique to switch between open dockable windows by first placing focus in a dockable window, then pressing Ctrl+Tab or Ctrl+F6.
Oracle Data Integrator introduces intuitive new features that improve usability:
Help Center/Welcome Page: The Welcome page has been transformed into the Help Center, redesigned to provide the user with quick access to help topics and common tasks, as well as links to useful Oracle resources.
New On-Line Help: The online help has been entirely re-written for supporting the new user interface.
Help bookmarks: The Help window has a tab labeled Favorites. While browsing the help, you can click on the Add to Favorites button to add the document to this tab.
Export/import is enhanced in this new release with the following features:
After objects have been imported, an import report displays the objects that have been imported or deleted in the target repository. In addition, missing objects referenced by the imported objects are indicated as missing references, and missing references fixed by the import are also indicated. Import reports can be saved in XML or HTML format
With this feature, importing objects becomes a very transparent operation as all changes can be identified and archived.
When importing objects across repositories, the following cases have been taken into account to avoid the risks of import errors and repository corruption:
The import in Synonym mode that may result in overwriting a text (for example, a mapping expression) with a text from a different origin (for example, a filter expression) is now verified and not allowed.
It is not allowed to import objects from two repositories with the same repository identifier into a target repository. This avoids object collision and corruption.
When attaching a work repository that contains objects imported from another repository, a warning is raised to the user.
In addition, import of objects that reference non-existing objects now create missing references, identified in the import report. Such references can be resolved by importing the missing object.
It is now possible to change the identifier of a master or work repository after its creation. This operation automatically updates the internal identifier of the objects created in this repository to match the new identifier.
This feature facilitates configuration management and fixing import/export situations when multiple repositories have been created with the same identifier.
The following improved and new knowledge modules have been delivered in 10gR3 patch sets and are available in this release.
Oracle Data Integrator uses Oracle GoldenGate to replicate online data from a source to a staging database. A Journalizing KM manages the Oracle Data Integrator CDC infrastructure and automatically generates the configuration for Oracle GoldenGate.
Oracle Data Integrator Knowledge Modules for E-Business Suite provide comprehensive, bidirectional connectivity between Oracle Data Integrator and E-Business Suite, which enables you to extract and load data. The Knowledge Modules support all modules of E-Business Suite and provide bidirectional connectivity through EBS objects tables/views and interface tables.
The Oracle Data Integrator Knowledge Modules for Oracle OLAP provide integration and connectivity between Oracle Data Integrator and Oracle OLAP cubes. The Oracle Data Integrator KMs for Oracle OLAP support reverse-engineering of Oracle OLAP data structures (all tables used by a ROLAP or a MOLAP cube) and data integration in an Oracle Analytical Workspace target in incremental update mode.
The Oracle Data Integrator Knowledge Modules for PeopleSoft provide integration and connectivity between Oracle Data Integrator and the PeopleSoft platform. These KMs enable Data-level integration for PeopleSoft and support reverse-engineering of PeopleSoft data structures (Business Objects, tables, views, columns, keys, and foreign keys) and data extraction from PeopleSoft.
The Oracle Data Integrator Siebel Knowledge Modules support reverse-engineering Siebel data structures (Business Components and Business Objects) and Enterprise Integration Manager (EIM) tables, data extraction from Siebel using data-level integration and data extraction and integration with Siebel using the EIM tables
The Oracle Data Integrator Knowledge Modules for JDE EnterpriseOne provide connectivity and integration of the JDE EnterpriseOne platform with any database application through Oracle Data Integrator. These KM support reverse-engineering of JDE EnterpriseOne data structures, data extraction from JDE EnterpriseOne (Direct Database Integration) and integration through the Z-tables to an JDE Application (Interface Table Integration)
The Oracle Data Integrator CDC Knowledge Module provides integration from Oracle Changed Data Capture Adapters/Attunity Streams Staging Areas via a JDBC interface. This KM reads changed data, loads this data into a staging area and handles the Oracle Changed Data Capture Adapters/Attunity Streams context to ensure consistent consumption of the changes read.
Knowledge Modules and technologies have been added for integrating the Hyperion technologies using Oracle Data Integrator.
These KMs support the following Hyperion products:
Hyperion Financial Management, to load and extract metadata and data.
Hyperion Planning, to load metadata and data into Hyperion Planning.
Hyperion Essbase, to load and extract Essbase metadata and data.
Knowledge modules supporting row-by-row loading (LKM SQL to SQL (row by row)) and integration (IKM SQL Incremental Update (row by row)) have been introduced for debugging purposes. These KMs allow logging of each row operation performed by the KM.
Teradata knowledge modules have been enhanced for Teradata to enable best performances.
This includes the following features:
Support for Teradata Utilities (TTU).
Support for customized Primary Indexes (PI) for temporary tables.
Support for named pipes when using TTU.
Optimized Management of Temporary tables.
The SAP ERP Adapter allows extraction of data from SAP ERP systems. The Oracle Data Integrator SAP ABAP Knowledge Modules included in this adapter provide integration from SAP ERP systems using SAP JCo libraries and generated ABAP programs.
The SAP BW Adapter allows extraction of data from SAP BW systems. The Oracle Data Integrator SAP BW Knowledge Modules included in this adapter provide integration from SAP BW using SAP JCo libraries and generated ABAP programs. This adapter supports ODS, Info Objects, Info Cubes, Open Hub and Delta Extraction.
The following knowledge modules enhancements are new to this release.
Knowledge modules have been enhanced to support the core features added in this version of Oracle Data Integrator. The following KMs have been updated to support these features:
Support for Partitioning: Oracle RKM reverse-engineers partitions.
Datasets and Set-Based Operators: All IKMs have been updated to support this feature.
Automatic Temporary Index Management: Oracle and Teradata IKMs and LKMs have been updated to support this feature.
Oracle Data Integrator provides the ability to reverse-engineer View Objects that are exposed in Oracle Business Intelligence Enterprise Edition (OBI-EE) physical layer. These objects can be used as sources of integration interfaces.
A new Integration KM for Oracle allows populating several target tables from a single source, reading the data only once. It uses the INSERT ALL statement.
A new Teradata Integration KM provides support for Teradata Multi-Statements, allowing integration of several flows in parallel.