on 01-02-2012 4:19 PM
I installed the NWDS 7.3 for customizing my portal 7.3 logon page. I am following an interesting blog for the same:
However I am yet to complete this task successfully due to a JVM vendor not supported error. I have a JAVA_HOME entry to the javaw.exe path. Also, i have vm entry of the same path in the NWDS shortcut- properties- target value. C:Program Files (x86)Javajdk1.7.0_02in
I chose program files (x86) for this installation bcos during my previous java error i read in my log that JVM 64 bit could not be run.
Initially i use to get JVM error during startup itself bcos of which i was not able to get to the home page of developer studio. I solved that error now by installing right version and making necessary entries as mentioned above. Now i get a pop up stating that oracle vendor is not supported (it says that i should have either a Sun or SAP provided java). Is it really the problem? If so, can some 1 get me the link to download it.
I am creating a new thread since the old ones posted by others on the same topic does not give me the solution.
Thanks in advance
Hi,
I also come to this warning. I did a little research, and found solution that worked for me by solving source of problem, without need of trying different JDK versions.
SAP NWDS:
- v7.30 EHP1 (7.31) SP10 PAT0001 (8.31.100001.140103092401 SP10 PAT0001)
- file: "nwds-extsoa-7.3-EHP1-SP10-PAT0001-win32.zip"
- Download location: https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/731/doc/auto_latest_distributions.html
JDK:
- v7 Update 51 - both x86 and x64 versions. As NWDS is x86 version, that platfotm is enought if you don't need native support for x64 applications.
- Latest version download location: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
- Older versions download location: http://www.oracle.com/technetwork/java/javase/archive-139210.html
- I'm not suggesting that you need to install last version. I tested it on this version and it worked for me, but I use NWDS only for few specific tasks. So I did't test all functions for JVM compatibility. But my solution should work for solving cause of vendor specific problem. Not other JVM problems. And installing newer Java may be source of other problems, like is every release. But with correct backup there shouldn't be a problem.
Problem is in older code of initial JVM check, where are specified allowed vendors. Oracle is not included in configuration, so warning is shown. Module is located in plugins folder:
"<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
Version number (orange) can differs based on NWDS distribution. In jar file is configuration stored in file "config.xml". There is this part, that specifies allowed vendors:
<supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
<vendor name="SAP AG">
<versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
</vendor>
<vendor name="Sun Microsystems Inc.">
<versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
</vendor>
</supportedRuntimes
Here you can see that only "SAP AG" and "Sun Microsystems Inc." from older Java releases are included. And that's the problem, as new versions are released by Oracle. So vendor differs and warning is here.
1) Locate file with JVM checking module:
"<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
As mentioned before, version number can be different in your release.
2) Create backup copy of current file. Call it for example "com.sap.ide.jvm.check_1.0.0.140103091951.jar.BAK".
3) Copy original file to temporary location. I used "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
4) Extract files from JAR. JAR files are basically ZIP files. I used 7-zip program to extract source to folder based on file name:
"C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\".
5) Locate and edit configuration file "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\config.xml". Add vendor node "Oracle Corporation" (part in green color). Just copy existing node and replace vendor name.
<supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
<vendor name="SAP AG">
<versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
</vendor>
<vendor name="Sun Microsystems Inc.">
<versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
</vendor>
<vendor name="Oracle Corporation">
<versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
</vendor>
</supportedRuntimes>
6) Pack directory. Pack whole content of directory from step 5) back to ZIP format. Change extension to .JAR in your favorite compression program, or rename new file from ".zip" to ".jar" after compression is done. Now we have our new corrected file for checking JVM version in NWDS - "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar".
7) Replace original file. Copy file over original one:
"C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar" -->
"<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar". Overwrite if asked.
😎 Done.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Tomas, great post. Exactly what I'm looking for. So many people say to just use the old JDK but there are big security holes in those old JDKs.
I have Winzip , so I just rename the .jar file to .zip, open it with winzip, locate the config.xml, edited it and updated the zip file (winzip will prompt when existing), rename the .jar back to .zip.
Cut down a lot of the steps and it worked for me.
Hi,
you're welcome. Sure some steps are not needed for skilled user, and it's possible to user another way around. I just tried to make it clear and detailed enough even for less experienced users.
PS: Also tested on new version:
SAP NWDS:
- v7.30 EHP1 (7.31) SP10 PAT0002 (8.30.100002.140207121738 SP10 PAT0002)
- file: "nwds-extsoa-7.3-EHP1-SP10-PAT0002-win32.zip"
Plugin file:
"<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140207094830.jar"
User | Count |
---|---|
78 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.