SAP Web Dynpro iView not working!

We are trying to run BI reports based on Web Dynpro ABAP in portal. I created a SAP Web Dynpro iView with following parameters
System : SAP_LocalSystem
Namespace : sap
Applicatioin Name : ZXXXXX_RRE (This is the template name)
When I try to preview the report I get portal runtime error with following error dump in log file
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template
'<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
I have checked SAP_BW system object and tested the connections all connection test for SAP_BW is successful. BI Portal system is set up with SAP web dispatcher, ITS and WEB host names in system object are configured something like xxxx.hostname.com:443 since it's SSL.
Am I missing anything here?
Thanks
Praveen

Hello Pravin,
Currently i am also facing the same error. I am having set of Webdynpro-ABAP applications, and accessing from Portal.
I tested respective applications from SE80, all are working fine.But while accessing from Portal its giving Portal runtime error-Unable to parse etc....
I checked my system object.. both WAS and ITS connections are successful.but i mentioned its related to ITS, where can i test my ITS further level..
Though these are WDA applications , how these related to ITS..
I am also getting same error message.. Please suggest how can i go head
Thanks in Advance
Ganesh

Similar Messages

Portal theme not picked for SAP Web Dynpro Iview

Hi,
We have used light framework page for our portal and all the iviews display the content within the iviews in the same set of colors (blue for buttons). However, for a WD java content, I have created an SAP Web Dynpro iView and the contents displayed here appear in the SAP colors without picking those set for the portal.
The same application parameters display the portal colors when we use the Web Dynpro Proxy iview.
Any idea how I can make the SAP Web Dynpro iView appear like the other portal iviews?
Note: The stylesheet property for the iview is already entered (ur), and I have also set the 'Supply Portal stylesheet' property to 'Yes'.
Please provide your inputs.
Thanks,
Vinay

Hi ,
In ABAP Webdynpro for similar problem we used WDFORCEEXTERNAL Sheet property of WDA.
The Web Dynpro framework automatically compares the versions of the portal and Web Dynpro
for ABAP style sheets. If the Web Dynpro for ABAP has a newer version, the WDA style sheet is used. This avoids unattractive rendering and JavaScript errors.You can deactivate this behavior again using the WDFORCEEXTERNALSTYLESHEET application parameter of WDA.See also SAP Notes 1033496 .
If you use the stylesheet of the portal to display the application, the rendering may not appear correctly and Javascript errors can occur(If portal style sheet is lower than WD).
Though Iam not familiar with WD java , the property force portal style sheet in WD java application should be enough to make WD accept portal theme.
Regards
Karthiheyan M

Error in SAP Web Dynpro Iview

Hi,
We are facing problem with iviews, created using SAP Web Dynpro iView Template. Whenever user clicks on any of SAP Web Dynpro iView , portal main page is opened instead of Web Dynpro application. Same problem is encounted on preview of the iView. Everything was working fine till yesterday and suddenly we are facing this problem.
Also, iview created using Web Dynpro Java Application option are working fine.
What can be the reason behind the problem?
Need your help.
Thanks in Advance,
Apurva

Hi,
Some times we get the home page instaed of the application.
This may be due to the application is not active.
Test from se80.
If it is working fine create the iview again i think there are changes made to the application.
Thanks,
gopal

Problem while creating SAP Web Dynpro iView

Hi,
I am creating SAP Web Dynpro iView from iView Template.
The SAP Web Dynpro System Object is being created. The System Alias is also being created.
The Test Connection is successful with Portal Server.
Now, while creating SAP Web Dynpro iView from Template in Step 4:
I am not getting my System while an old system which is being deleted is being displayed.
Name of my System Object is: WD_System and System alias is: WD_Alias.
The Step name is:
Step 4: Application Parameter
Enter the paramater(s) of the application for which you want to create the iView
Regards
Kaushik Banerjee

Hi Bala,
I am not getting the System Alias under:
User Administration-> User Mapping-> Logon Data(Select a Principal) (System Alias).
The System is successfully built under System Amininstration->System Configuration->System Landscape->Portal Content->kaushikb named WD_System and System Alias is named as: WebDynpro_alias.
The Test Connection is successful.
I am displaying the result below:
SAP Web AS Connection
Test Details:
The test performs the following:
1. Checks the validity of the system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Checks if a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (kolapon:50000)
5. The host name kolapon was resolved successfully.
6. The server kolapon was pinged successfully.
7. The WAS ping service http://kolapon:50000/sap/bc/ping was not pinged successfully. If the ping service is not activated on the WAS, you can try to call the ping service manually.
8. An HTTP/S connection to http://kolapon:50000 was obtained successfully.
Regards
Kaushik Banerjee

Update about SAP Web Dynpro iViews

Hello,
I would like to know if there is a workaround or way to integrate SAP Web Dynpro iViews into Microsoft Sharepoint iView Web Parts.
Best regards,
Tanguy

Hi see this link
_Interoperability between SAP NetWeaver Portal and
Microsoft SharePoint Technologies_
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0489149-5c93-2a10-8aaa-da1cd0b6edf3
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7e6af2a1-0301-0010-7da6-bd1d67fb24fc
Thanks,
Tulasi

Help with SAP Web Dynpro IView

Hi,
Our developer created an planning file upload web dynpro via transaction RSPLAN. I am looking to create a appropriate IView for this so I don't have to hardcode the URL in an URL IView. From the list of available IViews I selected "SAP Web Dynpro".
The URL to the Upload is the following:
https://<server>:1443/sap/bc/webdynpro/sap/zrsplf_file_upload?planning_sequence=ZDWHOSPSAL
For the IView parameters I have the following:
In "Application Name" I have zrsplffile_upload_
in "Application Parameters" I have planningsequence=ZDWHOSPSAL_
in "Namespace" I put ZSMD which is the package
When I execute the IView I get the following error.
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: Wrong WebDynpro-URL: no application name specified
Can anyone help me out with what I should put in the Namespace parameter and what else I might be doing wrong?

Hi,
This doc may be of use for you
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3e36d690-0201-0010-cd99-bfbb81bd33d9
Regards
Ayyapparaj

Web Dynpro applications not working on ECC 6.0 IDES

Hi,
I'm new to Web Dynpro and developed a custom Web Dynpro (including the application) on a ECC 6.0 IDES system. It's simple with a couple of input fields. When I test it (either via SAP GUI 7.1 or 7.2, or Web GUI), it appears on the browser ok but the screen is frozen. I can't enter anything into the fields, etc. I also tested SAP Web Dynpro applications and they act the same way, frozen screen. There aren't any errors displayed or any runtime errors in ST22. Please advise. I searched this forum but didn't see any issue similar to mine. The IDES vendor suggested I post the issue on SDN.
John

I guess it has do to with some sort of browser's font size or view settings.
press ctrl +0 make the zoom 100% and font size medium and try again.
thanks
sarbjeet singh

NW 7.3 + iView from remote source wizard + R3 Web Dynpro ABAP, not working

Hi,
I think this forum is my last resort.
I'm running NetWeaver 7.3 Enterprise Portal and also have an existing ECC6 on backend.
Our ABAP Programmer has built some WD4A application on ECC, I'd like to made them available
on EP as ABAP WebDynpro iView.
From the document, I know the way to create ABAP WD iView is different since 7.3. I have to use "iView from remote source" to do it.
On EP side, I have made an system alias (test ok) for ECC, assigned permission, provide mapping id/pwd, and test.
On ABAP side, all webdynpro app are activated (T-code sicf, /sap/bc/webdynpro, /sap/public/bc/webdynpro...). I can even test WAS by bringing up browser and access some sample ABAP webdynpro .
However, I cannot success on "iView from remote source" wizard and it always show me "Nothing found. Check your search Criteria.".   Eventhough I use "*" as search criteria.
Anyone has the similar situation ? I even doubt that it is a placeholder of a feature , not working for now. Anyone made it work on NW 7.3 ?
More detail:
My System Alias for ECC:
      Application Host: myr3.mydomain.com
      SAP Client: 600
      SAP System ID:   DEV
      SAP System Number: 00
      Server Port: <leave it blank>
      System Type: SAP_R3
      Logon Method: UIDPW
      User Mapping Type: admin,user
      ICM Host: myr3.mydomain.com:8000
      ICM Protocol: http
      ICM URL prefix: <leave it blank>
      SAP Netweaver AS Description: <leave it blank>
