Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

About Dynamic Deployment of Upgrades and Patches
About Dynamic Deployment of Upgrades and Patches
Upgrades of Sonic 7.5 and 7.6 installations requires some tasks—installing a launcher and
running an upgrade utility—on each host system to bring them into compliance with the
centralized installation and provisioning paradigm.
Going forward, upgrades and patches will no longer require any actions on distributed
systems in the domain. Importing upgrade and patch libraries into the Directory Service’s
Sonic File System will automatically provision the deployed components upon container
restart. Any additional upgrade or update actions will be performed through the
connection to the Domain Manager.
Rollout of changes can be controlled so that large scale deployments can specify a set of
hosts to upgrade, verify the results, and then apply changes to another set.
Enhancements to the ConfigAdmin Utility
The ConfigAdmin utility (located in MQ8.5/bin) has been enhanced to provide support for
centrally installing and dynamically deploying upgrades and patches.
To help support the centralized installation of upgrades and patches, new operations have
been added for manipulating the Directory Service's Sonic File System:
import-files
copy-files
create-folder
delete-files
rename-folder
rename-file
New operations have also been added to help centrally manage and optimize the
incremental deployment of upgrades and patches on a container-by-container basis:
where:
copy-ds-files-to-container-caches
|all-containers [exclude]
modify-archive-search-path
|all-containers [exclude]
● is a text file where each line is one container path
● [exclude] when specified, uses containers in the list as an exclusion list
Progress Sonic Installation and Upgrade Guide 8.5 47