Associate WebDynpro application to Resource type

Hi experts,
I have created a WebDynpro application to create/edit XML documents, which are stored in portal KM folders. These documents have a custom Resource Type.
I didn't use XML Form because it had too many limitations (static forms, only single-valued inputs...).
These documents are indexed by TREX, and can be retrieved during a search. When a user clicks on a search result, I want the item to be displayed in my webdynpro application (for editing purpose), and not as XML file, or in HTML using XSLT transformation.
Is this possible ? Do you know a workaround to that ?
Thanks a lot
Nicolas

Dear Mr. Srivastava,
thank you for the quick and helpful answer
but my problem isn't solved yet.
Regards,
Henrik

Similar Messages

We cannot type Polish (non-latin) characters in WebDynpro applications

We cannot type Polish (non-latin) characters in WebDynpro application (in runtime) because 'Browser Help Shortcuts' are fired.
To type a polish character in polish keyboard you need to press AltGr + letter (ie. AltGr + a/c/e/s/o/l/z/x/n). To type an uppercase polish character you need to press AltGr + Shift + letter. This comination is in fact the same as pressing Alt + Ctrl + Shift + letter (because AltGr produces Alt + Ctrl) and it fires some of 'Browser Help Shortcuts'. For example AltGr + Shift + O should produce a letter O with a dash on it's top but instead it fires 'Show nesting of HTML containers'.
We tried to turn off sap-wd-lightspeed, but then other key combinations are reserved for u2018Browser Help Shortcutsu2019.
We need to be able to use AltGr + Shift + a/c/e/s/o/l/z/x/n in runtime.
Product: SAP NW 7.11 SP04
WebDynpro for Java
I hope there is a somewhere a hidden parameter that solves our problem Maybe we're in some kind of debug mode?
Thanks for your help!!

The funny thing is that bold font [when message unread in message list] shows OK, ie in greek, but when i click on unread message, it is assumed to have been read, so it changes over to medium [non bold] and the encoding changes as well into the one that is not greek and thus unreadable. In ~/.sylpheed/sylpheedrc the fonts are:
widget_font=
message_font=-microsoft-sylfaenarm-medium-r-normal-*-*-160-*-*-p-*-iso8859-7
normal_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
bold_font=-monotype-arial-bold-r-normal-*-12-*-*-*-*-*-iso8859-7
small_font=-monotype-arial-medium-r-normal-*-12-*-*-*-*-*-iso8859-7
In /etc/gtk, for gtk1.2 apps the file refering to greek encoding [el] seems to be fine [exactly the same as in slackware 9.1].

Could not deploy policy for resource: type= url , application=MySecurex,

Hi
My situation :
I have 2 managed weblogic portal 10.3.0 managed servers in a cluster and 1 admin server. All are running as a service.
Deployments of new versions of applications are submitted by an automated script.
The steps in the script are :
- stop the services of the managed servers
- undeploy the previous version by using ant task
<target name="undeploy_old" description="undeploy old application" depends="downloadFiles">
 <java classname="weblogic.Deployer" output="./temp/${buildProject}_${deployEnv}/${buildVersion}/undeploy.txt" fork="yes">
 <arg value="-adminurl" /> <arg value="${adminurl}" />
 <arg value="-username" /> <arg value="${weblogic_user}" />
 <arg value="-password" /> <arg value="${weblogic_pwd}" />
 <arg value="-undeploy" />
 <arg value="-name" />
 <arg value="${buildProject}" />
 <arg value="-verbose" />
 <classpath refid="project.class.path"/>
 </java> - deploy the new version by using ant task
 <java classname="weblogic.Deployer"
 output="./temp/${buildProject}_${deployEnv}/${buildVersion}/deploy.txt"
 fork="yes"
 maxmemory="512m"
 inputstring="" >
 <arg value="-adminurl" /> <arg value="${adminurl}" />
 <arg value="-username" /> <arg value="${weblogic_user}" />
 <arg value="-password" /> <arg value="${weblogic_pwd}" />
 <arg value="-stage" />
 <arg value="-verbose" />
 <arg value="-upload" />
 <arg value="-deploy" />
 <arg value="-name" /> <arg value="${buildProject}" />
 <arg value="-source" /> <arg value="./temp/${buildProject}_${deployEnv}/${buildVersion}/${buildProject}.ear" />
 <arg value="-targets" /> <arg value="${deploytargetinstances}" />
 <classpath refid="project.class.path"/>
 </java>- start the services of the managed servers
