The Polycom RealPresence DMA system’s Software Upgrade API lets you upload a software upgrade package and install the upgrade on your system (both servers, if present). It also lets you roll back to the previous version, if necessary. This process can be used for patches, minor upgrades, and major upgrades. In all three cases, the current system configuration (including users, MCUs, Conference Manager settings, Call Server settings, and local cluster settings) is preserved. Content-Type: application/vnd.plcm.plcm-software-upgrade-details+xml. All attributes are used in ETag calculation except for entity-tag and atom-links.
| Name | Type | Description | Attributes |
|---|---|---|---|
| plcm-software-upgrade-history-list | plcm-software-upgrade-history-list | See Definition of plcm-software-upgrade-history-list | |
| atomLinkList | List of link | See Definition of link | |
| system-version | xs:string | Build version of the current DMA system. | Mandatory |
| roll-back-version | xs:string | Build version of the rollback DMA system. | |
| upgrade-version | xs:string | Build version of the DMA system on which upgrade has to be performed. | |
| sha1 | xs:string | It represents the SHA1 checksum of build. | |
| restart-required | xs:boolean | It represents system required restart for upgrade | |
| activation-key-required | xs:boolean | It represents system required any license key | |
| entity-tag | EntityTag | The unique value generated from the server object instance. This value is the same value that MUST be applied to the HTTP Entity Tag (ETag) header for a single instance of this object. Client modification of this field is not allowed for this instance. |
| Name | Type | Restrictions |
|---|---|---|
| EntityTag | xs:string | Length of value must be >=1 Length of value must be <=64 |