Quantcast
Channel: SCN : Unanswered Discussions - SAP NetWeaver Development Infrastructure (NWDI)
Viewing all 562 articles
Browse latest View live

NWDS 7.01 updates

$
0
0

Hi,

I'm using SAP Netweaver Developer Studio Version 7.01.06 (build id 201001061835).

I was wondering if there was some update of the NWDS running on JDK 1.4.2 that I could use.

Thank you,

Pietro


Consuming webservice in SAP ECC

$
0
0

Hi Experts,

 

We have a requirement in which we query data from an oracle based system directly from ECC (Without using XI/PI). Oracle guys have developed an API and have shared the WSDL with us. I am trying to create a proxy using the WSDL URL in SE80, but the system is not allowing me to create the proxy using the URL. It is giving the following error message when I am trying that - 'Proxy generation terminated: Message must have exactly one part'.

 

When I reached ORACLE folks with the above message, they said that its the standard that standard they are following and splitting it into single parting is not possible. I read in one of the SCN thread that SAP NetWeaver 7, Service Pack 14 onwards should support multiparting. We are on SAP NetWeaver 7, Service Pack 21, but still getting this message. Please guide.

 

Warm Regards,

Manjunatha

Ping on server 'http://hostname:port/dtr/' failed (server might not be available) - Read timed out

$
0
0

HI expert,

we are getting this warning

Ping on server 'http://hostname:port/dtr/' failed (server might not be available) - Read timed out

when im trying to checkout any component in my nwdi , the version of nwds is 7.31 , the activity view im not able logon and when im trying to check out above error is occuring please suggest a solution.

 

 

 

Regards

Govardan Raj

NWDI Track duplicate issue

$
0
0

Hello Expert,

 

Recently we were asked to create a new NWDI track and SCs. We were able to created a new track from scratch successfully, but for some reason, whenever the developer made any code changes from one track, the other track changes got reflected too. Not sure how has this happened...Also how do we migrate the DC from one track to another on the same SLD.

 

Your help is greatly appreciated.

SPM Portal Launch Error

$
0
0

Hi All

 

While login into the SPM portal as the portal launches the landing page it returns the below bug , we have not as yet maintained dimension nor measures as yet,

 

 

The error below is automatically return on portal launch

 

Failed to open cube <html><head><title>Application Server Error</title>

</head><body onKeyDown='return KeyDown();' onKeyUp='KeyUp();'>

<H2><b>503 Service not available</b></H2><br>

<hr>Fri Aug 7 18:49:23 2015

</body></html>

 

If you could please maybe advise

 

Thanks again


Regards

 

khuliso

NWDS and NWDI Handshake issue for SAP PO BPM development

$
0
0

Hi,

 

We have installed SAP PO 7.4 SP11 (Single Stack) and NWDI. PO and NWDI are installed in separate host.

We have followed SCN documentHow to setup NWDI with CM Services and CTS+ for Process Orchestration  to setup NWDI and it appears OK.

 

After NWDI setup, we followed below steps

 

1) Created a new Software Component (Axx_P2PCONTRACT_BPM) in SLD of PO

2) Created following dependencies for the same Software component in PO SLD

  • MOIN BUILD TOOL 7.4
  • DI BUILD TOOL 7.40
  • ESCONF BUILD TOOL 7.40
  • BPEM CONTENT 7.40
  • COMPOSITION BUILD TOOL 7.40
  • BPEM-BUILDT 7.4

 

3) Imported this software component in NWDI

4) After the import in NWDI, we only see DI BUILD TOOL 7.40 as the only dependency.

5) From NWDS, logged to NWDI development configuration and imported the newly create Software component.

6) In NWDS created a new Netweave BPM process under this Software component, However, when i tried to build in NWDS, i am seeing following error.

 

