SAPJVM 4.1 Switch Procedure Including Screenshots
SAP JVM 4.1 Switch Procedure
Purpose
The purpose of writing this document is to provide screen by screen procedure of the sapinst tool involved in the SAPJVM switch.
Why is SAPJVM Required?
Since 1st of October 2012, SAP JVM 4 is the only supported JDK for SAP Web AS 6.40 and SAP Netweaver 7.0 systems. JDKs from other vendors are not supported anymore. Please refer to notes Note 1495160 and Note 1708967 for more information.
Downloading the Standard Installation Guide
You can download the standard installation guide for your operating system from the http://service.sap.com/instguides under SAP JVM Switch Tool.
Please go through the installation guide before performing the SAPJVM switch.
Important Notes:
1665953 – SAP JVM Switch Tool Composite Note
1555341 – Downloading SAP JVM Switch Tool and SAPJVM 4
1367498 – SAP JVM installation prerequisites
1603093 – SAP JVM 4.1 parameters NetWeaver 2004 and 7.0
Downloading the required Software:
You can find the current download path in Note 1555341 . Please access this note for any latest changes.
SAPJVM Switch Tool:
Support Packages and Patches -> My Company’s Application Components -> Complimentary Software -> SAP JVM 4.1 Switch Tool
SAPJVMSWITCH<version>.SAR
SAPJVM 4.1 :
Support Packages and Patches -> My Company’s Application Components -> Complimentary Software -> SAPJVM 4.1
SAPJVM<version>.SAR
Performing the SAPJVM switching:
Perform the below steps in every application server Instance host of your system:
- Make a new directory in the local filesystem of the host of SAP instance and put the two SAR files SAPJVMSWITCH<version>.SAR and SAPJVM<version>.SAR
- Extract the SAPJVMSWITCH<version>.SAR using SAPCAR and do not unpack the SAPJVM<version>.SAR
- Start the sapinst that is extracted from the SAPJVMSWITCH<version>.SAR file and follow the below steps:
Enter the password of <sid>adm user:
Enter the path of SAPJVM software archive:
Please go through the note 1603093 before proceeding with the next step for the parameters that is changed as of SAP JVM 4.1
Server ID parameters:
Dispatcher ID parameters:
Server Bootstrap Parameters:
Dispatcher Bootstrap Parameters:
Instance Bootstrap parameters:
Check the box below
Adapt the Instance Profiles
1. Set the parameter jstartup/vm/home=<drive>:\usr\sap\<SAPSID>\<Instance>\exe\sapjvm_4.
2. Add the parameter SAPJVM_VERSION = <version of the SAPJVM4>
3. Restart the SAP instance
Verifying the SAP JVM 4.1 Switch
Go to http://<hostname>:5<Instance number>00/SystemInfo and you can see the JVM version as shown below:
Well documented and detailed explaination of requirements and execution steps for JVM upgrade. If possible, please include backup plan and steps, in case this upgrade fails, in your next version. Thanks.
Thanks for the feedback and suggestion Ankit. I will include the backout plan.
Good document to understand the need of JVM upgrade in current SAP environment.
Thanks for the feedback Amber.
The Document is having all the neccessary document needed for the JVM Switch. Since it is mandate to go for a JVM installation, this document will be of great help.
Good Work Pankaj..I am sure there is already ine document for JVM...http://scn.sap.com/community/netweaver-administrator/blog/2012/06/06/sap-jvm-switch-guide-with-screenshot....in SCN..but this a great work...in SAP BASIS always better to share and discuss..
Hi Jacob,
Thanks for the appreciation and the info. I just went through the blog. Nice work.
I thought of writing the document as I myself struggled to find the exact procedure of JVM switching. Anyways, this document contains some additional post steps and updated notes and it adds document in the forum.
Thanks,
Pankaj
we are using the new downloaded tool (SAPJVMSWITCH00P_13-20008224.SAR)
the automatically restart of the instance is now running since 61 min,
but it seems the jvmswitch-tool did not recognize, that the system is running!!!
what to do??? š
will a cancel of the tool-clientsession cancel the whole execute-step ?
Hi Christoph,
Sorry to reply to you late. You could have manually stopped the instance in case it was taking a long time. I hope the issue was resolved.
Regards,
Pankaj Pabreja
yes, the issue was solved - it seems, it was an IBM-i specific issue:
=> http://scn.sap.com/thread/3379069
Thanks.
Hi Pankaj, good document!. during the change a have some error and fix
http://scn.sap.com/blogs/error0/2013/09/24/error-change-jvmerror-transport-error-202-could-not-find-free-port-in-debug-port-range
Thanks, it will be always helpful.
Very detailed document.
Thanks for sharing.
Very nice, thank you!
Excellent blog Pankaj, self explanatory,has helped me a lot. Have one question though, is there any backout plan if some issue occurs in between. Do we have to take backup of JDK from some location?
Excellent blog and very helpful!