All other fileds are leave it as default value
I also assign a group to have "read" and "user" permission to this system
Also assign Alias to the system.
I also create a user belong to the group, assign his system mapping an ECC user ID & PWD to it.
I tested the System alias, it is working (both WEB AS test, and R3 test)
Then I try to create an iView on EP, under a PCD folder , new->iview->iview from remote source. A wizard show up. Then I can select the ECC alias just created, and provide * as application search criteria, and then select "WEB DYNPRO ABAP" as the application type. Then "GO"
as I mentioned, it always show "Nothing Found. Check your search crieteria"
But I'm sure the web dynpro applications are activated on R3.
OK, that's it, please help this one. Thanks
IF YOU DID MAKE IT WORK ON YOUR NW 7.3, PLEASE DROP A LINE HERE SO I KNOW IT IS MY OWN PROBLEM !!!
Edited by: Wilson KU on Nov 14, 2011 10:42 AM
Edited by: Wilson KU on Nov 14, 2011 10:46 AM

Thanks for the reply,
[About Backend]
I feel confident about the backend R3 system because I can use the WAS URL to access the sample WD4A application, for example, I can bring up the wd4a application ui in my browser. It is purely browser and R3 stuff, no EP involved.
http://soeprdev.mydomain.com:8000/sap/bc/webdynpro/bobf/demo_sales_order?sap-client=600&sap-language=ZF
I also already activate all nodes and sub-nodes (in SICF Services) under /sap/bc/webdynpro as well as /sap/public/bc/webdynpro. (and some other nodes to make icon and include work)
[About the system object in EP]
I have done all kind of test on the system object (alias):
1. In EP System Administration -> Landscape Configuration, I select the system object, click "Test Connection", It shows me a Check mark, and the detail message is SOE_DEV_600 connection
2. Edit the System object, then click on "Connection Tests" page, I see two lines there, check both and click test, here is the result:
SAP Web AS Connection:
: Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if an SAP system is defined in the system object
5. Validate the following parameters: Web AS protocol; Web AS hostname
6. Checks if the host name of the server can be resolved.
7. Pings the Web AS Ping service (works only if the service is activated on the Web AS, and only on ABAP Web AS)
8. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. System retrieved successfully
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ICM Protocol (http) ICM Host Name (soeprdev.mydomain.com:8000)
6. The host name (soeprdev.mydomain.com) was resolved successfully
7. The Web AS ping service http://soeprdev.mydomain.com:8000/sap/bc/ping was pinged successfully
8. An HTTP/S connection to http://soeprdev.mydomain.com:8000 was obtained successfully.
Connection Test for Connectors:
: Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back-end application using the connector defined in this system object
Results
Default alias retrieved successfully
Connection successful

Submit Button In Web Dynpro Layout not working.

Hi All,
         I have integrated an adobe form in my web dynpro application.According to my requirement the view of screen should change when the user clicks on submit button.So I have given the submit button as one of the UI element in my WD object along with the form.But when I click on the submit button the functionality doesnot work.
The same submit button works when there is no adobe form integrated in my WD application.
Please let me know what needs tyo be done so make that submit button work.
Thanks and Regards,
Sarang