Build failed for axx.com/p2pcon (axx.com_Axx_P2PCONTRACT_BPM) in variant "default": Illegal component usage: compartment "axx.com_Axx_P2PCONTRACT_BPM" does not use compartment "sap.com_BPEM-BUILDT" of used DC "sap.com/tc/bpem/bi/bp/buildtool"

Build failed for aol.com/p2pcon (axx.com_Axx_P2PCONTRACT_BPM) in variant "default": Check for used DCs failed: Illegal component usage: compartment "axx.com_Axx_P2PCONTRACT_BPM" does not use compartment "sap.com_BPEM-BUILDT" of used DC "sap.com/tc/bpem/bi/bp/buildtool"; using DC: com.sap.tc.devconf.internal.DCProxyMake@ee454

 

I am not sure why we are getting this error. Any help is appreciated.

 

Thanks

-Pradeep

NWDI crash/ Restore DC's

$
0
0

Hi Team,

 

We had NWDI setup (single instance) hosting two application environments. Unfortunately the system got corrupted and there is no backup was

restored from DB and File system . We had raised an OSS message,SAP looked into the system and suggested to go for new setup as most of the components were corrupted.

 

As of now we have a workspace backup(Projects created from Old NWDI DC's) for one WDJ application( Portal 7.0) with 10 DC'S and local backup for another WDJ MDM application(Portal 7.3) with 4 DCS.The dependency between the DC's are high.

 

What is the best possible way to rebuild all DC's and move it to NWDI with minimal effort.

 

New NWDI system is 7.4.

 

Let me know if you require more information.

 

Regards,

Mahesh

Release activities in NWDI Problem Exc=java.lang.NullPointerException

$
0
0

While trying to release the activities in NWDS a problem occurred and I got this error message:

com.sap.cms.organizerUI.ui.ReleasePredecessorDialog      [Thread[ModalContext,5,main]] Error:  Exc=java.lang.NullPointerException

erro nwds.jpg

erro nwds1.jpg

Here's the error log:

 

java.lang.NullPointerException

  at com.sap.cms.organizerUI.internal.PropagationPredecessorProvider.findPredecessorActivities(PropagationPredecessorProvider.java:171)

  at com.sap.cms.organizerUI.internal.PropagationPredecessorProvider.findPredecessorActivities(PropagationPredecessorProvider.java:282)

  at com.sap.cms.organizerUI.ui.ReleasePredecessorDialog$PredecessorTreeContentProvider.getChildren(ReleasePredecessorDialog.java:1066)

  at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:653)

  at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:454)

  at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:558)

  at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:301)

  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

  at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:289)

  at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:697)

  at org.eclipse.jface.viewers.AbstractTreeViewer$4.treeExpanded(AbstractTreeViewer.java:709)

  at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:175)

  at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:865)

  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:849)

  at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:1912)

  at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:3838)

  at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:659)

  at org.eclipse.swt.widgets.Control.windowProc(Control.java:2837)

  at org.eclipse.swt.widgets.Display.windowProc(Display.java:2545)

  at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method)

  at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1246)

  at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:156)

  at org.eclipse.swt.widgets.Tree.WM_LBUTTONDOWN(Tree.java:1520)

  at org.eclipse.swt.widgets.Control.windowProc(Control.java:2820)

  at org.eclipse.swt.widgets.Display.windowProc(Display.java:2545)

  at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)

  at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1313)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1727)

  at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)

  at org.eclipse.jface.window.Window.open(Window.java:563)

  at com.sap.cms.organizerUI.ui.ReleasePredecessorDialog.open(ReleasePredecessorDialog.java:345)

  at com.sap.cms.organizerUI.actions.ReleaseActivityAction$1.run(ReleaseActivityAction.java:203)

  at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)

  at com.sap.cms.organizerUI.actions.ReleaseActivityAction.execute(ReleaseActivityAction.java:200)

  at com.tssap.dtr.client.eclipse.ui.actions.VfsObjectSelectionAction$2.run(VfsObjectSelectionAction.java:494)

  at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:127)

  at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:24)

  at org.eclipse.swt.widgets.Display.syncExec(Display.java:2337)

  at com.tssap.dtr.client.eclipse.ui.actions.VfsObjectSelectionAction.run(VfsObjectSelectionAction.java:492)

  at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)

  at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)

  at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)

  at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)

  at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)

  at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)

  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)

  at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)

  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)

  at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)

  at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)

  at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)

  at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)

  at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)

  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.ide.eclipse.startup.Main.basicRun(Main.java:291)

  at com.sap.ide.eclipse.startup.Main.run(Main.java:789)

  at com.sap.ide.eclipse.startup.Main.main(Main.java:607)

 

