Portal page structure
Before customizing portal site, understand the underlying structure of the portal.The portal page is composed of JSPs and statically included JSP fragments (JSPFs) for screens, themes, and skins that are typically created by the Web designer of the portal. These JSPs reside in the corresponding /screens, /themes, /skins directories under :
- UNIX™ and Windows™: PORTAL_HOME/installer/wp.ear/installableApps/wps.ear/wps.war
- i: PORTAL_HOME/installer/wp.ear/installableApps/wps.ear/wps.war
Within this location, subdirectories for markup, locale, and client types are used to support portal aggregation.
- provide the navigation, appearance, and layout of the portal, including colors, fonts, and images outside of the portlet content area (Home screen).
screens
- the area of the portal that typically displays portlets (Home screen), but can also display other content in its place, for example, an error message. Screens are selected from navigation icons in the theme.
- represent the border rendering around components, such as row containers, column containers, or portlets. Skins are installed independently from themes. However, the administrator can set a default skin for a theme.
The starting place for building the portal page is Default.jsp in the /themes directory. The screen and skin are called by their corresponding tags from the portal-core tag library: the screen is called by the <portal-core:screenRender/> tag, while the skin is called by the <portal-core:pageRender/> tag.
The diagram below illustrates how themes, screens, and skins are used in the portal.
themes, screens, and skins refer to the text in this topic for more information.">
- Themes
You can add own elements to the HTML portal page and rearrange the layout by creating a new theme and changing the layout in Default.jsp and the JSPs that are included. Learn about the order and layout in which the portal page theme is built using the JSPs that are provided after installation. Use this information to learn how to include some of these components as you build own themes.
Learn about theme policy, theme policy attributes, and the theme policies available with WebSphere Portal. Learn about setting a theme policy on a page using the XML configuration interface, using theme policy in a JSP, creating your own theme policy, and updating, exporting, and deleting a theme policy.
By using the Eclipse Extension Point Framework, themes provide various points where theme functionality can be extended by simply putting a new JAR file in the classpath.
A screen is a page of portal content. When the portal page is first loaded, the Home screen is initially shown (Home.jsp). Other screens can also be displayed, such as the Error screen. Selection of screens is determined by links or buttons on the toolbar, which is provided by a theme. The Home screen includes the <portal-core:pageRender/> tag, which renders the pages layout and content.
Skins represent the border rendering around components, such as row containers, column containers, or portlets. The skin is loaded in the portal page by the <portal-core:pageRender/> tag. Skins are installed independently from themes. However, a skin can be associated with a theme.
WebSphere Portal provides fully dynamic aggregation of pages from page descriptors that are held in the portal database.
Parent
Set up a portal site
| | |
| 64 KB | pg_layout.jpg | 12/14/11 5:09 PM |
});