How To Guide Stores Application Updates
Introduction
An application update, as the term implies, involves updating a Device (POS, Back Office, PDP Server or Thin Client) with a latest version of the POS application.
The purpose of the Application Update Detail Maintenance is to allow users to record, in an Enactor table, the definition of an update. While this table will only hold the definition of an update with regards to its content and location, the target, schedule, and progress of applying that update are handled through another maintenance application - Application Update Broadcaster.
In essence, Application Update Detail enables a User to upload an Application Update through the UI which can be broadcast to target devices.
Overview
This How-to Guide covers the creation of an Application Update, broadcasting it to a POS Device and verifying that the update was applied successfully.
User Role Configuration
Below privileges should be enabled for the User:
| Application Package | Function ID | Description |
|---|---|---|
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.Run | Allows the EM User to run Application Update Detail Maintenance Application. |
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.Edit | Allows the EM User to edit a record in Application Update Detail Maintenance Application. |
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.New | Allows the EM User to add a new record to Application Update Detail Maintenance Application. |
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.Remove | Allows the EM User to remove a record from Application Update Detail Maintenance Application. |
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.List | Allows the EM User to list entries in Application Update Detail Maintenance Application. |
| Enactor Web Maintenance | enactor.updateDetailsMaintenance.SoftwareUpdate.View | Allows the EM User to view records in Application Update Detail Maintenance Application. |
Uploading an Application Update
Navigate to Application Update Detail Maintenance using the Search or the path:
Administration → Data Management → Broadcasts → Application Update Detail
Application Update Maintenance select page will list all current records.
Click on Create a new Application Update.
| Configuration | Description |
|---|---|
| Storage Type | Select File Repository from the drop list. |
| File Path | Click on the Upload icon to upload the update package XML, published with each application release. Update files are published for each device type. Ex: update-2.7.747.RC2.100.1127-POS-Min.zip for Thick POS devices update-2.7.747.RC2.100.1127-PDPClient-Min.zip for Thin Client update-2.7.747.RC2.100.1127-PDP-Min.zip for PDP Server update-2.7.747.RC2.100.1127-BO-Min.zip for Back Office Two versions of update files are available: Min.zip and zip file. update-2.7.747.RC2.100.1127-POS-Min.zip update-2.7.747.RC2.100.1127-POS.zip Min.zip file does not include an updated Java Run time environment. Unless there is a requirement to update the JRE files, it is recommended to upload the Min.zip file. Choose file location and select upload. Click on Extract Content. The zip file will be stored in the Enactor File Repository and the details will be updated. |
| Status | Drop list selection of Active or Inactive status. |
Click on Save.
The entry will be added to the list of Application Update Details. Update Detail ID is automatically assigned.
Broadcasting
Application Update Details should be broadcast to the relevant subscribed devices.
This is done through Application Update Broadcaster application.
Navigate to Application Update Broadcaster using the Search or the path:
Administration → Data Management → Broadcasts → Application Update Broadcaster
The functionality is comparable to Data Broadcasting.
| Configuration | Description |
|---|---|
| Application Update | Select the Application Update Detail from the drop list. |
| Run at Date/Time | Date and time when the Broadcast should be sent to the selected devices. This is defaulted to current date and present time. |
| Topics | Dropdown list selection of device type. |
| Applicable Time Windows | Time window when Application Update will be applied to a subscribed device. Since a device restart will be triggered after an application update, specifying this window is important to ensure business continuity. |
Broadcast status can be monitored through Broadcast History application.
Once the broadcast is successfully received by a Thick POS the Updates folder in the root directory of the Enactor Application will be updated.
Additionally, the manifest.XML file will be updated with the version details of the latest Application Update.