I'm using NWDS Version: 7.0.18.

 

Can anyone offer me any suggestions to solve this, please?

 

Thanks!


NWDI / NWDS Project Migration Error

$
0
0

Dear All

 

We have installed Biller Direct 6.35 on Netweaver 7.31, NWDI is configured, NWDS version is 7.31, JDK version is 1.7,

 

When we try to synch and create projects we are getting Project migration popup for the project fscm/bd/web/bd and if we continue to migrate we are   getting failure message, even quick fix option suggested by the failure log is not migrating the project.

 

As a result of this we are getting  errors in the web modules  fscm/bd/web/bd  and fscm/bd/web/shared.

 

We don’t have any issues with fscm/bd and fscm /bd/ebpp  biller direct  projects. Please see the attachment for details. Please  help me to move forward if anybody has a fix or solution for this.

 

 

Thanks

Bhaskar

Cant connect NWDS to CTS+

$
0
0

Hi All - I have installed PO 7.4. CTS+ has been configured and working. We do not have NWDI. Instead we are using NWDS to create ....

I am not able to connect to CTS using NWDS to create transports? I am sure there should be some settings that I need to enable to connect to.

 

Using NWDS I am able to connect to  integration builder but unable to connect to CTS. What am I missing?

 

NWDS ->  Process Integration --> open CTS organizer I am getting error " CTS Organizer not available on this server". I am new on NWDS.

 

Regards

Need folder location on server where NWDI projects get saved?

$
0
0

Hi Experts

I have a CE server on which I have created a SWCV on NWDI and created projects and saved it on DTR.

But now the server is down due to some issues and not coming up. Is there any way i can get the projects from the server even when the server is down.

Where will this SWCV and projects gets stored on the file system on server?

 

 

Regards

Osman

Migration of a 7.3.1 SC from "CMS" to "CM Services" with a 7.4 Version

$
0
0

Dear Experts,

 

We are migrating our "CMS" Configuration from server X to a new server Y as "CM Services". Server X Configuration is based on 7.3.1 Our target server Y Configuration has to be based on 7.4. For this we have followed following steps:

 

Our goal:

  • Source: Server X, CMS Track with 7.3.1 dependencies
  • Target: Server Y, CM Services Development Configuration with 7.4 dependencies.

Current result:

  • The SC component seems to be imported successfully. CBS and DTR shows the child DC. But in NWDS we don't see any DC belonging to the software component. The SC is empty.

 

  1. Defined a new SC version (2.0) on the source SLD with the 7.40 dependencies.
  2. Created a new CMS track on the source system containing the new 7.40 software standard components + our SC version 2.0 with also 7.40 dependencies.
  3. Created an 'Inbound Connection' from the Track containing the 7.31 SCs
  4. Imported the dependent SAP SCs of version 7.4.
  5. On the original Track (7.3.1), I assembled the SC and approved it for the new track.
  6. Import of the SC in the new track of server X to Development and Consolidation
  7. Assemble on the 7.4 track. Also CBS results were checked.
  8. Export the SCA under assembly tab of the new track.
  9. We checked the SCA file. The source files are in it (SOURCEARCHIVES)
  10. Copy the SCA file to the inbox of server Y (target)
  11. Add the Software Component of version 2.0 to the Development Configuration
  12. Now run the Sync service using SCA file from the inbox
  13. The result seems to be ok. We see the DC in the DTR and CBS. But NWDS cannot check out any DC from our SC.

 

