Examples of using exit plug

Hi there,
I am launching a WD app via the portal UWL. I'm using the action handler "SAPWebDynproABAPlauncher" and launching the app in a new window via the "launchinNewWindow" parameter.
What I'm trying to achieve is being able exit this WD app and launch a new WD app.
I've been advised to use an exit plug in the calling WD app but I'm trying to find a working example of how to code this as I obviously need to be able to construct the URL for the new WD app and somehow pass this URL as part of the exit plug?
I'm aware the exit plug needs to be defined as an interface outbound plug of the WD components' window but I'm stuck when it comes to how the firing of the exit plug and construction of the URL should be coded.
Any help would be greatly appreciated.
Michael

Hi Michael,
I'm not sure I understand your last question. Do you want to immediately close and exit app1 whilst launching app2.
Are you using app1 as some sort of redirect application?
As you mention that you are using the UWL - I'm guessing you're running within a portal?
In which case you could also use the portal navigation API which I believe can be fired from anywhere.
The good thing about this is that you can easily make it relative - easier to migrate through various development environments. But I guess that also depends on whether the app2 is indeed anothe WD app, whether you want to access it through the portal, use different authentication etc.
eg:
data lo_api_component type ref to if_wd_component.
data lo_portal_manager type ref to if_wd_portal_integration.
lo_api_component = wd_comp_controller->wd_get_api( ).
lo_portal_manager = lo_api_component->get_portal_manager( ).
call method lo_portal_manager->navigate_absolute
exporting
    navigation_target   = 'http://www.google.com'
    navigation_mode     = IF_WD_PORTAL_INTEGRATION=>CO_SHOW_EXTERNAL
*    window_features     =
*    window_name         =
*    history_mode        = IF_WD_PORTAL_INTEGRATION=>CO_NO_DUPLICATES
*    target_title        =
*    context_url         =
*    post_parameters     = ABAP_FALSE
*    use_sap_launcher    = ABAP_TRUE
*    business_parameters =
*    launcher_parameters =
hope it helps,
Cheers,
Chris

Similar Messages

Regarding Exit plug

Hi,
I would like to open an URL in a button click and also I want to close the window in which I have clicked the button.
I am trying to use Exit plug of interface view.
Please comment on this.
Regards
Vivek

Hi,
Open some URL,
First u have to create outbound plug in interfaceview
1)Open the node WebDynpro -
> Web Dynpro Components -
> <ComponentName> -
> Component Interface -
> Interface Views in that click <interfacename> interface view .
2) Select the Plugs tab in the Plugs area.
3)Choose New next to the outbound plug table.create new outbound plug.for example,Name GotoUrl, and choose Type Exit Plug.
4)Select the new outbound plug GotoUrl and choose New next to the parameter table.taEnter the name Url datatype as STRING.
5)Open the view in the View Designer and select the Properties tab. Choose Add next to the Required Controllers table and add the <interface name>InterfaceView
Place 1 button and check,
onActionButton write this code
wdThis.wdGetSampleInterfaceViewController().wdFirePlugGotoUrl(
"http://www.google.com");
Closing Window:
onActionClose()
wdThis.wdGet<your interface view controller>().wdFirePlug<your exit plug's name>("javascript:void(window.close())");
Check this thread also,
close main application window in WD for Java

Problem in Using an URL in Exit Plug (NW 2004s SP12)

Hi,
I have a Webdynpro application to specify the terms and conditions for the users when they login to the portal for the first time.
Upon Accepting the terms by the user, i used to loggoff the user and will redirect to the portal logon page again to relogin. (This was a requirment )
I was using an exit plug with the URL pointing to loggoff.jsp which invalidates the session and redirect to the portal login page again. This was working fine in NW 2004.
The code used to call the exit plug in the Window Interface view is,
wdThis.wdGetTermsandConditionsWindowInterfaceViewController().wdFirePlugToPortal("/globalportal/web/logoff.jsp");
When we upgarded into 2004s SP12 i am getting the folllowing error when firing the exit plug with the URL.
"The Exit Plug can not use an URL when used in Portal, use Portal Navigation instead"
We tried portal navigation as well, but seems that will work with PCD Objects only, where we need to redirect to the URL(logoff.jsp).
I tried the HttpServletResponse.sendRedirect() as well, but the control remains in the TermsandConditions view only.
Code Used:
WebCallback webcallback = new WebCallback();
HttpServletResponse response= webcallback.getResponse();
response.sendRedirect(URL);
Please let me know if somebody faced this issue and the work around for this.
My requirement is that upon clicking on the Accept button, i need to logoff the user by calling logoff.jsp will be destroy
the session and redirect to portal login page.
Please let me know the work around to call the URL in the view.
Appreciate your reply.
Thanks and Regards,
Sekar

