Tutorial "Using EJBs in Web Dynpro Applications" ClassCastException

Hi,
I went through the tutorial "Using EJBS in WebDynpro Applications" step-by-step.
If I run the application I always get the following error message:
java.lang.ClassCastException:com.sap.engine.interfaces.cross.ObjectReferenceImpl
if I try to make a lookup to the SessionBean.
I use the following code:
InitialContext ctx = new InitialContext();
facadeHome = (FacadeHome) ctx.lookup("FacadeBean"); <- the error is related to this line
facade = facadeHome.create();
I have nothing more to provide to be more specifiv.
What did I forget to specify or to define?
Thanks for any help.

Hi holger,
try to do it like this
InitialContext ctx = new InitialContext();
Object obj = ctx.lookup("FacadeBean");//where FacadeBean is your jndi name
facadeHome = (FacadeHome)PortableRemoteObject.narrow (obj,FacadeHome.class);
facade = facadeHome.create();
hope this helps,
regards,
rahul.

Similar Messages

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Using EJBs in Web Dynpro

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Thanks for your reply and your suggestion. I have posted in the Web Dynpro Java forum... and suggest those wishing to participate in this thread to refer to the Web Dynpro Java forum.
As for your answer, I'm afraid it doesn't satisfy me.
Reuse is hardly an issue, since the CommandBean is specifically tailor-made for the Web Dynpro application that needs to use it. I could hardly imagine building another application that would just happen to have the exact same needs as far as data structure and processing is concerned...
As for the right Eclipse environment... the CommandBean is not an EJB artifact - it is an EJB client. The aforementioned tutorial in fact suggests creating it in the Java perspective.
But thanks anyway for your time and suggestion

Using CSS for Web dynpro application in EP

Hi,
I have some CSS (Style sheets) which I need to apply to the portal, so that all the web dynpro applications can have the same look and feel.
I read something about Theme Editor in EP. Can I somehow use that to import the CSS contents into the EP theme?
Any pointer to using CSS for Web Dynpro applications will be appreciated.
Thanks.
Puneet

Hi,
Go thorugh the follwing Web Dynpro Java
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/nw04stack09themes.zip
To know how to use it and for the steps to be followed please follow the tutorial here
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to edit web dynpro themes.pdf
the last url gives you a step by step procedure with wizards..
Regards,
RK

Error using tabs in Web Dynpro application

Hi all,
I am working on a web Dynpro application where I want to use "tabs" to display different vendor details, basically I need two tabs one for header data, one for address data. What I did is I created a group and there created the element for the user to enter the vendor number and also created a button and binded it with the BAPI, now I created a tab using tabstrip and then inserting the tab and adding the element to the tab (in my case i m using the table type), once I finish this and try to do the syntax chek i am getting this error: "ACC: Element "TAB" does not have a header"
Can you please help me with this?
Thanks,
Rajat

Looks like i was missing some step... I deleted everything and then re created and this time it works.

Using an other web dynpro application into an actual application

Hello,
I have a web dynpro application into a developer component previously developed. I want to import it an another web dynpro application.
The goal is to click a button, display the window of the other application and then once it is finished, go back to the first application (with some context parameters)
Is it possible ?
Thanks
Quentin

Hi,
Solved same issue in this thread Re: Data transfer between two different Web Dynpro components
PradeeP

Using EJBs in Web Dynpro and others model tecnology patterns

I'm having difficults in order to implement the business logic in Java.
I did a simple application and I put all business rules inside de controller in the web dynpro. Everything is ok to users, but I know that this isn't indicate.
I tried to encapsulate de business rules and dao in a session bea, but I'm not sucessfull. I'd like to receive advices/tutorial about model, I found some treads in the forum, but almost all links in the sdn are browke. I was thinking in using hibernate and spring, but I don't know with it's a good choive to sap world.

Hi,
try these tutorials:
(ejb) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c
(hibernate) https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/14f55178-0801-0010-0bac-974ed17e51d3
Regards
Ladislav
PS. Consider rewarding helpful answers

DB access in Web Dynpro application in Portal

Hi,
I will develop a web dynpro application which will run in the EP and use an DB. How are the best practices in this scenario ? Should I use a Web Dynpro Model (EJB or WebService) for the persistence operations or should I use Portal Services ?
Regards
Flo

Hi Florian,
go trrough these docs:
EJBs in Web Dynpro Application Using Wrapper Class
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00be903b-8551-2b10-c28a-8520400c6451]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c]
Accessing database table using EJB and web dynpro
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70929198-0d36-2b10-04b8-84d90fa3df9c]
Oracle Connectivity with EJB using WebDynpro Application
[https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdjava/oracle%2bconnectivity%2bwith%2bejb%2busing%2bwebdynpro%2bapplication]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b657b7e-0c01-0010-74a4-b71518871800]
hpe it hlps u...
Regards
Khushboo

