The Rich Client Layout Administration Portlet is an extension to the Portal page customizer that is used to manage common rich client-specific metadata.
It can inject this data into any portlet on any page as portlet preferences. A typical application with one or more pages may include instances of several types of portlets. The placeholder and administration proxies serve to establish position of portlets on pages that project as views and perspectives on the client. JSR168 portlets also project as views but can in addition have client-side equivalents that run in the portlet container. Since JSR168 portlets do not have to be explicitly instrumented to manage rich client specific data, the same rich client unaware portlet can serve as an administration proxy for versions deployed at the rich client and be used as a "normal" portlet on the server for delivery through a browser. The Rich Client Layout Administration Portlet will not manage view-specific attributes such as wiring properties/actions or view configuration. If this is needed for a given view, an appropriately programmed administration proxy will be needed.
The Rich Client Layout Administration Portlet does not manage view-specific attributes such as wiring properties and actions or view configuration. If this is needed for a given view, you must use an administration proxy.
The Rich Client Layout Administration Portlet handles the parameters that are common to all perspectives and views:
These are defined once on each page and stored in the Portal parameters for the page.Page portlets
This is a list of portlets on the page and is generated when needed based on the current page layout configuration.Rich Client Properties
These describe execution properties of an Eclipse view on the client. They are stored in the portlet settings and portlet data.Feature Requirements
These are prerequisite features the client will need before starting the target view. They are stored in the portlet settings and portlet data.Layout Properties
These are the additional parameters needed to account for the Eclipse layout being more granular and complex than Portal. They are stored in portlet settings and portlet data.
Before you begin, make sure the Rich Client Layout Administration Portlet is installed on the Portlet server. The portlets are normally installed by running an appropriate installer under the /nci directory on the product CD. The portlets are present in directories under /nci/portal and can be installed manually by using the Portal administration dialog to install war files from /nci/portal/portlets, or by running xmlaccess scripts under /nci/portal/scripts. Additionally, you must have previously created a page structure to represent an application intended for client configuration.
Parent topic: Configuring client user interface layout