Portal has a set of page properties that it uses itself and has a GUI to edit them.
The server allows additional properties for a page as needed for client administration and has a generic page parameter editing GUI, but it requires you to know the exact spelling of each parameter name and manually ensure constraints on the values are met.
Since the parameters are processed remotely on a client, errors can be difficult and time consuming to diagnose. Part of the Rich Client Layout Administration portlet is to provide a GUI to edit the new page parameters added for use in the Portal Administered Client. This GUI provides descriptive titles and ensure constraints are met.
Handling of the content producing elements is more complicated. For layout purposes on Portal, there must be a portlet instance to represent each view instance under Eclipse. This surrogate portlet will have parameters for the additional layout information and be projected as an Eclipse view on the client. There is a standard set of parameters that the Rich Client Layout Administration portlet will create and edit for any portlet. Beyond those the surrogate portlet must be an administration proxy with its own configuration capability instead of just a placeholder relying entirely on the Rich Client Layout Administration portlet.
Parent topic: Managing Rich Clients using the Portal server