Problem:
When the managed servers are restarting and the new version is going to prepared status, an error occurs for the new version of the application :
####<27-dec-2011 13.42 u. CET> <Info> <Deployer> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758076> <BEA-149059> <Module MySecurexEarAdmin of application MySecurex is transitioning from STATE_NEW to STATE_PREPARED on server s40beaportacc1p9106.>
####<27-dec-2011 13.42 u. CET> <Error> <Security> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-090064> <The DeployableAuthorizer "myrealm_weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl" returned an error: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource.>
####<27-dec-2011 13.42 u. CET> <Error> <HTTP> <S40BEAPORTACC1> <s40beaportacc1p9106> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1324989758779> <BEA-101199> <Could not deploy policy for resource: type=<url>, application=MySecurex, contextPath=/MySecurexEarAdmin, uri=/campaigns/emails/*.
weblogic.security.service.ResourceCreationException: weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
 at com.bea.common.security.internal.service.PolicyDeploymentServiceImpl$DeploymentHandlerImpl.deployPolicy(PolicyDeploymentServiceImpl.java:173)
 at weblogic.security.service.WLSPolicyDeploymentServiceWrapper$DeploymentHandlerImpl.deployPolicy(Unknown Source)
 at weblogic.security.service.AuthorizationManager$HandlerAdaptor.deployPolicy(Unknown Source)
 at weblogic.security.service.AuthorizationManager.deployPolicy(Unknown Source)
 at weblogic.servlet.security.internal.ResourceConstraint.deploy(ResourceConstraint.java:108)
 at weblogic.servlet.security.internal.WebAppSecurityWLS.deployPolicies(WebAppSecurityWLS.java:253)
 at weblogic.servlet.security.internal.WebAppSecurity.registerSecurityConstraints(WebAppSecurity.java:140)
 at weblogic.servlet.internal.WebAppServletContext.prepareFromDescriptors(WebAppServletContext.java:1189)
 at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1121)
 at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:449)
 at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:424)
 at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
 at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
 at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
 at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
 at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
 at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
 at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
 at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
 at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.security.spi.ResourceCreationException: [Security:090310]Failed to create resource
 at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:119)
 at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:162)
 at weblogic.security.providers.xacml.authorization.XACMLAuthorizationProviderImpl.deployPolicy(XACMLAuthorizationProviderImpl.java:281)
weblogic.management.utils.CreateException:
 at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:241)
 at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
 at weblogic.security.providers.xacml.DeployableAuthorizationProviderV2Helper.deployPolicy(DeployableAuthorizationProviderV2Helper.java:112)
com.bea.security.xacml.PolicyStoreException: <openjpa-1.1.0-r422266:657916 fatal store error> kodo.jdo.FatalDataStoreException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
 at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:684)
 at com.bea.security.providers.xacml.store.BasePolicyStore.setPolicy(BasePolicyStore.java:576)
 at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:222)
 at com.bea.security.providers.xacml.entitlement.PolicyManager.setPolicy(PolicyManager.java:165)
<openjpa-1.1.0-r422266:657916 nonfatal store error> kodo.jdo.ObjectNotFoundException: The instance "netscape.ldap.LDAPException: error result (32)" does not exist in the data store.
FailedObject: netscape.ldap.LDAPException: error result (32)
 at com.bea.common.ldap.LDAPStoreManager.flush(LDAPStoreManager.java:370)
 at org.apache.openjpa.abstractstore.AbstractStoreManager.flush(AbstractStoreManager.java:277)
 at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
 at org.apache.openjpa.datacache.DataCacheStoreManager.flush(DataCacheStoreManager.java:554)
 at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
 at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2007)
