What's New in ODI 11g? - Part 3: Run-Time Experience
By FX on Aug 31, 2010
Oracle Data Integrator 11gR1 includes a large number of features and enhancements to the 10gR3 release. In this blog series I will try to explain the major directions taken by the product and give a quick overview of these features and enhancements.
For a detailed list of features, the following documentation link can be used as a reference.
There are major areas of changes in this release:
- New Architecture for Enterprise-Scale Deployment
- New Design-Time Experience
- New Run-Time Experience
- Core Enhancements to E-LT and Declarative Design
In this third part, we will focus on an overview of the changes and enhancement targeting specifically the Run-Time Experience.
Better Session Management and Control
In Part 1 I have described the new architecture and how HA could be enabled in this architecture.
In this architecture, components are made highly available and will restart in case of failure; In addition to this, the following new features exist in 11g to make production environments more resilient and easier to manage:
- If an agent looses the connection to his repository and this repository is stored in a HA-enabled database - such as Oracle RAC - a Repository Connection Retry mechanism makes the agent continue his activity, including his running sessions on a different database node.
- If an agent crashes or looses the connection to the repository, crashed sessions no longer remain in running state. A Stale Session management mechanism moves these sessions to an error state.
- Users can force a Kill Immediate on a session. Currently long running database statements are aborted and the session stopped afterward.
- Session Purge with the OdiPurgeLog tool is now possible based on a number of sessions to keep in the log. This tool also supports automated archiving of purged sessions.
Better Errors and Notifications
Oracle Data Integrator now uses the Oracle Logging Framework. Logging in any component can be configured in a single way and provides simple to extremely detailed logging information.
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.
This logging and notification systems comes in addition to the Enhanced Error Messages that provide precise and contextual information, including:
- Component lifecycle Information and errors (startup, shutdown, schedule refresh, etc.)
- Session lifecycle information and errors (incorrect scenario version, load balancing issue, agent not available, etc.)
- Session Tasks/Steps information and errors (source/target not available, interface error).
- Standardized Oracle Data Integrator error codes.
ODI Console unifies in a single web interface all the features previously included in Metadata Navigator, Lightweight Designer and Repository Explorer.
ODI Console becomes the the thin client to:
- Browse Design-Time, Topology and Run-Time Metadata
- Set up and configure a production environment and the topology
- View the Data Lineage and Flow Map for the integration jobs.
- Monitor the run-time activity.
This web interface is redesigned using ADF-Faces components.Figure 1: ODI Console is the thin client for accessing metadata in the repository.
In addition, ODI Console provides the capability to view and purge the content of the error tables created by the data quality check processes in the scenarios.
Fusion Middleware Control Plug-in
Fusion Middleware Control is the console used for monitoring Oracle and third-party components in an enterprise architecture. ODI Provides a plug-in in this console and allows administrators to:
- Monitor the status and metrics of the ODI Components (Repositories, Java EE and Standalone Agents, ODI Console).
- Receive the notifications raised by these components via JMX.
- Drill down into Oracle Data Integrator console
- Start and stop ODI Java EE components
- Monitor/search for session executions
In an enterprise-scale architecture, monitoring from a single place all the architecture components is critical. This plugin makes ODI components manageable along the other components of the Fusion Middleware stack.
The next blog post in this series will focus on the code enhancements made to Declarative Design and E-LT in this release. Stay tuned !
To learn more about the new ODI design-time features, please review the following documents: