Create and Deploy Afaria Clients and Unwired Platform Runtimes

When the user receives a client notification, they download the installer and install the Afaria client and any required Unwired Platform runtime files.

  1. Use the Afaria Create Client Installation wizard to create a client installer. This program is located only on the Afaria server: <AfariaServerInstallDir>\Bin\XSClientInstall.exe. A new Afaria client relies on connection configuration settings to connect back to the Afaria Server and run its first session. The Create Client Installation wizard creates seed data and stores it on the client as connection settings.

    CAB files must be signed and placed in the installation sequenced required. Otherwise, the user receives SMS or SMTP messages that link to the OTA Deployment Center in an incorrect order. See Afaria Reference Manual | Platform > Creating Clients > Creating Afaria Clients, and refer to the program's context-sensitive help as required.

    Note: If you select the Companion PC option, device users can also install by cradling the device and synchronizing the files and seed data from the corresponding desktop device manager (for example, ActiveSync).
  2. To make downloads available, publish components to the OTA Deployment Center. Use program called OTA Publisher, which is installed on the Afaria Server host machine in this location: <AfariaServerInstallDir>\Bin\OTAPublisher.exe. For details about how to use the OTA Publisher, see the program's context-sensitive help.
  3. Send a device notification to allow the user to trigger the provisioning process. See Afaria Reference Manual | Platform > Home > Client Deployment > Sending Notifications. Depending on the gateway you configured, that user address is checked and a message is sent using either SMS or SMTP.
  4. Validate performance by checking logs. See Afaria Reference Manual | Platform > Data Views > Working with Logged Actions
Parent topic: Setting Up the Afaria Environment