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.

Similar Messages

Cannot deploy Web dynpro application from NWDS

Hi,
I am new to EP. I created a web dynpro application in nwds and tried to deploy it. But it gives the following error .
Settings
SDM host : nw04
SDM port : 50118
URL to deploy : file:/E:/WINDOWS/TEMP/temp12188WelcomeWebDynproprj.ear
Result
=> deployment aborted : file:/E:/WINDOWS/TEMP/temp12188WelcomeWebDynproprj.ear
Aborted: development component 'WelcomeWebDynproprj'/'local'/'LOKAL'/'0.2007.05.02.19.35.01'/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
I have even configured J2EE server in the nwds through preferences. I have used the default passwords during installing sneak preview.
What should i do to deploy my application successfully??????

My Server settings are fine in preferences of NWDS. Every thing is showing green
I get the same problem even when i delpoy through SDM.
This is the error when i deploy through SDM
Deployment started Thu May 03 06:27:27 PDT 2007
===========================================================================
Starting Deployment of MyFirstWebDynProPrj
Aborted: development component 'MyFirstWebDynProPrj'/'local'/'LOKAL'/'0.2007.04.14.22.37.46'/'0':
Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool. For more information, see SAP note 701654.
com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
Deployment of MyFirstWebDynProPrj finished with Error (Duration 6656 ms)
It seems like a configuration issue in SAP J2EE Engine Config Tool.What should i do.
Highest points will be awarded if some one can help me in this

Examples of 'calling a web dynpro application with parameters'

Hi!!
I'm I have been watching manual 'Web dynpro for abap: advanced concepts' in the sections 'url parameters' and 'calling a web dynpro application with parameters'.
Is there some example where these terms are seen.
Thanks in advance.

Hi Ana,
a window inbound plug can have parameters.
These parameters are automatically fished out of the URL by the framework.
So your inbound plug handler method has easy access to the parameters.
URL
http://<host>:port/sap/bc/webdynpro/sap/<your application>?param1=xyz&param2=abc
The application is configured to call an inbound interface(window) and plug.
The plug can be declared with parameters.
Double click on window inbound plug and add your parameters.
The parameters are made available by framework if present in Launch URL.
You can also call an application that has parameters directly entered on the parameters tab.
ie Parameters can be part of the application launch.
regards
Phil

How to make use of Portal service in the web dynpro application

hi
I have some portal service and how to use that in the web dynpro application.
and also what is the main diff between Portal Component and web dynpro application.
do we required portal to run web dynpro application.
thanks
mmukesh

Hi,
>> I have some portal service and how to use that in the web dynpro application.
Yes. U can use Portal service in webdynpro. Check the link given by subathra.
>> and also what is the main diff between Portal Component and web dynpro application
Portal Components are components designed to run in portal server while webdynpro application can run in J2EE WebAS.
>> do we required portal to run web dynpro application.
No for general cases. Just WebAS is sufficient to run webdynpro appl. But if u use portal service in ur webdynpro appl, then make sure both (portal service and webdynpro appl) run on same J2EE engine. That is mandatory.
Regards,
Vijai

Errors in While trying to Deopy Web Dynpro Application

Hi,
I have NetWeaver 2004S in My local System. I am facing one problem while deploying that Web Dynpro Application from NWDS. Error is pasted below. But i can deploy EP Application. I am facing the same problem when i tried to Deploy from Remote GUI.
Can anyone help me in fixing this problem.
Thanks,
Sridhar
Exception i got while deploying.
Starting Deployment of SampleWD
Aborted: development component 'SampleWD'/'local'/'LOKAL'/'0.2006.06.05.11.29.10':
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [H1B-2F241-HMY] with user name: [Administrator] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
Deployment of SampleWD finished with Error (Duration 2473 ms)

