How to decide proper development platform for developing Portal Contents ?

[Former Member]

Dear Experts

There are several platforms on which we can make

portal contents for SAP Portal.

1)Web Dynpro for Java

2)Web Dynpro for ABAP

3)PDK for .NET

I am trying to find out which of them would be most

efficient while developing system for the client.

It may be that for one who knows Java, Web dynpro for

Java would be efficient and so on.

However, when there is a situation where the developers

need to be trained before the project, which of these

platforms would be the most efficient.

Beside the evaluation based on language of development,

are there some other evaluation based on criteria like the

ease of development, deployment and debugging, cost for the

softwares and hardwares needed for the projects, contents

of the class library, templates provided and so on?

Does anybody have some supporting document that describes

on which circumstances which of these technologies would

be efficient while making systems for the client?

It would be of great help if you could share your insights.

many thanks,

Sudeep

[Former Member · Accepted solution]

Scope for WebdynPro

��

WebdynPro is used when requirements ask for a prototype using minimal time n effort. Highly skilled programmers are not necessary to write a WebdynPro application it uses dynamic controls without reloading the page.

��

Web Dynpro means programming at a higher level than iView development.

��

With Web Dynpro your development will be significantly faster even if you use backend connections (e.g. R/3).

��

WebdynPro is not suitable when the Client Side operations are significant in an application. WebdynPro does not support any Client Side operations (like JavaScript)

��

Use WebdynPro (with standard controls) for developing UI's that connect to components like EJB, Portal Service, Web Service, RFC-Function Module. containing the business-logic. This would clearly encapsulate the logic. Communication between iViews would take place through (client-side) Portal Eventing.

��

If the UI you are designing is very complex then its generally is preferred to go for WebdynPro because then you can choose to go for Static development of the UI in WebdynPro, but if the UI development in WebdynPro is also dynamic then there is not much difference in coding in both (WebdynPro and JSPDynPage). But in the static development one more advantage is that you get a feel of the UI while you are designing the view in the WebdynPro Designer. This is not possible in the case of the JSPDynPage.

Scope of PDK Components

��

Use Java-iView (Portal API/DynPage/HTMLB with specific control over HTML/JavaScript-Code) for developing UI's that can not be developed with WebdynPro because specific control of Client side-Code is needed or the application runs completely in the Portal and has a simple UI.

��

Use Java IView combined with State pattern for developing UI which has complex navigation.

��

For the applications which need complex session handling advanced features like AJAX Java IView is the preferred approach.

And also check the following

links

/people/renald.wittwer/blog/2005/01/05/develop-a-web-service-that-sends-an-email

http://help.sap.com/saphelp_nw04/helpdata/en/44/46bb2e70e20597e10000000a155369/ htm

/thread/8961 [original link is broken]

If this helped u pls rewards points

Warm Regards

Shanto Aloor

[Former Member]

hi,

please follow the following links:

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3818] [original link is broken] [original link is broken] [original link is broken];

[]