Portal Pages 
Purpose
A portal page holds iViews and other pages containing iViews, organized in a layout. iViews retrieve information from various sources, helping users perform their business functions. Pages are one means of assigning the iViews to users and roles, and displaying the information that is retrieved.
For information on the components that construct a page, including the content you assign to it, and how it displays as an HTML page in the user’s browser, see Portal Page at Runtime.
Implementation Considerations
The portal lets you create two types of pages: the portal default page and the page based on Web Dynpro technology. Each type has its requirements and recommendations in terms of the content that you can add to it.
Before creating a page, consider the iViews that the page will hold and the possible potential uses of the page. For example, the following two issues can determine the layout you choose for the page:
¡ Each iView has an optimal display mode, depending upon the information it contains.
¡
The page might be assigned as a 
dynamic navigation
iView to another page.
· Before assigning iViews to a page, consider some of the issues that affect page performance:
¡
The cache level of
each iView, which determines from where iView data is
retrieved
¡ The isolation method of each iView, which refers to the relationship between an iView and its page, and the iView behavior on the page
Features
· You create a portal page by copying an existing page, or by running the Page Wizard.
During page creation with the Page Wizard, you determine:
¡ The technology on which to base the page
¡ The potential arrangement of the iViews
Depending upon your selection of an active layout and possible alternatives from among several predefined layouts, the new page will consist of one or more containers for holding iViews.
The open portal architecture lets you create and deploy custom layout templates based on portal technology. It is not yet possible to create custom layouts using Web Dynpro technology.
· You manage pages using the Page Editor.
The Page Editor lets you populate pages with the iViews required by the various users and roles in your organization, and edit that content.
· You determine the extent to which portal users can modify the content and layout of a page.
Users can:
¡ Move iViews from one container to another, but they cannot alter the arrangement of the containers.
¡ Select a different layout, with a different arrangement, from among the layouts you assign to a particular page.
·
After creating a page, adding content, and
fine-tuning the layout and properties of the content, you can use the Role
Editor to assign the page to a specific role or user. For information see Adding Content
Objects to Roles and Worksets.
Users have access to all of the portal pages assigned to all of their roles.
See Also:
Creating a Customized Page Layout Template