Sarang,
Lets go step-by-step.
1. Create two views in your applications lets say the names are View1 and View2.
2. Goto Diagram View of the Window in under Windows node in your Web Dynpro Explorer in NWDS.
3. Create Inbound and Outbound plugs for View1 namely inbView1 and outView1
4. Repeat the same for View2. So names will be inbView2 and outView2.
5. Create a navigational link between the Vies by creating a link from outView1 plug to inView2 plug.
6. Goto Layout tab for the View1. This is where you have embedded the Interactive form element.
7. Set the displayType property to native.
8. Under Events there will be onSubmit method, craete a new method called navigateToView2 and click Go. This will take you where you can implement your logic.
9. Fire the outbound plug of View1. See following code snippet:-
public void onActiong navigateToView2(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActiongotoView2(ServerEvent)
    wdThis.wdFirePlugOutView1();
    //@@end
10. Edit the Interactive form, it should open Adove LiveCycle Designer.
11. Drag-drop Submit button from WD Native library ontot the form.
11. Don't modify anything and check if you see below code snippet in the Editor.
// DO NOT MODIFY THE CODE BEYOND THIS POINT - 705.20051114114126.253659.250577 - SubmitToSAP.xfo
                      ContainerFoundation_JS.SendMessageToContainer(event.target, "submit", "", "", "", "");
                      // END OF DO NOT MODIFY
12. Now whenever you click submit button on the form, what it does is that it makes call to WD framework and the onSubmit action handler is called where you have written the code to navigate to View2.
Chintan

Error in opening sap web dynpro iview

hi all,
i am trying to open sap webdynpro iview in portal but getting the following error...
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
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).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs Found in negative cache -
Loader Info -
ClassLoader name: [local/SLAReporting_KM] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/com.sap.km.application sap.com/tcwddispwda sap.com/tcwdcorecomp service:webdynpro service:sld library:tcddicddicservices library:com.sap.aii.proxy.framework library:tcgraphicsigs library:com.sap.mw.jco library:com.sap.lcr.api.cimclient library:sapxmltoolkit library:com.sap.aii.util.rb library:com.sap.util.monitor.jarm library:tcddicddicruntime library:com.sap.aii.util.xml library:tccolapi library:com.sap.aii.util.misc library:tccmi library:tccol~runtime Resources: D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar Loading model: {parent,references,local} -
    at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
    at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
    ... 49 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0007.20060509173555.0000 (release=NW04S_07_REL, buildtime=2006-05-09:16:21:23[UTC], changelist=13857, host=pwdfm114), build date: Thu May 18 17:33:32 GMT+05:30 2006
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Wed Jul 12 09:17:18 GMT+05:30 2006 (Java Time: 1152676038656)
Web Dynpro Code Generation Infos
sap.com/pb
SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/pb_api
SapDictionaryGenerationCore 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:11[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0007.20060210160356.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:25:18[UTC], changelist=388986, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0007.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:14:35[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:31[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:31[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0007.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:15:22[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0007.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:22:56[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0007.20060210162212.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:27:38[UTC], changelist=389002, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
SapWebDynproGenerationCore 7.0007.20060228171604.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:30:40[UTC], changelist=391800, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0007.20060316153408.0000 (release=645_VAL_REL, buildtime=2006-03-18:15:45:50[UTC], changelist=394237, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for view com.lti.CSLs. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.<init>(DelegatingView.java:41)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.createUninitializedView(ViewManager.java:638)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:675)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:300)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:204)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:359)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:670)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:267)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:227)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1278)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
     at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:300)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)
     at sun.reflect.GeneratedMethodAccessor3364.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:659)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:532)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.ClassNotFoundException: com.lti.wdp.InternalCSLs
Found in negative cache
Loader Info -
ClassLoader name: [local/SLAReporting_KM]
Parent loader name: [Frame ClassLoader]
References:
   common:service:http;service:servlet_jsp
   service:ejb
   common:service:iiop;service:naming;service:p4;service:ts
   service:jmsconnector
   library:jsse
   library:servlet
   common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
   library:ejb20
   library:j2eeca
   library:jms
   library:opensql
   common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
   interface:resourcecontext_api
   interface:webservices
   interface:cross
   interface:ejbserialization
   sap.com/com.sap.km.application
   sap.com/tcwddispwda
   sap.com/tcwdcorecomp
   service:webdynpro
   service:sld
   library:tcddicddicservices
   library:com.sap.aii.proxy.framework
   library:tcgraphicsigs
   library:com.sap.mw.jco
   library:com.sap.lcr.api.cimclient
   library:sapxmltoolkit
   library:com.sap.aii.util.rb
   library:com.sap.util.monitor.jarm
   library:tcddicddicruntime
   library:com.sap.aii.util.xml
   library:tccolapi
   library:com.sap.aii.util.misc
   library:tc~cmi
   library:tccolruntime
Resources:
   D:\usr\sap\CX5\DVEBMGS00\j2ee\cluster\server0\apps\local\SLAReporting_KM\webdynpro\public\lib\app.jar
Loading model: {parent,references,local}
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
     at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:65)
     ... 52 more

Hi there,
Try re-deploy the application and restart the server. It will fix this problemn.
Regards,
Luciano

Web dynpro URL not working in user's UWL

Hi,
I am not sure if this is the right place for this question. I have created a web dynpro application and copied the URL and we put this URL in the UWL of a user using workflow, now the issue is when a user click on that URL on the portal side it's not doing anything but when I go r/3 side and click on the URL in my inbox I can see my web dynpro application running.
Any idea why is this happening.
Thanks,
Raj

