Web dynpro proxi page

Hi,
I read in last newsletter some articles about web dynpro.
So when i tried to created a web dynpro page and i follow the wizard the article suggest that we must choose web dynpro proxy page.
But when i tried to do that i only had the default page template.
How can make the web dynpro proxy page available???
Best Regards
João Fernandes

I am having a similar problem.
I cannot see the Default Page Template, and wondering what I need to do to make it available.
Has anyone got a solution.
Regards
Andrew

Similar Messages

What is Web Dynpro Proxy Page

hi
any body Could you please let me know the what is the diff between
Default Page Temple and Web Dynpro Proxy Page.
regards
mmukesh

hi Mukesh,
as wrote in the SAP Library
<b>Default Page Template</b>: Is a page based on the regular portal page template
<b>Web Dynpro Proxy Page</b>: Is a page based on Web Dynpro technology
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/db/b8df3d48b05d5ae10000000a11405a/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/db/b8df3d48b05d5ae10000000a11405a/frameset.htm</a>
Best Regards,
Gianluca Barile

Web Dynpro Proxy Page vs Default Page Template

Dear Experts.
I have the following doubt with I am creating Page in the portal.
The system display the two options following:
[Template Page|http://www.freeimagehosting.net/uploads/d2eb3ec600.jpg]
I found the following document:
[Document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/0c7b2f25-0c01-0010-f2a2-f8a65a9dcad9?QuickLink=index&overridelayout=true]
But I what know When I should use the Web Dynpro Proxy Page option and When I should use Default Page Template
Can Anyone help me with suggestions, please.
Best Regards
Juan.

Hi.
Default Page Template: Creates a page based on the regular portal page template
Web Dynpro Proxy Page: Creates a page based on Web Dynpro technology
But I created the page with the two options, but I not find differences between the two options with respect to Layouts, and others.
Can anyone help me with suggestions.
Thank You in advance.
Regards
Juan.

Custom Layout for Web Dynpro Proxy page

Hey all
I have a requirement to display 4-5 Web Dynpro for ABAP iViews on a page.
I have the option of using the standard PRT page to display these iViews for which I can create a custom layout using com.sap.portal.layouts.default.par and the simple JSP layout file in it.
However, they should really be on a Web Dynpro Proxy page but custom layouts created using above component wont work.
In the document [Integrating Web Dynpro and SAP NetWeaver Portal|https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/0c7b2f25-0c01-0010-f2a2-f8a65a9dcad9] it says -
Within the SAP NetWeaver 04s release it is not possible to define application specific page layouts for Web Dynpro pages. Within the SAP NetWeaver 07 release this will be possible. Layouts for Web Dynpro page are implemented then as Web Dynpro components implementing a special ILayout Web Dynpro component interface.
Has this been released as yet?
Anyone find the APIs or workaround for this?
Cheers

I have the same question, but can't find any good solutions for this.
For standard portal applications you can use com.sap.portal.design.layouts and modify layouts via JSP. But all webdynpro proxy pages are using their own layout.
I'd like to change that layout too.
Anyone?
Cheers,
Noel
I am using NW 701

EREC: theme for Web Dynpro ABAP pages (external candidate)

Hello,
I have created a custom theme in the SAP Netweaver Portal for my customer and now I have the requirement to use the same theme for my stand-alone Web Dynpro ABAP applications (pages for the external candidate). Is it possible to use the same stylesheet as in the portal, without having to recreate a theme?
I tried several options, but none of them did work:
A. Downloading the portal theme as a ZIP file and then uploading it in ERP using the report BSP_UPDATE_MIMEREPOS (after unzipping) to a location /SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME. After that, I call my application with the additional URL parameter sap-wd-themeroot=/SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME but it does not work (the app is displayed with the default sap_tradeshow stylesheet)
B. I also tried calling my app using the URL parameter sap-cssurl=/SAP/PUBLIC/BC/UR/nw5/themes/CUSTOM_THEME but here again, it does not work (the app is displayed with the default sap_tradeshow stylesheet)
C. Downloading the portal theme as a ZIP file and then uploading it (zipped) using the report WD_THEMES, but here I receive the error "no themes found in the ZIP file". I have the same error if I upload only the ur.zip I receive from the portal (instead of uploading the whole *.zip file)
I checked the UR versions both in portal & ERP, and we had a lower version in the portal than in the ERP, so we upgraded the portal version according to SAP note 1446099. Now we have a higher version in the portal than in the ERP. We regenrated the portal theme and downloaded it again, but with the same result.
Does anyone have an idea what could be the solution to our problem?
Thanks in advance!

I would recommend to try another way. If it is possible to access any SAP Portal from outside you can use two URL Parameters to integrate the Portal style sheets in a standalone WDA application. The parameter sap-cssurl contains the absolute URL address to the style sheet and parameter sap-cssversion the current SAP Portal style sheet version. For all external facing scenarios it is important to use the whitelist mechanism to block unknown URLs.
Example
?sap-cssurl=http://myportal.myserver.com:50000/irj/portalapps/com.sap.portal.design.urdesigndata/themes/portal/mytheme/ur/ur_ie6.css
&sap-cssversion=7.11.5.20.0
I canu2019t recommend to raise manually the version number. You will not get an consistent system this way. The meta data (project.zip) are outdated and of course you will get an outdated theme.

I am getting a error while executing the Web Dynpro Application Page.

Hi All,
I am getting a Error while executing a web dynpro application :::
: Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
I have checked this error description in ST22 :
What happened?
    The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
     along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_WDR_CLIENT_APPLICATION=====CP' has to be
    terminated.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
     and
    therefore caused a runtime error.
    The reason for the exception is:
    Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
    Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
Can u plz help me regarding this error.
Thanks,
Deepika

>Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

Controlling visibility of Web Dynpro Java iView in portal WDJ page

I should be able to use the WDPortalUtils interface in my Web Dynpro Java DC application to get the name of the iView in my Portal WDJ page using IWDPageService method getVisibleIViews(). My intent is to add another iView to this page and programmatically control the visibility of each iView from my WDJ application.
-> Instructions I have found through my online research indicate I should not have to specify a sharing reference because I am using the WDJ framework, but I tried it anyway. It didn't work.
-> I have added DC epbc.prtapi._api public part to my used DC's, and specified dependency at both Build time and Run time.
-> My portal page template is of type Web Dynpro Proxy Page.
-> My iView template is of type Web Dynpro Proxy iView.
-> The Page Content view of my page shows the 'visible' checkbox set for my iView.
The following statements in the wdDoInit() method of my DC's view controller should return the portal name of my iView:
IWDPageService pageService = (IWDPageService) WDPortalUtils.getService(WDPortalServiceType.PAGE_SERVICE);
String[] iViews = pageService.getVisibleIViews();
I get no compile time errors or runtime errors when I execute these statements.
BUT...
Instead of a String array, I get back a memory space pointer.
Example: [Ljava.lang.String;@664e664e
What am I missing?

Hi Jennifer,
That's what this forum is all about; finding solutions to hard-to-solve issues, which might also help someone who may face the same issue in the future. So I hope my input is valuable
The last thing I can think of is the method is been called before the portal page has been rendered completely, which may lead to the faulty results.
Is it possible to move the getVisibleIviews() to a method which is called later in the phase (for instance, at the bottom of wdDoModify or wdDoPostProcessing) or, even better, in an onAction event handler when a button is clicked?
If this doesn't work I'm afraid I'm running out of options and i would file an OSS message with SAP
Hope this helps!
Robin

500 Internal Server Error - Web Dynpro Content Administrator

500 Internal Server Error - Web Dynpro Content Administrator
Any help would be really appreciated...
I was trying to create/Maintain JCo destions on Web Dynpro Content Administrator caught up with the 500 Internal Server Error
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
Root Cause
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:869)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractSystemLandscapeFactory$1.checkStatus(AbstractSystemLandscapeFactory.java:310)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:483)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:534)
at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:750)
... 73 more

