You can create an update site to install feature updates and applications onto a device as well as create a full platform for installation on a device. You must manually transfer full platforms to the device. All workspace plug-ins to be included in the platform are built using the Target Platform chosen in the Platform Editor.
Platform configuration editor outputs
The device platform you have created contains features that are based on one of four device targets supplied by the Device Client runtime. The default target include the features placed on a device during a normal Expeditor installation. The full target includes all Expeditor features. Take note that installing all features will use a considerable amount of storage space on your device. The webApp target is the default target plus features needed to support web applications. The non-GUI target contains a very minimal set of features adequate only for running non-GUI applications.
When configuring for the Device Client, there are two sets of choices for the output.
- Platform Export Type:
- Update Site:
You can create an update site for users to install feature updates and applications onto a device. The Client Services Platform Editor creates a package that consists of platform specific fragments, features, and user updates. A user must manually transfer the package to a device or to a Web site to perform the update.
- Export Full Platform:
You can build a full Lotus® Expeditor device platform that provides a complete installation on a device. You can copy the installation directory directly to the device or unzip the platform on the device if the device has an unzip utility.
Note: Due to code signing requirements on Nokia phones, the Export Full Platform option is not supported for Nokia S60 targets.
Move your output to a directory.
Zip the output to make it easier to copy to another system.
folder includes a Win32 runtime and several device runtimes. The device runtimes can be used with Client Services Platform Editor to produce custom Expeditor platforms. However, the Win32 runtime is only for development purposes. Expeditor does not support custom Win32 platforms.
You can deploy a platform built by the Client Services Platform Editor to either the device internal storage or to a storage card. However, if deploying to a storage card, the default configuration puts the workspace on the device internal storage. If you want to put the workspace on the storage card, you must modify the platform's eclipse\configuration\config.ini file. To do so, uncomment the following line and modify the path:
For example, change to this line to:
Note that the folder name for the storage card may differ depending on the device's language setting. In addition to differing by language, it may also differ by Operating System. On WM6 it is /Storage Card
while on WM5 it is /SD Card
Testing the export
Expeditor on Devices, you can only test the runtime image on the platform it is intended for use on. For example, runtime images with a target environment of Windows
® Mobile cannot be tested on a Windows
Testing a full platform on Windows
Parent topic: Exporting a Client Services platform
- Copy the full platform zip file to your device and extract it into the root directory.
- Alternately, you can copy a non-zipped platform's Eclipse folder directly to your device's root directory.
- If the platform includes the eRCP UI feature, then execute the \eclipse\ApplicationManager shortcut in order to start Lotus Expeditor and generate application shortcuts. Otherwise, execute the \eclipse\LaunchExpeditor shortcut to start Lotus Expeditor. To always start a non-GUI Expeditor platform when the device boots, copy the LaunchExpeditor shortcut to \windows\Programs\Startup.