Replies to This Forum

Permalink Reply by BARUN JYOTI on March 6, 2012 at 20:02

thanks mam,

              This is very good research articals and journals. thanks for this.

• ▶ Reply

Permalink Reply by KUSUM Saini on March 1, 2012 at 18:53

 Relevant Portal Features 

The following is a list of the portal features that enable the implementation of an external-facing portal:

• Navigation Cache: The portal caches navigation hierarchies and nodes. For a user with the same navigation hierarchy as a previous user, the portal can retrieve the hierarchy from the cache instead of creating it again.

This feature improves portal performance.

For more information, see Caching Navigation Nodes.

• Short URLs: By default, URLs in the portal are shortened, with the navigation target converted (hashed) into a short GUID.

This feature reduces network traffic by shortening the URL, hides the internal content structure and enables users to share URLs that are shorter and easier to handle.

For more information, see Navigation with Short URLs.

• Quick Links: Administrators can assign short strings – that is, quick links – to navigation nodes so that users can quickly navigate to specific nodes.

This feature provides more Web-like behavior.

For more information, see Navigation with Quick Links.

• Light Framework Page: The portal provides a light framework page with the following characteristics:

○       Includes light navigation iViews that do not use HTMLB or client-side eventing (EPCM) JavaScript, reducing the resources required for rendering the page.

○       Renders the portal in a single frame, which enables Web-like behavior, such as, the use of the browser navigation buttons. The single frame also eliminates the need for JavaScript to enable communication between frames.

This feature provides more Web-like behavior and reduces network traffic.

• Resource-Sensitive Page Builder: The page builder can prevent the downloading of client‑side eventing JavaScript if an iView indicates it does not need eventing. The need for eventing is specified by a component’s EPCFLevel profile property. For more information about this property, see Components in the developer documentation.

In addition, even when a page requires client-side eventing JavaScript or HTMLB controls, the page builder only loads the required resources and not the entire libraries.

• JSP Tag Libraries: The portal provides tag libraries for easily developing navigation iViews and page layouts from JSP pages. The following tag libraries are provided:

¡        Navigation Tag Library: Enables you to develop iViews that access the current user’s navigation hierarchy. The tag library is generally used for top-level and detailed navigation iViews.

¡        Layout Tag Library: Enables you to develop page layouts, and to develop custom iView trays.

¡        Framework Tag Library: Enables the creation of links for various portal functions, such as logging off or personalizing the portal. The tag library is generally used for masthead and page title bar iViews.

The use of Knowledge Management and Collaboration capabilities in an external-facing portal should be limited to specific use cases and is subject to a number of restrictions. For more information, see the How-to guide Best Practices – Using KMC Capabilities in an External Facing Portal at service.sap.com/nw-km ® Media Library ® How-To Guides – KM and TREX.

For more information about the light framework page, resource-sensitive page builder and the JSP tag libraries, see Implementing an External-Facing Portal in the Portal Developer Guide.

 

• ▶ Reply

Permalink Reply by BARUN JYOTI on March 6, 2012 at 20:24

thanks ma'am

• ▶ Reply

Permalink Reply by KUSUM Saini on March 1, 2012 at 18:59

http://www.elag2004.no/papers/Carden.pdf

• ▶ Reply