NWDI Versions

I have read this document: NWDI vs. NWDI content
however, I'm having some doubts about it.
I'm currently on a project at a client trying to bring UCES online with some custom development.
I have 2 issues, this is one of them.
The Java AS is a separate box running Netweaver 7.00.
The NWDI system is on Netweaver 7.4.
I have created a track with 7.00 template and wrote a very simple "Hello World" application with a JSP page and a Java class in the WAR DC.
Everything compiled fine but I got a runtime error on the Java AS box:
class file has wrong version 50.0, should be 48.0
Please remove or make sure it appears in the correct subdirectory of the classpath.
So I'm wondering:
if the CBS of NWDI is on 7.4 and uses SAP JVM 6 to compile the SC, when it goes to the Java AS, which is on 7.00 running JVM 4, isn't there going to be a conflict?
and is there a way to tell CBS to use JVM 4 to compile my 7.00 track?
Thanks!
Eddy

Stefan,
Thanks for the info!
I have completed the following:
1. installed JDK1.4.2 on the NWDI
2. added key/value pair for JDK1.4.2_HOME in JDK_HOME_PATHS in CBS (left BUILD_TOOL_JDK_HOME blank)
3. added com.sap.jdk.home_path_key=JDK1.4.2_HOME to the default variant
Now I'm getting errors in NWDS when trying to compile:
Error: com.sap.tc.buildplugin.util.BuildPluginException: No JDK_HOME_PATH defined for key 'JDK1.4.2_HOME'
Is there something on the NWDS side I need to set?
Thanks!
Eddy

Similar Messages

Need latest SLD and NWDI version for PI 7.1 EHP1

Can any one update me the latest SLD and NWDI version for PI 7.1 EHP1?
Kindly provide me the path of implementation guides for SLD, NWDI which can be used with PI 7.1 EHP1. For PI 7.1 EHP1, can we use the same version of SLD and NWDI which used IN PI 7.1?
Please help me for the above questions.
Regards,
Yuvaraj.

Hi Yuvaraj,
Please check the NWDI Development Infrastructure 7.11 and SLD 7.11 for the PI 7.1 EHP1.
Go to Service Market Place - Software Download > Support Packages and Patches > Support Packages and Patches - Entry by Application Group > SAP NetWeaver and complementary products > SAP NETWEAVER PI > SAP EHP1 FOR SAP NW PI 7.1 >Entry by Component > Development Infrastructure.
Hope it will helps
Regards
Arun Jaiswal

NWDI version compatibility

Hi,
Does anyone know if there are any version compatibility constraints developing Java WebDynpro applications on an NWDI (WAS6.40) for deployment on a WAS7.00 instance (e.g. JDK's)?
I've yet to find a general recommendation similar to that seen for SLD (i.e. keep in line with the highest WAS version on the estate) or any clear documentation on version compatibility across WAS stacks with respect to NWDI.
We have a highly complex landscape with multiple component/ product versions, and we'd prefer to have a singel central NWDI instance, but I'm not sure if this is practical and/ or possible.
Any pointers/ documentation/ comments gratefully received
Cheers
Neil

While I can't remember where I've seen it, SAP does recommend that the DI always be kept patched to the latest levels, regardless of what version your landscape (or pieces thereof ) is at.
So, as long as your DI is at patched to at least the same level as your most 'advanced' system, you should not have any problem. You should also match your Developer Studio to the same level as your target system to avoid using any plug-ins that offer features not offered by the eventual runtime system. Yes, the required libraries will be ok (as long as you configure the SLD and the associated track correctly), but the Developer Studio itself needs to be matched up.
Hope that makes sense.

NWDI Version Level confusion

Hi all,
We will have two Portal landscapes (DEV.QAS and PRD):
1. NW04s SP15
2. NW04s SP09
The NWDI system (currently at NW04s SP09) will support development for both the above landscape/runtime systems.
What version/SP level should the NWDI system be at? Should it be at the latest SP level?
Any insights will be greatly appreciated. Thanks!
Regards, Neeta

Hi Neeta,
it will be better if it is at SP09 as per your landscape.
or you can go to higher version i.e. any SP level. but keep the dependencies compatible for SP09
as DI build at lower version can run on higher version WAS.
as downward compatiblity. But a DI build at higher version may not work on lower version WAS

Higher Track version as NWDI itself possible?

Hi,
we have currently NWDI Netweaver 7.0 SP14.
Is it possible to use this NWDI version to manage a track which is Netweaver SP18 based?
Thanx, Andi Lorinser

Well,
after the discussion I'm a bit confused.
What I heared so far: we should always use a NWDI-Installation, which is very joung, let's say NW7.0/SP18. Then Tracks should be managable, even if their code is older (let's say SP14).
And now my question. What if we have the other way round?
We have currently NWDI SP14 on our Portal DEV - Server and, before we upgrade, we must already prepare some jounger software tracks (e.g. SP18) before we upgrade NWDI itself. Is this allowed or not?
Thanx A.Lorinser