Possible Reasons:
1. Some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
empty) in SLD.
2. Ensure that the SLD is setup properly. Click on the u201CTest Connectionu201D to check that the SLD is up and running.
Check section "NullPointerException in the trace when maintaining JCO destinations" in below SDN document:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2 (Adaptive RFC- Troubleshooting Guide)
Edited by: Anagha Jawalekar on Jun 25, 2009 9:11 AM

Trying to run a Web Dynpro Simple Sample with no luck??

Hi I have downloaded a Web Dynpro and BPM simple sample application from this location: The problem is after configuring the CE instance and setting everything up, when i Deploy and Run this app i get the following error displayed can some one please help?? 500 Internal Server Error SAP NetWeaver Application Server/Java AS The initial exception that caused the request to fail, was: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) ... 115 more See full exception chain for details. Failed to process request. Please contact your system administrator. While processing the current request, an exception occured which could not be handled by the application or the framework. If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file). For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811. Correction Hints Exception could be caused by the development component: tcwdwebdynpro Note: The above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases. System Environment Client Web Dynpro Client Type AJAX Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; LLY-EMA-EN; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; LLY-EMA-EN; LLY-EMA-EN) Client Type msie7 Client Type Profile ie6 ActiveX enabled Java Applets enabled Accessibility mode disabled Inline CSS false Validate by rendering true Server Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.2001.20091210105536.0000', change number: '79724', codeline: NW720_01_REL J2EE Engine 7.20.3710.69682.20090922144234 System ID (SID) CE1 Server Node ID |3191650|31916|Server 00 00_31916|YHP30964.ema.lilly.com/40.205.138.181|SERVER|RUNNING Java VM SAP Java Server VM, version:6.1.007, vendor: SAP AG Operating system Windows XP, version: 5.1, architecture: x86 Application Java EE Application (deployable object) ides.com/soacmpssc~salsord Web Dynpro Application CreateSalesOrderApp Request URI /webdynpro/resources/ides.com/soacmpssc~salsord/CreateSalesOrderApp Version vendor: 'ides.com', name: 'soa/cmp/ssc/salsord', location: 'localDevelopment', counter: '20100329143545', change number: 'null' Session & Other Session Locale en_GB Session Timezone Greenwich Mean Time Time of Failure Mon Mar 29 15:38:53 BST 2010 (Java Time: 1269873533200) Session User ClientUser(id=USER.PRIVATE_DATASOURCE.un:Administrator, name=Administrator) Http Session Id tCJhFjXUItrW3M0cACKdKt9MDaBiM0upJwFiszAA_SAP Client Window Id Application Session Id b2a8d9023b4011dfb81f001b7889332c Web Dynpro Code Generation Infos ides.com/soacmpssc~salsord WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:22+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:22+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/ides.com/soacmpssc~salsord: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) sap.com/tcwdapi WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:05+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:31:32+0000, changelist=69541, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:18:18+0000, changelist=63859, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:52:50+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:22:47+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:19:24+0000, changelist=69781, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:26:44+0000, changelist=69542, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:34:20+0000, changelist=69853, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:23+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:53:55+0000, changelist=69852, host=pwdfm222, is-central=true) WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen 7.2001.20091202163157.0000 (release=NW720_01_REL, buildtime=2009-12-12T18:48:47+0000, changelist=64407, host=pwdfm222, is-central=true) Detailed Error Information Detailed Exception Chain com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session b2a8d9023b4011dfb81f001b7889332c. The causing exception is nested. RID=b2a8d9003b4011dfbdb7001b7889332c at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:606) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:335) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87) at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76) at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:98) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:79) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:381) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:566) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1438) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:603) ... 43 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:71) ... 48 more Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'ERP_META' and WS interface 'SalesOrderBasicDataByBuyerAndBasicDataQueryResponse_In'. One possible reason is that the metadata destination 'ERP_META' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:558) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:457) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:425) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:399) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:334) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateModelInfo(WSModelInfo.java:307) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:93) at com.ides.soa.cmp.ssc.salsord.findsomodel.FindSOModel.<init>(FindSOModel.java:114) at com.ides.soa.cmp.ssc.salsord.createsalesord.CreateSalesOrd.<init>(CreateSalesOrd.java:732) at com.ides.soa.cmp.ssc.salsord.createsalesord.wdp.InternalCreateSalesOrd.<init>(InternalCreateSalesOrd.java:8892) ... 53 more

