If you have WAS 8.5.5 and your application is not starting due to major minor version of class files errors on starting, you might be facing the JDK problem.
Websphere 8.5.5. is shipped with 1.6 JDK version( which is vague) but your application might have compiled code in recent version of Java.
So in this case your option is to upgrade to 8.5.5.11 where 1.7.1 and JDK 8 are supported.
Lets get started.
Download the upgrade fix pack from fix central, links below.
http://www-01.ibm.com/support/docview.wss?uid=swg24043005
Download both supplements and the main Websphere 8.5.5.11 fix pack(Around 7 Gb)
Extract in different folders.
Part1 of, both the core fix pack and the supplement will have a repository file which contains meta of the package.
Now its the right time to open your Installation Manager to upgrade the WAS ND installation.
Navigate to the installation manager folder and open IBMIM.exe
Lets break this task in to two parts:
Part 1 – Upgrading WAS Core
Part 2 – Upgrading the supplements.
Part 1 Upgrading WAS Core
Now Go to Preferences and add repository for core.
Click on add repository and navigate to part 1 of the fix pack.
Now click apply and press ok.
Go back to main screen of IM and click update.
Once you click update it will show you a panel about the installed products. Select the WAS server and continue.
Accept the defaults and continue, till the update button is visible on the panel at the bottom.
On clicking update, you might face an error regarding (file not found in native for nd only). This might be due to some wrong mapping in the repository.
Solution
To fix this copy the native folder from the part 2 of the core fix pack and paste it in the part 1 folder, as shown below.
Please note we will have to do the same activity in the supplements update in part 2, we will talk about it.
Now lets restart the update process again.
This time you will be able to pass trough the update step and WAS 8.5.5 core will be upgraded to 8.5.5.11 and now you are ready to use later versions of JAVA.
Part 2 Upgrading the supplements
Now we will be upgrading the supplements and we will add the repository to the preferences page of installation manager and update the packages.
Now we have added the repository path to the preferences of IBM installation manager and we are ready to upgrade the supplements.
This time we will be selecting HTTP server/Plugins and WCT from the panel as shown below.
Please make sure you copy native folder to the part 1 of supplements, else you will find the same error ( file zip not found in native of part 1), also this step is required to be done only due to some bug in the repository else in normal conditions repository fetches the right information accordingly.
Now we are all updated and we are on 8.5.5.11 version with both core and supplements.
Now its time to do the real thing,for which we upgrade the instance – The JDK update.
Download the online repo and plugin the preferences of Installation manager.
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.IBMJAVA.v71
Continue and install the new JAVA, now you should see multiple java in your Web sphere environment.
if you were facing Major/Minor version problem of compiled classes in appliction, read below else move on to next part.
==================================================================
You can download other version if you like, for me 7.1 will work because my problem was with the minor version 5.1.
Check major minor version table in case you are also facing same problem and your application is not starting due to major minor problems.
Nice article on stack overflow, check out here if you face this issue.
==========================================================
Ok lets come back to our original topic, lets enable the new JDK for our WAS nd installation.
Now we will see what all JDK is available via the managesdk.bat command inside the bin folder of AppSrv01
Lets enable jdk 7.1 for our WAS ND profiles (AppSrv01/Dmgr01)
*Make sure Dmgr is up while changing jdk for WAS 8.5.5
> managesdk.bat –enableProfile –profileName AppSrv01 –sdkName XXXX –enableServers
> managesdk.bat –enableProfile –profileName Dmgr01 –sdkName XXXX –enableServers
In case you face the error like
CWLCA0012E: The sdk 1.7XX is not available on node xxxxxNode02
Your node might need a restart , do a startNode.bat and stopNode.bat and try again, as shown in the above picture
This time it will be a success and you should be able to deploy the new application which has JDK 1.7.1 compatible code.
Keep Reading!
Action Item : Share,Recommend & Subscribe !
No comments:
Post a Comment