Error in basic web dynpro application

i went through the following link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cb243c45-0801-0010-eb9c-88669007f130
and it has a tutorial to creating a web dynpro application
i have done all the steps,but when the explorer opens i get the following error
The requested URL could not be retrieved
While trying to retrieve the URL: http://saptd:8000/sap/bc/webdynpro/sap/zz_00_sflight?
The following error was encountered:
    Unable to determine IP address from host name for saptd
The dnsserver returned:
    Name Error: The domain name does not exist.
This means that:
The cache was not able to resolve the hostname presented in the URL.
Check if the address is correct.
Your cache administrator is root. .
can any1 help me out on this

Hi
1.Go to Transaction RZ10
2. Select the Instance Profile and Check the radio button extended maintanence.
3. create a new parameter icm/host_name_full
   give the value as $(SAPLOCALHOST).domain.ext
5. save and activate your profile.
4. restart your application server.
Note: domain.ext can be any name.
Regards
Abhi

Using a Deployable Proxy in a Web Dynpro Application

Hi,
We have a Web Dynrpo application whose model is built from a set of Java business objects (POJOs.) These Java business objects currently make calls to a back-end R/3 system using JCo. We would like to provide the ability to allow the calls to be made over Web Services to the back-end system.
To call the RFMs as web services we have created a Deployable Proxy project, added the proxy as a public part, then referenced that public part in the web dynpro application. At this point we can write code to call the web service that looks something like:
InitialContext ctx = new InitialContext();
Object serviceObject = ctx.lookup("wsclients/proxies/meridium.com/rcmo~proxies/com.meridium.rcmo.ws.proxies.plants.PlantProxy");
Z_MRDM_GET_PLANTSService service = (Z_MRDM_GET_PLANTSService)ctx.lookup("wsclients/proxies/meridium.com/rcmo~proxies/com.meridium.rcmo.ws.proxies.plants.PlantProxy");
Z_MRDM_GET_PLANTSPortType port = service.getLogicalPort();
Z_MRDM_GET_PLANTS plantParameter = new Z_MRDM_GET_PLANTS();
plantParameter.setI_PLANTID(id);
plantParameter.setI_PLANTNAME(name);
Z_MRDM_GET_PLANTSResponse response = port.z_MRDM_GET_PLANTS(plantParameter);
MT001W[] plantArray = response.getET_PLANTS();
The problem is that when I call looup to retrieve the service implementation I get a ClassCastException.
The tutorials for using a proxy in web dynpro all assume that the web service is what the model is based upon but that's not possbile for our scenario we need to call the proxy from the business objects which are the basis for our model.
According to the help documentation for consuming a deployable proxy in a JSP page:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/b9766df88f4a24967dae38cb672fe1/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/b9766df88f4a24967dae38cb672fe1/frameset.htm</a>
It discusses adding JNDI mappings. Is this what's needed for the reference to work in a Web Dypro application too? If so, how would one add the JNDI mappings references to a Web Dynpro application?
Many thanks!

Hi Dheeram,
I'm not certain about JSPDynpage specifically, but in a general J2EE Enterprise Application project you can add a reference to the application-j2ee-engine.xml file. For example here's the content of an application-j2ee-engine.xml file that references a proxy:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.mw.jco</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.proxy.framework</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.util.misc</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="interface">tc/sec/destinations/interface</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">security.class</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="sap.com"
 target-type="service">tc~sec~destinations~service</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="sap.com"
 target-type="interface">tc~sec~destinations~interface</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="engine.sap.com"
 target-type="service">webdynpro</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="meridium.com"
 target-type="application">rcmo~proxies</reference-target>
 </reference>
 <provider-name>sap.com</provider-name>
 <fail-over-enable
 mode="disable"/>
</application-j2ee-engine>

Problems using remote debugging for Web Dynpro applications

Hello All,
Have anyone ever encounter the above mentioned problem ? I am not able to step through my codes nor break @ my breakpoints using the debugging features despite many attempts following the tutorial on "Debuggng Web Dynpro applications". The problem always occur when I click on the Run -> Debug -> "Click on Debug". The debug perspective will show the threads running but my application window dows not appear. Should attempts be made to "Terminate All" threads and relaunch my apllication again, I will get an error message saying "Deployment of archive file already running : XXX.ear" Then I will need to wait some 15 mnutes or so before I can try again. Any suggestions ? Thank you.
The status of my J2EE engine is as stated in the tutorial:
1) State = "Debugging"
2) Debug Mode = "On"
3) Restricted Load Balancing = "Yes"
4) Productive Use = "No"
I have posted similar queries under "JDI" and "Web AS General" but did not receive and sugestions.
from
Kwok Wei

