WebDynpro or JSPDynPage with HTMLB

[Former Member]

We'd like to develop JavaApplications (PortalService, EJB,..) that will be called through a Portal-iView.

Some people from SAP say that it is better to use Java-iViews for frontend and others say that WebDynpro is strategic.

When looking at it, Java-iViews run inside the PortalPage where WebDynpro is always integrated by a generic WebDynpro-Java-iView using URL-isolation (IFRAME). This means that the browser always calls the WebDynpro-Content as if it comes from a dedicated server.

But WebDynpro has an easier and more standardized UI-design than HTMLB.

What are other pro/con's or recommendations?

[Former Member · Accepted solution]

WebDynPro is great for building application quickly (because UI is drag and drop) where the backend is SAP based application. WebDynPro is meant for developing UI where business logic sits in any SAP based application , EJB or WebServices.

HTMLB gives you flexibility but UI is time consuming. You are not restricted to above three components. If you are planning to write a Portal Service then that has to be written in Portal only. There is no separation of business logic from UI but you could use MVC(model view controller) methodoly with HTMLB as well to separate the UI from business logic.

Message was edited by: Prakash Singh

[Former Member · Accepted solution]

Ok, it is clear to use HTMLB for applications that run completely on the Portal, but what is the better Strategy, when I want to develop Applications that are acessed through the Portal and where its business logic sits in R/3 or EJB etc: use WebDynpro (on Portal WebAs or dedicated / R/3-WebAS) or JavaiView-HTMLB (on Portal)?

Will the portal UI soon be based on WebDynpro?

[Former Member · Accepted solution]

Hi Manuel,

Use WebDynPro because you will spend less time developing UI. I don't know if you know but SAP has also released WebDynPro for ABAP. Portal UI for near term is still going to be HTMLB. My recommendation is build all your complex application in WebDynpro and use HTMLB for simple application.

[Former Member · Accepted solution]

Hi Prakash,

so for conclusion there would be the following possibilities for developing WebApplications being accessed through the Portal:

- use WebDynpro (with standard controls) for developing UI's that connect to components like EJB, PortalService, WebService, RFC-FunctionModule... containing the business-logic. This would clearly encapsulate the logic. Communication between iViews would take place through (client-side) PortalEventing.

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

- use ABAP-BSP for developing UI's when there is no WebDynpro for ABAP available on the same server and the application can not be implemented by RFC-FunctionModules.

Taking this scenario, looking at where the UI'Component would run:

- the Java-iView must run on the PortalServer

- the WebDynpro must run on the PortalServer when using PortalService

- the WebDynpro could run on the PortalServer or a dedicated server when using WebService or RFC-FunctionModule

- the WebDynpro must run on the same (dedicated) server when using EJB, ABAP

-> is this correct (e.g. EJB must be on same server as WebDynpro) and does it make sense?

[Former Member · Accepted solution]

I totally agree with you. That's a very good summary. I think EJBs has to reside on same server where the WebDynpro is deployed(You might want to confirm this but posting a question on WebDynPro Forum).