on 02-17-2006 8:36 AM
Hi all,
I have a WD application that contains various iFrame each one linked to different BSP.
For this I'm using an absolute url, e.g. this:
I would like to use a relative address (not absolute) in order to have a protable application, that I can use in different environment/server.
In addition, it's possible to pass parameters from a WD to a BSP and obtain output from BSP? It's possible to create a true communication from WD and BSP and viceversa?
Any help or suggestion on this issue will be appreciate.
Thanks,
Vito Palasciano
Vito,
The only way WD application may communicate with "outside world" is portal eventing.
Valery Silaev
EPAM System
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Vito,
Strat from <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/webas/webdynpro/tutorial%20on%20integrating%20web%20dynpro%20in%20portal%20-%2019.htm">Integrating Web Dynpro in Portal</a> tutorial.
This describes eventing from WD side. I'm not a BSP expert, so please search SDN/SAP Help yourself.
Valery Silaev
EPAM Systems
Vito,
This is a dead way:
1. WD IFrame is reloaded on every action (like selection in table, sometimes selection in combo-box, expanding tree etc). At every this action your BSP application will be restarted. Is it what you need?
2. WD does not allow embedding custom JavaScript, so implementing your own client-side communications will be impossible.
3. WD has no mechanism to transport parameters from non-WD application to WD application (except for portal eventing). Common J2EE data sharing idioms do not work here (HTTP servlet session, request forwarding etc).
Re-consider your own customize portal in light of these restrictions.
Valery Silaev
EPAM Systems
Hi Vito,
in <u>SAP NetWeaver 04s</u> Web Dynpro will provide a new mechanism to navigate from a Web Dynpro to a non-Web-Dynpro (like JSP) application and back again without the Web Dynpro application beeing destroyed before.
<b>New Web Dynpro Interoperability concept in NetWeaver 04s</b>
This new navigation technique is based on socalled <b>Suspend/Resume Plugs</b>. Within a Web Dynpro application which is not running in a SAP NetWeaver Portal you can fire a supend-plug for triggering this navigation. The parameter transfer is based on plug-parameters; the resume-plug eventhandler receives the parameters sent by the non-WD target application.
Within a Web Dynpro application which <u>is</u> running in a SAP NetWeaver Portal the navigation and the parameter transfer is based on portal navigation. The suspend-state of the Web Dynpro application can then be enabled by calling a Web Dynpro API method instead of firing a suspend plug with the same effect: the Web Dynpro keeps alive while the target application is displayed on the UI.
Regards, Bertram
Hi Bertram,
your news is very interesting. So, you can confirm me that it's possible to exghange parameters between Web Dynpro/non-Web-Dynpro (like BSP) applications in bi-directional way!
In this case, could you please post any links regarding useful documentations.
Your assertion open a wide range of development possibilities in order to realize interaction between applications.
Thanks,
Vito Palasciano
Hi
I ve the similar requirement. I ve to communicate to external web application from webdynpro application and vice versa. Could u please help me out in this. i'm new to web dynpro. I read a lot regarding this supend and resume plug. but i ve not seen any step by step implementation of this. So please tell where can i find help or send me some tutorial or sample code.
Thanx
Tony
User | Count |
---|---|
83 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.