A couple of weeks ago Oracle released JDeveloper 18.104.22.168.0 with many new features we all waited for.
Great news … but wait, what to do with your running test, QS and production environment. As usual I assumed a new WLS to use with the new JDev. However, this time Oracle did not ship a new WLS but olny a patch (patch 12611176), which is only available if you have a valid support contract. This patch upgrades an existing WLS 10.3.5 with the new ADF Runtime 22.214.171.124.0.
We are using Windows 7 64bit for our development PC and a Linux box for the WLS. Currently we are on jdev 126.96.36.199.0 and WLS 10.3.4. The task to do is the upgrade to 188.8.131.52.0. Here are the steps:
- update WLS 10.3.4 to WLS 10.3.5 (or do a fresh install if you like, doesn’t take more time). This is necessary as the patch requires WLS 10.3.5
- install ADF Runtime 184.108.40.206.0 on the WLS 10.3.5
- check the WLS 10.3.5 installation using JDev 220.127.116.11.0, check if Enterprise Manager (EM) is running
- load patch 12611176 from mos and read the instructions how to apply the patch
- apply the patch
- test the patch installation using JDev 18.104.22.168.0, check if EM is running
This blog entry deals manly with the last two point in the list. The other points are documented well and it shouldn’t be a problem to do them.
After loading the patch and reading the instructions from the patch file, I installed the patch. This all was pretty straight forward, installation was OK.
After starting the WLS I noticed that the EM was not running. A look into the AdminSever log showed
A close look at the stacktrace shows a ClassNotFoundException. A search for the missing class reveals that it’s from the A JSF2.0 library
This clearly suggests that the new ADF runtime libs are not present in the WLS 10.3.5. Well, John Stegeman mentioned in a twitter entry that he too had the problem that the EM did not start after upgrading to 22.214.171.124.0 and filed a SR for this (this resulted in Bug 12691349). At the time I testes this the bug was not jet published. So I tried many different ways to install the patch and get EM working which all resulted in the above stacktrace:
- update WLS 10.3.4 to WLS 10.3.5; install ADF Runtime 126.96.36.199.5 with EM installed; install patch
- update WLS 10.3.4 to WLS 10.3.5; install ADF Runtime 188.8.131.52.5 without EM installed; install patch; install EM
- Fresh install of WLS 10.3.5; install ADF Runtime 184.108.40.206.5 with EM installed; install patch
- Fresh install of WLS 10.3.5; install ADF Runtime 220.127.116.11.5 without EM installed; install patch; install EM
After rereading all available information about how to apply the patch again and the now available bug on MOS, I noticed one difference. The ‘README.TXT’ for the patch, after which I applied the patch, did not mention the need of executing a wlst command ‘upgradeADF’. The bug on MOS stated calling the ‘upgradeADF’ command as a possible cause of the bug.
The information about the command is only given in the ‘Release Notes for 18.104.22.168.0’ in the ‘Deployment’ section.
In the end I used the following method: fresh install of WLS 10.3.5; install ADF Runtime 22.214.171.124.5 with EM installed; install patch
OK, so lets execute the ‘upgradeADF’ command. Here you have to be careful which wlst installation you use for the command.
The WLS server has it’s own wlst command interpreter installed at ‘$MW_HOME/wlserver_10.3/common/bin/wlst.sh’ whereas the patch installed a second on at ‘$MW_HOME/oracel_common/common/bin/wlst.sh’.
Using the first will throw errors like you see in the next picture:
After running the wlst command ‘upgradeADF’ from the correct path ‘$MW_HOME/oracel_common/common/bin/wlst.sh’ and restarting all servers the result look like:
As you can see the EM is up and running. Note also that two JSF versions are running (1.2 and 2.0).
It looks like the bug John posted is dependent on the environment, as he uses a WIN 7 64bit installation whereas I’m using a Linux box. Still I would like Oracle to make clear in the patch documentation ‘README.TXT’ that you have to run ‘upgradeADF’ from the right location to get the patch installed properly.