You can enable your Lotus® Expeditor Client workstations to receive configuration information from a WebSphere® Portal server. This allows you to centrally administer your Lotus Expeditor Client environment.
Centrally administered role-based access control is a critical requirement of all large enterprises. WebSphere Portal provides a set of powerful functions specifically targeted at these requirements. The Managed Browser Administration Portlet exposes each instance of the browser as a portlet. Additionally, configurable elements of the browser instance (such as address bar, URL restrictions, for instance) are also exposed through the portlet. By exposing these configurable elements, they can now be managed in a role-based fashion. Integrating with WebSphere Portal allows the overall user administration to remain as unified as possible, which reduces both financial and personnel cost.
Administrators can use the same page and place management, user management, and access controls to integrate, manage, and reuse application components running across a variety of device types, ranging from pervasive devices such as cell-phones and PDAs to browser-based desktops. The Portal-administered client extends this reach further to support “rich client” desktop devices based on Lotus Expeditor Client.
The term Portal-administered client
simply means a side of the Lotus Expeditor Client that can install, load, and run applications defined by Portal. Portal applications are a specific kind of application that ultimately means a collection of pages, portlets, policies and roles. A WebSphere Portal application by definition is much different than other applications, for example, a rich client application
in terms of Eclipse. The equivalent of a Portal application on the rich client is a set of navigable perspectives (pages) that contain views (portlets) and are configured with Eclipse preferences (policy) and can communicate through a property broker (wiring).
A Portal portlet maps to an Eclipse view, not a client portlet. This view can be any proper Eclipse view resident on the client. One of the views included with the client is a viewer to render HTML output from a real portlet running in the portlet container on the client. This portlet viewer view is treated in special ways on the client and in the administration portlets so it is easy to get a little loose with terminology and say a portlet maps to a portlet.
Portal gives you the ability to define a series of pages for your application and a navigation hierarchy for how those pages are represented. What this means is every single application can actually define a complete hierarchy of pages all contained within a single Portal application. This further implies that a projected Portal application on the rich client has n
number of perspectives associated with that application.
Root Page 1
Root Page 2
Sub Page 2.1
Sub Page 2.2
Sub Page 3.2
Sub Sub Page 3.2.1
WebSphere Portal applications running on the client need extended client side properties that need to be specified on the pages and portlets on the server. To make the process of specifying these attributes easier, use the following portlets. These portlets would expose Properties and Actions that map to the Eclipse counterpart on the client. The WAR file would then need to have an equivalent SWT plug-in that uses the same WSDL for the client-side property broker registration. This usage is basically SWT applications that are aggregated on Portal and deployed from Portal.
Rich Client Layout Administration Portlet
This 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 Generic Placeholder portlet
This portlet is used to aggregate any generic eclipse view that does not expose properties and actions, or require view specific custom configuration. This portlet is little more than a container for the common layout preferences managed by the Rich Client Layout Administration Portlet (for example, view ID, ratio, feature requirements). This portlet is included in the web module with the Rich Client Layout Administration Portlet and can be copied and renamed as necessary by the administrator, then placed on pages to represent views."Administration proxy" portlet
Unlike the generic placeholder portlet, an administration proxy is tightly coupled to the rich client view it represents. It may expose "dummy" properties and actions so that the portlet wiring tool can be used to create wires between administration proxies that are then sent in the composite application XML from the Portal server. This assumes the plug-in developer has implemented an action that can scope the wire to a specific view/secondary id within the plug-in. This portlet may also provide a custom JSP that is used to manage view-specific configuration properties. Lotus Expeditor Client includes two administration proxies; the Managed Browser Administration portlet and the Rich Client WSRP Viewer Enablement Portlet. In general an administration proxy must be created by the developer as part of the process of developing client-side plug-ins that support wiring and/or view configuration.
These portlets are installed on the Portal server by the Network Client Installer. See Installing with the Network Client Installer
for information about the Network Client Installer.
This section describes how to manage the Lotus Expeditor Client using the WebSphere Portal server.
Parent topic: Managing the client runtime: XPD622
Configuring managed settings: XPD622