Hi experts,

I´m having a problem when i try to make deploy of a process in nwdi. The message i´m getting is in the file i´m attaching, i am able to make deploy of others process.

Any idea of how can i solve this problem?

Thank you.

Hello All,

We are facing weird issue while login NWDI from NWDS .We used to access NWDI via sld .

Now issue is , when I try to import configuration from sld , NWDS ask to login sld , here I am able to login successfully. Now after logged in , NWDS show all available tracks , when I select any track and click finish , NWDS again ask to login NWDI and DTR , here I am able to login DTR url but not in NWDI. Both url are same except DTR at end in DTR url. Also I tried login with same url and credential in browser and able to login successfully. I am attaching screenshot what exactly I am seeing . Kindly let me know anything else needed from my side. Thanks in advance.

Regards,

Mayank Jain

Hi Experts,

In NWDI,  Build Server Setting is mentioned as http://NWDIHost:port

Please suggest.

Regards,

Samir

Hi,

Is this build variant sufficient in NWDI track ( 74 track in NWDI 7.01)  for NW74 code to run on NWDI7.01 ; or we have to actually install a JRE1.6 somehwere in NWDI / NWDI’s CBS ?

Please suggest.

Regards,

Samir

Dear Experts -

We have re-configured CM Services with Source Transport deployment(Activity based transport).After that configuration, we are trying to move a transport to the QA environment. The transport log shows successful, but users are not able to see the changes or code in the QA system which were part of the transport. We are doing with ChaRM. We tried with different transports and different objects ,but the issue is still same.

Attached the screenshots of the transport logs to this thread. Request you to please take a look at it and please provide us the resolution.

Thanks,

Nagendra.

Hi Experts,

I'm new to creation of new track and SCs.

We are currently using an SLD development track (XYR4) which has SCs with version 4. It has SCs and Dev't Components on it which are working fine in production environment. We have a new project which requires us to create a new SLD track (XYR5). The XYR5 will need to have the latest copy of the SCs and DCs of XYR4.

What we have done so far are the following:

1. Created the XYR5 track in our SLD.

2. Copied the SCs from XYR4 to XYR5 track but the SC versions in XYR5 is 4.0 not 5.0.

What we need to do:

3. Copy the DCs from XYR4 to XYR5 track.

Questions:

• Should the product version be 5.0 for the copied SCs in XYR5 instead of 4.0? What is the difference between incrementing the SC version and retaining the current version?
• What is the best approach for copying the DCs of XYR4 to XYR5 track in their respective SCs?

I have been looking for documentations/blogs but the one I found so far was about moving the DCs to a new SC. But I'm not sure if I can follow it as I'm wondering if there could be other better steps than that. I also have a doubt that moving the DCs could cause changes in the current track (XYR4) which I should not be modifying.

BTW, we are currently using NW7.2 but with the new track it will be used under an upgraded NW7.4.

Hoping to get your advises on this.

Regards,

Michael

Hi,

I have a requirement where I want just want to have some code in a central repository with versioning functionality . I don't have a requirement to build the code, so I want to know if I can go for NWDI-->Creation of tack. Please let me know if below basic steps are correct.

1) Creation of track in NWDI

2) Create a SC (Software component) under the track in NWDI

3) Download the SC to your local (NWDS)

4) Create a DC under the SC in NWDS ( SC which has been downloaded from NWDI track to your local)

5) Put your java code in these DCs (I am not bothered about their build)

6) Configure your NWDS with NWDI (Connection)

7) Check-in the code to NWDI

Any steps I am missing or any here are any corrections in the above steps needed ? Please guide.

Hello,

I am currently working for a client who has some stringent HA requirements for up and coming releases. In a nutshell they are; fully resilient, instant mean time to repair, on Active Active, And we need some help in understanding what can be done within the constraints of their available infrastructure services.

The client is using Oracle Data Guard + other measures to provide HA throughout the stack and would like to run all SAP component Active Active. However, we understand this is not possible for ASCS/SCS, which are designed to run Active Passive. We also understood ASCS/SCS require hardware clustering for automatic failover. Unfortunately hardware clustering is not something available to the client for various reasons, thus, failover of ASCS/SCS would have to be manual, which is not acceptable.

This point is the crux of my question; is it possible to run a full Active Active including ASCS/SCS? Or can the ASCS/SCS failover being automated without hardware clustering?

The client currently has NW 7.31 ABAP and 7.4 JAVA for different software components and would like HA available on both.

Thanks in advance

Laurie

Hello,

We had a contractor who upgraded our internet sales for ERP application with custom developments from ISA 7.0 to 7.32 SP 4. He created a track on our NWDI 7.3 system and resolved integration conflicts, merged our code with SAP code etc. Now that he left, we have our dev workspace and cons workspace out of sync. Which means our dev workspace has different number of DCs than our cons workspace(SC: SAP-SHRWEB). I also see there are broken DCs on the cons workspace. I am not able to perform an assembly on the cons workspace because of broken DCs. We know that the Dev workspace is perfect and working. How do we integrate or replicate the Dcs from Dev to cons workspace? Is there a way to sync up the DCs in both the workspaces?

