Show TOC

Portal Page at RuntimeLocate this document in the navigation structure

Use

This section applies to regular portal pages, not Web Dynpro pages.

A portal page is constructed during runtime. All the main elements are installed with the portal and consist of a:

  • Portal application

    A portal application consists of various layoutTemplate.jsp files, the portalapp.xml descriptor file, and other elements needed to produce an HTML page.

  • PageLayout component

    The PageLayout component reads the layoutTemplate.jsp file and places page content according to the tag definitions in the file. Together with the layoutTemplate.jsp file, PageLayout creates the HTML page that is displayed in the browser when you launch a page.

  • PageBuilder component

    PageBuilder is the portal component that creates the portal page at runtime. It gathers the content of all the iViews that have been assigned to the page and assembles the entire HTML output. PageBuilder uses the PageLayout component to place all iViews in their designated locations on the page.

    PageBuilder references:

    • Portal and iView cache property settings to determine whether iView content is to be collected at the server or at the client. For more information, see Navigation Caching .

    • The Isolation Method property of each iView to determine how to present it on a page. For information about isolation methods, see Isolation Method of iViews .

    • The content of a page, and performs automatic optimization regarding network traffic overhead (code generated by the page). The resulting page consumes less bandwidth and loads faster. To further enhance performance, set the property Use API of Tray to No . This tells the page that iView tray functionality is not needed for the iViews on the page.

Calling a Page

When a page is called, it usually displays after all its iViews have retrieved their content. Some iViews may be heavy and take a long time to load. To prevent users having to wait until all the content has been fetched, you can set a timeout for the page. Upon expiration of the timeout, the page and all its iViews are forced to display as follows:

  • An iView with a valid cache, or one that finishes loading before the page timeout, displays its content.

  • An iView with an expired cache shows the invalid content with a message to the effect that the displayed content is not current.

  • An iView that has not finished fetching its content, and has no cached content, displays a message to the effect that a timeout has occurred and there is no content to show yet.

Note

In the last two scenarios, the iView continues fetching content, which is displayed after a page refresh.

This does not apply to pages containing only iViews whose isolation method is set to URL.

Setting Page Timeout

To set a page timeout, in the Property Editor, locate the PageTimeout property and enter a timeout value. The default value is 150000 milliseconds .