Support For T2P Where JDeveloper Is Installed Into The Same MW_HOME As Other Fusion Middleware Components
(Doc ID 1617840.1)
Last updated on MARCH 20, 2020
Applies to:Oracle Fusion Middleware - Version 184.108.40.206.0 to 220.127.116.11.0 [Release Oracle11g]
Information in this document applies to any platform.
Determine if T2P is supported for MW_HOMEs where JDeveloper is installed with other Fusion Middleware (FMW) components such as (SOA, WebCenter Suite, PFRD etc.).
See Bug 11818179 : INVENTORY IS CORRUPTED WHEN JDEVELOPER AND WEBCENTER INSTALLED IN SAME HOME
See Note 1435962.1 JDeveloper/ADF 18.104.22.168, 22.214.171.124 and WebLogic Server 10.3.6 Setup
Depending on what you want to do with the JDeveloper installer and target WebLogic Server, you have to take the following considerations and/or actions:
|If want to install...||On top of...||You can...|
|JDeveloper 126.96.36.199, 188.8.131.52||WebLogic Server 10.3.5||Use:
- Same Middleware home.
- A new one.
|JDeveloper 184.108.40.206, 220.127.116.11||WebLogic Server 10.3.6||Use a new Middleware home.|
|ADF 18.104.22.168, 22.214.171.124||WebLogic Server 10.3.5||Use:
- JDeveloper installer.
- ADR installer.
|ADF 126.96.36.199, 188.8.131.52||WebLogic Server 10.3.6||Use ADR installer.|
Running T2P in an Environment which has both Jdeveloper and other FMW Components can result in errors such as:
This occurs because JDeveloper is installed in the same MW_HOME as other components and is not supported.
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