....>
My workaround:
Delete the <domain>\servers\s40beaportacc1p9106\data\ldap directory on the managed servers and restart
Does anyone knows what causes the error and how to solve it?
The goal is to be able to deploy our application by automation.

You must use not the original bean that you coded. You must use the bean generated by axis-wsdl2java.
The bean generated by axis-wsdl2java is:
- in the first beanMapping: MSPCSService.SMSMO
- in the second beanMapping: MSPCSService.SMSMOResponse
As you can see, the bean the axis-wsdl2java will generate is build with the namespace + "." + qname. If you use an domain like java.sun.com in namespace, then the package name you will use is inverted (in the sample, com.sun.java). Look at the code generated.
You client must use this beans, not the original coded by you.
This must work, worked for me :)

Need help in developing a webdynpro application using UWL API

Hi developers,
Iam developing a new WebDynpro application for UWL using UWL API.the functionality is to dispaly the summary of UWL like number of unread items, total items.
Iam getting the problem while deploying the application, iam getting warning while deployed the application.
I have given all possible ways mentioned in the below forum link
Re: Accessing PortalRuntime at runtime?
The exact problem is coming at reference file.
Please giude me how to move forward.
1. Below is the error when given "tckmcbc.uwl~api" in the service entry
deployed with warning :
Finished with warnings: development
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application local/UWLCountDemo and wait. Reason: Clusterwide exception: server ID 21763550:com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to prepare application local/UWLCountDemo for startup. Reason=Clusterwide exception: Failed to start dependent service ''tckmcbc.uwl~api'' of application ''local/UWLCountDemo''. Status of dependent component: STATUS_MISSING. Hint: Is the component deployed correctly on the engine?
2.Below is the error when i gave PORTAL:sap.com/tckmcbc.uwl~api in the sharing refernce entry
Finished with warnings: development
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application local/UWLCountDemo and wait. Reason: Clusterwide exception: server ID 21763550:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application local/UWLCountDemo cannot be started. Reason: it has hard reference to resource tckmcbc.uwl~api with type application, which is not active on the server.
Thanks in Advance
Sekhar.
Edited by: sekhar c on Mar 21, 2009 11:24 AM

Please see Kenichi Unnai in his blog "How to use UWL API for NetWeaver BPM Tasks"
How to use UWL API for NetWeaver BPM Tasks
The .sca-file can be found on the sap service marketplace, afterwards you need to import the .sca-file, add the SC to your "MyComponents" and then you can select your necessary DC's.

Exception During Testing WebDynpro Application in Developer Studio

Hi,
I am trying to test webdynpro application in developer studio as they have mentioned in the url -http://help.sap.com/saphelp_nw04/helpdata/en/c1/c6213e225f9a0be10000000a114084/frameset.htm
1)During Recording i am getting successful result as follows
Application Url: http://pawanm:50100/webdynpro/dispatcher/sap.com/compositeapp~webdynpro/MyApplication
Port: 12000
The Server is ready to accept Xml files from the Web Dynpro Runtime on Port 12000
-->Client Connected....
XML file received from runtime
The Server is closed and it will not accept any more Xml documents from the Web Dynpro Runtime.
The script has been stored on the local file system.
2)But when i am trying to reply the script generated by recording then i am getting
following error in console
->Contacting XML Client on Server to get initial XML document.
ERROR: Contacted the Xml client on the J2EE Server, but did not receive an Xml document from it.
And in log viewer i am getting following error
Date : 03/30/2007
Time : 20:44:47:481
Message : Cannot send an HTTP error response [500 Application error occurred during request processing. (details: java.lang.NullPointerException: null)].
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: The stream is closed.
Exception id: [0014222FC3E20052000009490000077C00042CE65506EC3A]
Severity : Error
Category : /System/Server/WebRequests
Location : com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl
Application : sap.com/tcwddispwda
Thread : SAPEngine_Application_Thread[impl:3]_10
Datasource : 17409750:C:\usr\sap\J2E\JC01\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 0014222FC3E200520000094B0000077C00042CE65506EF1F
Source Name : com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction :
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : /System/Server/WebRequests
Resource Bundlename :
Session : 0
Source : com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl
ThreadObject : SAPEngine_Application_Thread[impl:3]_10
Transaction :
User : Guest
So anyony please help me by giving some guideline or send me some document or url from where i can get usefull document.
And also please let me know that how to test CAF application by using some tool provided by SAP.
Thanks in Advance
Pawan Mishra

