Scribd
Upload
33 views3 pages

Note 718901 - How To Change The JDK of The J2EE Engine

This document provides two options for changing the JDK used by the Java application server. Option 1 involves editing the instance profile to specify the new JDK location, which updates all processes. Option 2 uses the configuration tool to change the JDK path for each server instance. Both options require deleting property files after the change to take effect on restart.

Uploaded by

subramks
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views3 pages

Note 718901 - How To Change The JDK of The J2EE Engine

This document provides two options for changing the JDK used by the Java application server. Option 1 involves editing the instance profile to specify the new JDK location, which updates all processes. Option 2 uses the configuration tool to change the JDK path for each server instance. Both options require deleting property files after the change to take effect on restart.

Uploaded by

subramks
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

SAP Note 718901 Engine

Note Language: English

How to Change the JDK of the J2EE


Version: 7 Validity:
Valid Since 18.12.2006

Summary
Symptom
Due to JDK problems it might be necessary to upgrade the JDK.

More Terms
JDK Upgrade ConfigTool

Cause and Prerequisites Solution


There are two options to change the JDK that the engine is using. The first way is the recommended way.

Option 1:
Edit the instance profile in /usr/sap/<SID>/SYS/profile/<SID>_JC<num>_<host> and add the following line jstartup/vm/home = <location of the new jdk> Notes: o Because this setting has precedence over individual JDK settings in the J2EE Engine configuration database and the sdm_jstartup.properties file, the new JVM will be picked up by all processes which are started through the startup framework including the SDM. Manually changing the sdm_jstartup.properties file is not necessary. The Visual Admin, ConfigTool, and SDM GUI have their JDK configured in the startup batch files. Please change these scripts for the new JDK.

Please delete the following files after changing these values (they will be recreated on the next restart of the engine): /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/instance.properties.vmprop /usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdm_jstartup.properties.vmprop

Option 2:
Open the J2EE Config Tool, open the cluster-data subtree, then open the instance_ID<num> subtree. Please make sure you change the JDK path (Java Home) in all of the following locations: o o o On the General tab of the instance_ID <num> page On the General tab of the dispatcher_ID<num> page On the Bootstrap tab of the dispatcher_ID<num> page

For every server node below instance_ID<num> apply the changes


01.11.2009 Page 1 of 3

SAP Note 718901 Engine


o o

How to Change the JDK of the J2EE

On the General tab of the server_ID<num> On the Bootstrap tab of the server_ID<num>

Change the JDK for the SDM as described in SAP Note 743583. Delete the following files after changing these values (they will be recreated on the next restart of the engine): /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/instance.properties.vmprop /usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdm_jstartup.properties.vmprop

Notes:

The SDM server does not get the JVM location from the database but from the property file "sdm_jstartup.properties" located in the /usr/sap/<SID>/JC<num>/SDM/program/config directory. The location of the JDK for the Visual Admin, ConfigTool, and SDM GUI still have to be changed. If you have installed the Full Strength Jurisdiction Policies in the old JDK (you could check this using Note 739043), then you must also install the Full Strength Jurisdiction Policies corresponding to the new JDK. If you use Wily Introscope refer to note 856909: Autoprobe Connector has to be recreated for each new JVM version

Header Data
Release Status: Released on: Master Language: Priority: Category: Released for Customer 18.12.2006 14:59:44 English Recommendations/additional info Upgrade information

Primary Component: BC-JAS Java Application Server - Please use sub-components Additional Components: BC-JAS-SF Startup Framework

Valid Releases
Software Component SAP-JEE SAP-JEE Release 60 7.00 From Release 6.40 7.00 To Release 6.40 7.00 and Subsequent

01.11.2009

Page 2 of

SAP Note 718901 Engine Related Notes


Number 1319038 1159935 1008619 1004255 981804 970039 913972 879289 861215 856909 830140 810008 746299 743583 723909 716604

How to Change the JDK of the J2EE

Short Text DB2-z/OS:Recommended Settings for IBM 142 J9 JVM on zLinux IBM JDK 1.4.2 x86_64 option unrecognised: -Xjvm:j9vm23 java.lang.OutOfMemoryError in BEx Web Applications How to create a full HPROF heap dump of J2EE Engine 6.40/7.0 Add. info. on upgrading to SAP SRM LAC 6.0 Add. info. on upgrading to SAP NW 7.0 SR2 Java Add. info. on upgrading to SAP NW 7.0 SR1 Java Support Package Stack Guide - SAP NetWeaver 7.0 Recommended Settings for the Linux on AMD64/EM64T JVM Error after JDK upgrade on system with Wily Introscope Problems caused by MD5 related bug in the 1.4 JDK on AIX Recommended Settings for the Linux on POWER JVM DB2-z/OS:Recommended Settings for 142 JVM on zLinux - IBM How to change the JDK of SDM Java VM settings for J2EE 6.40/7.0 Access to Sun J2SE and recommended J2SE options

01.11.2009

Page 3 of

You might also like