This section describes the tasks you can perform to configure the Lotus® Expeditor runtime on the user's machine.
Configuring Java system properties: XPD621
Applications might require specific system properties to be set at startup when running the Lotus Expeditor platform. To minimize the number of parameters that you must specify on the command line, you can add configuration lines to the rcpinstall.properties
file, which resides in the <installation directory>/rcp/
Configuring Java VM arguments: XPD621
Applications might require the addition of JVM specific arguments when the platform starts. To minimize the number of parameters that must be specified on the command line, you can add vmarg.* configuration lines to the <installation directory>/rcp/rcpinstall.properties
Configuring native library references: XPD621
The recommended approach is that all native library objects be included in operating system/processor specific fragments. In general, this is sufficient to allow the application code and the operating system to locate the desired library. However, there might be cases where it is not possible to organize the libraries within a fragment, or the library loading requirements inhibit this approach. Therefore, library search path must be updated.
Configuring Java Bootclasspath libraries: XPD621
The recommended approach is that all class libraries that are needed by applications reside within plug-ins or fragments. If there are cases in which the libraries must be placed on the Java bootclasspath, then you will need to update the –Xbootclasspath
line(s) in the rcpinstall.properties
Configuring the platform launcher: XPD621
You can configure additional arguments to use when the user launches the Lotus Expeditor. For example, you can specify that a console is displayed when launching the client.
Configuring deployment settings: XPD621
The provisioning system of the client platform provides the feature install and life cycle management. The provisioning system extends the capabilities provided by the underlying Eclipse Update Manager.
Configuring the Web Container: XPD621
The Web Container provides a runtime environment for Web applications in which Web applications can be run both disconnected and connected.
Configuring the Portlet Container: XPD621
The Portlet Container provides a runtime environment for JSR 168 portlet applications in which JSR 168 portlets can be instantiated, used and finally destroyed.
Configuring portlet preferences: XPD621
You can remotely manage and update the default set of portlet preferences.
Configuring mobile Web services: XPD621
No local configuration is needed to deploy Mobile Web services. Mobile Web services providers will listen on the same port of the Web container.
Configuring Apache Axis Web services clients: XPD621
Apache Axis is an open source implementation of the SOAP. It has been enable to provide runtime support for the JAX-RPC based clients in Lotus Expeditor.
Configuring managed settings: XPD621
The managed settings framework allows you control over the runtime behavior of client applications by letting you set the values of the settings that the applications are reading out of the Eclipse preference store.
Configuring the network layer: XPD621
You can configure the platform proxy settings and the network status polling interval using eclipse preferences.
Configuring the Web Browser Application: XPD621
You can configure the Integrated Browser Application with a defined Eclipse preference for your environment. For example, you can specify not to display the Web Browser preference page in the IBM® Lotus Expeditor Preference dialog.
Configuring platform synchronization: XPD621
Use the Lotus Expeditor platform to manage and configure synchronization.
Configuring platform security: XPD621
The desktop client platform can use either the IBM J9 Virtual Machine (VM) that implements the Java specifications with DesktopEE class libraries or the IBM J9 VM with the Java 2 SE 5.0 class libraries. The security configuration options are different depending upon the VM that is used.
Configuring the platform help: XPD621
Based on your product’s requirements, you can either remove the Help
menu completely or remove the Help Contents
menu items under Help
Configuring the Lotus Expeditor sidebar: XPD621
Use the sidebar to perform tasks in other applications on the side without distracting from your work in the current application.
Disabling menus and menu items: XPD621
Eclipse Activities (defined through the org.eclipse.ui.activities extension) can be used to hide contributed menus and menu items.
Modifying platform configuration files: XPD621
The client platform contains several configuration files that may require updates to successfully deploy and run applications.
Enabling platform single signon: XPD621
Single sign-on (SSO) authenticates users by prompting them for a user name and password a single time. Enabling platform single sign-on gives users secure access to the platform keystore without displaying additional authentication prompts.
Managing secure keystore: XPD621
The Java KeyStore is the standard storage abstraction for security-sensitive information like keys, certificates and passwords.
Managing problem determination artifacts: XPD621
Configure the Problem Determination Artifact Manager to ensure that the file system artifacts used for resolving errors are appropriately managed.
Managing accounts: XPD621
You can store, access, and use properties that are required to make a connection to, and communicate with, a remote service.
Managing Eclipse preferences: XPD621
The platform and application plug-ins can use Eclipse preferences for storage of configurable information. Examples can include window settings, server locations, and synchronization settings.
Managing OSGi preferences: XPD621
The client platform includes an implementation of the OSGi Preferences service for use by OSGi-related applications.
Managing UserAdmin settings: XPD621
The client platform includes an implementation of the OSGi UserAdmin service. The UserAdmin service provides a mechanism for storing user definition, user credentials, user roles, and group information.
Managing ConfigurationAdmin settings: XPD621
The client platform includes an implementation of the OSGi ConfigurationAdmin service. The ConfigurationAdmin service provides a mechanism for configuration information for a service.
Managing life cycle: XPD621
This section describes the life cycle of the client platform.
Configuring and administering micro broker components: XPD621