Hi
You should Create and Deploy if you want to reflect the code changes that you just did. However if you just want debug to an existing code then you need not Create and Deploy.
This can also be done as a two step process where you first deploy from NDS and launch Debug without create and deploy.
Is the issue that after you launch debug that it does not launch the application window.
Regards
Pran

Problem with HowTo guide - Use the BI Java SDK in a Web Dynpro Application

Hello,
I am following the HowTo guide - Use the BI Java SDK in a Web Dynpro Application
at <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e49be590-0201-0010-0c83-fc20e5da124f">this link</a>.
I have configured the connector on the WAS as needed.
The problem is that when I run the application I receive an Unauthorized error on the connector URL.
If I open this URL on a browser I receive a pop-up for UID and PWD and when I enter the same UID and PWD I used to configure the connector I am able to login and see the WSDL.
Any ideas?

I've never tried using BI in WebDynpro !!!
But i foond one posting on the connection problem https://forums.sdn.sap.com/click.jspa?searchID=955524&messageID=2133396
Regards,Anilkumar

How to change the Portal Password using a link from Web dynpro application

Hello Everybody,
I have a requirement to change the user password from a web dynpro application which is available on a mobile device. Firstly User will log into the portal through a mobile device and after getting authenticated user will be redirected to the mobile application. Within this mobile application there will be a link to change the login password(Portal login). Can somebody tell me how can i change the portal login password from a link available within the mobile application. Looking forward for a suitable reply.
Thanks to all,
Regards,
Saby.

Hi Maksim,
Thanks for your reply..but i would also like to know can we directly use the Change Password Iview "persoUserPassword" from the portal. Can i directly Pass the URL of this iview from the portal to a "Change Password" link in the web dynpro application, so that when the user click this link he should be able to see this Iview on his/her mobile device and should be able to change the password from there. But i dont know whether this iview will appear properly on the mobile device or we have to have a custom web dynpro application for this purpose...Please reply with a suitable answer.
Thanks in advance.
Regards,
Sarabjeet Singh.

Web dynpro application using workflow

Hi all,
I have developed a web dynpro application and attached that to the portal, so the user will login into the portal and will access the application. We have a new requirement now, when a user enters the data and hit save button on the web dynpro application, the workflow should trigger and should send the filled out (everything filled in) web dynpro application to his superior, the supervisor should be able to click on a link (which he should get through workflow) and should get the web dynpro application filled in. I am not sure how can I do this, so can you please guide me through.
Thanks,
Raj

Hi Raj,
could I suggest perhaps that you have a good search of SCN - there have been multiple posts about this sort of thing in the past.
for example : the wiki article
[Integrating WebDynpro ABAP applications with UWL for workflow in Portal|http://wiki.sdn.sap.com/wiki/display/WDABAP/IntegratingWebDynproABAPapplicationswithUWLforworkflowin+Portal]
is it perhaps that you do not use the UWL at your site? Or do you want to to send an email to the manager with a link directly to the approval application? The last case is one that I've come across many times before - it just means that you'll need to generate an approval task that is ended by a wf event and send an email to the manager with a URL parameter in the launch of the WDA application so that the app can pick up the details required to display and raise the WF event to complete the approval wf task.
There are all sorts of ways of persisting the information in the form so that the manager can see it in the approval. You can use the workflow container, you can use a db table, you could even use a shared memory area (not that I'd recommend this for this usage). But this is more a case of how to persist information in a workflow and probably a better question (search first, it's probably been answered already) for the WF forum and not the WDA forum.
Good luck in designing and building your application. Perhaps when you are done you could write a blog about your experience and further share how to do this with others.
Cheers,
Chris

How to make use of Portal service in the web dynpro application

hi
I have some portal service and how to use that in the web dynpro application.
and also what is the main diff between Portal Component and web dynpro application.
do we required portal to run web dynpro application.
thanks
mmukesh

Hi,
>> I have some portal service and how to use that in the web dynpro application.
Yes. U can use Portal service in webdynpro. Check the link given by subathra.
>> and also what is the main diff between Portal Component and web dynpro application
Portal Components are components designed to run in portal server while webdynpro application can run in J2EE WebAS.
>> do we required portal to run web dynpro application.
No for general cases. Just WebAS is sufficient to run webdynpro appl. But if u use portal service in ur webdynpro appl, then make sure both (portal service and webdynpro appl) run on same J2EE engine. That is mandatory.
Regards,
Vijai

Tutorial "Using EJBs in Web Dynpro Applications" ClassCastException

Similar Messages

Maybe you are looking for