Any help is much appreciated.

Thanks

MLS

Hello,

This is my first post here. Me and my colleagues are experiencing issues in finding NWDS 7.31 sp09 patch lvl higher than 0000

We are using this link for downloading NWDS Download Links - Java Development - SCN Wiki

Do you have any idea how can I obtain patch higher than 0000? My colleagues told me that there was a link there before, but the page is changed and now the links are different. According to the update matrix (available here) updates for 7.3x are possible using the built in update function:

• From the menu path, choose Help -> Check for Updates.

After checking, the error is that there are no new updates. We are not using proxy and we have tested it on different networks and laptops.

Any help would be appreciated.

Hello All,

I am working on nw7.01 version. I have nwdi setup in my landscape. I have imported the track in my nwds from dc perspective and from the inactive DC i have created a project. Now i am able to see the project in webdynpro perspective.  I have a requirement where i have to modify the ess benefits service. My question is suppose if I make any changes to my view and if i deploy the application through SDM then will it replace the current application that is running on the j2ee server. Appreciate any inputs on this.

Regards

Kiran.

Hi,

I have a requirement where I want just want to have some code in a central repository with versioning functionality . I don't have a requirement to build the code, so I want to know if I can go for NWDI-->Creation of tack. Please let me know if below basic steps are correct.

1) Creation of track in NWDI

2) Create a SC (Software component) under the track in NWDI

3) Download the SC to your local (NWDS)

4) Create a DC under the SC in NWDS ( SC which has been downloaded from NWDI track to your local)

5) Put your java code in these DCs (I am not bothered about their build)

6) Configure your NWDS with NWDI (Connection)

7) Check-in the code to NWDI

Any steps I am missing or any here are any corrections in the above steps needed ? Please guide.

Hi Experts,

I am facing java.lang.UnsupportedClassVersionError when am trying to run the application from nwds.

I found so many threads related to the issue and tried with the solution, but the issue still exist.

I changed java version and tried with jdk 1.4,16 and 1.7 also.

we are using jdk 1.6 version and NWDS 7.01

Below is the error trace:

java.lang.UnsupportedClassVersionError: com/sap/xss/essservices/cc/ccesspcd/wdp/InternalCcEssPcd : Unsupported major.minor version 50.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(ClassLoader.java:635)

at com.sap.engine.services.deploy.server.ApplicationLoader.defineClassWithInterception(ApplicationLoader.java:168)

at com.sap.engine.services.deploy.server.ApplicationLoader.loadLocalClass(ApplicationLoader.java:140)

at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:127)

at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)

at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)

at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:208)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)

at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:187)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Please help me out from this.

Hi dear SAP Community,

We need to migrate existing project in nwdi infrastructure.

The project is quite old and has a very long history (in terms of SVN).

Is it possible to migrate the SVN history into DTR?

How to do this?

Thanks in advance.

Best Regards

Sergey

Hi Experts,

Currently we have an existing dev config in our NWDI (let's say track1) and this is the code version we have in production. We have a requirement to create a new dev config in the same NWDI server (let's say track2). I need to copy all the SCs and DCs from track1 to track2 so that we can apply our codes on top of the SCAs from track1.

I've been reading posts and answers about this, until I found some about "forward operation" in CMS Approval tab.

What I have done so far are the following:

1. Opened track1 in CMS, I have Approved the most recent SCs(target SCs to be copied to track2) that are pending for approval in Approval tab of CMS.

2. Still with track1 in CMS, I clicked "Forward from History" button, selected the SCs I approved, populated track2 in "Target Track" and executed "Forward".

3. Opened track2 in CMS (same NWDI server), and opened "Development" tab. I found the SCs I forwarded from track1 and they were ready for import. I selected the SCs and imported them successfully.

4. In NWDS - Development Infrastructure, I imported the track2 from SLD, and I found all the DCs under the SCs I have forwarded from track1 to track2.

5. In my NWDS - Development Infrastructure, I right clicked on each DCs and created project. The download of project per DCs is successful.

Questions:

1. Will this approach copy also the sources codes?

2. If I modify the source codes in track2, will it be independent from the activities in track1 or vice versa?

3. Am I missing anything in what I described above that could cause issues in the future?

I just need expert opinions on this as the descriptions in help.SAP did not quite explained to what purpose we can use forward operation and what are the limitations.

Thanks in Advance!

Michael

Hi Team,

I've found this thread many times and everywhere it has been mentioned that we should delete the workspace and dev config files and reimport the development configuration. But nothing seems to work for me. Hopefully we can look a this issue with anther angle freshly here.

Problem:

1. Import of Dev config from SLD Successful ie the 3 logs to SLD, DTR and NWDI shows successful and the DTR structure in the DEV Config is visible and expandable.
2. After I close the NWDS and try to reaccess the dev configuration. Login at NWDI gets denied citing the following error

eclipse.buildId=@qualifier@

java.version=1.6.0_25

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en

Command-line arguments:  -os win32 -ws win32 -arch x86

 

 

 

 

Error