Hi Anixan
Please update the SAP AS Java at windows >> Preference >> SAP AS Java >> Add new SAP >> Put instance Hostname like 'CE1' and Instance Number like '00'. Then please verify that is connected or not in NWDS at windows >> show view >> Others >> Server >> Servers
**Also update the Update your server IP address and host name in host file entry at (Start > RUN > drivers > etc > host file)
and update JAVA_HOME system enviromental variable in my computer (My computer > Priperties >> Advance >> Startup and Recovery >> Enviromental Variable >> System Variables >> Add new JAVA_HOME parameter with path for installed Java JDK)
Please check here http://help.sap.com/saphelp_nw70/helpdata/EN/43/3976df43b33575e10000000a11466f/content.htm
Hope it helps
Regards
Arun

Adobe Reader error with SAP interactive form in Web dynpro ABAP

Hi,
We are having a strange intermittent problem with Adobe Reader. When we try to open PDF files from SAP Frontend we get an error pop-up. The pop-up does not have any text. The title of the pop-up has "Adobe Reader". There is a blue question mark and an OK button. The form is inserted into Web Dynpro ABAP page. This web dynpro application is executed in SAP GUI by this program:
REPORT TEST1 MESSAGE-ID SWDP_RUNTIME.
start-of-selection.
CALL FUNCTION 'WDY_EXECUTE_IN_PLACE'
    EXPORTING
     PROTOCOL               = 'HTTPS'       " HTTP | HTTPS
    INTERNALMODE           = 'X'    "SPACE - browser is started
    PARAMETERS             =
      APPLICATION            = 'Z_FORM'
     CONTAINER_NAME         = 'TEST'
    EXCEPTIONS
      INVALID_APPLICATION    = 1
      BROWSER_NOT_STARTED    = 2
      OTHERS                 = 3.