Hi
Try
WDClientUser.forceLogoffClientUser(null);
url - the URL of the page that is shown to the user after logoff was done. If the parameter is null, the redirect is done to the "LogoffURL" URL that can be specified in the application properties. If this URL is also not defined, a redirect to a Web Dynpro internal logoff page is done.
So you may either accept default logoff-page (just text "Web Dynpro application terminated. Good bye!" or provide your own page via application properties).
Next, it is impossible to just log-off to auth screen. It is necessary to set as log-off URL some application that requires authentication also.
This way WD will first log-off user, then shows auth-screen and then login him again to the target application.
So try the following:
In NW IDE open your application properties, and add standard property "log-off URL", for example "/useradmin/userAdminServlet?userProfileView";
Regards
Ayyapparaj

Using PSE9 Plug-In or Aperture?

I have heard of Dfine 2 by Nik Software as a plug-in.
My ultimate question is if this plug-in is worth it or is it superseded by a capability on Aperture (or another plugin/application) getting rid of the noise and softening skin tones on high ISO photographs?
If Dfine 2 is better, then, is this plug-in able to go on PSE9 or just the CS5, and/or can it be a plug-in on Aperture?

Download Dfine 2 and do a Version comparison with Aperture's built-in noise-reduction tool. The trial is free (and your own judgement is worthsome). Would you mind posting your results here? I have done a similar test, but not on people or at high ISO. Thanks in advance.
Here is a link to the Dfine "How-to" video on Nik's site. Worth watching. The video is shot using Dfine 2 in Photoshop, but the controls and the interface are the same as the Aperture plug-in.
http://niktrainingvideos.com/video/completecollection/cc_dfine.html
Be sure to set your Aperture export preference for 16-bit TIFF ("Aperture→Preferences→Export→External Editor File Format").
When you use the plug-in, Aperture will duplicate the currently selected Version, export it in the file format specified, and open the plug-in with the newly created exported file loaded. When you save and exit the plug-in, control is returned to Aperture with your edited file (now a TIFF in my example) imported and saved over the duplicate Version created prior to launching the plug-in.
I have heard nothing but good about Noise Ninja, btw. I would have purchased it had I not I purchased Dfine as part of the Nik package.
Afaik, Nik tools come as either Aperture & Lightroom plug-ins, or as Photoshop plug-ins. If you want both (Photoshop and Aperture/Lightroom), you have to purchase both.
I think Dfine 2 is a 32-bit program. (If you are running Aperture 3 in 64-bit mode, you will be asked to close it and then it will be automatically re-opened in 32-bit mode.) Iirc, Nik has stated that the 64-bit version will be available before the end of the year.

Problem with POPUP and exit plug

Hi together,
in my case under certain conditions i create a popup window from a view with the method "if_wd_window_manager->create_popup_to_confirm( )"
The popup displays an error or success message to the user and a "OK" button is available. I stored the popup window in the attributes of the underlying view. So an action "OK_BUTTON_PRESSED" of the view is assigned to the OK-button of the popup using method "if_wd_window->subscribe_to_button_event( )".
In the action handler two commands are executed:
1) closing the popup with "if_wd_window->close( ) method of the popup reference stored in the view attributes".
and
2) firing a navigation plug from the view to the underlying window which calls its own window exit-plug.
Now my problem is that the popup window does not close when i leave the view with the navigation plugs. Without the plugs everything is working fine. It seems that the underlying view/window must still be available to close the popup.
In my case the exit plug is called. I can see it because a new URL is called and i can see the new page but the modal popup is still there and not closed.
Has anyone an idea how to solve that problem?
Edited by: Dirk Jäckel on May 23, 2008 3:34 PM

hi dirk......
what you can do is first execute the close method and set an attribute to 'X' once this close is over. then in your wddomodify method of the view check for that attribute and fire that plug. so the firing should take place in the modify view method.
---regards,
alex b justin