Error while check-in CAF DC on NWDI "No prefix found"

Hi experts!
I receive The following error when I try to Check-in a CAF DC on NWDS.
FAILED: No prefix found for development component "mycompany/name/caf/dictionary"
Appropriate development component prefix should be configured in SLD (Restart IDE after reconfiguring SLD).;
I already tried the solutions described on this threads:
Error while Check-in DC's on NWDI: No Prefix found for DC
Problem With Checkin
CAF check-in to NWDI error
No prefix found for development component
None solved to me.
After I receive that error message I did:
- Reserved the name prefix "mycompany/name/caf" on SLD on category "Development Component Name" with purpouse "Used everywhere"
- Enabled the option "Enable this SLD as Name Server for NWDI"
- Registered the NWDI on SLD as "Landscape" with type "NWDI Systems" and two systems, one with type CMS and another with type SLD.
- Stop/Start SLD
- Stop/Start NWDI
- Update CMS on NWDI.
The problem is still happening. The NWDI version is 7.1 SP4.
Any ideas?

Thanks Jan! It solved!
I have already created another workspace after all the tests just to be sure that the problem wasn´t on NWDS.
It solved to me when I removed the reservation on SLD and recreated.
Thank you so much!
Gabriela

Migrating/Upgrading NWDI from 7.0 to CE 7.1

Hi,
Currently we have application developed on NW 7.0 (Web Dynpro, J2EE, EJB etc) and we have NWDI 7.0 for code repository.
Now we are planning to migrate the NW 7.0 (Web Dynpro, J2EE, EJB etc) to CE 7.1 (we have documents & procedure to do this).
My question is:
1. Does repository NWDI 7.0 supports for all kind of DC/applications if we migrate NW 7.0 (Web Dynpro, J2EE, EJB etc) to CE 7.1, If not what are the chanllenges?
2. Is it required to upgrade repository from NWDI 7.0 to NWDI CE 7.1? If so how we can achieve/migrate the code to NWDI 7.1
Please suggest.
Regards,
Patana

Hi Patana,
Let me give you some background first...
*1) Yes, NWDI 7.0 will support all the developments that you will be migrating to CE 7.1
2) There is no 7.1 version of NWDI, that means you ned not worry about NWDI version as, it is just a platform that acts as repository for your source code and version control.*
So you don't need to upgrade your NWDI.
But wait it doesn't mean that you don't have to upgrade anything from NWDI side .
As your Application Server will now be running on 7.1 version, you will have to get a compatible CE 7.1 version of developer studio too.
Also the Tracks that are present in your NWDI 7.0 version will be required to be upgraded with the latest build time dependent SCA files of the 7.1 version too.
This is a step-by-step guide for setting up NWDI for Composition Environment.
Link:[HOW TO SETUP AN NWDI TRACK FOR COMPOSITION ENVIRONMENT DEVELOPMENT (SAP NETWEAVER CE 7.1)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
To update all the tracks with the latest .SCA files, follow the below mentioned steps...
1) you need to copy all the standard .SCA files of 7.1 version from the path /usr/sap/<SID>/SYS/EPS/buildarchives/ as mentioned in step 10 of the above manual to the CMS transport directory (<specified in the domain tab>CMSinbox) directory in order to make these dependencies available for your tracks.
2) Then, in SLD you have to modify all your software components that are used in track and replace all their build time dependencies to the 7.1 version.
3) Update the CMS,
4) Remove and add the tracks SCs back for your track.
5) Save the track, while saving always choose Save & Re-import button.
6) Check-In the latest 7.1 version SCA into Development and Consolidation tab.
You have repeat this for all the tracks.
Please revert in case of any further clarification.
You can also refer to the thread Re: source code of a track nwdi, for understanding how NWDI works under the hood.
Regards,
Shreyas Pandya

NWDI 7.01 DC Build failed in variant "null"

