Migration of JDK 1.4.2_16 to SAP JVM

Dear Techies,
We are trying to migrate JDK 1.4.2_16 to SAP JVM 4 of our solution manager 7.0.
I have Downloaded.Both JVM switch Tool and JVM 4 version
SAPJVMSWITCH00_1-20008223.SAR,
SAPJVM4_1-10009724.SAR.
Iam trying to run the switch tool.
while follwing the steps Iam encountering the error as mentioned below.
An error occurred while processing option Switch JDK to SAP JVM > Switch JDK( Last error reported by the step: System call failed. Error 3 (The system cannot find the path specified. ) in execution of system call 'CreateProcess' with parameter (NULL, Program Files/sapinst_instdir/NW70/SWITCH_JDK, &StartupInfo, &ProcessInfo), line (578) in file (synxcchapp.cpp), stack trace: iaxxejsctl.cpp: 146: EJS_ControllerImpl::executeScript()
d:\depot\bas\720_rel\bc_720-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\ejs\iaxxejsbas.hpp: 461: EJS_Base::dispatchFunctionCall() iaxxejsexp.cpp: 178: EJS_Installer::invokeModuleCall() iaxxbprocess.cpp: 407: CIaOsProcess::start_impl() synxcchapp.cpp: 232: CSyChildApplicationImpl::start(false) synxcchapp.cpp: 256: CSyChildApplicationImpl::doStart() .). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/NW70/SWITCH_JDK.
Iam working in win2003 sr2 64 bit environment.
SAP is installed in E:\
Windows in C:\ and D:\ is our cd drive.
Please suggest how to go ahead.
Thanks in advance.
Regards,
Kiran.

Hi,
The system cannot find the path specified
Looks like a required file is missing or not accessible. COuld you check for the last updated log files in the location C:\Program Files/sapinst_instdir/NW70/SWITCH_JDK?
These may give info about the missing file.
Regards,
Srikishan

Similar Messages

SAP JVM 4

I'm planning to install SAP Netweaver 7.3 (PI) on X86_64 running Redat Hat Linux 5.8. A prerequisite is installing JDK. According to SAP note 1172419, you can install IBM JDK, but the recommended is SAP JVM.
I was not able to find any documentation on installing SAP JVM. All the documentation is about switching to SAP JVM.
Are there any documentation for installing SAP JVM?

Hi,
Check this Link: [SAP JVM|http://venkata-pagolu.blogspot.in/view/flipcard#!http://venkata-pagolu.blogspot.com/2012/02/sap-jvm-update-procedure.html]
Also check this Note 1439013 - SAP Systems based on SAP NetWeaver 7.3: Windows
Regards,
Venkata S Pagolu

Installing SAP netweaver 7.3 -- JDK VS SAP JVM

Hi Guru's,
We are trying to install NW 7.3 on windows .
-->I came to know that NW 7.3 is 64bit only, running on SAP JVM 6 (JAVA) and Unicode version
--> Note 1495160 - SAP JVM as replacement for Partner JDKs 1.4.2
So , Is that mean before installation I don't require JDK 1.4. X . I and no need to use Switch tool to upgrade to SAP JVM 4 etc
then How could SAP JVM 4/6 comes to the picture ?
How to get SAP JVM4/6 . Is it going to be there in the installation suite itself ?
Please update me ASAP.

Hi Ratnaji ,
Thanks for sharing ..
"SAP JVM6 is required for NW 7.3 ."
How can I get this SAP JVM6 ? .
If it is of partner jdk's like 1.4... I would have downloaded from service marketplace and during sapinst installation I would have given that over there.
So , In case of SAP JVM6 how to proceed ?
Regards
Sandy

CORBA problem after migration to JDK 1.5.0_05

Hi,
I faced some errors with CORBA, after performing migration from JDK 1.4.1 to JDK 1.5.0_02
on Solaris 8 2/02 (SPARC version).
I've spend few days on digging in java.sun.com bug database and google archive,
but haven't found similar case.
The problem occurs in a web application launched on Tomcat 5.5.7, if JDK 1.5.0_02 is used and trying to connect with CORBA server.
If using JDK 1.4.1 the CORBA stuff works fine.
I isolated the problem code and found out, that Tomcat
can not cause the error, because i receive the same error while invoking test class from command line.
I use IOR file for obtaining the object reference and default JDK Orb.
The stacktrace(see below) goes through new package in JDK 1.5 com.sun.corba.se.impl.* and java.lang.Class which was
rewriten in JDK 1.5 in order to use generics. Is it possible that the bug lies somewhere in this classes?
I've already spent few days on searching cause of the bug, and found no clues.
Is this a known issue? Does anyone have a workaround?
Have you seen some similiar behavior associated with migration to JDK 1.5.0 ?
I'm running out of ideas, on debugging this stuff, any help or suggestion could be helpful.
Thanks In Advance, Kuba
PS. I attach the received stack trace below:
org.omg.CORBA.BAD_OPERATION:   vmcid: 0x0 minor code: 0 completed: Maybe
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:897)
        at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:99)
        at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:572)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:430)
        at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:326)
        at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:129)
        at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
        at generated.from.idl.package._ServerFactoryStub.FindServer(_ServerFactoryStub.java:25)