In the sync logs I have found following (whole log is attached on the thread):

 

Initialize the compartment ag.ch_KTAG_UI_EAGE that CBS gets to know the move.
Propagatable: 9f375f1945b811e5ac47000000167312 / http://sapdi0.ads.ktag.ch:50000/dtr/system-tools/reports/ResourceDetails?resourceID=9f375f1945b811e5ac47000000167312&path=&command=Show exists allready in the repository. No import necessary.


Not sure if it is relevant. Can you recognize what we might be missing on our approach?


Thanks and Regards,

Koray

Install NWDI Solution Manager 7.1

$
0
0

analysts

I have a Solution Manager 7.1 environment and need to install the NWDI in my application .
You know me know what packages I have to install to enable this tool.

I tried to access the URL http: // hostname : port / devinf
http: // hostname : port / trt

In JSPM the solman .
Soon the log displays a message
Which has no domain controller for the NWDI .

But it is not enabled .

I'm waiting to support you.

Thank you.

NWDI SDM-Deploy fails: 'Administrator' could not be connected to the specified host and port

$
0
0

Hello experts,

 

 

1. We have NWDI track configured to connect one external-SAP portal system in DMZ zone, as runtime system, through 5NN04 (P4) port.

When we try to import (SDM deploy) any component from NWDI to that external portal [in CMS->Transport Studio], it fails with below error:

 

 

SIDadm> cat <TRACK_NAME>@<XXX><TIME_STAMP>SDM-deploy.log

<TIME_STAMP> Info   :Starting Step SDM-deploy at <TIME_STAMP> -5:00

<TIME_STAMP> Info   :start deployment of archives:http://<SAP_PORTAL_SERVER_NAME>:5NN04

<TIME_STAMP> Fatal  :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'Administrator' could not be connected to the specified host '<SAP_SERVER_NAME>'and port '5NN04'.:The user 'Administrator' could not be connected to the specified host '<SAP_PORTAL_SERVER_NAME>'and port '5NN04'.

com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'Administrator' could not be connected to the specified host '<SAP_PORTAL_SERVER_NAME>'and port '5NN04'.

        at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:170)

        at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:188

 

 

[NN = External portal instance number].

 

 

2. I initially suspected issue is in firewall rules, so had our network team opened port 5NN04 for external portal in DMZ.

 

 

Now from NWDI system I can do:

 

NWDISIDadm> telnet <SAP_PORTAL_SERVER_NAME> 5NN04

Trying <IP_SAP_PORTAL>...

Connected to <SAP_PORTAL_SERVER_NAME>.

Escape character is '^]'.

^]

telnet> quit

Connection to <SAP_PORTAL_SERVER_NAME> closed.


From SAP portal to telnet to NWDI is also working.

 

SAP_PORTAL_SIDadm> telnet <SAP_NWDI_CI> 5MM00

Trying <SAP_NWDI_IP>...

Connected to <SAP_NWDI_CI>.

Escape character is '^]'.

^CConnection to <SAP_NWDI_CI> closed by foreign host.

 

[MM = NWDI Instance no.]

 

3. We are using deploy controller with P4 (5NN04) port (as we are in NW 7.4) in run time system configuration in NWDI.

 

 

4. Other two steps before SDM-Deploy: Repository-import and CBS-make are finishing successfully, only SDM-Deploy is failing.

 

5. Our configuration in NWDI should be alright since this import works fine in internal portal with same P4 ports. Also we have NWDI set up for a long time.

 

 

a. Can any expert please tell me what could be the issue? What am I missing?

b. When we import any component from NWDI to runtime system, I hope there is a two way communication (NWDI to portal port 04 and portal to NWDI port 00) ? Is there any other port associated with this? How this import happens internally?

c.what are the other possible checks can be carried out to determine where is the actual problem?

 

 

 

