Packaging web dynpro application

hi all,
how can we package our WebDynpro projects with all the created iviews, roles, etc. so that we can deploy it to our app server  and just add the roles to the users
thanks

HI! fiel,
  create a transport package like this.
Transport the PCD(iviews,pages,worksets,roles,etc) objects from Development server to Quality Server to Production server..
Follow this steps in Development server
First login into development server
1)Try to keep all the objects in one folder(say myfolder) under portal content.
2)Now come to system administrator->tranport-> tansport package->export->portal content-> create a new folder
3)Select this new folder right click new transport package-> give the name and id->finish ->and close the transport package.
4)Now open the transport package which u have created just now.(make sure that u r transprt package is opend at right in content area)
5)Now select your folder which contains actual content(i.e iviews,pages,worksets,roles,etc ,, in this case my folder) right click add all objects to tansport package
6)Click on export button
7)Click on start export button
8)Download the export file using downlaod export file link
9)Save on your desktop
Now login into production server or quality server
Now importing the object inot quality server.
1)Go to system administartor->tansport->transport package-> import
2)Source for package file as client. click on browse and and select the .epa file which u have saved on to desktop (i.e from 9 step from above)
3)Click on upload
4)Select content to be overwritten as all and click on import
5)You get a message a import successful.
To check the object are present in your quality server or productin server
Go to the content administartor->portal content and check u r folder(i.e myfolder)
regards,
Mithileshwar