Wed Dec 02 09:30:17 EST 2015

set Online of C:\Users\biswas.v\Desktop\P&G\eclipse\workspace.jdi\1\ failed      [Error: com.sap.ide.dii05.lib.internal.login.AbstractDevConfContext  Thread[Worker-5,5,main]]

 

 

com.sap.tc.devconf.login.LoginException: com.sap.tc.devconf.DevConfigException: VFS client must not be <null> (VFS client must not be <null>)

at com.sap.tc.devconf.internal.DevelopmentConfiguration.performLogin(DevelopmentConfiguration.java:5124)

at com.sap.tc.devconf.impl.login.LoginContext.login(LoginContext.java:56)

at com.sap.ide.dii05.lib.internal.login.AbstractDevConfContext.goOnline(AbstractDevConfContext.java:348)

at com.sap.ide.dii05.lib.internal.login.AbstractDevConfContext.setOnline(AbstractDevConfContext.java:283)

at com.sap.ide.dii05.ui.internal.login.DevConfContext.setOnline(DevConfContext.java:50)

at com.sap.ide.login.ui.LoginDialog$2.run(LoginDialog.java:469)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Caused by: com.sap.tc.devconf.DevConfigException: VFS client must not be <null>

at com.sap.tc.devconf.impl.dtr.VFSHandler._findOrCreateBuildServer(VFSHandler.java:121)

at com.sap.tc.devconf.impl.cbs.CbsServiceAdapter.initializeBuildServer(CbsServiceAdapter.java:85)

at com.sap.tc.devconf.impl.cbs.CbsServiceAdapter.initializeBuildSpace(CbsServiceAdapter.java:67)

at com.sap.tc.devconf.impl.cbs.CbsServiceAdapter.getInitializedBuildSpace(CbsServiceAdapter.java:57)

at com.sap.tc.devconf.internal.DevelopmentConfiguration.initializeBuildSpaceProxy(DevelopmentConfiguration.java:4455)

at com.sap.tc.devconf.internal.DevelopmentConfiguration._goOnline(DevelopmentConfiguration.java:4405)

at com.sap.tc.devconf.internal.DevelopmentConfiguration.performLogin(DevelopmentConfiguration.java:5121)

... 6 more

 

eclipse.buildId=@qualifier@

java.version=1.6.0_25

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en

Command-line arguments:  -os win32 -ws win32 -arch x86

 

 

 

 

Error

Wed Dec 02 09:30:17 EST 2015

An internal error occurred during: "Logon to".

 

 

java.lang.NullPointerException

at com.sap.ide.dii05.lib.internal.login.AbstractDevConfContext.setOnline(AbstractDevConfContext.java:299)

at com.sap.ide.dii05.ui.internal.login.DevConfContext.setOnline(DevConfContext.java:50)

at com.sap.ide.login.ui.LoginDialog$2.run(LoginDialog.java:469)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Please help here. I haev tried many things over many days not sure which this ....

Regards,

VB

Hi,

We are seeing error while building the migrated DC (we removed depreacted dependancies), below is the error. Also, below is the image of New DC's dependencies.

ERROR: N:\NWDS Install Files\workspace.jdi\LocalDevelopment\t\9D46F866BA01AE3BBC7DC169104B9248\gen_wdp\packages\useradminmaint\UserAdminMaint.java:66: package com.sap.security.core.securitypolicy.assertions does not exist

     [javac] ERROR: import com.sap.security.core.securitypolicy.assertions.SecurityPolicyConstants;

     [javac] ERROR: ^

     [javac] ERROR: N:\NWDS Install Files\workspace.jdi\LocalDevelopment\t\9D46F866BA01AE3BBC7DC169104B9248\gen_wdp\packages\useradminmaint\UserAdminMaint.java:75: package com.sap.security.core.securitypolicy does not exist

     [javac] ERROR: import com.sap.security.core.securitypolicy.*;

[javac] ERROR: ^

Below are the dependencies :

Please let know, if we are missing anything or can add some dependencies to get rid of this build error.

Regards,

Samir

Dear Experts,

during migration of webdynpro java dc from 7.0 to 7.3 i am getting errors like

sun.awt.image.image cannot resolved and com.sap.tc.webdynpro.clientserver.uielib.standard.impl

does not exist,kindly guide me to resolve the issue.

Thanks  & Regards ,

Smruti Ranjan Moharana

I am patching my EHP1 for SAP Netweaver 7.0 ESS Portal landscape (DEV, CON, TEST, PRD ) with the most current Support package stack. (17) I use NWDI/NWDS for the Portal Java development for the ESS portal.  In the stack there is no ESS patch but there are technical patches.  Normally with each stack I copy/create a new track for the new packages for the stack.  In this case the only packages in the stack are technical. ( EPBUILD17, SAPJEE17, SAPBUILD17, SAPJTECH17)  Do I need to create a new track in NWDI or can I just apply the technical packages to the current track?

Hi Experts,

We are doing the 7.01 to 7.4 migration for the WebDynpro Java applications ;

Please suggest us the missing DC or the replacement for deprecated DCs below