Skip to Content
avatar image
-1
Former Member

NWDS 7.5. Missing (NWDI) Development Infrastructure perspective

Hello guys,

i have just installed for the 7.50 NWDS almost all SP versions from 0 - 8 on a Windows Server 2016 environment and something is strange, i can´t see any perspective as I am used to see in 7.3 versions that allows me to connect to any development track.

There is only a new option i am not used to called "Process Integration" , but this seams to be related to a different functionality.

Can anyone help me out to get this working?

The documentation below also highlights that there is supposed to be a NWDI component visible, but nothing shows. Also within the "Preferences" i can´t find any option to maintain the URL for the SLD.

https://help.sap.com/viewer/39222f18c2ab428985c7f3e041b11e26/7.5.6/en-US/492ace185d561907e10000000a42189c.html

btw. i also tried using SP9 version, but this release seams to be not the full distribution. I is missing all executables for eclipse and contains only the plugins and feature folders

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Nov 01, 2017 at 08:00 PM

    1. NWDS 7.5 is a tool for LOCAL development. It should never be installed on Server O.S. One of the main reasons for this is - the NWDS 7.50 requires workspace located on the local drive (not a network one) 2258252

    2. NWDS 7.50 is supported only when it runs over Windows 10.

    Please check PAM and install the NWDS 7.5 on a supported O.S.

    3. Also please make sure NWDS 7.5 does use SAPJVM8. No other JVM is supported neither.

    Add comment
    10|10000 characters needed characters exceeded

  • Nov 01, 2017 at 06:09 PM
    -1

    put it in your local machine.

    nwds is not for server

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 02, 2017 at 10:24 AM
    -2

    In the past we never experienced issues with Windows Server and i would disagree with the statement, it only can run "LOCAL". Many clients have setup their developer environments within Terminal Servers and there is no statement, that NWDS is not running in Windows Server.

    My failure maybe was to assume, that it would still work on the newest Windows Server 2016 version.

    I found a log message, which indicates the issue might be with the JCO Connector plugin. It can´t be loaded hence all dependent plugins are not enabled.

    !MESSAGE FrameworkEvent ERROR
    !STACK 0
    org.osgi.framework.BundleException: Could not resolve module: com.tssap.dtr.client.vfs [1683]
      Unresolved requirement: Require-Bundle: com.sap.di.dtrclient.protocol; visibility:="reexport"
        -> Bundle-SymbolicName: com.sap.di.dtrclient.protocol; bundle-version="2.0.0.171013102333"; singleton:="true"
           com.sap.di.dtrclient.protocol [1012]
             Unresolved requirement: Require-Bundle: com.sap.base.technology.facade
               -> Bundle-SymbolicName: com.sap.base.technology.facade; bundle-version="2.0.0.171013092333"; singleton:="true"
                  com.sap.base.technology.facade [969]
                    Unresolved requirement: Require-Bundle: com.sap.jco3; visibility:="reexport"
                      -> Bundle-SymbolicName: com.sap.jco3; bundle-version="3.0.17.170906130305"; singleton:="true"
                         com.sap.jco3 [1416]
                           Unresolved requirement: Require-Capability: osgi.native; native.paths:List<String>="sapjco3.dll"; filter:="(&(osgi.native.osname~=win32)(osgi.native.processor~=x86_64))"
      Unresolved requirement: Require-Bundle: com.tssap.dtr.client.lib.deltavlib; visibility:="reexport"
        -> Bundle-SymbolicName: com.tssap.dtr.client.lib.deltavlib; bundle-version="2.0.0.171013102333"; singleton:="true"
           com.tssap.dtr.client.lib.deltavlib [1682]
             Unresolved requirement: Require-Bundle: com.sap.di.dtrclient.protocol
               -> Bundle-SymbolicName: com.sap.di.dtrclient.protocol; bundle-version="2.0.0.171013102333"; singleton:="true"
             Unresolved requirement: Require-Bundle: com.sap.base.technology.facade
               -> Bundle-SymbolicName: com.sap.base.technology.facade; bundle-version="2.0.0.171013092333"; singleton:="true"
      Unresolved requirement: Require-Bundle: com.sap.base.technology.facade; visibility:="reexport"
        -> Bundle-SymbolicName: com.sap.base.technology.facade; bundle-version="2.0.0.171013092333"; singleton:="true"
      Unresolved requirement: Require-Bundle: com.sap.di.util; visibility:="reexport"
        -> Bundle-SymbolicName: com.sap.di.util; bundle-version="1.0.0.171013082333"; singleton:="true"
           com.sap.di.util [1013]
             Unresolved requirement: Require-Bundle: com.sap.base.technology.facade
               -> Bundle-SymbolicName: com.sap.base.technology.facade; bundle-version="2.0.0.171013092333"; singleton:="true"
    	at org.eclipse.osgi.container.Module.start(Module.java:444)
    	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
    	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
    	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
    	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
    	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
    	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
    	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
    Add comment
    10|10000 characters needed characters exceeded

    • Dear Mr. Halbig,

      Whether you would agree or not is entirely up to you choice.

      In case your dtr workspace is located on a network drive - synchronization from the NWDS will simply not work.

      Moreover, you might not do anything else but accept what is stated in P.A.M. -

      you have to use Windows 10 and SAPJVM8, in case you would like to receive support about NWDS 7.5, by SAP

      Best Regards,

  • avatar image
    Former Member
    Nov 02, 2017 at 11:25 AM

    Hi guys,

    again thank you for your help. I found the solution for my problem.

    The article below is about Windows 8, but it is the same problem. The java property "os.name" is for my server edition "Windows Server 2016", but the lookup name is "win32". Since "win32" is actually not the value most people have for their system, eclipse is using a mapping table to cover up all different windows names. I assume this entry has not yet been added to the mapping table for the osgi plugin since it is a reasonable new version, so that the native library could not be found.

    https://eclipsesource.com/blogs/2013/03/28/running-eclipse-applications-on-windows-8/

    I have added therfore to the "eclipse.ini" the command to overwrite/set the system property. Furthermore i forced the system to use the JDK 1.8 version since SAP relies on that version. After the change the IDE starts up and all the missing plugins showed up

    openFile
    -vm
    C:\Progra~1\Java\jdk1.8.0_144\bin\javaw.exe
    -vmargs
    -Dorg.osgi.framework.os.name=win32
    
    Add comment
    10|10000 characters needed characters exceeded