Hi,
Have you checked the proxy settings in server? If yes use this code
URL u = new URL("http://download.finance.yahoo.com/d/quotes.rss?s=gm&d=t&f=l1t1c1");
System.getProperties().put("proxySet", "true");
System.getProperties().put("proxyHost", <HTTP Proxy Host> );
System.getProperties().put("proxyPort", <HTTP Proxy Port> );
InputStream is = u.openStream();
DataInputStream dis = new DataInputStream(new BufferedInputStream(is));
You can check the proxy settings in System Administration - >System Configuration -> Service Configuration -> Applciations ->com.sap.portal.ivs.httpservice -> Services -proxy.
Regards
Suresh Bachimanchi

After applying SP21 the web dynpro is not working (WDTypeNotFoundException)

Hi
We have recently applied SP21 to our NW04 system.
The patch was successfully applied. But while accessing the Web Dynpro, we are getting WDTypeNotFoundException exception.
The Error Message is as follows :
+500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Hide
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).
Root Cause
The initial exception that caused the request to fail, was:
500 Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Hide
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).
Root Cause
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type jp.co.companyname.projectname.pp.fnp09.datapreparemodel.types.Ru_cnfind not found
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:224)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:517)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.addAttribute(NodeInfo.java:530)
at jp.co.companyname.projectname.pp.fnp09.main.RawMaterialView.wdDoModifyView(RawMaterialView.java:191)
... 28 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4021.00.0000.20070905102710.0000 (release=630_VAL_REL, buildtime=2007-09-19:20:40:15UTC, changelist=460812, host=PWDFM026)
J2EE Engine 6.40 patchlevel 109749.313
Java VM Java HotSpot(TM) Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Other
Session Locale ja
Time of Failure Mon May 17 18:35:52 JST 2007 (Java Time: 1197884152810)
Web Dynpro Code Generation Infos
companyname.co.jp/pp~fnp09
SapDictionaryGenerationCore 6.4010.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-12-09:22:23:41UTC, changelist=280522, host=PWDFM026.wdf.sap.corp) +
If you have any ideas please let me know.
thanks and Regards
Raghunahth L

Hi raghu,
You can go to Visual administrator (/usr/sap/<SID>/JCxx/j2ee/admin--go.bat)
Give administrator credentials..
Cluster-Server-Services-webdynpro Runtime.
See if it is stopped.You can see red croos,if it is stopped.If it is,
Right click on Webdynpro Runtine and start.
One more option,you can give a try is start all teh srvices manually through
telnet
This can be done with "run' command on you system
telnet <IP adress> telnet port
telnet port will be http port ending with 8.
then give administrtaor credentials.
then go with these commands,
jump 0
add deploy
list_app
start_app-all
Try looki in for detailed error messages in default trace and application logs.
Loc : /usr/sap/<SID>/JCxx/j2ee/cluster/server0/log
Regards
Usha

Trigerring BPM from Web Dynpro screen not working

Hi Guys,
I am trying to trigger a BPM process from a Web Dynpro screen so I created a BPM process and created a WSDL and consuming the WSDL in the Web Dynpro app but getting an exception "Exception on creation of service metadata for web service mass config parameters service reference ID '28af57ab-9212-4ffd-90c6-0779c78a8da3' and application name 'demo.sap.com/testwd'. Check mass configuration has been done properly."
Please assist with what I am missing.
Thanks,
-Ash

I ran into the same error when attempting to consume a Process as a web service from my Web Dynpro component. I found that it is actually succeeding in kicking off my process, but it looks like it fails from my calling component. It seems to be related to calling a service meant to be asynchronous as a synchronous service. In my case, it throws a SOAP fault "com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Process start has been triggered" when I run it from the WS Navigator manually. It turns out that the same error is getting wrapped by the exception you were experiencing. Try using the getCause method to see if the same is true for you. This environment is still new to me so I don't have good solution on how to make it not throw that error in the first place.
[addendum] I ran across [this|Start BPM Process Trigger - Read timed out] thread that explains exactly what I had guessed. You can remove the response part of your WSDL and it will get called successfully in an asynchronous manor. Note that you must manually remove some of the entries in the WSDL since the visual editor with the 7.1 environment doesn't clean up after itself as well as it should.
Edited by: Joseph Robertson on Jan 12, 2011 11:04 PM

Calling SAP Web Services does not work