We have installed a new NWDI, version 7.01.03, created the track with 5 SCs, and imported the 4 required components EP_BUILDT, SAP-JEE, SAP_BUILDT, and SAP_JTECHS. Everything looks good with the track, I then imported the congifuration into NWDS. I then created a new DC and imported a par file - the files look good and the used DCs have been assigned. When I try to build the DC I am getting the following error:
Build failed for compass-usa.com/cgad/custmh(compass-usa.com_CPMCONT_1) in variant "null": null.
I was able to create a new DC yesterday that I was able to build. The difference that I can see is in the gen folder, the one that errors on the build has a subfolder called null, the one that works has a sub folder called default. Any ideas what the problem could be, what may have changed?
Thanks,
Jeff Mathieson

I know that this is an old thread, but I had a similar issue. I hope this will add some value by posting my solution
The "buildvariant.config" file seams to be only written, when you import a "Developer Configuration" to your local NWDS. If you modify later on the Track, this file does not get updated even if this nice fancy popup is informing you about changed configurations - obviously somebody missed to include updates to the "buildvariant.config" file.
Simple solution is, that you completely remove the whole "Developer Configuration" for the track, which you modified within the NWDI. Once it is remove, just re-improt it and the file gets updated.
I would not manually modify it as the system knows better which associated SCs are also required to be added beside the SC, which you added to your Track.
Cheers,
Andreas

Unable to Deploy a Webservice.

Hello All,
I created a java bean and put the implemented code in some of the methods etc. ( By the way the code is generated using a WSDL using the SAP Netweaver libraries )
Now when I attempt to actually create the webservice out of the implemented Java Bean.
( By right click - > Webservice -> Create webservice.)
It create the EJB Jar and also create EJB EAR file but I am unable to deploy this EAR archive.
It throws following exception trace :
Can any of you please throw some light on this . ?
I am using NWDS Ce 7.1 SP05 .
Can we get this problem if the NWDS and NWDI are not in Same version and same patch ?
IWAB0014E Unexpected exception occurred.
Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
      java.lang.IllegalArgumentException: Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
      at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.invokeMethod(DataFlowManager.java:275)
      at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.process(DataFlowManager.java:124)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:411)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358)
      at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:253)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:252)
      at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
      at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
      at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:222)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:96)
      at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:147)
      at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
      at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
      at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
      at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
      at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
      at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
      at org.eclipse.jface.window.Window.open(Window.java:796)
      at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
      at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
      at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
      at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
      at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
      at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
      at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
      at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
      at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1144)

Hi Ravi,
can you please indicate the NWDS and NWDI versions and JDK being used?
Regards,
Désiré

NWDS Build Error JDK_HOME_PATH not set

Hi,
I am having two problems.
1. I am getting the classic
     Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'
This is the whole log,
Jul 24, 2014 3:12:01 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: ess/sg/fam: Build failed for sap.com/ess/sg/fam(sap.com_SAP_ESS_1) in variant "default": The Build terminated with errors
------------------------------------- Build log ------------------------------------------------------
Development Component Build (2014-07-24 15:11:51)
Component name: ess/sg/fam
Component vendor: sap.com
SC compartment: sap.com_SAP_ESS_1
Configuration: ND1_EHRESS_D
Location: ND1_EHRESS_D
Source code location: http://zq4c1:50100/dtr/ws/EHRESS/sap.com_SAP_ESS/dev/inactive/DCs/sap.com/ess/sg/fam/_comp/
DC root folder: C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\
DC type: Web Dynpro
Host: zq4c1
DC Model check:
   All used DCs are available locally
   validating dependency to build plugin "sap.com/tc/bi/bp/webDynpro"
   validating dependency to public part "default" of DC "sap.com/tc/col/api"
   validating dependency to public part "default" of DC "sap.com/tc/cmi"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/ddicruntime"
   validating dependency to public part "default" of DC "sap.com/tc/ddic/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/tc/wd/webdynpro"
   validating dependency to public part "default" of DC "sap.com/tc/logging"
   validating dependency to public part "default" of DC "sap.com/tc/wdp/metamodel/content"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.proxy.framework"
   validating dependency to public part "default" of DC "sap.com/com.sap.aii.util.misc"
   validating dependency to public part "default" of DC "sap.com/com.sap.exception"
   validating dependency to public part "default" of DC "sap.com/com.sap.mw.jco"
   validating dependency to used DC "sap.com/pcui_gp/xssfpm"
   validating dependency to used DC "sap.com/pcui_gp/xssutils"
   validating dependency to used DC "sap.com/ess/per"
   DC model check OK
