Multiple versions of the same Web Dynpro application on the same SAP Portal

I have a single application (local development) and deploy directly to a SAP Portal(NW 7.0) from NWDS Version: 7.0.15
No problems there, works like a charm.
But I want to have multiple versions of the same application on one portal. Eg. ill build a version 1.0 for test and deploy this. Then continue to work on version 1.1 deploying this directly on the portal. The two versions should now co-existing under different names and/or packages.
Please help.

Hi Kim,
May be you can try this and see if this works for you. I am not 100% sure if it will work for you, but worth a try I guess. Create a Test WebDynpro project and try the following steps on this project. If they work out correctly and serve the purpose for you only then try them on your actual Web Dynpro project.
1. Create a test Web Dynpro project say "TestWDProject" with Component say "Comp1" and the default views and windows etc.
Also create some working application our of this component and Windows using the Context.
2. Right click the "Comp1" and select Copy.
3. Right click 'Components" node in the project structure and select "Paste"
4.This step will try to paste the copy of Comp1 as a new Component.
5. You can change the Name and Package of the Component.
6.Similarly you'll get the prompts for views,windows etc.
7.Once you have copied everything, Just check if everything looks good.
8.Now you can create a new Application using this new component and the Component Interface View and Deploy it.
9.Test whether the Application created out of this copy works same as the original component.
You can also try to create another Web Dynpro project and paste the Comp1 in the Components node of that new project and perform the same steps.
Again, try with these Test Projects and see if this serves your purpose before applying the steps on actual projects.
Regards,
Ajay

Similar Messages

Restrict simultaneous login to a web dynpro application by the same user

I have a stand alone web dynpro application and used the sap.authentication for user to login into the application. How can i restrict a user from accessing the application from two different browsers using the same userid?

Hi,
 You can try the following approach:
1. Create an outbound plug to some dummy view which shows the message to the user that he/she is already logged in. Let's call this plug "ToMessageView".
2. In the "wdDoInit" method of the component controller write the following code:
String loggedInUserID = WDClientUser.getLoggedInClientUser().getClientUserID();
String[] apps = WDServerState.getActualApplications(loggedInUserID);
//All entries of apps will look like <application-name>/<application-id>
boolean isRunningParallely = false;
for (String app : apps) {
 if(app.split("/")[0].equals(wdComponentAPI.getApplication().getName())){
 isRunningParallely = true;
 break;
if(isRunningParallely)
//fire the plug to message view here
FYI, I haven't tested this but do try it out.
Regards,
Satyajit

Web Dynpro application Session time expired in Portal

Hi All ,
   I am runnnig my web dynpro application in portal. When i log in for first time its working fine. But if if lof off and try to log in again in portal in same browser and try to access that web dynpro application then i am gettting error as follows in the browser. And even if i click on link the application could not be refreshed/opened.
500   Internal Server Error
The Web Dynpro Application 'WhowhoAppl' has expired. Restart the application using the Refresh button or via the following link WhowhoAppl.
Details:   No details available
I am also sending detail log trace below. Reply how to send this issue.
#1.#001083FEF475004D00000024000003E00004458D7D628B13#1202373905933#com.sap.tc.we
bdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmana
gement.ExceptionHandler.handleExpiration#J2EE_GUEST#0####fb017f90d55811dc93ff001
083fef475#SAPEngine_Application_Thread[impl:3]_31##0#0#Warning#1#/System/UserInt
erface#Java###Session unknown: Request with URI= was sent to unknown session.
Either request with wrong session parameters was sent, or session has expired b
efore . Current request parameters=. Is termination request=. Request w
as sent from host with IP=/name=. Hint: see SAP note 842635 for more detai
ls on session expiration. RID=
[EXCEPTION]
#8#/webdynpro/dispatcher/asianpaints.com/Whoswho/WhowhoAppl#Thu Feb 07 07:44
:39 IST 2008#{}#false#172.18.40.57#172.18.40.57#faf5bfc0d55811dccc92001083fef475
#com.sap.tc.webdynpro.clientserver.session.SessionExpiredLongJumpException: Sess
ion has expired due to a concurrent invalidation or logoff request. Hint: This m
ight occur if multiple logoff requests are sent to Web Dynpro by the portal as i
t is the case when a logoff is executed and the portal has active embedded and i
solated Web Dynpro applications. Only the first logoff request is processed, all
following logoff requests will lead to this message but but can be ignored. Ple
ase restart the application.
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doSessionMana
gementPostProcessing(ClientSession.java:868)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(
ClientSession.java:302)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing
(RequestManager.java:149)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doConte
nt(DispatcherServlet.java:62)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(D
ispatcherServlet.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.runServle
t(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReq
uest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:387)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServle
t(RequestAnalizer.java:365)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebCo
ntainer(RequestAnalizer.java:944)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(Requ
estAnalizer.java:266)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:9
5)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor
.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSes
sionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRu
nner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:3
7)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.ja
va:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:1
70)
Edited by: kavita chavan on Feb 8, 2008 12:04 PM