Hi,
I replying to my own post for persons who, have a similar problem.
I've used external ORB implementation, and the stuff started working properly.
www.jacorb.org.

JDeveloper 11g and JDK 1.4.2_16

Hi! I just created a new simple app in JDev 11g and selected the JDK 1.4.2_16 for the model project. I created a set of business components from tables, built the project and them attempted to run the AppModule tester.
I got the following error:
/usr/java/j2sdk1.4.2_16/bin/java -server -classpath /opt/app/oracle/product/jdevstudio1111/BC4J/jlib/bc4jtester.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/bc4jsyscat.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/db-ca.jar:/opt/app/oracle/product/jdevstudio1111/jlib/jdev-cm.jar:/opt/app/oracle/product/jdevstudio1111/lib/xmlparserv2.jar:/opt/app/oracle/product/jdevstudio1111/jlib/ohj.jar:/opt/app/oracle/product/jdevstudio1111/jlib/help-share.jar:/opt/app/oracle/product/jdevstudio1111/jlib/share.jar:/opt/app/oracle/product/jdevstudio1111/jlib/jewt4.jar:/opt/app/oracle/product/jdevstudio1111/jlib/oracle_ice.jar:/opt/app/oracle/product/jdevstudio1111/jlib/ojmisc.jar:/opt/app/oracle/product/jdevstudio1111/ide/lib/idert.jar:/opt/app/oracle/product/jdevstudio1111/ide/lib/javatools.jar:/usr/java/j2sdk1.4.2_16/jre/lib/rt.jar:/usr/java/j2sdk1.4.2_16/jre/lib/i18n.jar:/usr/java/j2sdk1.4.2_16/jre/lib/sunrsasign.jar:/usr/java/j2sdk1.4.2_16/jre/lib/jsse.jar:/usr/java/j2sdk1.4.2_16/jre/lib/jce.jar:/usr/java/j2sdk1.4.2_16/jre/lib/charsets.jar:/usr/java/j2sdk1.4.2_16/jre/classes:/home/mcruz/development/11g/SessionTest11g/.adf:/home/mcruz/development/11g/SessionTest11g/Model/classes:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adf-share-support.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adf-share-ca.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adf-share-base.jar:/opt/app/oracle/product/jdevstudio1111/jlib/identitystore.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/bc4jmt.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/bc4jwizard.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/groovy-all-1.0.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/bc4jct.jar:/opt/app/oracle/product/jdevstudio1111/jlib/commons-el.jar:/opt/app/oracle/product/jdevstudio1111/jlib/jsp-el-api.jar:/opt/app/oracle/product/jdevstudio1111/jlib/oracle-el.jar:/opt/app/oracle/product/jdevstudio1111/jlib/resourcebundle.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/api/jaxb-api.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/api/jsr173_api.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/activation.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/shared/sun.jaxb/2.0/jaxb-xjc.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/shared/sun.jaxb/2.0/jaxb-impl.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/shared/sun.jaxb/2.0/jaxb1-impl.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adfshare.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adfm.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/jlib/adfui.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/adfbinding.jar:/opt/app/oracle/product/jdevstudio1111/adfdt/lib/adfdtatrt.jar:/opt/app/oracle/product/jdevstudio1111/adfdt/lib/adftransactionsdt.jar:/opt/app/oracle/product/jdevstudio1111/adfdt/lib/adfdt_common.jar:/opt/app/oracle/product/jdevstudio1111/mds/lib/mdsrt.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jazn.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jazncore.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jps-api.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jps-common.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jps-internal.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jps-fmw.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/jps-unsupported-api.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/jacc-api.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/oc4j-unsupported-api.jar:/opt/app/oracle/product/jdevstudio1111/jdbc/lib/ojdbc5dms.jar:/opt/app/oracle/product/jdevstudio1111/jlib/orai18n.jar:/opt/app/oracle/product/jdevstudio1111/jlib/ojdl.jar:/opt/app/oracle/product/jdevstudio1111/jlib/dms.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/lib/bc4jdomorcl.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/jlib/bc4jdatum.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/servlet.jar:/opt/app/oracle/product/jdevstudio1111/jlib/commons-cli-1.0.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/commons-collections.jar:/opt/app/oracle/product/jdevstudio1111/jlib/xmlef.jar:/opt/app/oracle/product/jdevstudio1111/lib/xml.jar:/opt/app/oracle/product/jdevstudio1111/rdbms/jlib/xdb.jar:/opt/app/oracle/product/jdevstudio1111/javacache/lib/cache.jar:/opt/app/oracle/product/jdevstudio1111/diagnostics/lib/ojdl.jar:/opt/app/oracle/product/jdevstudio1111/j2ee/home/lib/pcl.jar:/opt/app/oracle/product/jdevstudio1111/ucp/lib/ucp.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/shared/oracle.javatools/11.1.1.0.0/dafrt.jar:/opt/app/oracle/product/jdevstudio1111/lib/java/shared/oracle.javatools/11.1.1.0.0/javatools-nodeps.jar:/opt/app/oracle/product/jdevstudio1111/BC4J/jlib/bc4jui.jar:/opt/app/oracle/product/jdevstudio1111/dvt/lib/dvt-client.jar:/opt/app/oracle/product/jdevstudio1111/dvt/lib/dvt-utils.jar:/opt/app/oracle/product/jdevstudio1111/jlib/LW_PfjBean.jar: oracle.jbo.jbotester.MainFrame -X 116D6D52C8E -H jar:file:/opt/app/oracle/product/jdevstudio1111/jdev/doc/studio_doc/ohj/bc4j_f1.jar!/bc4j_f1.hs
Exception in thread "main" java.lang.UnsupportedClassVersionError: oracle/jbo/jbotester/MainFrame (Unsupported major.minor version 49.0)
     at java.lang.ClassLoader.defineClass0(Native Method)
     at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
     at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
     at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
     at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
     at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