Hi Pawan
Is your engine functioning properly.I mean go to http://localhost:port/index.html then chech out the webdynpro links and other links available on this page .I am suggesting this so that we can check if sap.com/tcwddispwda
is working fine.Then we can look into the speacific application you are working on
Reward suitable points

Internationalizing a Webdynpro application

Hi friends,
I want to internationalize my webdynpro application which will run in SAP Enterprise Portal 6.0 SP11.I have followed the standard procedures of internationalizing as per documentation but what i see is that the application takes the browser locale language instead of the Portal language(which i desire).
Thus i want my application to show messages in that language which the user selects in the Portal.
Would be very grateful if u guys can provide me with any inputs on this.
Thanks,
Jitendra Chaudhari.
India.

Hi,
Pointers for the same is follows:-
Internationalization is used for adapting already existing Webdynpros application
Without changing the source code so that they can be used in several multi lingual languages.
Here we keep text strings separately from the application source code in a particular format(keys & values) so they can be processed in the standard translation mechanism.
Here frequently used texts such as labels or titles are stored as java dictionary simple types objects.
To do internationalization, copy the automatically generated *.xlf files and save them under the new name in the same directory.
For eg :- file convention like <old filename>_<language key>.xlf. Ex:- For German use the language key de.
For a particular user the locale is specified by the User management engine.
If not the locale is handled by the browser setting(HTTP Headers)
If not the default locale specified by the application will be returned.
If not default locale of the Virtual Machine(VM) is returned
This locale is passed to java.lang.ResourceBundle in the J2EE engine.
This will load the physically existing resource bundle either from any one of the following :-
Resource bundle of WD(if exists) or resource bundle of VM (if exists) or
Resource Bundle of without language suffix(always exists) given by the developer.
Also pls go thro' the blogs which is being mentioned by RK(my colleague) which will definitely give you a better insight.
Regards,
Guru

Webdynpro application running error

Hi
i am trying to run my webdynpro application, i got an error in webpage like .....
Error when processing your request
What has happened?
The URL http://secp:8000/sap/bc/webdynpro/sap/wdr_test_application_api was not called due to an error.
Note
 The following error text was processed in the system EC6 : Die URL enthält keine vollständige Domainangabe (secp statt secp.).
 The error occurred on the application server secp_EC6_00 and in the work process 0 .
 The termination type was: RABAX_STATE
 The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
 If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system EC6 in transaction ST22.
 If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server secp_EC6_00 in transaction SM21.
 If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server secp_EC6_00 . In some situations, you may also need to analyze the trace files of other work processes.
 If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 001 -u: SAPUSER -l: E -s: EC6 -i: secp_EC6_00 -w: 0 -d: 20080812 -t: 161055 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
help me how to solve this ........
Regards
Karuna

No Cross Posting!
Read the "Rules of Engagement"
Regards
Juan

View custom payslip using the standard webdynpro application in ESS

Dear All,
We want to display a custom developed payslip in the Salary Statement webdynpro application in the ESS. Our Custom Payslip gets called from a custom program. Can anyone please let us know how to call this program from the standard webdynpro salary statement appplication.
With Regards,
Kaustuv Goswami.

Hello,
What you have to do is create an iview for Webdynpro Application which you deployed on the portal ....add it to the workset and the role ....then copy the PCD Location of it and then goto the ECC SPRO -> Cross Application Components -> Home Page Framework -> create a new Resource and specify the PCD Location in the URL of the PCD Column of it ...then create a Service ...assign the resorce created for it ...and then finally add the Service to the SubArea you want and it will show in the portal under that SubArea like Personaol Information or others....
Hope it helps.
Shikhil
Edited by: Shikhil Arora on Dec 4, 2008 3:56 AM

