glp/0/{SID}/rq/dev/{Edge_Protocol_ID}/{Handle}/do glp/0/{SID}/rq/grp/{Handle}/do glp/0/{SID}/rq/do |
The IAP Load do Action supports loading data to edge devices and edge servers. This can be used to update and upgrade executable firmware images, but can also be used for applications beyond firmware upgrades. For example, the service can transfer and install language packs for localization, additional software components, software licenses, or supplementary data such as device interfaces or device resource files.
...
The CMS reads the manifest in the outer image file and constructs an IAP load action request. When the inner image is embedded within the outer image, the CMS hosts the inner image in a suitable location and computes the HTTP or HTTPS download URL and access credentials. When the inner image is not embedded within the outer image, the CMS takes the inner image URL and access credentials from the manifest.
...
The inner image integrity can be checked with an MD5, SHA256, or SHA512 checksum. This is optional, but recommended unless the image itself includes a way to verify its integrity. The checksum is provided with the manifest, which is part of the outer image file.
The manifest is a text file named "manifest" (no period or file extension) that is provided with the outer image. The manifest contains a JSON object that provides meta data about the inner image, and is not part of the inner image. For example:
{ method: "native", |
See the Load Action and Manifest Properties table for a description of the contents of the manifest.
...