test

Sun Java System Portal Server 7 Developer Sample Guide

Changing the Header and Footer of the Theme, Content, and Layout Pages

Depending on the Desktop, the particular header and footer files for in the Theme, Content, and Layout pages are determined by the container that contains the Theme, Content, and Layout pages.

For example, when you access the Content page for JSPTabContainer, JSPContentContainer is the container that is used to include the header and footer files that the tab container is using. The contentedit.jsp file, located in the JSPContentContainer directory, uses logic, based on the container, to access the appropriate header and footer files.

To brand the header and footer of the Theme, Content, and Layout pages:

Use Changing the Header and Footer of the Theme, Content, and Layout Pages to determine the appropriate header and footer JSP files to edit. This two column table lists the Desktop containers in the first column and the corresponding header and footer files in the second column.

Table 8–1 Header and Footer Files for Theme, Content, and Layout Pages

Desktop Container 

Header and Footer Files for Theme, Content, and Layout Pages 

FrameTabContainer 

framePreferenceHeader.jsp and framePreferenceMenubar.jsp

JSPSingleContainer 

singlePreferenceHeader.jsp and singlePreferenceMenubar.jsp

JSPTabContainer 

tabPreferenceHeader.jsp and tabPreferenceMenubar.jsp

JSPTableContainer 

tablePreferenceHeader.jsp and tablePreferenceMenubar.jsp

Containers not listed in Changing the Header and Footer of the Theme, Content, and Layout Pages use defaultHeader.jsp and defaultMenubar.jsp files. These two files are actually the same as singlePreferenceHeader.jsp and singlePreferenceMenubar.jsp files. If you want a default look and feel for the container’s header and menubar, customize these two JSPs. Currently, the sample portal does not use defaultHeader.jsp and defaultMenubar.jsp files.

ProcedureTo Change the Header and Footer of the Theme, Content, and Layout Pages

Steps

  1. Change to the appropriate directory.

    That is, change to PortalServer-DataDir/portals/portal-ID/desktop/developer_sample or change to the specific desktop type subdirectory associated with the target user or organization.

  2. Edit the JSP files.

    For example, change the HTML title and logo in the header file, and change the product name in the footer.

  3. Run the touch command.

    For example, type touch *.jsp.

  4. Reload the Desktop to verify the change.