Default expiry time of a webdypro is 3600 sec.Try to increase it in the visual j2ee admin tool.

Web Dynpro Application is not openeing from Portal UWL

Hi,
I have developed a WD application which is integrated in the portal. This WD application navigates through several levels of approval by triggering the workflow. Initially USER will create the request launching the WD application from portal and upon clicking the SUBMIT button -> Workflow will be triggered and Work item will be sent to Approver UWL list in the Portal.
Link will be displayed in the UWL list and upon clicking that link WD application need to be opened where the details will be displayed and can approve the request by clicking on APPROVE button.
Here, We have created a PFCG role which can be assigned to USER to access the WD application to create the request from portal. But for Approvers, we have not assigned any such roles except UWL role.
Workflow is working fine, Workitem is displayed in Approvers UWL but when they click on the link -> WD Application is not opening. Configuration in SWFVISU is done.
I think we are missing some roles which need to be assigned to Approvers. We cross checked by assigning SAP_ALL profile to the Approers and found WD application is getting opened and everything is working fine. But we are not supposed to give SAP_ALL in the PRD.
Please help what are the other roles that need to be assigned to Approvers.
Thanks,
Bharath.

did you try by assigning pfcg roles to approvers along with Uwl?
Regards
Srinivas

Reg: Closing and Opening Web Dynpro Application in same browser

Dear Experts
In my webdynpro application when i click a button another web dynpro application is opened in another window(another browser) .
But i want to open the second web dynpro application inside the same browser in which closing the first applicaiton and opening the second web application in same browser window .
Please guide me to do this.
Regards
Arun

hi ,
Exit plugs have the special property that they use the defined URL parameter. After you have created the URL parameter in the parameter list on the Outbound Plugs tab page in the window editor, you can specify a value for this parameter in the method that calls the exit plug.
ref
link:[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ca3351508f04e7e10000000a42189c/content.htm]
it would help u
regards,
amit

Can the role info be passed from portal to ABAP web dynpro application

Hi,
We have some roles in the portal. We call the ABAP web dynpro applications from the portal. Is it possible to pass on the role from the portal to the Web dynpro ABAP application so that we can use this role information in the application.
Thanks,
Pooja

Hi,
you can try to add the expression
role=<IView.PCDUnit>
as part of the Application Parameters in the iView. This will be the role in 99%. However not all iViews started in the Portal must belong to a role. You can start iViews using page navigation that are not part of a role. Therefore the PCD does not talk about roles but about "units" which is the superordinate term.
the value will be the PCD path of the role - e.g:
portal_content/myFolder/roles/myRole

Call a ABAP Web-Dynpro-application via a BSP-Application

We have a BSP-Framework, that call several applications among other things other BSP-Applications, ITS-Application and other systems. Now I want to integrate a ABAP Web Dynpro-Application.
For the moment I can call the ABAP Web Dynpro-Application from our application.
This application runs in the same session as the Framework (verify in transaction sm04).
When I want to call another application in the Framework, the session will be killed (no more sessions in sm04). This happens also, when I want to call the ABAP Web Dynpro-Application a second time.
I guess, that the ABAP-Framework thinks I want to go outside the system (for example www.google.de) and close the session. I found out, that this wouldn't happen, if the application were suspended. But I found no way to tell the application via a url-parameter to suspend.
Can someone help me?

