Portal Implementation

[Former Member]

Hi

1) what is the Abstract Portal Component?

2) what is the IPortalComponenet?

and what is the difference b/w these two

3) what is the difference b/w Dynpage and JSPDynpage

Regards

sureshbabu

[detlev_beutner · Accepted solution]

Hi Suresh,

An AbstractPortalComponent extends the interface IPortalComponent, and only the method <i>doContent(...)</i> is declared abstract. It is technically a base component with few framework support (of course, it's methods are called in a predefined order, but there is no support for JSP etc.; on the other hand, you can use an AbstractPortalComponent if it is urgent that the framework hasn't written something into the reponse object - for example, if you want to offer some binary (like PDF, ZIP or whatever) to download).

See https://media.sdn.sap.com/javadocs/NW04/SPS15/ep/com/sapportals/portal/prt/component/IPortalComponen... for the interface and the implementing abstract class.

See http://help.sap.com/saphelp_nw04/helpdata/en/55/b85d421e1e5542e10000000a1550b0/frameset.htm for a more detailed introduction.

A DynPage -- see http://help.sap.com/javadocs/NW04/current/hb/com/sapportals/htmlb/page/DynPage.html -- is a bit more sophisticated, but does not support the setting of a JSP; it expects that the rendering happens programatically within the class itself.

In a JSPDynPage you can set the view (the JSP) which should be rendered (and you calculate at runtime which JSP of different this will be). So it supports the MVC-pattern directly. Help is offered at the links given above.

Hope it helps

Detlev

[Former Member]

Hi Suresh,

These all are various ways in which we can build Portal Applications. Things are less abstract in implementing each of these concepts that you have asked about.

The application majorly aims to implement MVC architecture-Model View Controller.

Each application consists of different Components. AbstractPortalComponent is a Component that renders the functionality at runtime by the Portal Runtime. Everything is written using requests and responses, that is all in code.

DynPage is a next stage of development in MVC architecture. Here the component and its elements are rendered through HTMLB api. That is in the code itself the HTMLB controls are added to the form and that is added to the component. This has increased the application development consistently.

The next method is using the JSPDynPage, which enables us to develop, customize the look and feel of the application in the JSP, put the logic and the functionality in a JSPDynPage that renders the component. Thus truly the MVC architecture is implemented.

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/8a/4dae42cb9f0f31e10000000a1550b0/frameset.htm">Here</a> you can get a clear structure of a component.

This <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/44/46b9d670e20597e10000000a155369/frameset.htm">tutorial</a> might help you in developing applications in whichever method you choose.

Regards,

Sujana