Hi,
using this little program, I try to get a simple "Hello World" from a webservice in SAP.
require 'soap/rpc/driver'
s = SOAP::RPC::Driver.new('http://server:port/sap/bc/srt/rfc/sap/Z_WS_RUBY/', 'urn:sap-com:document:sap:soap:functions:mc-style')
s.add_method("Z_WS_RUBY", "StringIn" )
p s.Z_WS_RUBY("World")
Unfortunately there is an error:
in `parse_local': unknown namespace qualifier: xml (XSD::NS::FormatError)
     from D:/rubyy/InstantRails/ruby/lib/ruby/1.8/soap/encodingstyle/soapHandler.rb:532:in `decode_attrs' ETC
In the WebService Recorder I find that the call is going through with request:
<?xml version="1.0" encoding="utf-8" ?>
- <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <env:Body>
- <n1:Z_WS_RUBY xmlns:n1="urn:sap-com:document:sap:soap:functions:mc-style" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<StringIn xsi:type="xsd:string">World</StringIn>
</n1:Z_WS_RUBY>
</env:Body>
</env:Envelope>
but response ist like:
- <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
- <soap-env:Body>
- <soap-env:Fault>
<faultcode>soap-env:Client</faultcode>
<faultstring xml:lang="en">Operation not supported</faultstring>
</soap-env:Fault>
</soap-env:Body>
</soap-env:Envelope>
What am I mssing here ?
Any help is appreciated.
Regards
Marcus
Message was edited by:
        Marcus Schiffer

Hi,
I am using SAP WAS Rel. 7.0. SAPWAS is of 0.11.
Couldnt retype your exact example, but I hope it works with my simple program too.
I activated the trace, here the result:
ignored element: Feature
ignored element: useFeature
Wire dump:
= Request
! CONNECT TO myserver:myport
! CONNECTION ESTABLISHED
POST /sap/bc/srt/rfc/sap/Z_WS_RUBY?sap-client=800&sap-language=EN HTTP/1.1
SOAPAction: "urn:sap-com:document:sap:rfc:functions"
Content-Type: text/xml; charset=utf-8
Authorization: Basic gzhtfzu=
User-Agent: SOAP4R/1.5.5 (/146, ruby 1.8.6 (2007-03-13) [i386-mswin32])
Date: Thu, 14 Jun 2007 08:14:05 GMT
Content-Length: 332
Host: myserver:myport
<?xml version="1.0" encoding="utf-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
    <n1:ZTestWsRuby xmlns:n1="urn:sap-com:document:sap:rfc:functions">
      <STRINGIN>dd</STRINGIN>
    </n1:ZTestWsRuby>
</env:Body>
</env:Envelope>
= Response
HTTP/1.1 500 Internal Server Error
set-cookie: sap-usercontext=sap-language=EN&sap-client=800; path=/
set-cookie: sap-recorder_sid=%2cc%3dID6-95D8115601C54670F9E2221A00000000--1%2co%3jhggz; path=/; domain=mydomain
content-type: text/xml; charset=utf-8
content-length: 264
sap-srt_id: 20070614/101842/v1.00_final_6.40/466FCFE5847D01C50000000095D81156
server: SAP Web Application Server (1.0;700)
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Body><soap-env:Fault><faultcode>soap-env:Client</faultcode><faultstring xml:lang="en">Operation not supported</faultstring></soap-env:Fault></soap-env:Body></soap-env:Envelope>
The call does not ecven go through to the Function Module in SAP.
Here is the call that worked from my VB Program:
<?xml version="1.0" encoding="utf-8" ?>
- <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <env:Body>
- <n1:ZTestWsRuby xmlns:n1="urn:sap-com:document:sap:soap:functions:mc-style" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<STRINGIN xsi:type="xsd:string">wert</STRINGIN>
</n1:ZTestWsRuby>
</env:Body>
</env:Envelope>

SAP BW Query iView not working.

Hi,
We have a WB Query iView which displays a Report correctly on the Portal. When the user right clicks and selects a menu (a dialog appears which changes the currency settings) and clicks ok he gets "Internet Explorer cannot display the web page" Error occurs. This particular report seems to work for some users and not for others.
Please Help.
Thanks
Rajendra P Venkata

Hello Prasad
I am reporting succesfully on WEBI 4.0 on BEx queries with Characteristic Restrictions (if I understand correctly SAP have changed the name back again to WEBI). My experience so far with BO4 is that you need to place a lot of calls to SAP to iron out some of the teething problems, so I suggest that you rairse a note with SAP to get direct support from them.
So I suggest develop in WEBI and get SAP involved to iron out the error messages.
Regards
Phillip

SAP Web Dynpro iView not working!

Similar Messages

Maybe you are looking for