Runtime Agent Oracle Data Integrator runtime agent has been enhanced with the features listed in this

section. Java EE Agent 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. Standalone Agent 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. Connected Scheduler 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. HTTP Protocol for Component Communication 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 WebLogic Server Integration Oracle Data Integrator components integrate seamlessly with Oracles Java EE application server. Java EE Agent Template Generation 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. Automatic Datasource Creation for WebLogic Server 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. Pre-Packaged WebLogic Server Templates for Java EE Components 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.

Web Services Oracle Data Integrator web services support has been enhanced with the features listed in this section. JAX-WS Support for Web Services 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. Web Services Changes and Reorganization 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.

Advanced Security Capabilities Security in Oracle Data Integrator can be hardened with the enterprise features listed in this section. External Password Storage 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. External Authentication and SSO 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. Default Password Policy Oracle Data Integrator is now installed with a default password policy that prevents from setting passwords with a low security level. Java EE Components Passwords in Credential Store 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 users password is not stored within the application configuration, but centralized in the WLS Credential Store. The configuration will refer to this centralized store.

Production and Monitoring Oracle Data Integrator provides new features for an enhanced experience in production. Enhanced Error Messages 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.

Enhanced Notifications and Logging 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 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. Purge Log on Session Count 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. New Oracle Data Integrator Console 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 Fusion Middleware Control Console Integration 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.

Kill Sessions Immediate 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. High Availability For an enterprise scale deployment, the features enable high available of the Oracle Data Integrator components. Stale Session Detection and Management 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. Repository Connection Retry

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. Support for WLS Clustering 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. OPMN Integration 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. Improved Integration Design Integration interface design and performance are enhanced with the following features. Partitioning 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. Lookups 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

Datasets and Set-Based Operators 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. Export/Import Export/import is enhanced in this new release with the following features: Import Report 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. Repository Corruption Prevention 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. Repository Renumbering 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.