Similar Messages

  • The Web Dynpro application was called up with the wrong URL parameters

    Hi all,
    I am using the systems below:
    ERP STACK :16
    EHP : 4
    EHP SP Stack :4
    EA-HR * : 604(SP12)
    SAP-HR * :604(SP12)
    XSS JAVA components : SAP ESS 603 SP05
    SAP MSS 600 SP16
    PCUI_GP 603 SP05
    Business Package : BP ERP05 ESS 1.41 SP04
    BP ERP05 MSS 1.41 SP04
    BP ERP05 COMMON PARTS 1.41 SP04
    I am getting below error after clicking on the appraisal document:
    App. Called Up Incorrectly
    The Web Dynpro application was called up with the wrong URL parameters.
    Note
    Enter the URL parameters and their use.
    You can find more information on the functions that you can perform in the catalog for appraisal templates in the Implementation Guide (IMG) for Objective Setting and Appraisals under Edit Forms.
    I already applied the below notes also:
    1468466 Performance Management Launchpad Configuration
    1463821 Performance Management Portal Configuration
    1416756 OBN Configuration in Performance Management
    1408243 Configuration for object-based navigation
    Plz advise me??
    Thanks,
    Anumit

    can you paste the exact error. also you can take a HTTP trace and see which resourse or UWL is being launched!

  • Web-dynpro application -ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)

    i have created my web-dynpro application in development. and sent to quality . whenever i will execute my dynpro in quality  i got one message
    ERROR: ICF service node "/sap/bc/webdynpro/sap/zqm_cto_arr_general1" does not exist (see SAP Note 1109215) (termination: ERROR_MESSAGE_STATE)
    whenever i saw  sicf  transaction my web-dynpro is not seen . my dynpro application name is more then 15 character. what i will do . please give me valuable suggestion.....

    Hi Ashok,
                   for your requirement the application is not exist in particular place. It means, the webdynpro application is saved at different package or different location.
                  Please change the webdynpro component name and save it in particular request in package, then transport it to quality ..(development server )
    then go to SICF  t.code .. sap->bc->webdynpro->sap->find  out your application and activate the service of your webdynpro application.
    Now test it ... this solution might helpful to you .
    Regards,
    Naveen M

  • 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

  • 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:
    - <b>It violates the MVC paradigm</b> 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).
    - <b>Doesn't carry its own weight</b>. 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 ??
    - <b>Unnecessarily complicates error handling</b>. 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 !
    - <b>Produces unnecessary DCs</b>. 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 ?
    - <b>Not a typical application of the Command pattern</b>. 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

  • Example "Designing Component-Based Web Dynpro Applications" in NWDS 7.1

    hi,
    importing Designing Component-Based Web Dynpro Applications.zip into NWDS 7.1, I get ~ 200 errors.
    after repairing the projects (in WEB-Dynpro View) ands migrating, there are 76 errors:
    Component 'CustomersUIComp': Used component/component interface is missing: ComponentInterfaceImplementation com.sap.cd355.comp.adv.modelcomp.ModelCompInterface Hint: Check availability of public part archive     LocalDevelopmentcd355compadvui_final~sap.com/src/packages/com/sap/cd355/comp/adv/ui/customers     CustomersUIComp.wdcomponent     ModelComponent     1240309796017     1800
    TextView 'city_editor.text': Context attribute 'CustomersView.Customers.Address.city' does not have a type and cannot be bound to a UI element. Hint: Remove the binding or bind a context element matching the property's type.     LocalDevelopmentcd355compadvui_final~sap.com/src/packages/com/sap/cd355/comp/adv/ui/customers     CustomersView.wdview     text     1240309796032     1821
    ViewUsage 'com.sap.cd355.comp.adv.ui.customers.CustomersUICompInterfaceViewCustomersUIComponentUsage1': Embedded View/InterfaceView is missing. InterfaceView com.sap.cd355.comp.adv.ui.customers.CustomersUICompInterfaceView Hint: Repair Window     LocalDevelopmentcd355compadvmaster_final~sap.com/src/packages/com/sap/cd355/comp/adv/master     MasterComp.wdwindow     Unknown     1240309796503     1823
    hermann

    Seems like your example requires some other DCs as well, which don't appear to be part of the zip you mentioned.

  • Geo MAP in Web dynpro Application

    Hi all,
       we are trying to test the GeoMap Functionality in SAP Help we found that some Software Component is required to run the Geo Map Web Dynpro Application as given below
    "The GeoMap UI element can only be used with a special software component that is provided by the geographical maps.
    This software component which you can use to expand the Internet Graphics Service (IGS) is not included in the delivered SAP Web Application Server package. It must be purchased from a third-party provider. The GeoMap UI element cannot be displayed without this complementary software component. "
    can u help me with some pointers to these third party providers.
    Regards
    Sai Krishna Reddy

    Hi Sai,
    you can see the following tutorial
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tutorial on using geo services with web dynpro - 22.htm
    for GeoService information you can visit the following sites
    1.  http://www.geomap.com/
    2.  http://www.nacgeo.com/geoservices.asp
    Regards,
    Shubhadip

  • How to make changes to stdandard web Dynpro applications used in ESS

    Hi all
          I have uploaded the standard ESS Business Package,
    now the requirement is to change some features in the web dynpro application in it.How do I go about it?
    Regards
    Mansoor

    Even though those are tow different tabs, but both are under one view controller.
    So create a node and pass the data.. so data will be available to both tabs.
    View controller is local controller
    component controller is global controller.
    if you want to access the node outside your view then declare the node in component controller.
    Regards
    Srinvias

  • How to transport web dynpro applications to QA.

    Hi All,
    I am requred to transport the portal objects from Dev to QA. THe portal has about 3 web dynpro applications. Overall there are only few objects to be transported and JDI is not used.
    Now if I make a EPA file and upload it in QA will the web dynpro applications work? If not, what are the steps needed to make it functioning, please advice.
    Thanks for your help.
    Regards
    Suresh

    Hi Suresh.
    I think the easiest way is to deploy the Web Dynpro application at QA and to create a transport package of the PCD elements.
    That way you are in control of what is deployed and what is not deployed.
    Another solution might be to check the 'Include all dependent objects', but be careful to select 'None' in the overwrite dropdown box when importing. Or else standard SAP templates will be overwritten.
    Best regards,
    Jacob

  • Error - Creating a Web Dynpro Application Accessing ABAP Functions

    Dear All,
    we are trying to implement a web dynpro application with accessing ABAP functions.
    Previous tasks:
    -     insert the ABAP system into the SLD from the NWDI System (Transaction RZ70; the ABAP system is correctly insert into the SLD => technical systems)
    -     equipped the JCO connections with the web dynpro content manager (ping and test = OK)
    It’s the standard tutorial out of the SDN called “Creating a Web Dynpro Application Accessing ABAP Functions”.
    Some hints:
    -     There are no errors after the implementation and the “rebuild” of the project in the NWDS
    -     The auto deployment works fine to the development runtime system. The application is shown in the Web Dynpro content manager
    -     The In the build log I found these entries:
    System.err] [Invoked from  com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:585)]
    [System.err] java.net.UnknownHostException: FRASAPP562: FRASAPP562
    [System.err]      at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
    [System.err]      at com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:575)
    [System.err]      at com.sap.s2x.tools.GUID.<clinit>(GUID.java:179)
    [System.err]      at com.sap.s2x.tools.S2XGUID.getGUID(S2XGUID.java:19)
    [System.err]      at com.sap.ide.metamodel.core.i18n.LanguageState.createS2XID(LanguageState.java:191)
    [System.err]      at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:52)
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java:703)
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java:646)
    [System.err]      at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
    [System.err]      at com.sap.ide.webdynpro.checklayer.MDOChecker.check(MDOChecker.java:23)
    [System.err]      at com.sap.ide.webdynpro.checklayer.view.ViewChecker.check(ViewChecker.java:52)
    [System.err]      at com.sap.ide.webdynpro.checklayer.controller.ViewControllerChecker.check(ViewControllerChecker.java:96)
    [System.err]      at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:119)
    [System.err]      at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:56)
    [System.err]      at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:181)
    [System.err]      at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:56)
    [System.err]      at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2039)
    [System.err]      at com.sap.ide.webdynpro.generation.Generation.generatePersistentComponent(Generation.java:1296)
    [System.err]      at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:175)
    [System.err]      at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
    [System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
    [System.err]      at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
    [System.err]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [System.err]      at org.apache.tools.ant.Task.perform(Task.java:364)
    [System.err]      at org.apache.tools.ant.Target.execute(Target.java:341)
    [System.err]      at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [System.err]      at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
    [System.err]      at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:112)
    [System.err]      at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
    [System.err]      at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
    [System.err]      at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
    [System.err]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
    [System.err]      at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
    [System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [System.err]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [System.err]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [System.err]      at java.lang.reflect.Method.invoke(Method.java:324)
    [System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
    [System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
    [System.err]      at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
    [System.err]      at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
    [System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
    [System.err]      at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
    [System.err]      at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
    -     I’m able to start the application out of the Web Dynpro content manager with “run” => only the user interface is displayed without any functionality
    -     The “normal” start over the NWDS fails => error text
    “com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/J08_Flugdat_Daventdcflight~xxx.com' and application 'FlightListApp' are not deployed on the server. Please check the used URL for typos.”
    There two different URLs in use.
    Start via NWDS:
    http://frasapp562:50000/webdynpro/dispatcher/J08_Flugdat_Daventdcflight~xxx.com/FlightListApp
    Start via web dynpro content manager:
    http://frasapp562:50000/webdynpro/dispatcher/xxx.com/aventdc~flight/FlightListApp
    For test purposes, we started the BAPI (BAPI_Flight_Getlist) on the ABAP system directly. It works.
    Any ideas about the system behaviours (different URLs and missing functionality)?
    Thanks a lot in advanced!
    Best regards
    Christoph

    The Error has been solved – The implementation of a method was missing....
    Thx
    Christoph

  • Passing a parameter while calling a web dynpro application on portal

    hi
    I am having a web dynpro application which retrieves data from R/3 system via RFC using Jco destinations define in the Portal.
    Now we have different kinds of portals running on the same WAS, now I want the application to run which access data from different R/3 systems thru different JCo destinations.
    I need to create a logic such that mu application runs fine on any portal with any Jco destination.
    Is there any provision to achieve this.
    kindly let me know about this.
    Thanks and regards
    kris

    Gopi,
    there's an parameter called "sap-wd-arfc-useSys" you can pass to the application, to change the used JCo-Connection (read more at http://help.sap.com/saphelp_erp2005/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm)
    so, if you're running the WD-aaplication on <b>one</b> WAS and call it from different portals, you have to create three (or six with the META-connections) JCo-Connection on your WD-WAS.
    In a WD-application you can access URL-Parameters with:
    WDWebContextAdapter.getWebContextAdapter().getRequestParameter("<your URL Parameter-Name>");
    kr, achim

  • SDM failed when deploying a Web Dynpro application

    SDM failed when deploying a Web Dynpro application - I get the following error message:
    Sep 19, 2006 2:25:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : eix-blade-011
    SDM port : 50118
    URL to deploy : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp43621sap.comwelcome.ear
    Deployment exception : Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011
    Inner exception was :
    Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011

    Amr Azim,
    You must have logged in thru a dedicated connection to any server through say VPN before deploying.This way the sdm uses the same login as that of already establised connection.
    So 'sign of'  all connections to any servers before deploying and redeploy your application.Here you will be prompted to supply the sdm password and deployment shall proceed.

  • I am getting a error while executing the Web Dynpro Application Page.

    Hi All,
    I am getting a Error while executing a web dynpro application ::: 
    : Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    I have checked this error description in ST22  :
    What happened?
        The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
         along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_WDR_CLIENT_APPLICATION=====CP' has to be
        terminated.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
         and
        therefore caused a runtime error.
        The reason for the exception is:
        Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
        Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    Can u plz help me regarding this error.
    Thanks,
    Deepika

    >Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
    Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

  • Error while accesing ABAP web dynpro application

    Hi Experts,
    We are getting warning symbol on web page status bar, when we are accessing the ABAP web dynpro application
    only first page of application is getting loaded and when we click on page it is showing error on status bar and we can perform any thing.
    once we double click on warning icon,
    below details are coming:
    Line: 1491
    Char: 3
    Error: Object Expected
    Code: 0
    URL: url of the ABAP web dynpro application
    This scenario is occuring for many ABAP WD application for a client.
    Please guide how to solve this issue?
    Thanks!
    Piyush

    Hi
    First try a very simple application with nothing in it just one text saying Hello World
    Run it and see what happens.
    Also check if your url uses FQDN name. something like https:
    company.name.co:50000\.......
    If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
    dropdowns.
    regards
    Yuval.

  • Error while implementing a web service in web dynpro application

    HI All,
    I am trying to use a webservice in a web dynpro application.
    Web service description:- This is a very simple application which takes two String inputs and when submitted displays the string in the concatenated form.
    Web dynpro:- I used this web service in the web dynpro as an adaptive web service model.
    The Layout design consists of two input fields which are mapped to the request fields
    ex : - Request_Add.Add.S1 and Request_Add.Add.S2
    A text area to display the response:- Request_Add.Response.AddResponse.Response
    And a button which invokes the execute method
    public void onActionWebserviceCall(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionWebserviceCall(ServerEvent)
        wdThis.wdGetWebserviceCompController().executeRequest_Add();
        //@@end
    When I am trying to run the application I am getting error:-
    Exception on execution of web service with WSDL URL 'http://<Host>:<Port>/EjbWebservice/Config1?wsdl' with operation 'add' in interface 'EjbWebserviceVi_Document'
    Kindly reply.
    Thanks
    Neha

    Hi,
    Yes I have tested the web service in Navigator . The WSDL is also properly generated.
    I have not publish the web service in UDDI but as per my understanding this is not necessary. please correct me if I am wrong.
    Thanks
    Neha

Maybe you are looking for