Process exited with exit code 1.
Am I to assume that jdk1.4.x is no longer supported in JDeveloper and that I should start using JDK1.5.x? But apps built with JDK1.5.x are not supported in AppServer 10.1.2.0.2, which is J2EE 1.3 compliant... Does that mean that JDeveloper 11g is suitable only for apps deployed on OAS 10.1.3.x and above? (OAS 10.1.3.x is J2EE 1.4 compliant, and OAS 11g will be J2EE 5.x compliant).
Comments please.
Thx!

be on OracleAs 10.1.3 at a minimum<<The problem (for us) with Oracle AS 10.1.3 is that Portal 10.1.4 will not run on it (not certified). We want to take advantage of ADF RC and we hope to be able to produce JSF portlets or "portletized" apps. But at the moment we are "stuck" with 10.1.2.0.2 and JDK 1.4.x/J2EE1.3...
While you can have a 10.1.2 farm and add a 10.1.3 separate instance it is not a clean/complete integration (you can't manage all services from the 10.1.2 farm EM and others; this is what I've seen so far, IMO).
We can't wait for OAS 11g to come out and take a look at that. And I certainly hope that Portal will be certifed on 11g so that we can just jump there.
Another wish: WebCenter functionality in Portal, or Portal/WebCenter rolled out into one.

Identifying problems when migrating to JDK 5/6