How to close a Webdynpro Application with some action, if it is opened with a Tcode

Hi Experts,
I am looking to get some info regarding my post over here.
Scenario 1:
I opened my webdynpro application in SAP GUI (created a tcode for my webdynpro application and ).
Now, I have to add some button where I have to write a piece of code to close the GUI screen along with the webdynpro application. (ie, entire Tcode where the webdynpro application is shown, should be closed)
Please let me know if you have some info on this.
Scenario 2:
If the above scenario is not possible, then I wanted to know if I can call some screen in SAP GUI.
Note: The GUI screen must be called only from the webdynpro application that is opened with a tcode in SAP GUI.

Hello,
Please try this:-
Window Plugs: Startup and Exit - Web Dynpro for ABAP - SAP Library
You can close the WD Application by follwoing way-
Create a button in a view and assign an action on it.
Create on exit plug in window level and fire that in the view button action level.
Z2-wd comp.
NAME
EXT:-Window
exit plug name.
DATA lo_z2 TYPE REF TO ig_z2 .
lo_z2 = wd_this->get_z2_ctr( ).
lo_z2->fire_ext_plg(

Issue in webdynpro application while calling from UWL

Hi All,
I am working on APPRAISAL workflow in HCM module.
In new version of SAP has provided ABAP web dynpro application HAP_MAIN_DOCUMENT (component HAP_MAIN_DOCUMENT)
but it is not integrated with workflow. Earlier insted of this application there was a BSP application and this was integrated with workflow.
Now to integrate ABAP webdynpro application with workflow I have created new web dynpro application and calling HAP_MAIN DOCUMENT application and when I test through SE80 transaction then I am just passing Work Item ID and it is opening HAP_MAIN DOCUMENT application. I have done it as follows.
In swfvisu I am passing Work Item ID and In application I am getting business object details using this I am createing a URL and then using exit plug I am calling HAP_MAIN_DOCUMENT application
*METHOD exit1 .*
* DATA lo_nd_new_url TYPE REF TO if_wd_context_node.
**DATA lo_el_new_url TYPE REF TO if_wd_context_element.**
**DATA ls_new_url TYPE wd_this->element_new_url.**
**DATA lv_url TYPE wd_this->element_new_url-url.**
**DATA: l_cmp_api TYPE REF TO if_wd_component,**
 **result TYPE REF TO if_wd_window,**
 **l_window1 TYPE REF TO if_wd_window_manager.**
*** navigate from <CONTEXT> to <NEW_URL> via lead selection**
**lo_nd_new_url = wd_context->get_child_node( name = wd_this->wdctx_new_url ).**
*** @TODO handle non existant child**
*** IF lo_nd_new_url IS INITIAL.**
*** ENDIF.**
*** get element via lead selection**
**lo_el_new_url = lo_nd_new_url->get_element( ).**
*** @TODO handle not set lead selection**
**IF lo_el_new_url IS INITIAL.**
**ENDIF.**
*** get single attribute**
**lo_el_new_url->get_attribute(**
 **EXPORTING**
 **name = `URL`**
 **IMPORTING**
 **value = lv_url ).**
**wd_this->fire_exit_plg( url = lv_url ). "abap_true**
*** l_cmp_api = wd_this->wd_get_api( ).**
*** l_window1 = l_cmp_api->get_window_manager( ).**
*** result = l_window1->create_external_window(**
***url = lv_url ).**
*** result->open( ).**
**ENDMETHOD.**
In SE80 it is opening application perfectly in same session of new Z webdynpro application.
But when I click on UWL workitem it is not opening.
In dubugging I checked that workitem ID is passed correctly also URL is created correctly for HAP_MAINDOCUMENT but it is not opening.
Please let me know is there any setting in UWL config.
Edited by: Akshay Kale on Nov 17, 2009 11:51 AM
Edited by: Akshay Kale on Nov 23, 2009 10:07 AM

Hi akshay,
 Check the following links ,
Workitems, UWL and Web Dynpro for ABAP
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20f4843e-314f-2a10-2a88-8c4afa20dda6
another that talks about swfvisu
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a002d1eb-33f0-2b10-f391-e1e0c3057c17&overridelayout=true
hope this helps.
Thanks,
Sahiba

Dump in Webdynpro application

Hi,
I get the following error when processing a webdynpro application.
Kindly guide on hoe to overcome this error.
Error when processing your request
What has happened?
The URL xxxxxxxxxxxxxxxxx:8002/sap/bc/webdynpro/sap/dswp_ci_issue_management/ was not called due to an error.
Note
The following error text was processed in the system XXX : View usage MAIN_USAGE_1 does not exist in window ISSUE of component DSWP_IM_ISSUE_VIEW
The error occurred on the application server XXXXXXand in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_WDR_RR_VIEW_CNT_ASSIGNMENT~GET_EMBEDDED_VUSAGE of program SAPLWDR_RUNTIME_REPOSITORY
Method: IF_WDR_RR_VIEW_CNT_ASSIGNMENT~GET_DEFAULT_VIEW_USAGE of program SAPLWDR_RUNTIME_REPOSITORY
Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT_CONTROLLER of program CL_WDR_INTERFACE_VIEW=========CP
Method: INIT of program CL_WDR_CONTROLLER=============CP
Method: GET_VIEW of program CL_WDR_VIEW_MANAGER===========CP
Method: BIND_ROOT of program CL_WDR_VIEW_MANAGER===========CP
Method: INIT of program CL_WDR_VIEW_MANAGER===========CP
Regards,
Subhashini.

Hi,
I guess you might have deleted some view and didnot delete the same in the WIndow Embed view.
Is this dynamic programming.
Check the MAIN_USAGE_1 doesnt exists in your component.
Regards,
Lekha.

Error while running webdynpro application with an Interactive form

Hi all,
I am getting the following defect when I run a adobe interactive form (webdynpro application). Any pointers?
Regards,
Deepak
500 Internal Server Error
Failed to process request. Please contact your system administrator.
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.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
 at java.net.Socket.connect(Socket.java:464)
 ... 47 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; InfoPath.1)