Regards,

Sujit Kumar Banerjee.

NWDI / NWDS Project Migration Error

$
0
0

Dear All

 

We have installed Biller Direct 6.35 on Netweaver 7.31, NWDI is configured, NWDS version is 7.31, JDK version is 1.7,

 

When we try to synch and create projects we are getting Project migration popup for the project fscm/bd/web/bd and if we continue to migrate we are   getting failure message, even quick fix option suggested by the failure log is not migrating the project.

 

As a result of this we are getting  errors in the web modules  fscm/bd/web/bd  and fscm/bd/web/shared.

 

We don’t have any issues with fscm/bd and fscm /bd/ebpp  biller direct  projects. Please see the attachment for details. Please  help me to move forward if anybody has a fix or solution for this.

 

 

Thanks

Bhaskar


how I can upgrade tc~uddi component in NW 7.1

$
0
0

hi

I have 2 SAP servers

NW 7.1 & 7.4.

On 7.4 have component sap.com\tc~uddi. Please help, how I can import or upgrade sap.com\tc~uddi on NW 7.1 for extend functionality. Where I can download tc~uddi new component for NW 7.1

Invalid Response content type. Server returned code (500) with message and content type . Http proxy info: none

$
0
0

Hello Experts

 

I´m having a problem using BPM when I try to call a WS I get a message saying:

 

 

Error in connection:Invalid Response content type. Server returned code (500) with message <Internal Server Error> and content type <text/html>. Http proxy info:  none

 

Error occured while executing the service: Error in connection:Invalid Response content type. Server returned code (500) with message <Internal Server Error> and content type <text/html>. Http proxy info:  none

 

When I log in the NWA Connectivity Log and Trace I get a message saying that the Call of the status failed. with the following log:

 

