Oracle Data Integrator (ODI) 12.2.1.4.0 — End-to-End Installation & Configuration Guide on Oracle Linux 8
This guide walks through a
complete Oracle Data Integrator (ODI) 12.2.1.4.0 deployment on Oracle Linux 8 —
from environment prerequisites through product installation, master/work
repository creation, ODI Studio connectivity, and configuration of a Standalone
Agent domain. It is written from hands-on implementation experience and is
shared for engineers and architects preparing similar Oracle Fusion Middleware
deployments.
1. Prerequisites
Before launching the installer,
the target Oracle Linux 8 host was validated against the following minimum
hardware, kernel, and software requirements.
|
Category |
Requirement |
|
Operating System |
Oracle Linux 8 (x86-64) |
|
RAM |
●
Minimum physical RAM: 4
GB ●
Minimum available memory
(RAM + SWAP): 8 GB |
|
Disk Space |
●
FMW Infrastructure: 2.2
GB ●
/tmp: minimum 300 MB free ●
Additional temporary
space for installer extraction |
|
JDK |
●
64-bit certified JDK 8 ●
Documented/tested with
JDK 1.8.0_211 |
|
Kernel Parameter |
kernel.shmmax = 4294967295 |
|
Required RPMs |
●
binutils ●
gcc ●
gcc-c++ ●
glibc ●
glibc-devel ●
libaio ●
libaio-devel ●
libgcc ●
libstdc++ ●
libstdc++-devel ●
libnsl ●
sysstat ●
motif ●
motif-devel ●
redhat-lsb ●
redhat-lsb-core ●
openssl ●
make ●
xorg-x11-utils |
Note:
This guide assumes the Oracle Database
used to host the ODI Master/Work repositories is already installed and
reachable, and that JDK 8 is already installed on the target host. Steps to
install the database and JDK are not covered here.
Java Runtime Verification
With the required JDK installed,
the Java version was verified on the target host prior to installation:
Figure 1 — Verifying the installed JDK
version
2. ODI 12.2.1.4.0
Installation on Oracle Linux 8
The Fusion Middleware
Infrastructure installer for ODI was launched from the command line as the
oracle OS user:
[oracle@odi12c ODI12c]$ java
-jar fmw_12.2.1.4.0_odi.jar
Launcher
log file is
/tmp/OraInstall2026-09-21_01-39-41AM/launcher2026-09-21_01-39-41AM.log.
Extracting
the installer . . . . . . . . . . . . . . . . . . Done
Checking
if CPU speed is above 300 MHz. Actual
1608.002 MHz Passed
Checking
monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Checking
swap space: must be greater than 512 MB.
Actual 6019 MB Passed
Checking
if this platform requires a 64-bit JVM.
Actual 64 Passed (64-bit not
required)
Checking
temp space: must be greater than 300 MB.
Actual 62390 MB Passed
Preparing
to launch the Oracle Universal Installer from
/tmp/OraInstall2026-09-21_01-39-41AM
Log:
/tmp/OraInstall2026-09-21_01-39-41AM/install2026-09-21_01-39-41AM.log
The graphical installer then
guided the setup through its standard eight-step flow:
Figure 2 — Installer step: Welcome
Figure 3 — Installer step: Auto Updates
Figure 4 — Installer step: Installation
Location
Figure 5 — Installer step: Installation
Type
Figure 6 — Installer step: Prerequisite
Checks
Figure 7 — Installer step: Installation
Summary
Figure 8 — Installer step: Installation
Progress
Figure 9 — Installer step: Installation
Complete
3. ODI Master and
Work Repository Creation
With the binaries installed, the
Repository Creation Utility (RCU) was used to create the ODI Master and Work
repository schemas in the target database.
Figure 10 — Launching the Repository
Creation Utility (RCU)
The RCU wizard was completed
end-to-end — connecting to the database, selecting the ODI schema components,
setting schema passwords, mapping tablespaces, and confirming schema creation:
Figure 11 — Repository Creation Utility,
step 1
Figure 12 — Repository Creation Utility,
step 2
Figure 13 — Repository Creation Utility,
step 3
Figure 14 — Repository Creation Utility,
step 4
Figure 15 — Repository Creation Utility,
step 5
Figure 16 — Repository Creation Utility,
step 6
Figure 17 — Repository Creation Utility,
step 7
Figure 18 — Repository Creation Utility,
step 8
Figure 19 — Repository Creation Utility,
step 9
Figure 20 — Repository Creation Utility,
step 10
Figure 21 — Repository Creation Utility,
step 11
Figure 22 — Repository Creation Utility,
step 12
4. Connecting ODI
Studio to the Repository
Once the schemas were in place,
ODI Studio was configured with a new repository login pointing to the Master
Repository connection and the Work Repository (WORKREP):
Figure 23 — ODI Studio repository
connection details
5. Creating a
Standalone Agent
A Standalone Agent was created
and registered against the Work Repository to handle scenario and load-plan
execution outside of the WebLogic-managed environment:
Figure 24 — Standalone Agent creation
Figure 25 — Standalone Agent
configuration details
Figure 26 — Standalone Agent creation
confirmation
6. Creating the
Domain for the Standalone Agent
The WebLogic domain
configuration wizard was then run to build the domain that hosts the Standalone
Agent, walking through server, node manager, and startup configuration:
Figure 27 — Launching the Configuration
Wizard
Figure 28 — Domain Configuration Wizard,
step 1
Figure 29 — Domain Configuration Wizard,
step 2
Figure 30 — Domain Configuration Wizard,
step 3
Figure 31 — Domain Configuration Wizard,
step 4
Figure 32 — Domain Configuration Wizard,
step 5
Figure 33 — Domain Configuration Wizard,
step 6
Figure 34 — Domain Configuration Wizard,
step 7
Figure 35 — Domain Configuration Wizard,
step 8
Figure 36 — Domain Configuration Wizard,
step 9
Figure 37 — Domain Configuration Wizard,
step 10
Figure 38 — Domain Configuration Wizard,
step 11
Figure 39 — Domain Configuration Wizard,
step 12
7. Starting,
Verifying, and Stopping the Agent
Standalone Agent Startup / Shutdown Scripts
Figure 40 — Standalone Agent startup and
shutdown scripts
Verifying the Agent After Startup
Figure 41 — Confirming the agent is up
and registered
Stopping the Agent
Figure 42 — Stopping the Standalone Agent
Comments
Post a Comment