You can enable your Lotus® Expeditor workstations to receive configuration information from a WebSphere® Portal server. This is one way to centrally administer your Lotus Expeditor environment.
The portlet container allows for many different client side architectures with the composite application infrastructure. There are two primary ways applications can run on the client:
- A standard widget toolkit (SWT)-based application aggregated and deployed by Portal. This application is composed of SWT-based views and is placed on the Portal with the various view components wired together with the Portal wiring tool.
- Locally running portlets. Properly bundled portlets can be run locally and off-line in the Lotus Expeditor. This ability, mixed with Property Broker, allow for the locally running portlets to inter-communicate with each other. These disparate components can then communicate with each other using the declarative wire expressed in the composite application XML.
Additionally, a third way of encapsulating Web applications with other components is by wrapping the Managed Browser in a managed browser SWT view that exposes property broker actions and properties. This has the same effect as a traditionally wired experience of any portlet or view driving another component (in this case a browser taking in URLs).
For more information, see Managing Rich Clients using the Portal server
Parent topic: Understanding Expeditor Client runtime configuration: XPD621