Invalid Response content type. Server returned code (500) with message <Internal Server Error> and content type <text/html>. Http proxy info:  none
[EXCEPTION]
com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response content type. Server returned code (500) with message <Internal Server Error> and content type <text/html>. Http proxy info:  none
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handle500Response(SOAPTransportBinding.java:728)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:580)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1376)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:997)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:951)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.portal.connector.webservices.execution.functions.esp.ESPInteractionRuntime.execute(ESPInteractionRuntime.java:100)
at com.sap.portal.connector.webservices.execution.functions.CCIInteraction.execute(CCIInteraction.java:86)
at com.sap.portal.connector.webservices.execution.functions.CCIInteraction.execute(CCIInteraction.java:144)
at com.sap.tc.wd4vc.core.std.infoactors.java.GenericSAPR3Infoactor_1_1_0_0.processExecution(GenericSAPR3Infoactor_1_1_0_0.java:325)
at com.sap.tc.wd4vc.core.xgl2_2.infoactors.java.PortalWebserviceInfoactorXGL2_2_V_1_1_0_0.executeService(PortalWebserviceInfoactorXGL2_2_V_1_1_0_0.java:70)
at com.sap.tc.wd4vc.core.std.infoactors.java.WebServiceInfoactor.executeService(WebServiceInfoactor.java:46)
at com.sap.tc.wd4vc.core.std.infoactors.GenericInfoactor.execute(GenericInfoactor.java:286)
at com.sap.tc.wd4vc.core.std.infoactors.wdp.InternalGenericInfoactor.execute(InternalGenericInfoactor.java:144)
at com.sap.tc.wd4vc.core.std.infoactors.GenericInfoactorInterface.execute(GenericInfoactorInterface.java:134)
at com.sap.tc.wd4vc.core.std.infoactors.wdp.InternalGenericInfoactorInterface.wdInvokeMethod(InternalGenericInfoactorInterface.java:175)
at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
at com.sun.proxy.$Proxy3641.execute(Unknown Source)
at com.sap.tc.wd4vc.xglengine.java.XGLInterpreter.evaluateInfoactor(XGLInterpreter.java:2826)
at com.sap.tc.wd4vc.xglengine.java.XGLInterpreter.doEvalStep(XGLInterpreter.java:2740)
at com.sap.tc.wd4vc.core.xgl2_2.xglengine.java.XGL2_2Interpreter.doEvalStep(XGL2_2Interpreter.java:1754)
at com.sap.tc.wd4vc.xglengine.java.XGLInterpreter.processStep(XGLInterpreter.java:1908)
at com.sap.tc.wd4vc.core.xgl2_2.xglengine.java.XGL2_2Interpreter.processStep(XGL2_2Interpreter.java:5377)
at com.sap.tc.wd4vc.xglengine.java.XGLInterpreter.processPlan(XGLInterpreter.java:1869)
at com.sap.tc.wd4vc.core.xgl2_2.xglengine.java.XGL2_2Interpreter.processAtomicActionCall(XGL2_2Interpreter.java:883)
at com.sap.tc.wd4vc.core.xgl2_2.xglengine.java.XGL2_2Interpreter.processActionCall(XGL2_2Interpreter.java:796)
at com.sap.tc.wd4vc.core.xgl2_2.xglengine.java.XGL2_2Interpreter.processAction(XGL2_2Interpreter.java:595)
at com.sap.tc.wd4vc.xglengine.XGLEngine.processAction(XGLEngine.java:540)
at com.sap.tc.wd4vc.xglengine.wdp.InternalXGLEngine.wdInvokeEventHandler(InternalXGLEngine.java:199)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.invokeEventHandler(DelegatingComponent.java:248)
at com.sap.tc.webdynpro.progmodel.components.Component.fireEvent(Component.java:492)
at com.sap.tc.wd4vc.core.std.interactors.pane.wdp.InternalGenericPaneInterface.wdFireEventGenericEvent(InternalGenericPaneInterface.java:249)
at com.sap.tc.wd4vc.core.std.interactors.pane.Generic.onActionGenericAction(Generic.java:489)
at com.sap.tc.wd4vc.core.std.interactors.pane.Generic.onActionValidatingAction(Generic.java:513)
at com.sap.tc.wd4vc.core.std.interactors.pane.wdp.InternalGeneric.wdInvokeEventHandler(InternalGeneric.java:179)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:367)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:490)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)


Any idea what can be causing the WS to fail? or what can be checked to be able to make the call succesfully?

Issue regarding NWDI deployment (Waiting SC also got imported)

$
0
0

Hi All,

 

currently i am facing an issue ,

 

scenario: We had imported customer interaction module and sales transaction module in Test system using NWDI ,

First customer module was assembled followed by sales transaction  module and imported in to Test system in the same order respectively.

 

Both the modules are waiting for approval in approval tab of NWDI CMS , but after that there was a need to import only sales transaction module to production , so we approved only sales transaction module and imported it in to production .

 

The issue is when we imported sales transaction module along with it customer interaction module also got imported which we haven't approved.

 

 

I want to know whether there are any dependencies between sales transaction and customer interaction module and why both the module got imported into production.

 

 

Thanks in advance,

 

Regards,

Santosh.B

How to get .SDA file from .ear in nwdi(7.0)

$
0
0

Hi ,

 

Can any one let me know how to download the .sda file from an existing  ear file from  nwdi( NWDS 7.0)

Since we are trying to deploy ear file through telnet it is converting to sda file and the vendor is changed to JAVAEE from xxxxxx and the changes are not deploying as a result of vendor change ( ear is not overwritten).

 

Quick response is helpful.

 

Thanks

 

Kumar

Error while saving SC

$
0
0

Hello Experts,

 

I am in the process of saving an SC when the following error appears:

 

Unable to save development configuration: Unable to create workspace "xxxxxx" on repository "http://<host>:<port>/dtr" using user "NWDI_CMSADM" [DICONF_CREATEWORKSPACE]: Not implemented"

 

Any help on this would be greatly appreciated.

 

Thanks,
Mike

Viewing all 562 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>