IF sy-subrc EQ 1.
    MESSAGE a400.
ELSEIF sy-subrc = 2.
    MESSAGE a401.
ELSEIF sy-subrc = 3.
    MESSAGE a667.
ENDIF.
Adobe Reader version is 9.1.2
Is there any solution for this?
Many thanks for answer.

Jiri,
The reason why I thought downgrading would help is because Reader 9 and above is probably not fully supported by SAP yet.
You can maybe open an OSS and see if Adobe 9 is fully supported or not.
Chintan

Call WAPI error in web dynpro app

I write a very simple demo workflow, there is a approve step that call a web dynpro app.
I pass workitemid to my web dynpro program, then It call fm SAP_WAPI_RESERVE_WORKITEM and SAP_WAPI_WORKITEM_COMPLETE to comlete workitem programmly.
In SAPGUI workplace ,I receive a message ,then I execute workitem,web dynpro UI page is showed.When I execute approve operation(call two wapi fm above in approve event handler),SAP_WAPI_RESERVE_WORKITEM and SAP_WAPI_WORKITEM_COMPLETE's export parameter "return_code" is 1.
But I test/execute my web dynpro program standalone in workbench,all is ok,demo workflow continue.
I have spent a plenty of time for it,help me!
I'm sorry for my poor english .

Thanks for your advice. I am a new one for SAP development.
According to your advice, I use SAP_WAPI_DECISION_COMPLETE instead of SAP_WAPI_RESERVE_WORKITEM and SAP_WAPI_WORKITEM_COMPLETE, I get the same result.
test web dynpro application standalone, it's ok;in SAP workplace ,SAP_WAPI_DECISION_COMPLETE method's exporting parameter "return_code" is 1.
My code is following :
CALL FUNCTION 'SAP_WAPI_DECISION_COMPLETE'
EXPORTING
    WORKITEM_ID          = l_wi_id
    LANGUAGE             = SY-LANGU
    USER                 = SY-UNAME
    DECISION_KEY         = 0001
    DO_COMMIT            = 'X'