We are interested in migrated from JDK 1.4 to 6.
I found an article on walmart.com's experience.
"Java 1.5 introduced several changes or enhancements to its XML API (SAX, DOM and XSLT in particular). These changes first became apparent when running code that relied on JSP’s imports. Previous versions of the XML API allowed the same XML attribute to be defined more than once in a single JSP. Quite a few JSP pages, dynamic and static, broke when running under Java 1.5 because of the attribute repetition. "
[http://www.theserverside.com/tt/articles/article.tss?l=MigratingtoJava5]
Please identify what the author means exactly by "XML attribute" and provide an example of this behavior/bug. I'm trying to understand this so I can identify if we have this in our codebase or not. thx.

The migration from Designer 6.0 to 6i requires careful planning. Please read the migration guide on OTN (http://www.oracle.com/technology/products/designer/index.html) for advice and to assist you with the migration.
Regards
Sue

Using JRockit for SAP JVM (JDK 1.4.2_37b02)

Can I use JRockit to monitor SAP JVM (J2EE) threads, memory, Garbage Collector?
We are running on Windows 2003, SP2 with MS SQL 2005. We run SAP NetWeaver Portal 7.02 on Sun Partner JDK 1.4.2_37
SAP has there own SAP Memory Analyzer Profiler tools, but there graphs, messaging (email, sms, etc.) as well as reports are weak.
Thanks.
James

No, this will not work. The SAP JVM is based on Hotspot, while the JRockit tools require the JRockit JVM to work.
Henrik

New IBM JDK 1.4.2 for SAP NetWeaver 2004 and 2004s

In May 2006 IBM System p brand and SAP announced the direction to enhance the IBM AIX 5L JDK 1.4.2 for SAP NetWeaver 2004 and SAP NetWeaver 2004s based applications. The new IBM JDK 1.4.2 for SAP NetWeaver applications on AIX 5L is 100% upward compatible for all SAP business applications and, compared to the classical AIX JDK, provides a more consistent runtime behavior, enhances memory management, and improves debugging capabilities.
<b>General Availability (GA) of the new IBM JDK 1.4.2 for SAP NetWeaver 2004 and 2004s on AIX 5L</b>
As part of a staged release process aligned between IBM and SAP a customer pilot program was started in August 2006 followed by a Controlled Availability (CA) program. Based on positive customer feedback resulting from real production usage and the very encouraging internal test results, the new IBM JDK on AIX 5L is/will be generally available
     for SAP NetWeaver 2004 SP14 and above starting at 5th of February 2007
                and
     for SAP NetWeaver 2004s SP06 and above starting at 30th of March 2007.
This means systems running above SAP NetWeaver releases in an AIX 5L environment are allowed to use the new IBM JDK without restrictions.
This announcement does not affect the use and support of the classical AIX JDK outside SAP environments.
<b>Transition Plan to the new IBM JDK 1.4.2 on AIX 5L</b>
SAP will support the classical and the new JDK in parallel for a limited number of NetWeaver support packages. Afterwards only the new IBM JDK will be supported:
     for SAP NetWeaver 2004 the first support package only supporting the new JDK will be SP21 (planned date for SP21 see http://service.sap.com/~sapidb/011000358700001130682005E),
     for SAP NetWeaver 2004s it will be SP14 (planned date for SP14 see http://service.sap.com/~sapidb/011000358700004584092005E).
So please plan a transition to the new JDK prior to the upgrade to these support packages.
SAP and IBM strongly believe that the switch to the new JDK will improve your experience with JAVA based SAP applications on AIX 5L. Both companies recommend upgrading to the new IBM JDK 1.4.2 for SAP applications running on AIX 5L as soon as it matches your companys maintenance plans.

You can download the JDK directly from the sun java website...
http://java.sun.com/products/archive/j2se/1.4.2_12/index.html
I don't think Ubuntu is supported...
Regards
Juan

SAP JVM switch SAPINST GUI not launching

Hi All,
I have performed SAP JVM switch in all portal servers. One of the server is giving issue. I is not launching sapinst GUI screen. There was 2 JDK versions installed j2sdk1.4.2_13 and j2sdk1.4.2_29. I keep tried changing j2sdk1.4.2_29 in some properties file besides java home is pointing to j2sdk1.4.2_29. I also changed SAPINST_JRE_HOME property in environment variables with j2sdk1.4.2_29 to be in sync. Now below log is showing j2sdk1.4.2_29 but it is still not launching sapinst gui. Please help. System: Portal 7.0.
Program starter log:
Program is starting... Please wait!
SAPinst build information:
Version:       2014.09.0
Build:         1521363
Compile time: Okt 05 2014 - 16:33:50
Make type:     optU
Codeline:      720-2_REL
Platform:      NTAMD64
Kernel build: 721, patch 319, changelist 1516453
Exe directory: C:\WINDOWS\TEMP\1\sapinst_exe.6052.1416864069
guiengine: 2014-11-24 16:21:19 Waiting for client connection (1)
SDT start mode [Java: C:\j2sdk1.4.2_29-x64\bin||Home: C:\Documents and Settings\epdadm||Cd: E:\Workarea\SAP_JVM] => /default/
Starting GUIServer using:
SAPinst port         : pipe:480:456
GUIServer port       : 21212
GUI autostart        : on
GUI mode             : normal
Curdir               : E:\Workarea\SAP_JVM
command       : C:\j2sdk1.4.2_29-x64\bin\java.exe -cp "C:\WINDOWS\TEMP\1\sapinst_exe.6052.1416864069\jar\instgui.jar" -Xmx256M -Dsun.java2d.noddraw=true -Dsap.env.var.javahome=SAPINST_JRE_HOME SDTServer "rootdir=C:\Documents and Settings\epdadm\.sdtgui" config=jar:sdtserver.xml guiport=21212 -nolock -srvarg=/SAPinstService/host=127.0.0.1 -srvarg=/SAPinstService/port=pipe:480:456
CurrentDirectory: E:\Workarea\SAP_JVM.
Thanks,
Kavitha Rajan.

very true Reagan.
Kavitha, you just need to make sure that the instance profile has the right details.
    SAPJVM_VERSION. Enter the new version of the SAP JVM e.g.:
    SAPJVM_VERSION = 4.1.028
    and
    jstartup/vm/home = <location of the new jdk>
    for example:
    jstartup/vm/home = /usr/sap/<SID>/SYS/exe/jvm/hpia64/
                       sapjvm_6.1.028
After the change, delete following files (they will be recreated after the j2ee restart):
/usr/sap/<SID>/<INSTANCE>/j2ee/cluster/instance.properties.vmprop
/usr/sap/<SID>/<INSTANCE>/SDM/program/config/sdm_jstartup.properties.vmprop
Now do a complete cluster restart.
Regards,
Hemanth

SAP JVM 4.1

Hi All,
I am installing ERP EHP5 on linux suse 11 sp1 verion.
As per SAP Note 1172419 - Linux: Supported Java versions on the x86_64 platform. I couldn't able to find following version.
SUSE Linux Enterprise Server for SAP applications 11
u2022     java-1_4_2-ibm-sap-1.4.2_sr13.10-0.3.1.x86_64.rpm
u2022     java-1_4_2-ibm-sap-devel-1.4.2_sr13.10-0.3.1.x86_64.rpm
Can we use SAP JVM 4.1 ? or we have have to install IBM java only?
Thanks
Siva

Hi Siva,
Note 1310037 - SUSE LINUX Enterprise Server 11: Installation notes
The following is again from the same note.
If your SAP component requires the java jdk 1.4.2 you need to install the java JDK from the additional SDK media. This media is available at:
           http://download.novell.com
           Select the "SUSE Linux Enterprise Software Development Kit" as product and version 11 (same Service Pack) of this product. Press the button "search" to get a download list. You will need a Novell account to proceed with the download.
Br,
Venky

SAP JVM default keystore file for Active MQ JMS SSL integration?

Hi all,
does the SAP JVM still have a default keystore file?
I'm asking this question because I would like to integrate with Active MQ JMS SSL. The MQ-Libs are refering to the VMs default keystore in order to find the certificate for the SSL handshake.
Kind regards,
Heiko

Same here, with almost the same things (JDK @ 1.5.0_16) but same WLS version, as well as Eclipse & WTP.
Also have the Bea WLS Tools plugin 1.1.1
Ideas right here...?

SAP JVM 5.1 / SAP JVM 6.1 - versus SUN

With WAS 7.1 / 7.2, per PAM the only supported JVM's are SAP JVM 5.1 / SAP JVM 6.1. Specifically that means, SUN, IBM and HP are no longer supported. Question: Where can I find details on SAP JVM 5.1 / SAP JVM 6.1? I assume those are essentially SUN SDK 1.5/1.6 with SAP's own implementation around; is that correct?

Hi,
use this: https://cw.sdn.sap.com/cw/docs/DOC-106773
as your start for exploring the SAP JVM.
To my knowledge, the SAP JVM is 100% Java standard compliant but offers a better (long-term) support compared to other vendors. After all, the SUN Java entered end of maintenance from SUN some years ago and the version for SAP is now the -b, business version of the JDK 1.4.
Should be interessting to know if the SAP JVM is the same for all OS supported (like: AIX, HPUX, Linux, Windows, etc), in terms of performance, bugs (?) and parameters.
br,
Tobias

The Java startup framework must be updated - SAP JVM 4

Dear All,
While execution of switch from JDK to SAP JVM 4.1 on java instance we get the message "The Java startup framework must be updated in order to use SAP JVM 4"
Please help or guide for further steps
Regards,
Ajay

Hi Ajay,
Hope you are doing good.
If the issue persists, kindly update the kernel to the latest level as this will update the native libraries which the JVM needs. This is the next step in these kind of cases.
The below links will help you if there are any queries with the
kernel update procedure.
If you wish to do a Manual Kernel Upgrade:
<http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70d8838d-cb8f-2c10-7ab8-d1504670fbb8>
Kernel upgrade using JSPM:
<http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/11219>
and
SAP Note No. 19466: Downloading SAP kernel patches
Thank you and have a nice day :).
Kind Regards,
Hemanth
SAP AGS

Instructions for Installing SAP JVM

Hello,
I have downloaded the SAP JVM to use it for Java instances 7.3 as recommended by SAP.
Do i have to do more configuration other than Decompressing the SAP_JVM.SAR file .
Is there a specific path where to decompress it? are there some Variable Environments to modify?
Thanks in Advance
Hassan

Thanks for your answer,
Actually i do not want to use at all the IBM JDK (i will install the SAP on Redhat EL5, X86_64)
Before the installation i will not have the path: /usr/sap/<SID>/<INSTANCE><NR>/j2ee/JSPM/go , shiould i have to craetae it and then decompress the SAP JVM inside? or i put it usually where the IBM JDK is usually installed in /opt
And for starting the /sapinst we need to have the JRE which is including in the SAP JVM.
Thats why i need to have it before having the instance installed.
Best Regards

EWA: Outdated SAP JVM Information - Update Stores

Dear Experts,
I have already switched to SAP JVM about a month ago. The EWA alerts for the system are still showing the message:
"SAP JVM 4 is recommended to use instead of SAP partnersu2019 JDK 1.4. Please refer to SAP Note 1495160 for more details."
The jvm switch was performed succesufully and I´m able to confirm this at: http:// configuration:
Instance.properties and instance.properties.vmprop are OUTDATED. The information from the files as operating system level was taken about 3 months ago, and at this point the java jvm hasn't been updated yet.
Then, my question is how to get updated datain my EWAs? or if I´m right about that thin info is taken from the stores then, how to manually trigger a store update??
Regards,
Diego.

Diego,
What I say is what needs to be done to resolve this issue.
There is not a Note that states this to my knowledge.
There may be a reference to this int he COnfiguration guides.
You may take my advice or not. You can wait for others to confirm what I have stated.
I have attempted to help you. If you do not wish to accept the assistance that is your choice.
However if you would like this issue resoloved, then you need to do perform a managed system setup.
It shouldn't be as work intensive as you are making out, as it should have the old values retained, and you really will be changing very little, as you will be accepting the values there from the last setup.
But I stand firm, Java systems must have the Managed system setup performed when the software is updated.
And this is especially true for EWAs to be correctly generated.
Your own diagnosis has determined that SMD stores for SAPJVM have not been created....why? You have not run the Managed system setup. You have stated you changed the JVM and the EWA is not reflecting it. Why? Because you have not
run manage system setup.
If you want this issue to resolve, then I recommend you accept the advise and run the Managed system setup on this system again.
Regards,
Paul

Migration of JDK 1.4.2_16 to SAP JVM

Similar Messages

Maybe you are looking for