Thx for the tip,
but I can't firea suspend plug. Because I'm in BSP. I understand the docu so, that you have the option to call a other apllication like BSP from a ABAP Web Dynpro.
I want to call the ABAP Web Dynpro form BSP like this way.
1. Start BSP-Framework
2. Call ABAP Web-Dynpro-Application from BSP
3. Call another Application from BSP without automatically logout by unload ABAP Web Dynpro. (I have a chance to call the ABAP Web Dynpro again via url to suspend before I call the other app.)
Regards Stefanie

Web Dynpro application callable object error: Page Builder Not available

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

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

Access Web Dynpro application on different WAS ??????????

Hi All,
Current Scenario -
We have deployed ESS & MSS Business package on one WAS and the iviews are present on another WAS.We have created a Dedicated R/3 system which is pointing to the WAS where these packages are deployed.
All these things are working fine i.e. once the user maps the id pswd it directly runs the Web Dynpro applications in the iviews.
That means, even if application is running on one WAS, and the user personalises data on another WAS, it still retrieves the credentials and shows the appropriate results for ESS MSS Packages.
Query-
Now i need to implement the same scenario in my Web Dynpro application
Steps
1) I have the WD application running on one WAS and portal on another
2) In portal there is a R/3 system created
3) The Web Dynpro application needs to know if the user has personalised mapping against that system created on portal(other WAS)
4) If yes show him the home page else take him to the login page.
Just as it is implemented for ESS MSS Packages.
How can i pass the mapped data to the Web Dynpro iview ?
Thanks and Regards,
Samta Nichani

Amol,
as this questions existed twice, I've deleted one.
As roles are in the UME, you can access them. But why do you want to do this? You could login to that user, but then the question is what you want to do....
Regards,
Benny

Consuming an outbound iDoc from a Java Web Dynpro application on EP front

Hi,
I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
Regards,
Chandrima.

Hi,
I am trying to consume an outbound iDoc from a SAP system into a Java Web Dynpro application. The result would be displayed on the Enterprise Portal. Could anyone help me with the process to be followed for the same.
Regards,
Chandrima.

Web Dynpro application on different WAS ???????????

Hi All,
Current Scenario -
I have a Web Dynpro based application which gets the mapped id and pswd of R/3 system created on portal
It works fine if both portal and Web Dynpro application are on same WAS.
Problems -
1) Can i run this application on another WAS other than portal.
2) Where would this system be created i.e. on the WAS where portal is present or where the application is present.
3)If the latter is true, can i get the mapped id and pswd of a system which is present another WAS.
Thanks and Regards,
Samta Nichani.
Please help.
Thanks and Regards,
Samta Nichani

Hi Samta,
I try to understand your issue, so generally you can separate all the entities using different WAS, but this is strange. Why you want to use different WAS??
Regarding the authentication you could use Single sign-on, choosing the target system for authentication. Some links here:
http://help.sap.com/saphelp_nw04/helpdata/en/b9/5fc040fa717b2de10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/02/d4d53aa8a9324de10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm (SAMl protocol)
Hope this help you,
Vito

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 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 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

Developing a web dynpro application compatible to two JCO destinations

I have created a web dynpro application and integrated into a portal, which access R/3 using a JCo destination and retieves the data using a BAPI.
But I want to integrate the same application into another portal, which would access the different R/3 system having the same function module.
Is there any way for switching between two Jco destinations as the same application could be made to work for both the systems.
please suggest me as I am stuck up with this issue.
Thanks and regards
kris

hi Radha Krishna
Thanks for your reply,
Currently I have three iviews for the complete application Can you please tell me where to do the settings:
In the application properties dothe following:
Use the following url parameter to the
application URI sap-wd-arfc-useSys=<DEFAULT_SYSTEM>:<SUFFIX_OF_MAPPED_SYSTEM>
In the default system you can change your JCo destination name.
where do I do all these settings.
Kindly let me know.
Thanks and regards
kris

Multiple versions of the same Web Dynpro application on the same SAP Portal

Similar Messages

Maybe you are looking for