Hi Sridhar,
Please follow the steps below:
1. Open ConfigTool ( drive:\usr\sap\J2E (your instance)\JC01\j2ee\configtool
2. Go to Secure Store and change the password for the property admin/password/J2E (This password should same as the one you are trying to login to portal)
3. Click Add
4. Click Save and restart your server.
Should be able to deploy your components.
Happy deploying
Best Regards,
Shiva

Error While Deploying A Web Dynpro Appln thru NWDS

HI,
I am getting an error while deploying a Web Dynpro Application through NWDS.Following is the Exception
Aborted: development component '<ComponentName>'/'local'/'LOKAL'/'0.2006.07.26.15.06.05':Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [sapsbx28] with user name: [J2EE_ADMIN] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.] (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
When i give a request for deployment it asks for the SDM password. I enter a valid SDM pwd. If i enter a invalid SDM pwd i get some other exception. So the pwd SDM entered by me is correct.
can any one help me in solving this
regards
Nilesh Taunk

Hi Nilesh,
Try opening Visual Admin if your not able to login with username(administrator) and password. Problem with NWD2004s do the following steps.
C:\usr\sap\J2E\JC01\j2ee\configtool->configtool.bat->open it
1. Click on Secure store
2. Right you will find :
admin/password/J2E->retype your admin passowrd which you gave during installation=>SAVE properly
Restart the server and try login visual admin
Deploy now...Other wise see this thread same error solved:
Re: An Deploy Problem about Credentials.
Regards
Suresh

Problem of Creating a web dynpro application based on a car rental web serv

Based original SAP developer studio examples shipped with the developer studio, I first create J2EE application QuickCarRental. It works at http://192.168.254.4:50300/QuickCarRental.
A web service QuickCarRentalWebService is defined in J2EE application QuickCarRental. My web dynpro application TutWD_CarRental is web service consumer invoking QuickCarRentalWebService.
When I deploy TutWD_CarRental on SAP J2EE engine and run the application at http://192.168.254.4:50300/webdynpro/dispatcher/local/TutWD_CarRental/CarRentalApp, i can see the web dynpro web application interface right.
however, I get the following error when I input some data and Click button rent a car.
Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
when i click Display all bookings, the error is:
Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
I install SAP developer studio on my winXP desktop, and the SAP developer studio version is 2.0.10.
I have my SAP Web application server and J2EE engine Version 6.40 run on a different machine. the SAP server IP address is 192.168.254.4
could anybody give me some clue on this. is that because i miss some configurations on SAP server for enabling web services of QuickCarRentalWebService?
Thanks!
Thomas

HI
Find here.
https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/9fc0e990-0201-0010-199c-e38fc6dafb5d
Thanks
Lohi.

Example storing data in the default schema with a Web Dynpro application

Hi,
is there any example or tutorial for storing data in the default schema with a Web Dynpro application via SQLJ or Hibernate by using the default DataSource?
Thanks for Help,
Dirk

Hi,
When you create the TAB-Strip object you should be able to set the default displayed TAB against the properties of the TAB-Strip.
Gareth.

How to Debug a BAPI from a Web Dynpro application

I have a Web Dynpro application calling a BAPI, and I would very much like to see what data the Web Dynpro application is passing into the BAPI, and then debug the BAPI.
Is there a way to do this? I'm wondering if it is possible to somehow set up the ABAP stack so that on receipt of the BAPI call, it appears on the tRFC queue waiting for execution.
However it is done, I need a way to step through the BAPI on the ABAP stack.
BR,
Tony.

Hi Anthony,
The ABAP runtime environment contains various tools that you can use for analysis purposes, such as for debugging source code. All source code written for Web Dynpro applications in ABAP can normally be tested using the debugger.
To allow it to test other Web Dynpro-specific program entities too, the debugger has been equipped with a special enhancement. In the phase model in the active application, you can typically see the following information at various points in time:
-The structure of the content of the current controller,
-The properties of the UI elements in the layout of the current view
-The currently instantiated component usages
Starting the Debugger
The functions for debugging Web Dynpro entities are embedded in the new debugger. You therefore need to have selected the new debugger in your Workbench settings.
Selecting the New Debugger
1. In the menu, choose Utilities -> Settings.
2. A dialog box now appears that contains two nested tab page areas. Choose the parent tab page ABAP Editor.
3. The settings for ABAP Editor always open with the content of the child tab page Editor. Here, select Front End Editor (New).
4. Now switch to the Debugging tab page in the ABAP Editor settings and select New Debugger.
5. Save your changes and close the dialog.
Starting the Debugging Process
To run an application in debugging mode, you first need to set an external breakpoint in display mode in one of the methods in the component.
Now start a test run of the application from ABAP Workbench as usual.
The method in which you set the breakpoint depends on the purpose of the test run. To debug a view, for example, it is best to set the breakpoint in method WDDOMODIFYVIEW. Provided that the context of the view controller is not filled using a supply method, the view is fully instantiated in the phase model at this point in time.
Selecting the Web Dynpro Tool in the New Debugger
When you start the application, another session opens automatically for the debugger. If you have not yet saved any personal settings with regard to the layout of the debugger, the Editor tool will now appear on the left, with the Display Variables tool on the right.
1. Select one of the three desktops in order to reconfigure it for debugging the Web Dynpro application (see Designing Work Areas).
2. The right-hand edge of the debugger window has a bar of function icons. Choose the Replace Tools icon:
3. In the next dialog box (New Tool) open the lowest node (Special Tools) and choose Web Dynpro.
4. Confirm the dialog box.
On the right of the debugger desktop, you will see that the previous tool has now been replaced by the Web Dynpro debugger. You can save this setting for future debugging activities. To do this, choose Save Layout In the debuggers general toolbar.
Thankyou,
Ramganesh.

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

I am not able to create a callable object of my web Dynpro application

Hi,
I have my Portal server installed with NW2004S and with other components as follows.
·WAS 7.0 SP9
·EP7.0 SP9
·CAF 7.0 SP9
·VC 7.0 SP9
But now my webdynpro application is not reflecting in web Dynpro Component(GP Interface) during the design time, when I am trying to create a callable object.
So please can you suggest what is the problem and how I will get it corrected.
Regards,
Paresh.

Hi Aliaksei,
I had created a complete CAF application which was working fine. Then the server got crashed and i lost everything.So then i again installed the server and upgraded it to SP7.But than i was not able to see my web dynpro application while creating callable object. So i created another instance in the server at the base level(SP4) and i was able to create callable object.
There is no problem in the webdynpro application.I have added runtime library referece to my project : sap.com/cafeugp~api and also implemented the Interface IGPWebDynproCO in my component.
So i dont know where i am going wrong while i am upgrading the server.
Regards,
Paresh.

Assigning a login module to a Web Dynpro application

Hi everybody,
I would like a Web Dynpro application to use a custom login module for authentication. How can I do this?
What I found is the Security Provider (in the Visual Administrator tool) where I can add a login module to the "form" authentication mechanism for example. But if I do this I think all applications using this mechanism have to use my custom login module, right?
I wonder if I have to add my Web Dynpro application as a component to the Security Provider so that I can assign login modules to it. Am I on the right way? If yes, how can I do this? If I choose "Add" from the "Policy Configurations" tab a popup appears where I can enter the name for a new component. How do I specify my application there?
Thanks in advance for all answers,
Torben

Hi,
Web Dynpro applications use the ticket authentication template. U wud need to add your login module to the ticket template's login stack.
Incase you are accessing the Web Dynpro applications thru the EP u wud need to make changes to the authschemes.xml file too.
regards,
Vishal

Calling an interface METHOD of another abap web dynpro application

Hi Experts,
Can u plz tell how we can Call an interface METHOD of another abap web dynpro application in main WD Component.
Thanks
Mahesh

Hi ,,
   Example ALV interface method calling   GET_MODEL interface method
   View attribute   declaration   :    M_WD_ALV type      IWCI_SALV_WD_TABLE
     DATA lo_INTERFACECONTROLLER TYPE REF TO IWCI_SALV_WD_TABLE .
      wd_this->M_WD_ALV =   wd_this->wd_cpifc_alv( ).   "ALV is the usage name
     DATA lv_value TYPE ref to cl_salv_wd_config_table.
      lv_value = wd_this->M_WD_ALV->get_model( ).   " interface method calling in ALV component usage.....
Regards,
Devi

Using a Deployable Proxy in a Web Dynpro Application

Hi,
We have a Web Dynrpo application whose model is built from a set of Java business objects (POJOs.) These Java business objects currently make calls to a back-end R/3 system using JCo. We would like to provide the ability to allow the calls to be made over Web Services to the back-end system.
To call the RFMs as web services we have created a Deployable Proxy project, added the proxy as a public part, then referenced that public part in the web dynpro application. At this point we can write code to call the web service that looks something like:
InitialContext ctx = new InitialContext();
Object serviceObject = ctx.lookup("wsclients/proxies/meridium.com/rcmo~proxies/com.meridium.rcmo.ws.proxies.plants.PlantProxy");
Z_MRDM_GET_PLANTSService service = (Z_MRDM_GET_PLANTSService)ctx.lookup("wsclients/proxies/meridium.com/rcmo~proxies/com.meridium.rcmo.ws.proxies.plants.PlantProxy");
Z_MRDM_GET_PLANTSPortType port = service.getLogicalPort();
Z_MRDM_GET_PLANTS plantParameter = new Z_MRDM_GET_PLANTS();
plantParameter.setI_PLANTID(id);
plantParameter.setI_PLANTNAME(name);
Z_MRDM_GET_PLANTSResponse response = port.z_MRDM_GET_PLANTS(plantParameter);
MT001W[] plantArray = response.getET_PLANTS();
The problem is that when I call looup to retrieve the service implementation I get a ClassCastException.
The tutorials for using a proxy in web dynpro all assume that the web service is what the model is based upon but that's not possbile for our scenario we need to call the proxy from the business objects which are the basis for our model.
According to the help documentation for consuming a deployable proxy in a JSP page:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/b9766df88f4a24967dae38cb672fe1/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/2d/b9766df88f4a24967dae38cb672fe1/frameset.htm</a>
It discusses adding JNDI mappings. Is this what's needed for the reference to work in a Web Dypro application too? If so, how would one add the JNDI mappings references to a Web Dynpro application?
Many thanks!

Hi Dheeram,
I'm not certain about JSPDynpage specifically, but in a general J2EE Enterprise Application project you can add a reference to the application-j2ee-engine.xml file. For example here's the content of an application-j2ee-engine.xml file that references a proxy:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.mw.jco</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.proxy.framework</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">com.sap.aii.util.misc</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="interface">tc/sec/destinations/interface</reference-target>
 </reference>
 <reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="library">security.class</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="sap.com"
 target-type="service">tc~sec~destinations~service</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="sap.com"
 target-type="interface">tc~sec~destinations~interface</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="engine.sap.com"
 target-type="service">webdynpro</reference-target>
 </reference>
 <reference
 reference-type="weak">
 <reference-target
 provider-name="meridium.com"
 target-type="application">rcmo~proxies</reference-target>
 </reference>
 <provider-name>sap.com</provider-name>
 <fail-over-enable
 mode="disable"/>
</application-j2ee-engine>

Web Dynpro Application Deployment need server restart?

Hi Everyone,
When deploying Web Dynpro application on production environment, do we need to restart the sap portal system and server?
I have this issue that when ever we deployed new develop Web Dynpro application with new Abap Function module we need to restart our Enterprise portal production server. Is this really necessary. Is there other way to deploy Web Dynpro application with new Abap function module without restarting the server.
Please help,
Michael Mondelo

Hi michel,
for example , assume you imported a RFC bapi_flights from r/3 to webdynpro dc , and both rfc requests and webdynpro application is deployed to the development server and then moved to quality server.
now you have done some changes in the rfc bapi_flights i mean change in the structure .
case 1 : now with out reimporting the change to webdynpro application and you move the request to the quality r/3, your application dumps . because the structure change is not incorporated at your webdynpro DC.
case 2 : you have re imported the rfc incorporating the changes to the web dynpro applicaiton dc, now with out moving the structure changes request to the quality r/3 and you deploy the webdynpro Dc having the changes to your quality EP , still the applicaiton dumps because your appliction refers to the rfc with out structure change in quality r/3.
case 3 : you have moved the abap request having the strucutre change and also the webdynpro development component where the changes are also incorporated , now on moving both , your application might dump , because the meta data cache might have been not updated with the new structure change in the quality ep server. so you have invalidate the cache in the JCos you have used to import the rfc. or else on restarting the EP server , the new structure change will be updated in the server.
most of the cases Invalidation of cache works and in some cases you have restart the server fo the changes to update.
Regards
Govardan Raj

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

Similar Messages

Maybe you are looking for