Introduction

A Client Package is an installer that is specifically designed to fit in for a given target handset.

For a Symbian device one will obtain a .cab .arm file.

Client package creation is a 2-step process:

• Configuration
• Packaging

Prerequisites

Application configuration can be accessed from the Service > Service Settings > Application configuration tab in Workbench Developer.

In order to customize an application one will need to specify:

• Standard settings, i.e. application name, application id, application version, application icon (see requirements below)...
• (optional) Advanced settings, i.e. screen orientation changes handling...

Icon

The application icon must be in ICO format, 256 colors max. ICO file must contain 16x16 and 32x32 sizes.
The order of the icons in the .ico file does matter, put them in growing order. If the good icon is not found the system will resize the icon. This will probably produce a blur effect.
Please refer to this [article] for additional information.

Packaging

Wizard

Application packaging can be accessed from the Service > Create Client Packages menu option in Workbench Developer.

In order to package an application one will need to specify:

• Targeted device(s), i.e. select all devices the application is supposed to support
• Application configurations, i.e. all defined configurations (as defined in the Prequisites section above) can be set / updated here
• Rich Media Server information, i.e. required parameters to access Streamezzo Rich Media Server instance if any (i.e. if the application contains server-side scenes)
• Output, i.e. output folder and pattern (this last parameter is mandatory in case multiple devices are selected for packaging, as each application installer will need to be dumped in a separated and identified folder, inside the output folder)

Once the "Finish" button is pressed, all requested client packages will be generated for each selected device.

If specified in the configuration, the application will be automatically signed.

The progression of the client packages creation can be followed in the Client packages creation view.

Once a client package has been created, its output folder can also be accessed from here.

Ant task

Some operations as accomplished above with the wizard can be performed relying on an Ant task, which is usually comfortable to reiterate a client package creation in a given configuration (i.e. selected devices, configuration, output...) in a 1-click operation.

In order to do this one can follow those steps:

• Create an Ant build file
• Open it in the Workbench Developer editor
• Right-click in the editor area and select Wizards > Create client package target
• Follow the same wizard steps as detailed above; once the "Finish" button is pressed, the Ant build file will be automatically filled accordingly (instead of really creating the client package(s))

The obtained Ant task looks like this:

<?xml version="1.0" encoding="UTF-8"?> My description

The Ant build file can then be dumped in the Ant view and executed from here.

The progression of the running Ant task can be followed as successive logs in the Console, ending with message "BUILD SUCCESSFUL" in case it succeeded.

Distribution

Once properly packaged, a Windows Mobile application can be distributed OTA by any applicable mean, i.e. FTP, Provisioning Server...