Start build plugin:
   using build plugin: sap.com/tc/bi/bp/webDynpro
   starting build plugin from : C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\tc\bi\bp\webDynpro\_comp\gen\default\public\webDynpro\
Build Plugin 'WebdynproPlugin', Version 7.00 SP 15 (645_VAL_REL, built on 2008-02-16 00:51:04 CET, CL79160)
   development component: ess/sg/fam (sap.com)
      software component: SAP_ESS (sap.com)
                location: ND1_EHRESS_D
                    type: Web Dynpro
           build variant: default
         output location: C:\Documents and Settings\nd1adm\.dtc\1\DCs\sap.com\ess\sg\fam\_comp\gen\default
       generation folder: C:\Documents and Settings\nd1adm\.dtc\1\t\9BEBB9B83BED543CBB6BD26A34D713CE
       plugin start time: 2014-07-24 15:12:00 GMT+08:00 (SGT)
                 Java VM: Java HotSpot(TM) Client VM, 11.0-b15 (Sun Microsystems Inc.)
General options:
convert *.xlf to *.properties: yes
include sources for debugging: yes
Warning: Source folder "META-INF" does not exist and will be ignored.
Checking path lengths for sources
Path length checks finished in 0.265 seconds
Preparing data context..
No public part descriptor found for component "tc/col/api" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/cmi" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/ddicruntime" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/ddic/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wd/webdynpro" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/logging" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "tc/wdp/metamodel/content" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.proxy.framework" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.aii.util.misc" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.exception" (vendor "sap.com"), public part "default", using legacy mode.
No public part descriptor found for component "com.sap.mw.jco" (vendor "sap.com"), public part "default", using legacy mode.
Error: com.sap.tc.buildplugin.util.BuildPluginException: No JDK_HOME_PATH defined for key 'JAVA_HOME'
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaCompiler(JavaMacroContextProvider.java:235)
at com.sap.tc.buildplugin.JavaMacroContextProvider.setupJavaEnvironment(JavaMacroContextProvider.java:180)
at com.sap.tc.buildplugin.JavaMacroContextProvider.execute(JavaMacroContextProvider.java:35)
at com.sap.tc.buildplugin.PrepareContextBuildStep.prepareTechnologySpecificData(PrepareContextBuildStep.java:187)
at com.sap.tc.buildplugin.PrepareContextBuildStep.setupBuildFileCreatorContext(PrepareContextBuildStep.java:95)
at com.sap.tc.buildplugin.PrepareContextBuildStep.execute(PrepareContextBuildStep.java:56)
at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:196)
at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:168)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:5633)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction.buildDCs(DcCreateProjectAction.java:1027)
at com.sap.ide.eclipse.component.provider.actions.dc.DcCreateProjectAction$1.execute(DcCreateProjectAction.java:299)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:71)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
Error: Build stopped due to an error: No JDK_HOME_PATH defined for key 'JAVA_HOME'
Build plugin finished at 2014-07-24 15:12:01 GMT+08:00 (SGT)
Total build plugin runtime: 1 second
So what am I doing?
I am trying to do? I am trying to sync the sources. (attachment snc2.png)
I already changed/added the java home at 3 locations,
Visual administrator (attachment snc3.png)
vmparam file (attachment snc4.png)
I downloaded all the java versions are 32 bit.
But even after doing all these I am still facing the issue.
My NWDI version and details.
are ver. 7SP15
and NWDS is 7.0.12
And the NWDS when I clicked on configuration details I noticed this log and the first few lines are really fishy..
** Date: 7/24/14 4:36 PM
*** System properties:
JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10
JDK1.4.2_HOME=C:\j2sdk1.4.2_17
JDK1.4_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10
allUserDir=C:\Documents and Settings\All Users\Application Data
awt.toolkit=sun.awt.windows.WToolkit
Notice that JDK1.3.1_HOME=C:\Program Files (x86)\Java\jdk1.6.0_10, it is pointing to jdk1.6.0, but where to change to that? is this the issue?
Tried all possible things and solutions that I could find online but no use.
2
I have problem with the server (DTR) keep disconnecting once in a while, it says
DTR server http://<hostname>:50000 unreachable.
Socketclosed...
temporarily what i am doing is that to restart my instance from mmc and that works for a while, I believe it is the FQDN name that I have to change for the dtr, but where can I change that? and also what is the reason that it is able to connect the first few times when i restart the server but not later?
Thanks for your time.

No, that is not the issue, it was already set as well. But apparently have to change the buildpath in the build variant in the CBS

