How to design webdynpro aplication

[Former Member]

Hi freinds,

I need urgent help in understanding how to start designing application.

I know How to design a particular webdynpro application for one page functionality. Please help me to get bigger picture to disgn for entire assignment which has so many pages, funtionalities.

1. should I maintain only one project strucure in studio and keep adding different applications for different funtionalities for the complete work.

or:-

2. should I develop one project structure in studio for each funtionality,which can give me one page creation?

3. If muliple project hirarchy, is it possible to add multiple components?

If multiple projects.. then how to navigate from one project hirarchy to another hirarchy?

Do I need to use Interface controller, development component etc? How to use it?

Thanks in advance.

[pravesh_verma]

Hi Nav,

It is better is you start working webDynpro DC's. In that case you can easily divide your work in various teams then combine the complete project in one afterwards by including this DC in the main project. We generally work in DC's only if the project complexity is too high!!

<b>1. should I maintain only one project strucure in studio and keep adding different applications for different funtionalities for the complete work.

or:-

2. should I develop one project structure in studio for each funtionality,which can give me one page creation?</b>

<b>Ans:</b> It totally depends on your requirement. But it will be prefferable that you create different components in the same application and then provide the functionality to each component (By coding fo view and windows of this particular Component). By doing this you can easily maintain the data flow of your application since you can use the component level interaction within an application.

<b>3. If muliple project hirarchy, is it possible to add multiple components?

Ans:</b> Yes, it is very much possible to do that. As I have mentioned for last question. In fact this is genrally preffered instead of making individual view for each functionality.

<b>If multiple projects.. then how to navigate from one project hirarchy to another hirarchy?

Ans:</b> There are many tutorials on net for inter component interaction on SDN and www.help.sap.com, you can refer to those tutorials anytime.

<b>Do I need to use Interface controller, development component etc? How to use it?

Ans:</b> Yes, definately you would require them. Again I would say that refer to help.sap.com, this is the best place to learn any new thing. There are step by step tutorials for learning all these things.

Also refer to these threads for tutorials:

1) https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/bd0e0401-0801-0010-aaab-d0e1742da383

2) https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/751d003a-0b01-0010-8996-afbaa3fd5339

I hope this would help you!!

Regards

Pravesh

PS: Please consider rewarding points if helpful and solved.

[Former Member]

Hi Parvesh,

Thanks a lot for very nice help.

so, I am desging like one proejct hirarchy, and I will add different aplications with different or resued components inside it.

As my assignment involves about 20 funtionalities, so as you said, we use DCs if complexity is too high, so should I go without DCs?

also, Should I use only one component controller as a central location for common fields?

[pravesh_verma]

Hi Nav,

See dear, your can go anyways.. Your first proposal will also suffice.. I mean you can create a application and for each functionality you can create a component. Well if you want to interact within component then I have already provided you with the tutorial.

And, If you go with DC's then also in any case you hvae to include all Dc's in one main DC finally. In DC's case you have to make DC's with different functionalities, and then you have to create a final DC which will be adding all these DC's as used components.

I would again say just disscuss both these architechtures with your team and decide upon that.

One advantage which you will be having when going with DC's is you can work in various teams, where each team is working on different functionalities and then finally for shipment you can add all DC's into one, which is somewhat difficult in the first case.

I hope this would help you!!

Regards

Pravesh

PS: Please consider rewarding points if helpful and solved.

[Former Member]

Hi,

Depending on the requirements and dependencies between applications, you can create multiple applications under a single webdynpro project and each application in turn have multiple views (pages). Multiple applications under a single project will enable you to share components.

It is suggested to create Development Component of Web Dynpro Type instead of a plain 'Web Dynpro project'. This enable the web dynpro application as a reusable component.

Regards

Srinivasan T