Version null
DOM version null
Client Type msie7
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.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Oct 10 10:17:00 EDT 2007
J2EE Engine 7.00 patchlevel 109044.44
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
Session & Other
Session Locale en_US
Time of Failure Thu Oct 18 17:39:22 EDT 2007 (Java Time: 1192743562661)
Web Dynpro Code Generation Infos
local/NIBCOSecurityFormWD
SapDictionaryGenerationCore 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates (unknown)
SapGenerationFrameworkCore 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCore 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to UPDATEDATAINPDF
 at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:418)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterApplicationModification(ClientApplication.java:1132)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.afterApplicationModification(ClientComponent.java:895)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRespond(WindowPhaseModel.java:573)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:152)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: PDFDocument Processor failed to process Render Request.
 at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:55)
 at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:100)
 at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInteractiveFormHandlingContext.execute(PDFDocumentInteractiveFormHandlingContext.java:123)
 at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:340)
 ... 29 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:408)
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.render(PDFObject.java:3948)
 at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRenderHandler.handle(PDFDocumentRenderHandler.java:148)
 at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
 ... 32 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
 java.net.ConnectException: Connection refused: connect
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:385)
 ... 35 more
Caused by: java.net.ConnectException: Connection refused: connect
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
 at java.net.Socket.connect(Socket.java:464)
 at java.net.Socket.connect(Socket.java:414)
 at java.net.Socket.<init>(Socket.java:310)
 at java.net.Socket.<init>(Socket.java:125)
 at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:648)
 at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
 at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:550)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
 ... 37 more

Hi Deepak,
If you have solved the issue could you kindly close the thread with the solution as this will help others as well. If not kindly update the thread with the status.

