® Expeditor Client runs under Eclipse so the display window is laid out mostly using perspective containers with the content generated by views.
The Rich Client Layout Administration portlet supports server administration of view parameters and view placement within a perspective. At a high level this maps nicely to portlets placed on a page. The hierarchical arrangement of pages on Portal has no direct equivalent on Eclipse but the effect is achieved through the Lotus
Expeditor Client code that understands both arrangements.
At a detailed level the Eclipse environment is more complex so several parameters must be added to the Portal configuration to effectively represent the client layout. For example, under Eclipse there can be functions called activities started automatically when a perspective is opened. Portal pages have no similar concept so the client code recognizes an additional page parameter to specify the activities. The Portal server aggregates the output of portlets on a page automatically and a web browser renders the page according the HTML generated by the server and space available in the window on the client. Under Eclipse the views can be controlled more precisely by specifying relative ratios of the total perspective space, so the client code recognizes an additional portlet parameter for the ratio.
The Rich Client Layout Administration portlet supplied with the Lotus
Expeditor Client provides a GUI to configure the common parameters for pages and perspectives and portlets and views. Other portlets address Eclipse preferences, custom view parameters for Managed Browsers, a WSRP client enabler and the Lotus
Expeditor Client contributions that are not configured as views under perspectives.
The layout administration on Portal consists of arranging pages and portlets hierarchically under a single Content Root. You can add pages starting directly under the root or to one of the pages predefined when the Portal is installed. The Lotus
Expeditor Client retrieves information only from under Content Root
-> Application Root
. This is where the Portal server places its Composite Applications. However, the administrator will normally use the Template Library functions under the Templates
link on the Home page. Here you can import and create application templates, then use them to create Composite Applications in the Application Library. Applications can also be divided into categories with the Lotus
Expeditor Client normally requesting the list of applications in the MyClient category.
Regardless of the starting point, each page can then have pages under it and portlets on it. During normal operation, child page selection is displayed according to a theme with tabs being common. The content generated by the portlets fills the remainder of the window. Note that there is also a label element, basically a page that has child pages but no portlets, and a URL element that is a link to outside the Portal or sideways to an existing page. The root of a composite application is technically a label, but since this document concerns the layout and content of pages with portlets, the label and URL are mentioned if appropriate but not discussed further.
In Portal, pages are artifacts that exist only within the content of items in a database. The associated page properties and container layout are also information kept by the server in a database. The page content references real portlets that execute code to produce the rendered output seen in a Web browser. Likewise, Eclipse has metadata to describe perspectives and their contained views, and the content of the views comes from code in plug-ins written as SWT applications. The original IBM
® API portlet execution environment and the base SWT environment are very different so the content generating code is also very different. This is changing as a portlet container in the Lotus
Expeditor Client can run newer standard portlets (JSR 168 compliant) such that portlets not using any Portal specific functions or Eclipse specific function can run in either. But the Eclipse environment remains more flexible and complex so additional page and layout information still must be added to what Portal keeps to accurately describe layout of Eclipse elements.
Parent topic: Managing Rich Clients using the Portal server