IMPORTING
    RETURN_CODE          = returncode

Web Dynpro Java code changes

Hi,
I need to put some validations in web dynpro java page which is "employee address page". I checked the BADI's but no badi exists which serve my purpsoe.
Now I want to make the code change in web dynpro java. Pls answer the followng questions.
1- I have installed NWDS on my local machine. Do i need to install NWDI also?
2- How to import and export the required page and from where?
3- How to modify the standard code, I mean in ECC we have enhancement and modification concept.
Thanks,

NWDI is a part of NWDS, So you would need both as mentioend
NWDI - Netweaver Development Infrastructure is an SAP sytem for java development & change management. It's a repository for java code and change management system.
NWDS is a developer tool to build applications similar to Eclipse. NWDS uses NWDI to check-in & check-out java code and move java changes to SAP runtime systems (like portal etc).
Read the basics of NWDI and its utility in the below help document
http://help.sap.com/saphelp_nwce72/helpdata/en/48/bc23b1a70a0611e10000000a42189b/frameset.htm
Also go through how to import ESS configurations in NWDI
ESS/MSS Customization Make it Simple
NWDI cookbook in SAP note : 872892
The specified item was not found.
Edited by: Siddharth Rajora on Nov 9, 2011 9:28 PM

Web Dynpro & Adobe Forms: Context Mapping

Hi Experts,
By assigning a form to a view via templateSource the option to automatically generate context. With sample data, implemented in the view its working fine.
Now I want to use data out of the component controllers' context, but I can't map the views context nodes to the component controller nodes without deleting the context structure out of the form.
In other words; how can I connect the automatically generated context from the form with the context of the component controller?
How can I solve this issue?
An option is to read out the component controllers context into itabs and save them in the views context.......
not very nice, but my only idea right now.
Does anyone has an idea?
Thanks in advance,
Tan

Hi again,
I've found this [documentation|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/63a47dd9-0b01-0010-3d8e-de27242bf011?quicklink=index&overridelayout=true], chapter "Integrating a PDF in a Web Dynpro Application" (Page 192-193) and followed the print scenario.
My intention is not to create an interactive form. I just want to display a generated pdf which is provided with data out of web dynpro context.
That's what I did:
In my views' layout tab in properties list I've entered a (not existing) form name (as templateSource) to create a new form. Then double cklicked on it to create it, entered a interface name (which was not existing also) and selected a context (the context was mapped before out of the component controller). Then se80 switched to form builder. The context nodes are available so I dragged some into the form, save & activate.
The result is, the dragged fields are visible, but there are no values assigned, the corresponding fields are empty.
I checked whether the context nodes are filled --> they are....
Any idea what's going wrong?

Web Dynpro application callable object error: Page Builder Not available

Hi, SDN Fellow.
I created a callable object of Web Dynpro application. The callable object is atatched to an Action, and Action --> Block, and Block --> Process.
I initiate the process in GP Runtime, when it comes to the Action screen the Web Dynpro application atatched to, I got the following error:
The page builder required to display this application UI inside the portal environment is not available.
As aa comparison, another callable object that atatched to a Web Dynpro component (that implement GP interface) is working fine.
Please advise.
Thanks in advance,
KC

Hi KC,
When you start your process from GP Runtime, does the actual action/callable object open in a new window?
Have a look at this SAP Note:
[Error when executing a GP task - Page builder|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393831353137%7d]
Although the error message you are getting is different, but if your callable object opens in a new window, then the problem (in most probability) is the same as mentioned in the SAP Note.
Also, try testing the Web Dynpro callable object in standalone mode. For more information on this, see:
[Testing Callable Objects|http://help.sap.com/saphelp_nw04s/helpdata/en/4c/588041a17e060de10000000a1550b0/frameset.htm]
Bye
Ankur

I want to give custome error page in web dynpro application

Hi ,
I want to give custom error page for time out condition in my web dynpro application .
Kindly give me a soulation ASAP.
Thank's and regard's.
Vikash.

Refer this :
default error page
May be it helps you.

Web dynpro proxi page

Similar Messages

Maybe you are looking for