Primary Note for ODI High Availability Configurations
(Doc ID 424105.1)
Last updated on APRIL 05, 2021
Applies to:Oracle Data Integrator - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Not every application can run in a high-availability cluster environment, and the necessary design decisions need to be made early in the software design phase. In order to run in a high-availability cluster environment, an application must satisfy at least the following technical requirements:
- There must be an easy way to start, stop, and check the status of the application.
- The application must be able to use shared storage (NAS/SAN).
- The application must store its state on non-volatile shared storage and be able to restart on another node at the last state before failure (using the saved state from the shared storage).
- Application must not corrupt data if it crashes or restarts from the saved state.
ODI 11g and ODI 12c provide a complete set of components for designing, deploying and managing data integration processes. Data integration processes move and transform data from source data servers to target data servers, using an Extract-Load-Transform approach that eliminates the need for a transformation engine by delegating all transformations to the source and target data servers.
This document is intended to define what high-availability (HA) for Oracle Data Integrator (ODI) means, and how this could be configured.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. High availability for J2EE Agents|
|2. High availability for the database holding the ODI Repositories|