Closing window of web dynpro application with exit-plug don't run in the EP

Hi everybody,
I want to close a window that contains a Web Dynpro with a close button, because it's used and create as a popup from an other iView (that's not created with web dynpros) in the EP. I read the different threads how to close a window in web dynpro, like JavaScript in WD
I create a HTML file with the javascript code to close the window and it works fine, when I start the application separately.
If I used it in the portal and click the close button I get the following error message:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
I tried also: ...wdFirePlugExit("javascript:self.parent.close();") or some other javascript code, but got the same error message.
Then I tried:
WDPortalNavigation.navigateAbsolute(url,WDPortalNavigationMode.SHOW_INPLACE,(String) null, (String) null,(String) null);
instead of fireing the outbound plug in the action of the close button
(...InterfaceViewController().wdFirePlugExit(url);)
but than a new window with the EP open and the old is still there!
We use the NWDS2004s an the EP 7.00.
It must be possible to close a (this) window!
Thanks for any hint
christian

Hi,
This is what you can do:
1. You have already created the HTML file with the necessary javascript in the foloowing folder structure :
src->Mimes->Components-><your component name>-><fileName.html>.
2. Create a new iView of type URL in your portal.
3. Get the absolute URL of this HTML file inside your project. This will be in the following format:
http://<server>:<port>/webdynpro/resources/sap.com/<development ComponentName>/Components/<namespace>/<fileName>.html
You can find it thus:
try {
String u = WDURLGenerator.getAbsoluteWebResourceURL(wdComponentAPI.getDeployableObjectPart(),"filename.html");
wdComponentAPI.getMessageManager().reportSuccess(u);
} catch (WDURLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
4. Now enter this URL string as the URL for the iview.
5. Do a normal portal navigation to this iview on-click of the button.
Regards,
Satyajit.

Exit plug url parameters without XSS encoding

Hi,
I fire an exit plug with POST_PARAMETERS = 'X' and passing a different postParameters='sap-client=101&sap-user=5E224C57E11&sap-password=Asdf1234'. However the special characters are encoded and not passed correctly to the webdynpro app.
I got this behavior from CREATE_EXTERNAL_WINDOW with USE_POST = abap_true settings. I am trying to hide the sap-user and sap-password from the URL when redirecting to a new WebDynpro app in the same way, but remain in the current window.
My question is how can I prevent the automatic XSS encoding? I have turned off the login XSRF flag in SICF, but it has no effect on this.
Another option if somebody can tell me how can I do the same as CREATE_EXTERNAL_WINDOW in the same window, it should also be fine.
Your help is appreciated.
Charlie

>
Frederic Wood wrote:
> Thank you Frank! This accomplished exactly what I asked. Points awarded!
>
> However...
>
> What is bugging me now is the fact that the BSP app is processed on the lo_client->send( ) and my POSTed parameters are visible, but the BSP is not displayed. Then, when I actually Fire my WD outbound plug to display the BSP, the BSP is processed and displayed, but the POSTed parameters have been lost...
>
> Your thoughts?
That is because there are two very different calls to the BSP application occuring. The solution that you said worked is using the HTTP Client (browser if you will) of the application server. Therefore it is the ABAP system itself that is calling the BSP application. That is why nothing is displayed on the client side - because the server itself is making the request and receiving the response. This approach is really only usable if you need to call a data service (REST based or something like that), not if you actually need to dispaly the response to the user.
When you fire the navigation plug, it is the browser on the client machine that is making the request to the BSP application. This is completely separate from the request made from the application server in the previous step.
If you can't use GET and URL parameters, then you should just consider using Server Cookies. I don't think that hte HTTP Client class approach is going to get you what you want.

Webdynpro ABAP exit plug browser auto popup.

Hi Experts,
We are using the exit plug to close a webdynpro ABAP application.When this plug gets fired a auto popup from browser comes up with option yes and cnacel.When we are clicking on cancel the application is getting hanged instead of getting blank.
Is there any way to skip that browser auto popup using close window method or by some other means.
Thanks In Advance
Pradeep

Can check this article for hints.
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0018077-f0c9-2b10-87af-eb9bb40776d4&overridelayout=true
Also check this thread had a similar requirement.
Exit button for web dynpro within portal
Thanks
Avik
Edited by: AVIK SANYAL on Aug 20, 2009 12:00 PM

Exit Plug not working in Portal

Hi experts,
I have a web dynpro application (WDP A) which fire an exit plug to another web dynpro application (WDP B). It works fine in normal web dynpro runtime. The architecture of the application is shown [here|http://img232.imageshack.us/img232/7172/exitplug.png].
Now i have created an iView in the EP for WDP A. When the button which fires the exit plug is clicked, i get this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
Seems exit plug is not working in portal run time. Any one has an idea on how to solve this?? Use portal navigation?? What is that?? any guideline and documentation on that??
Thanks in advance.
Best Regards,
kityein
Edited by: kityein lai on Aug 5, 2009 10:04 AM

Hi,
Now that your WD apps are running in a Portal they should be more "Portal aware".
What I mean is that now they are part of a larger framework and you cannot just call the other WD app.
To do this properly (as the error message says) you should use the portal navigation.
Portal navigation consists of many variants: Normal, Dynamic, Quicklinks etc etc.
I personally advice to use Quicklinks if you want to navigate between 2 applciations running in the portal but are not native-portal apps. Altough this might not fit your requrements in this scenario, I cannot say....
In addtions here are some help resources:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/38/5dc53e5ae84d3be10000000a11405a/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/97/b0ef8b24a64ae884f0ab246e54cae5/frameset.htm
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/43/00c110606a5277e10000000a1553f7/frameset.htm
Hope this helps you a bit...
Benjamin Houttuin

Strange behavior after using NIK plug-ins

Every once in a while I encounter this strange behavior of Aperture. I first process the NEF's in Aperture (white balance, Exposure, Enhance... and, when needed, Cropping) and then I fine tune the image with the NIK plug-ins; when needed DfIne 2.0, Viveza, Color Efex Pro 3.0 and Sharpener Pro 3.0 Output Sharpener.
If I look at the processed picture then, I get a perfect presentation of the photo;
!http://users.skynet.be/fc419085/Aperture-1.jpg!
But when I press Z to zoom into a 100% preview I get this;
!http://users.skynet.be/fc419085/Aperture-2.jpg!
When I select the Loup in the normal view mode I get this;
!http://users.skynet.be/fc419085/Aperture-3.jpg!
This doesn't happen with all my pictures, yesterday I processed a series of 8 pictures an 6 of them showed this behavior the other two acted normal and I can't see what I did differently whit these last two.
When I export the strangely behaving photo's to a Tiff or a Jpeg, I get perfectly normal pictures.
The original NEF behaves normal. I have seen this behavior with NEF's from a Nikon D200, D2x and a D300. I have Aperture 2.1.2 running on a 2.33 GHz Intel Core Duo MacBook Pro running Mac OS X 10.5.6
Does anybody know what's happening and if so, how to solve this problem?
Cheers,
Ivan

I did some testing and what I found is too weird to be true.
First this mashed up look doesn't only happen after using NIK plug-ins, it also happens when making a roundtrip to Photoshop, given that certain conditions are met.
Give it a try yourself. Crop an image to an uneven pixelcount dimension, for example 4227 x 2797 and make a roundtrip to Photoshop. Then have a 100% view look at the new image in Aperture. You'll have a mashed up view, at least I do.
Now crop the same original image to an even pixelcount dimension, for example 4228 x 2798 and make an roundtrip to Photoshop once more. When you have a 100% view of the new image now, you'll see a perfectly normal photo.
Do you think Aperture developers are reading this forum?

WDRuntimeException: Exit-Plug must no be triggered with an URL when running

Dear SAP,
In our SRM-JAVA system, when I am leaving a web page, I get this error :
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal.
Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMasterWindowInterfaceView.wdFirePlugToApplicationPlugOUT
(InternalMasterWindowInterfaceView.java:205)
at com.sap.mdm.srmcat.uisearch.master.Master.callOCIComponent(Master.java:1119)
at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.callOCIComponent(InternalMaster.java:940)
... 32 more
More detail :
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMasterWindowInterfaceView.wdFirePlugToApplicationPlugOUT(at com.sap.mdm.srmcat.uisearch.master.Master.callOCIComponent(Master.java:1119)
at com.sap.mdm.srmcat.uisearch.master.wdp.InternalMaster.callOCIComponent(InternalMaster.java:940)
at com.sap.mdm.srmcat.uisearch.master.MasterView.onPlugfromResultSetViewIn(MasterView.java
Thanks in advance for your input.
Best regards
SAP NetweaverAdmin
Edited by: SAPNetWeavAdmin on Jan 14, 2011 7:11 PM

Hi,
could you please take a look at the following SAP note and see if this is relevant for you?
1450826 - Error when SLD administration called in portal environment
About your problem, is this happening every time you leave a web page?
Regards,
Jonas Cella

Replacement of Exit Plug to navigate to some URL

Hi All
After upgrade from Netweaver2004 to 2004s,
Webdynpro application doesnt support Exit Plug to navigate to some URL, when webdynpro application is run in Portal.
It gives following errors
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application
I tried using WDPortalNavigation.navigateAbsolute, but it is not working as expected.
Please guide me what can be done
Thanks and Regard
Sonal Mangla

Hi Sumit
 String deployableObjectName =
 wdComponentAPI.getDeployableObjectPart().getDeployableObjectName();
 WDDeployableObjectPart deployableObjectPart =
 WDDeployableObject.getDeployableObjectPart(
 deployableObjectName,
 "IsrlAddrApp",
 WDDeployableObjectPartType.APPLICATION);
 // Get the URL of the application
 String urlToTargetApp =
 WDURLGenerator.getApplicationURL(
 deployableObjectPart,
 new HashMap());
and now passing urlToTargetApp.
I am not sure WDPortalNavigation.navigateAbsolute works for such urls also or does it work for only pcdid paths.

Details on Exit plug

Hi,
I am working on Webdynpro for ABAP and would like to implement the Exit Plug functionality.
Can any one provide me one sample program for my reference, so that it would be easy for my development.
Regards,
Ramya.

<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%20creating%20an%20extended%20web%20dynpro%20application%20-%202.htm">Creating an Extended Web Dynpro Application</a>
Topics covered:
Creating a Web Dynpro application with multiple views and a more complex navigation structure
Working with actions and event handlers
Reading contents from the property resource bundles and storing them in a Web Dynpro context
Dividing data between view controllers and component controllers using context mapping
Manipulating UI element attributes at runtime using data binding
Leaving a Web Dynpro Application using an exit plug
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com
P.S. Hint: always check <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d">web Dynpro Sample Applications and Tutorials</a> section before posting question.

Firing Exit plug from the embedded component

Hello All,
I am working on a scenario where I am developing a Webdynpro component which is child to the MainComponent.
MainComponent view has links to access my child component as I have exposed my child component as Public part.
Once my application is access by MainComponent, I can only go back to MainComponent.
Now I need to fire an exit plug with URL (say sdn.sap.com) from my child component which will open new URL in same browser.
When I defined exit plug and passed on Url parameter to it, my component throughs exception saying "Cannot fire exit plug from embedded component".
Is there anyway I can achieve this?
Please guide me.
Ashutosh

Ashutosh,
I can not use WDClientUser.forceLogoffClientUser(url) as I need user to be logged in.
Actually, no. It is optional -- you may be either logged-in or not, in later case WD runs under some internal Guest account. So forceLogoffClientUser works in either case.
Valery Silaev
SaM Solutions
http://www.sam-solutions.net

Error while firing a WD Exit Plug in Portal :(

Hello All,
Am new in WD and created the Quiz Demo Application referring to help.sap.com.
I have added a URL to the Exit plug as:
wdThis.wdGetQuizInterfaceViewController().wdFirePlugGotoUrl("http://toyouamit.googlepages.com/home")
The application is working fine when run while deploying (from NWDS). But when run from the WD iView, the exit plug gives the following error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead.
In attempt to resolve this we have created an URLiView but in vain!!
Please guide
Awaiting Reply.
Thanks & Warm Regards,
Ritu

Hi,
the error tells it:
"Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead."
See here: http://help.sap.com/saphelp_nw2004s/helpdata/en/56/b4544251dcc153e10000000a1550b0/frameset.htm
There is also another thread where this was discussed, you can find some hints to implement portal navigation:
Closing window of web dynpro application with exit-plug don't run in the EP
Kind Regards
Stefanie

Examples of using exit plug

Similar Messages

Maybe you are looking for