Problem synching SAP_BUILDT

I've created a new SC/track/Dev Config, imported the Dev Config, and am creating a new Dictionary type Development Component. I get the following warning.
May 9, 2006 4:21:10 PM /userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[main,5,main]] WARNING: jdidemo/msg/dic: Sync used Dcs: Failed to sync used archives from compartment : sap.com_SAP_BUILDT_1
I've done this successfully before. The only difference I can think of is that before I was using NWDI SP 15 with NWDS SP 15 (and NWDS SP 13). In this casse I'm using NWDI SP 13 with NWDS SP 15. (I'll be deploying to an SP 13 system.) Does anyone think the discrepancy between the NWDI version and the (higher) NWDS version could be the problem? Or any other suggestion? The source of my required .SCA files was
<sap-dir>/<SID>SYS/global/CMS_CBS/plugins
on the SP 13 system, so I'm confident they are the correct version (SP 13) of the archives.

Pascal,
I had checked CBS: 38 DCs for SAP_BUILDT SP 13 (41 for SP 15).
At the moment, I don't have the luxury (time) to swap in and out different versions of NWDS. I do understand the importance of NWDS and NWDI being at the same level, and I've had other problems in the past when they weren't.
But those problems deal with functionality. At least as a matter of speculation, can you think why the version of NWDS should matter regarding the required archives (like SAP_BUILDT)? I declare the proper dependency in SLD; I copy into the transport directory, check in and import the correct version of the physical files into the CBS archive pools; I import the Development Configuration, which pulls in the required archives. What is it about a (slightly) higher version of NWDS that would prevent the archives from synching? I can't believe the synching functionality changes from NWDS version to version? Again, at least as a matter of speculation, what do you think?

Unable to deploy workshop webservice (8.1SP2)

I have recently upgraded to WLS8.1SP2, created a workshop domain, deployed a workshop webservice application using ant and ran into the below error. Please help!
deploy:
[wldeploy] weblogic.Deployer -debug -remote -upload -noexit -name spider -sourc
e \opt\sfc\spider\local\spider.ear -targets -adminurl t3://127.0.0.1:7001 -user
admin -password ******** -deploy
[wldeploy] DeploymentData : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] Files:
[wldeploy] null
[wldeploy] Initiated Task: [0] [Deployer:149026]Deploy application spider on cg
Server.
[wldeploy] Task 0 failed: [Deployer:149026]Deploy application spider on cgServe
r.
[wldeploy] Deployment failed on Server cgServer
[wldeploy] dumping ApplicationException message
[wldeploy] Exception:weblogic.management.ApplicationException: prepare failed f
or avsWebSvc
[wldeploy] Module: avsWebSvc Error: Could not load avsWebSvc: weblogi
c.management.DeploymentException: [HTTP:101283]ServletContext(id=1223009,name=av
sWebSvc,context-path=/avsWebSvc): jspServlet "weblogic.servlet.WlwJSPServlet" de
fined in weblogic.xml could not be loaded.
[wldeploy] java.lang.ClassNotFoundException: weblogic.servlet.WlwJSPServlet
[wldeploy] at weblogic.utils.classloaders.GenericClassLoader.findClass(Gene
ricClassLoader.java:198)
I double check the classpath and knex.jar is definitely on the classpath server startup script:
CLASSPATH=C:/opt/bea/weblogic81/common/lib/jms1.1.jar:C:/opt/bea/weblogic81/serv
er/lib/weblogic_knex_patch.jar:C:/opt/bea/weblogic81/common/lib/log4j.jar:C:/opt
/bea/weblogic81/server/lib/debugging.jar:C:/opt/bea/weblogic81/server/lib/knex.j
ar:C:/opt/bea/weblogic81/javelin/lib/javelin.jar:C:/opt/bea/weblogic81/server/li
b/wlw-lang.jar:C:/opt/bea/jdk141_05/lib/tools.jar;C:/opt/bea/weblogic81/server/l
ib/weblogic_sp.jar;C:/opt/bea/weblogic81/server/lib/weblogic.jar;C:/opt/bea/webl
ogic81/server/lib/ojdbc14.jar:C:/opt/bea/weblogic81/server/lib/ant/ant.jar:C:/op
t/bea/jdk141_05/jre/lib/rt.jar::C:/opt/bea/weblogic81/server/lib/webserviceclien
t.jar:C:/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:C:/opt/bea/weblo
gic81/server/lib/xbean.jar:C:/opt/bea/weblogic81/server/lib/wlxbean.jar:C:/opt/b
ea/weblogic81/server/lib/xqrl.jar:C:/opt/bea/weblogic81/server/lib/netui/netui-c
ompiler.jar:C:/opt/bea/weblogic81/server/lib/wli.jar:C:/opt/bea/weblogic81/serve
r/lib/fop.jar:C:/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.j
ar:

Hi Ravi,
can you please indicate the NWDS and NWDI versions and JDK being used?
Regards,
Désiré

Cannot select vendor when creating new DC

Hi all,
I'm using NWDI, version is 7.14.
When I try to create a new DC the vendor dropdown is disabled and all I see is sap.com (see snapshot - http://img390.imageshack.us/my.php?image=newprojectjq3.jpg).
I have opened several projects in the past with no problem (and I could choose my own vendor, the one I created in the SLD).
How can I solve this?
Thanks,
Omri

Hi Pascal,
I don't see any errors in the NWDS log file:
!SESSION נוב 17, 2008 11:07:54.359 -
java.version=1.4.2_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=iw_IL
Command-line arguments: -os win32 -ws win32 -arch x86 -feature com.sap.java.ide C:\j2sdk1.4.2_09\bin\javaw.exe
-Xmx512m
-Xms128m
-XX:PermSize=32m
-XX:MaxPermSize=128m
-DallUserDir='C:\Documents and Settings\All Users\Application Data'
-cp C:\Program Files\SAP\IDE\IDE70\eclipse\SapStartup.jar com.sap.ide.eclipse.startup.Main
-os win32
-ws win32
-arch x86
-feature com.sap.java.ide
-showsplash C:\Program Files\SAP\IDE\IDE70\eclipse\SapIde.exe -showsplash 600 -data C:\Documents and Settings\mmm\Documents\SAP\workspace -install file:C:/Program Files/SAP/IDE/IDE70/eclipse/
!ENTRY Startup 1 0 נוב 17, 2008 11:07:54.359
!MESSAGE Sap NetWeaver Developer Studio - Build: 200711102147
Under http://<server>:<port>/dtr/system-tools/administration/NameServerConfiguration I see the following URL: http://<server>:<port>/sld/cimom with nwdi admin user and password and 'TrustedCAs' as 'Trusted Store'. I only have entries under the 1st name server (the 2nd is empty).
When I navigate to http://<server>:<port>/sld/cimom I get 'This is the location of the SLD CIM Object Manager that processes WBEM requests (CIM operations over HTTP).'
When I check the name server prefix 'haifa.ac.il/hu' in the SLD the 'Disable this SLD as Name Server for NWDI' button is active...
Regards,
Omri

NWDS: can't select dev. component type

Hello Community,
I'm using a NWDI System in Version 7.4 SP9.
I want to develop for my PO System 7.4 SP6, so I selected the NWDI version 7.3-EHP1-SP11-PAT0010.
The NWDI is configured with CMS. It's attached to the SLD of the PO-dev system.
I created a track for my project and created a SC with the wizard and selected "Composite Application 7.40 (with Business Process Management)" from the templates, so the dependencies should be set correctly.
I imported the configuration in my NWDS but I can't select a development component type. No one is active. See attached screenshot:
I want to use Java EE.
How can I fix this?
best regards
Bastian

Hi Bastian,
this is becaus if missing SC imports in CMS webui (Transport Studio).
See more at :
1584553 - Cannot create DC project due to DC types being grayed out in NWDS DC project creation wizard
Best Regards,
Ervin

DTR Migration

Greetings--
I need some help understanding DTR projects and if its possible to migrate closed activities onto another system or can this ony be done via Java System Copy?
We are currently using DTR for storing portal projects that are sdeveloped in eclipse, we now have been tasked to move NWDI onto another piece of hardware.
My question is: Since we are only using DTR and not CBS/CMS/SLD, can I simply migrate closed activites onto a separate installation (the will be 2004s).
Original NWDI version (NW04 SPS18)
Proposed NWDI verions (2004s SPS18)
-John

The way that we did was to manually move all the DCs to the new NWDI server. I am not sure if there is an automated way of moving the DTR workspaces from one system to other.
The method we followed was similar to moving the local DCs to NWDI. Follow this blog, it might be helpful.
/people/raj.peddisetty/blog/2007/03/02/migrating-localdcs-onto-jdinwdi-track
Revert back with questions.

NWDI Versions

Similar Messages

Maybe you are looking for