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

Phases of Upgrades from 7.5 and 7.6 to Sonic 8.5
Editing a non-Domain Manager upgrade.properties file
The result of extracting an upgrade.properties file for a container and its hosted
components can provides the migration tool all the information needed for the upgrade.
You might need to perform some edits to the upgrade.properties file before running the
upgrade:
● Add 8.5 license keys for SonicMQ broker components in the product.controlNumber
properties.
● If the container includes a broker with paths to the broker’s data store and logs as
relative paths, add the explicit path to the container.previous.working.directory
property.
● Extend the root.list to include multiple containers on the local host, and then add
container-specific properties for each additional container.
● For management over Dynamic Routing, add a management routing node’s central
connection properties, and add the local connection and management node to
containers that use a management routing node.
● Adjust broker database and log actions and locations for the upgrade.
● Specify paths to SSL paths to certificates
● Establish a Windows Service for a container
Important Use forward slashes '/' in path values on Windows. For instance, c:/Sonic/MQ8.5/ct01.xml.
The tables of upgrade properties are distinguished as general properties and containerspecific
properties.
Running a non-Domain Manager Upgrade
◆ To perform the upgrade of the container:
1. Open a console window at the 8.5_launcher_install_root/Upgrade/bin location that
contains the upgrade properties file you want to run.
2. Enter:
upgrade upgrade.properties
The container and its components and their stores are migrated to the 8.5 subdirectory of
the 8.5 Launcher’s Containers directory.
Progress Sonic Installation and Upgrade Guide 8.5 199