This content has been marked as final. Show 4 replies
You should not install jdev into an existing WLS home. Check https://blogs.oracle.com/onesizedoesntfitall/entry/solution_for_installing_the_adf if you only want to install the adf runtime libraries onto the existing wls.1 person found this helpful
Is there a jDeveloper installation that is coupled with wls 10.3.6?
I also tried jDeveloper 188.8.131.52 but its the same.
This seems to be a bug in 184.108.40.206.
Try to install jdev 220.127.116.11.0 in different Middleware home.
May be you have tried to install jdev into the same middleware home where you installed the stand alone wls 10.3.6?
Install JDev into a new middleware home,then you should not see this error.
There is no Jdeveloper installation for 18.104.22.168 coupled with WLS 10.3.6. It comes with WLS 10.3.5 only . You will have to install WLS 10.3.6 separately if you need it.
Quoting Chris Muir from https://blogs.oracle.com/onesizedoesntfitall/entry/adf_runtimes_vs_wls_versions
Note with the release of JDeveloper 22.214.171.124.0 there is a subtle change in the ADF Runtime to WLS version pairing. The latest ADF Runtimes 126.96.36.199.0 can run against WLS 10.3.6 and 10.3.5.
This is the first time in the 11.1.1.X branch we've seen a version run on two versions of WLS.
As such if you have a 10.3.5 WLS server or have just installed WLS 10.3.6 you can also happily install the 188.8.131.52.0 ADF Runtimes on either.
Customers need to be careful though as this does not imply the opposite.For your issue see -
If you install WLS 10.3.6, only the ADF Runtimes 184.108.40.206.0 are certified, the 220.127.116.11.0 ADF Runtimes are not (though the 18.104.22.168.0 ADF Runtimes are still of course certified against WLS 10.3.5).
Not able to install Jedeveloper on SOA Suite 11g 22.214.171.124
Tip - "Make sure you install JDeveloper and WLS+SOA in totally Different middleware homes (different folders)"Edited by: Sudipto Desmukh on May 17, 2012 2:21 PM