Trigger the exit plug of a standard application from enhancement

Hi,
I've enhanced a standard web dynpro application and placed a view and window in the enhancement. Now from that view, I want to call the exit plug of the standard application. How do I achieve the same?
Thanks
Nidhi

Hi Nidhi,
In order to call the EXIT plug of the standard Window, firstly you need to create an Outbound plug from your view.
Enhance your Standard application by creating another Inbound plug in the window which contains the EXIT plug.
Now to create a Navigation link from the Outbound plug created, and the enhanced Inbound plug created in the Standard Component.
Now in this Inbound plug created in the Standard component, call the EXIT plug of the window present in that Standard component's Window.
I hope the process is clear.
One of my assignments has the same requirement and did the same.
Hope it helps.
Thank you,
Good day!
Regards,
Shashikanth. D

Similar Messages

  • What is the best way to port complete applications from DEV - Test - PRD?

    Hi,
    One of my customers recently asked me, Supposing I do the complete integrations and modelling in SOA Suite on the DEV Environment. Then,
    What is the best way to port complete applications from DEV -> Test -> PROD ??
    Also, since the URLs in use in the DEV environment would be very different from other environments, what is the easiest way to maintain them, and to build in Access Control mechanisms ?
    Best Regards

    Hi AJ,
    Nice PDF !
    Though the PDF does give a basic idea as to how we can go about the deployments using ANT and EM in Test and Prod, it doesn't really give extensive details. For eg. ANT would obviously need huge ANT scripts to be written for migrations to multiple Test servers, etc.
    Similarly, when we talk about EM, does it mean each of the services has to be manually deployed on Production ?
    I am sure we would be looking more towards a fully automated solution. No ?
    Best Regards
    Nitin

  • What is the best way to port complete applications from DEV - Test - PROD

    Hi,
    One of my customers recently asked me, Supposing I do the complete integrations and modelling in SOA Suite on the DEV Environment. Then,
    What is the best way to port complete applications from DEV -> Test -> PROD ??
    Also, since the URLs in use in the DEV environment would be very different from other environments, what is the easiest way to maintain them, and to build in Access Control mechanisms ?
    Best Regards

    It has been discussed here in detail-
    SOA 11g  Composite Deployment across multiple Instances: Best Practice
    since the URLs in use in the DEV environment would be very different from other environments, what is the easiest way to maintain them, and to build in Access Control mechanisms ?You may use deployment plan for this purpose. For access control, you may use Role Based access of Weblogic and EM. Please refer -
    http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10226/appx_roles_privs.htm#BABIHDFJ
    Regards,
    Anuj

  • How to trigger the exit event of a subform?

    hi there,
    we added some code to the exit event of a subform to do some validation, but we found out that
    if the user save the form after filling it and without clicking somewhere outside the subform,
    the exit event will not be trigger, so the code will not check ,then the form got saved with errors.
    could you pls tell us how to solve this?
    br.
    zj

    Hi,
    Instead of writin code in Subform just write the code in exit of the individual field.
    thanks,
    Amish.

  • What is the easiest way to open an application from Labview?

    I need to open an application from labview and depending on a user's selection, load one out of a group of files for the application that is opened. I need to know what is the best or easiest way to open an application and load a file that is used by the application based on a selection.

    Here is the response that I got from Cognex when I asked them about how to do this. Do you understand what they are talking about?
    In order to do something like this you will probably want to look into the Display Control/SDK for In-Sight. The Display Control gets installed along with In-Sight Explorer and includes a control that can be used in an environment like Labview to communicate with In-Sight sensors while the SDK is an enhanced version of the Display Control that gives you more control and functionality. I am not very familiar with the Labview environment so I will give some code snippets in VB.Net and hopefully you can adjust them as necessary. Specifically I see 3 possible avenues to do this:
     1) Using the Display Control you have access to many of the dialog boxes that are used in In-Sight Explorer including the Load Job dialog box. You can spawn this dialog box through a line of code similar to cvsInSightDisplay1.Edit.OpenJob.Execute(). I am not certain if the Labview environment will be able to spawn and display this dialog though. 2) With the addition of the SDK (additional purchase) you can directly access sensor properties including the job. There is a method called LoadJobFile to load jobs from on the sensor and LoadJobFileLocally to load jobs from the host machine. A typical line of code might be cvsInSightDisplay1.InSight.File.LoadJobFile("myjob1.job").3) If Labview cannot handle the dialogs and the SDK is not an option for you then you may still be able to do this using Native Mode commands. Native Mode commands are sent through a socket on the telnet port (typically port 23). Keep in mind that you will need to handle the username/password prompt and response when you first open the socket before issuing any Native Mode commands. The command to load a job file from the sensor would be the Load File command which would be a string similar to "LF myjob1.job". The Native Mode commands are documented in the In-Sight Explorer help file. 

  • Erase standard application from SSD hard drive

    Hey
    Ive got an 60gb ssd harddrive that is my main harddrive, and Iwant to erase application suchas appstore, automator, calculator and calendar... But is says “Automator” can’t be modified or deleted because it’s required by Mac OS X."
    I replaced the DVD reader for a extra SSD 60gb harddrive, so I still got the standard harddrive with 250gb and all the application.

    Some core apps cannot be deleted because they are just that... CORE APPS.  A better option would have been to buy a larger SSD instead of your second 60GB one and move your OS to that.  I understand that 60GB SSD are cheaper, but sometimes the "cheaper" solution isn't the right solution or a solution at all.

  • Exit plug - Error when tyring to close application

    Hi,
    I get the following runtime error when trying to close my WD Application:
    -> Parameters of exit plugs and suspend plugs must be of type STRING or TIHTTPNV
    My outbound plug og type exit takes 1 parameter:
    CLOSE_WINDOW of type Boolean.
    My code for calling the exit plug:
    DATA: l_ref_main_window TYPE REF TO ig_main_window .
      data: l_close_window TYPE boolean.
      l_close_window = 'X'.
      l_ref_main_window =   wd_this->get_main_window_ctr( ).
      l_ref_main_window->fire_exit_plg( close_window = l_close_window ).
    Thanks,
    Morten

    Hi Morten,
    There are certain restrictions or certain conditions to be considered before using the CLOSE_WINDOW  parameter in the exit plug, you may find them here.
    http://help.sap.com/saphelp_nw70/helpdata/en/45/1bc575ba064574e10000000a114a6b/frameset.htm
    Regards,
    Runal

  • 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,
    <b>wdThis.wdGetTermsandConditionsWindowInterfaceViewController().wdFirePlugToPortal("/globalportal/web/logoff.jsp");</b>
    When we upgarded into 2004s SP12 i am getting the folllowing error when firing the exit plug with the URL.
    <b>"The Exit Plug can not use an URL when used in Portal, use Portal Navigation instead"</b>
    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.
    <b>Code Used:
    WebCallback  webcallback = new WebCallback();
    HttpServletResponse response= webcallback.getResponse();
    response.sendRedirect(URL);</b>
    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

  • 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

  • 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

  • Close the application from a window or a view

    Hi,
    I need to check some prerequisities in the WDDOINIT of a window. If they are not
    available I send a pop up window to confirm to the user with the missing information.
    When the Ok button is selected I would like the application to be exit, I mean I'd like the browser to disappear.
    Any idea how to reach this?
    I tried the following:
    WDDOINIT of the view checks prerequisities, if not avaialable, the view sends a
    confirmation dialog. the ok button of the pop up is handeled by the action call_exit of this view.
    This action fire an outbound plug to an inbound plug of the window.
    The handle function of the window's inbound plug fire an intreface exit plugout.
    According to
    http://help.sap.com/saphelp_nw04s/helpdata/en/45/1bc575ba064574e10000000a114a6b/content.htm
    the associated application should end automatically.
    The effect I get is that the window disappears and the browser content gets completely white.
    I would like the browser (client) window to disappear, as well.
    Is this possible?
    kind regards,
          Sahla

    Hello,
    thank you all for rely.
    I solved the problem in the following way:
    (I found this in a previous forum question)
    So basically the exit plug is fired, but the setting the CLOSE_WINDOW parameter is necessary!
    I didn't do this in my firt trial.
    method ONACTIONON_COMPLETE .
    data : l_view_cntr type ref to if_wd_view_controller,
    l_win_cntr type ref to if_wd_window_controller,
    l_window type ref to if_wd_window,
    l_parameter_list type wdr_event_parameter_list,
    l_parameter type wdr_event_parameter,
    l_val type ref to data.
    field-symbols <fs> type any.
    l_view_cntr = wd_this->wd_get_api( ).
    l_win_cntr = l_view_cntr->get_embedding_window_ctlr( ).
    l_parameter-name = 'CLOSE_WINDOW'.
    create data l_val type c.
    assign l_val->* to <fs>.
    <fs> = 'X'.
    l_parameter-value = l_val.
    insert l_parameter into table l_parameter_list.
    l_win_cntr->if_wd_view_controller~fire_plug(
    exporting plug_name = 'EXIT_PLUG'
    parameters = l_parameter_list ).
    endmethod.
    kind regards,
           Sahla

  • 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
    <b>Leaving a Web Dynpro Application using an exit plug</b>
    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.

  • 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

  • Usage of Exit Plugs

    Dear All,
    Please give me the scenario where we should use an EXIT plug to close an application.
    In which hook method should the plug be fired?
    What are the possible parameters of the plug?
    Thank you.
    Regards,
    Prosenjit.

    hi,
    Please give me the scenario where we should use an EXIT plug to close an application.
    there are two scenarios :
    1. When you want to close a Window.
    2. When you want to open new window by giving the URL.
    What are the possible parameters of the plug?
    There are two parameters of this plug:
    1. URL of type String.
    2. Close Window type boolean.
    In which hook method should the plug be fired?
    You can call this plug on any ONAction.
    Ex :
    Do the following steps :
    -> Make an Outbound Plug to the Window.
    ->Make the type of Outbound plug to Exit Type.
    ->Add URL of type String as a parameter to the outbound plug of Window.
    ->Do remember to add Component Name in the Properties Tab of View ( othervs Calling Outbound plug of window from view wont b possible ).
    To open a new URL with closing the previous one write this Code in OnAction of Button : ( this Code can be get from Code Wizard too ).
    DATA lo_zexit TYPE REF TO ig_zexit . <zexit is name of my Component>
    lo_zexit = wd_this->get_zexit_ctr( ).
    lo_zexit->fire_out_window_plg(
    url = 'http://www.google.com' " string
    Similarly you can do for Closing a Window using parameter Close Window.
    Thanx.
    Edited by: Saurav Mago on Apr 17, 2009 10:32 AM

Maybe you are looking for