My Oracle Support Banner

Troubleshooting the ODI J2EE Agent Configuration Issues (Doc ID 1443453.1)

Last updated on APRIL 06, 2021

Applies to:

Oracle Data Integrator - Version and later
Information in this document applies to any platform.


The purpose of this document is to help Customers and Oracle Data Integrator (ODI) engineers in collecting and analyzing the information susceptible to help troubleshooting the issues with deployed ODI J2EE Agents.

Troubleshooting Steps

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
Troubleshooting Steps
 1. Is ODI Studio connecting to the expected Repositories?
 2. Is the Physical Agent correctly defined in the ODI Topology?
 3. Which users defined in the ODI Security have SUPERVISOR privilege?
 4. Is the J2EE Agent correctly deployed in WLS?
 (a). Deployment, and deployment plan
 Validate the settings inside the .ear deployment file
 Verify the Web application name in the XML deployment plan (if any)
 Verify the overwritings in the XML deployment plan (if any)
 (b). Targets
 Verify the Targets
 5. Is the Coherence cluster properly configured?
 6. Are the ODI Datasources correctly defined in WLS?
 7. Restart the Managed Server in the WLS domain.
 8. Redeploy the ODI J2EE Agent Application.
 9. Verify the Domain and Managed Server log files.
 10. Verify the ODI Agent log file.
 11. Additional references.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.