Error while previewing deployed webdynpro application.

Hi,
I am a newcomer to the EP environment. After installing the server and configuring NWDS, I created a simple webdynpro application. I was able to successfully deploy it to the portal but when I try to preview it I got the following error. Please shed some light on this. I am working on EP 6.0.
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Hide details
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322), 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
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC local/Test_WD:
SapDictionaryGenerationCore: 6.4019.00.0000.20061005103449.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:17:59[UTC], changelist=419709, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro: 6.4019.00.0000.20061005104005.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:23:05[UTC], changelist=419717, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore: 6.4019.00.0000.20061005103956.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:11:19[UTC], changelist=419716, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates: 6.4019.00.0000.20061005104024.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:50:52[UTC], changelist=419718, host=PWDFM026)
SapWebDynproGenerationCTemplates: 6.4019.00.0000.20061005104024.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:50:52[UTC], changelist=419718, host=PWDFM026)
SapGenerationFrameworkCore: 6.4019.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:10:28[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 6.4019.00.0000.20061005104123.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:27:18[UTC], changelist=419723, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary: 6.4019.00.0000.20060119123716.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:15:01[UTC], changelist=385561, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon: 6.4019.00.0000.20061005103956.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:11:28[UTC], changelist=419716, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCore: 6.4019.00.0000.20061005104123.0000 (release=630_VAL_REL, buildtime=2006-10-26:20:27:47[UTC], changelist=419723, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates: (unknown)
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
No information available
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_05-b04, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
java.lang.NoClassDefFoundError: com/sap/tc/webdynpro/progmodel/api/IWDEventHandlerId
 at java.lang.Class.getDeclaredConstructors0(Native Method)
 at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
 at java.lang.Class.getConstructors(Class.java:865)
 at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:68)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.<init>(DelegatingInterfaceView.java:44)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:131)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:374)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 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:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi,
In NWDS, have you depoyed this application? while deploying does it throw any error??or successfully getting deployed? for deploying the application please choose deploy and Run option.This will deploy as well as run your application.
Regards,
Ameya
Message was edited by:
 Ameya Pimpalgaonkar

Error while executing webdynpro application : he URL does not contain full

Dear All,
I had installed SAP in my system.But when I am testing webdynpro application I am getting the belwo error. Please let me knwo what setting I need to do to avoid this error.
Error when processing your request
What has happened?
The URL http://hari:8000/sap/bc/webdynpro/sap/z_test_pg was not called due to an error.
Note
The following error text was processed in the system DEV : The URL does not contain full domain specification (hari statt hari.<domain>.<ext>).
The error occurred on the application server HARI_DEV_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DEV in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server HARI_DEV_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server HARI_DEV_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 800 -u: SAPUSER -l: E -s: DEV -i: HARI_DEV_00 -w: 0 -d: 20080109 -t: 073032 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team

Hello,
Little extract from the SAP online help :
In Web Dynpro ABAP it is imperative that a client browser with a fully qualified domain name (FQDN) has access to the AS-ABAP. For this reason the full URL must be assigned to a Web Dynpro ABAP application when it is called. The URL must not be shortened (for instance, no domain specification).
More info on how you should do this can be found here :
[Click|http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm]
This will solve your problem.
Success.
Wim

SBO Mailer Error - The specified resource type cannot be found in the image file

Hi Experts,
I have created an alert in SBO and selected email and internal option for same. I get internal message however email is not getting delivered, I checked the Event Viewer of Windows and below error is shown for SBOMail.
The description for Event ID 62 from source SBOMail cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Failed to mark records error [-1]
The specified resource type cannot be found in the image file
I can send email from sbo for other documents but the alert is not delivering email.
Please advise.
Thanks
Deepak

Hi Deepak..
Check with these threads...
http://scn.sap.com/thread/966957
http://scn.sap.com/thread/1295818
SBOMail Application log error
SBOMail error in event log
Hope Helpful
Regards
Kennedy

Associate WebDynpro application to Resource type

Similar Messages

Maybe you are looking for