Elements of a Layout PAR File 

The mandatory files in a layout PAR file are:

·        The various layoutTemplate.jsp files

A layoutTemplate.jsp file uses a dedicated jsp tag library to place iViews on a page by defining the location of their containers.

The layoutTemplate.jsp file can contain any jsp content, such as html, java code, taglibs, and so on, that will be used to assemble the HTML page.

The layout template may also contain htmlb components. The standard portal layouts contain htmlb context tags (hbj:content, hbj:page), which wrap the layout containers and enable htmlb components by the layout implementation.

 

If the PAR file contains more than one layoutTemplate.jsp file, each .jsp must have a different name. There is no mandatory naming convention, except for the .jsp extension.

 

·        The portalapp.xml descriptor file

The portalapp.xml file is a standard part of any PAR file and stores the portal application definitions.

Several layout templates can be stored in one PARfile, and all of them can be described in one portalapp.xml file. Each layout template is stored as one portal component.

·        Any other resources that may be required to produce an HTML page