Push auto-update mechanism configuration

To enable the push auto-update mechanism, use the following configuration procedure.
  1. Two files, both located on the "Main" server, control the push mechanism from an on-premise BlackBerry Workspaces server:
    • /var/www/html/download/VersionManifest.xml
    • /var/www/html/download/VersionManifestSync.xml
  2. Edit the following parameters in both files.
    Once the parameter edits are saved, the new application upgrade will start rolling out to end users.

    Variable

    Value Format

    Details

    LatestVersion

    versionNumber.revisionNumber (e.g.5.5.0.)

    Application version that will be pushed to users. Should be the most recent version deployed on the specific server.

    PublishedDate

    dd/mm/yyyy

    Date in which auto-upgrades will begin. Usually this would be today's date.

    MaximumVersionToUpgrade

    		versionNumber.revisionNumber (e.g.5.5.0)

    This field enables pushing upgrades only to users with older versions of the application. For example, if you wish to push 5.5.0 only to users that have versions older than 4.5.0, the value of the field will be 4.5.0.xxxxx. Normally, the value would be identical to "LatestVersion", ensuring that ALL users will be upgraded.

    FullUIUpgradeStartDate

    dd/mm/yy

    By default, the "push" is silent and no notification is shown on the user's screen. Silent notifications can only execute while 3rd party software is closed on the user's computer. To accelerate the upgrade process, there is an option to push the application with a visible notification for end-users. This field will determine the date when a UI upgrade, with a balloon notification begins.