The developer needs to edit the display profile document and specify the <Container> and <Provider> display profile elements where applicable. The tags that should be modified are:
<Provider name="provider" class="provider class"> <Container name="container" provider="provider"> |
For JSP files, the <Properties> tag for the provider contains the following property tag, which references the JSP Content page:
<String name="contentPage" value="value"> |
The <Properties> tag for the channel can have values that override the properties set in the <Provider> tag. Thus, if desired, you could set the JSP contentPage value here. You do not reference template-based providers, or other providers you might develop, in this way.
The <Available> and <Selected> tags are required for all containers in the display profile.
The JSP-based tab, table, and frametab containers have additional properties requirements.
There is a distinction between a provider element in the display profile and the Java class for the provider.
<Provider name="JSPTableContainer" class=com.sun.portal.providers.containers.jsp.table.JSPTableContainerProvider> |
com.sun.portal.providers.containers.jsp.table.JSPTableContainerProvider |
You can modify display profile objects by performing one of the following:
Using the Portal Server software administration console to download the display profile and uploading it after modifying it.
Manually editing an existing display profile document and then loading it at the appropriate LDAP node by using the psadmin modify-display-profile subcommand.
Creating a new display profile document from scratch and then loading it at the appropriate LDAP node by using the psadmin add-display-profile subcommand.
For more information on display profile and the psadmin subcommands to manage the display profile, see the Sun Java System Portal Server 7 Command-Line Reference.