Since JDev 126.96.36.199.0 is out we have to think about where to deploy the apps to which are developed with the new version. Bad new is, that you can’t use existing WLS 10.3.2 and just delpoy application compiled or developed with the new JDev 188.8.131.52.0 version. Good news is, that you don’t have to setup a whole new WLS 10.3.3, at least if you have a valid support contract.
Log in to MOS and download the upgrade installer for WLS 10.3.3 (from the patch and update section) and the ‘Oracle Application Development Runtime 11g Patch Set 2’ (from E-Delivery)
In this short post I’ll just describe the ease routine of updating an existing WLS 10.3.2 :
- remove all your applications running on WLS 10.3.2 (first stop them, then delete them)
- stop WLS 10.3.2
- make a backup of all the files in WLS you have changed. The upgrade process does this for only a barely minimum of files.
- run the upgrade installer for WLS 10.3.3: this is just pointing to the existing ‘Middleware’ folder (the folder you installed the WLS 10.3.2 to) and let the installer do the rest of the work
- run the ADF runtime installer patch to 184.108.40.206.0: this is patch installer, so you need to have ADF 220.127.116.11.0 installed, otherwise you’ll get an error. The only thing to do is to point to an existing domain in the now upgraded WLS.
- start WLS now 10.3.3
- deploy your apps (compiled with JDev 18.104.22.168.0) again
That all you need to do. For more complex scenarios like clusters and/or WLS installation which have been adopted to special needs you my have to do some more work. This is all well documented in the README.TXT file you get together with the upgrade installer.