Skip to end of metadata
Go to start of metadata

Table of Contents

Engine not displayed in preferences

Symptom:
AS Java Server is not visible from NWDS:

Answer:
Open DEFAULT.PFL file in /usr/sap/(SID)/SYS/profile and set service/protectedwebmethods to DEFAULT (from SDEFAULT) and then restart the engine.

Workaround:
In case you would face any problem when applying the above solution, then use the workaround:
in NWDS' menu go to Window -> Show View -> Other, and select the Management Console. Right click on SAP Systems, add system, and enter the hostname and instance number. A pop up will ask to enter an adm user and password, enter them both. Then go back to the Preferences, SAP AS Java screen and your system will be there.

See also the note that deals with the popup about the OS user:
#1834579 OS level login dialog appears in SAP MC (Developer Studio) and #2088024 - OS Logon to SAP J2EE Host popup in NWDS 


 Back to top .

 

How to solve _java.lang.UnsupportedClassVersionError in NWDS

Symptom: How to solve java.lang.UnsupportedClassVersionError: Bad version number in .class file provoked by a calling a WebDynpro app developed in NWDS EhP1 for CE 7.1?

Answer: Probably, the deployed class is Java 6 whereas WebAS is Java 5. Steps to solve the issue:

  1. NWDS -> Preferences -> Java -> Compiler -> "Compiler compliance level" has to be 5.0
  2. Rebuild and redeploy and call the app.
  3. If error still occours, NWDS may not use Java 5 JDK/JRE.
    1. Close NWDS. 
    2. Check if you have a Java folder jdk1.5.0_xx (jdk1.5.0_16 for example) and xx has to be >= 14. If you don't have such JDK version, please go to the official site http://java.sun.com/products/archive/and download and install the old version.
    3. Way 1: Open <NWDS CE7.1.1 install dir>\eclipse\SapNetweaverDeveloperStudio.ini and make sure that the parameter -vm points to a Java 5 installation. If not, change it accordingly.
      Way 2: Rename all Java 6 folders (e.g. prefix "x") so NWDS can not find them any more. Restart the NWDS. NWDS shall complain about missing JDK/JRE and, depending on your version, may show the JDK/JRE-selection dialog like at very first startup after installation.
    4. Start NWDS.
    5. Rebuild and redeploy and call the app.
  4. In case this does not work check the build configuration of the development track
    1. Open Development Infrastructure perspective
    2. Select development configuration that you are using for development
    3. In "Component Properties" view, open "Technology Specific" section.
    4. Check that the JDK for local build is configured to JDK1.5.0_xx (jre may not work here)
    5. Rebuild and redeploy and call the app.



Back to top .

 

NWDS build fails due to wrong JDK

Symptom:
Your build fails, and you can see in the build log:

javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
	at org.apache.tools.ant.taskdefs.compilers.CompilerAdapterFactory.getCompiler(CompilerAdapterFactory.java:105)
	at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:929)

and

Error: Build stopped due to an error: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK
Error: Build stopped due to an error: Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK

In your analysis JAVA_HOME is set up properly.

Answer: Most probably your NWDS is using JRE instead of JDK. Check the startup script in the properties of the NWDS icon on the desktop.

Back to top .

 

Update via the Update Site is not possible

Symptom:
You installed NWDS >=71X and updaing it or setting the proxy is not possible due to the following errors.

  • Error #1: you face when trying to ping the proxy from the preferences:

    Could not connect to https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/711/policy.xml.
    
  • Error #2 when you try to "Help - Software Updates - Find and Install...":

    Error parsing site stream. [Premature end of file.]
    

Answer: You need to set up the proxy properly, the update site uses SSL, see the image:

This is also described under NWDS Update Site's Troubleshooting

Back to top .

 

Authentication popup appearing when adding AS JAVA server in NWDS

Symptom:
You are in NWDS – Window – Preferences – SAP AS JAVA

When the details of the server are entered the user is prompted to enter OS user id and password. The developer does not have this information and will not be provided this information.

Answer:
SAP provides a lot of security features and one of them is to restrict the access to the provided web methods from SAPControl web service. The change in NW 7.3 EHP 1 is that by default almost all of the provided web methods are restricted (authorization is required). It is done in the profile file with changed value DEFAULT to SDEFAULT for parameter:
service/protectedwebmethods. To resolve the problem the corresponding webmethod must be revoked from the restricted list as per this note suggests:

#2088024 - OS Logon to SAP J2EE Host popup in NWDS 

See also:
#927637 – Web service authentication in sapstartsrv as of Release 7.00
#1439348 – Extended security settings for sapstartsrv

Back to top .

 

Setting share point for the NWDS workspace not allowed

Symptom:
You specified a share for workspace in the NWDS shortcut icon
Example: „...--data \\myserver\myworkspace..."

Answer:
This is not supported, only local space definition is allowed.
Example: „...--data C:\myserver\myworkspace..."
Else among the many many side-effects you will face massive performance issues as well.

Back to top .

 

Can not add AS JAVA server in NWDS

Symptom:

You are in NWDS Window Preferences SAP AS JAVA
When adding AS Java server the following popup appears on the screen:


 

Answer:

First you should verify you use the correct instance number.
If the instance number is correct the 3. solution of the KBA 1439348 (Restrict network access) can help.
Verify the ACL list is set correctly (if it includes your System.) If you change the list you must restart the affected service sapstartsrv.

 Back to top .

4 Comments

  1. Former Member

    You should definitly add the link update not possible via https "Update via the Update Site is not possible". Unfortunately I am not allowed.

  2. nwds-extsoa-7.3-EHP1-SP11-PAT0003-win32.zip

    nwds-extsoa-7.3-EHP1-SP09-PAT0001-win32.zip

    nwds-extsoa-7.3-EHP1-SP09-PAT0005-win32.zip

    I have tested the above NWDS. It is only possible to add one sap as java system in
    window-preferences-sap as java

    when trying to add more servers nothing happens, nothing is logged.

    Using MMC perspective (SAP management console) to add more servers works though.

  3. In Java EE perspective, when right clicking EAR project and choosing  "run as - run on server" all servers are not displayed. Restarting NWDS multiple times solved the problem and made the servers finally display.

  4. >In Java EE perspective, when right clicking EAR project and choosing  "run as - run on server" all servers are not displayed.

    I fix it by opening SAP MC perspecive at first, then Deployment perspective.

     

    Another bug when generate Java Bean skeleton: sometimes auto-create for EAR/EJB projects raises abort message so you should create projects manually. Sometimes vice versa (smile)