SAP Note

Header Data

Symptom

You want to update the SAP JVM 4.1 manually.

Other Terms

Patch install

Reason and Prerequisites

Your system is already switched to use a version of SAPJVM 4. The replication of an instance local copy of the SAPJVM from a central DIR_CT_SAPJVM may or may not be activated.

Solution

Warning: The steps described in this note could cause serious problems if applied inappropriate. Therefore patching the SAP JVM should be done carefully and in NetWeaver 6.40 systems only. For NetWeaver 7.0x you have to use the Software Update Manager (see SAP note 1133020). Logon as <sid>adm and do the following for each Java instance:

1. IBM i only: If you are not using a 7.20 downward compatible kernel skip to step 7

2. Create a new directory for the new SAP JVM version. This is a subdirectory of /usr/sap/<SID>/SYS/exe/jvm/<platform> named sapjvm_<version>. For example, when the new SAP JVM version is 4.1.009 create a directory named: /usr/sap/<SID>/SYS/exe/jvm/<platform>/sapjvm_4.1.009

3. Change to the newly created directory using the "cd" command.

4. Extract the archive with the new SAP JVM version using SAPCAR, e.g. SAPCAR -xvf <location of the archive>

5. Open the SAP JVM manifest file (sapjvmmanifest.mf) with a text editor to verify the version again. Make sure the line "sapjvm version:" matches with the name of the directory you have created before. Otherwise rename the directory.

6. In case you need the "Unlimited" JCE Jurisdiction Policy files you have to replace the standard provided "Strong but limited" JCE Jurisdiction Policy files as described in SAP note 1240081.

7. IBM i only: If you are not using a 7.20 downward compatible kernel persist the (new) SAP JVM objects in the kernel, see SAP note 1563545.

8. Edit the instance/start profile and change the profile parameter SAPJVM_VERSION.

              Enter the new version of the SAP JVM e.g. : SAPJVM_VERSION = 4.1.009

              If no SAPJVM_VERSION parameter exists in your profile, you might need to modify the parameter jstartup/vm/home. That is, if jstartup/vm/home contains a path which includes a JVM version directory, it should be updated. This can happen in a 6.40 system.

9. Prepare the J2EE to detect the new JDK. Delete the instance.properties.vmprop file in the /usr/sap/<SID>/<instance>/j2ee/cluster directory. During the first J2EE startup this file will be recreated with the new JVM version information.

10. IBM i only: Log off and log on again as <sid>adm in order to refresh your environment. If you are not using a 7.20 downward compatible kernel apply the kernel you prepared in step 7. You need to stop the system before doing that.

    1611326 - Patching the SAP JVM 4.1 manually for NetWeaver 2004 and 7.0  

Version   9     Validity: 09.01.2013 - active   Language   English (Master)

Released On 09.01.2013 17:19:17

Release Status Released for Customer

Component BC-JVM SAP Java Virtual Machine

Priority Recommendations / Additional Info

Category Upgrade information

11. If you are using Wily Introscope to monitor your NW AS Java, you might have to generate new autoprobe connectors for the SAP JVM, since Wily Introscope modifies JDK classes, which have to fit exactly to the Java VM used. Note 856909 describes how to create new autoprobe connectors.

12. To update the SDM to use the new JDK follow the steps described in SAP note 743583.

13. In order to activate the changes in the instance profile, restart the instance. In case of Windows restart the according running Windows services too.

14. Not IBM i: Set JAVA_HOME environment variable of the <sid>adm user

              Some NW AS Java Tools, such as Config Tool, Visual Administrator and JSPM, use the JAVA_HOME environment variable to find the java executable. Therefore it is necessary to set the JAVA_HOME environment variable for the <sid>adm user, since he is usually runnning this tools. Java standalone server tools exist on central instances only, thus the update of JAVA_HOME is required at these instances only.

a) Login as <sid>adm OS user to the host where SAP central instance is located.

b) Go to directory '/usr/sap/<SID>/SYS/profile' (for UNIX systems) or '\\<SCS_host>\sapmnt\<SID>\SYS\profile' (for Windows systems).

c) Run "sappfpar pf=<SID>_JC<instance_number>_<instance_host>" if this is J2EE only system or "sappfpar pf=<SID>_DVEBMGS<instance_number>_<instance_host>".

d) Get the value of instance profile parameter "jstartup/vm/home". This is the new JAVA_HOME path.

e) Modify JAVA_HOME parameter for <sid>adm OS user:

¡ For Windows systems: open 'System properties -> Advanced system settings -> Environment variables' and modify the value of JAVA_HOME for the current user who is <sid>adm.

¡ For UNIX systems: go to directory '/home/<sid>adm', open file .j2eeenv(_host).(c)sh and modify the value of JAVA_HOME where it has been initially set.

15. Proceed accordingly for all instances you want to operate with the new version of the SAP JVM.

16. Not IBM i (if you are not using a 7.20 downward compatible kernel): Optionally remove files and folders below directory /usr/sap/<SID>/SYS/exe/jvm/<platform> of SAP JVM versions which are no longer in use.

Validity

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (6)

Software Component From Rel. To Rel. And Subsequent

SAP-JEE 6.40 6.40  

7.00 7.02  

SAPJVM 4.1 4.1  

1745807   SAP Solution Manager 7.1 SR1 hang in Setup Local SLD

1641062   Single component update and patch scenarios in SUM

1613370   IBM i: "...SYS/exe/jvm" not existing or not a link

1563545   IBM i: Persisting SAP JVM objects in the kernel

1495160   SAP JVM as replacement for Partner JDKs 1.4.2

1133020   How to import a SAP JVM patch into an AS Java

1133020   How to import a SAP JVM patch into an AS Java

1641062   Single component update and patch scenarios in SUM

1563545   IBM i: Persisting SAP JVM objects in the kernel

1495160   SAP JVM as replacement for Partner JDKs 1.4.2

1613370   IBM i: "...SYS/exe/jvm" not existing or not a link

1745807   SAP Solution Manager 7.1 SR1 hang in Setup Local SLD