Progress Sonic 8.5 Installation and Upgrade Guide - Product ...
Progress Sonic 8.5 Installation and Upgrade Guide - Product ...
Progress Sonic 8.5 Installation and Upgrade Guide - Product ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
◆ To perform the updgrade of the backup Domain Manager:<br />
Upgrading Other Configuration Objects<br />
1. On the backup Domain Manager system, use the console window that is open at the<br />
<strong>8.5</strong>_install_root/MQ<strong>8.5</strong>/bin location.<br />
2. Enter:<br />
upgrade upgrade.properties<br />
The backup Domain Manager components <strong>and</strong> stores are moved to the <strong>8.5</strong> location<br />
<strong>and</strong> file structure, <strong>and</strong> then upgraded.<br />
3. Start the upgraded backup Domain Manager.<br />
When the Directory Services finish synchronizing, the <strong>8.5</strong> Domain Manager is<br />
running with the primary in ACTIVE state <strong>and</strong> the backup in STANDBY state.<br />
4. Start the <strong>8.5</strong> <strong>Sonic</strong> Management Console, <strong>and</strong> connect to the upgraded Domain<br />
Manager.<br />
The upgrade of the fault tolerant management framework is complete.<br />
Upgrading Other Configuration Objects<br />
A few other deployed components need additional h<strong>and</strong>ling to be upgraded.<br />
Note <strong>Sonic</strong> Event Monitor -- In releases prior to <strong>8.5</strong>, <strong>Sonic</strong> Event Monitor was a separately<br />
licensed product. As of <strong>8.5</strong>, that is no longer the case; a license key is not required for<br />
creating, using or upgrading to a release <strong>8.5</strong> or newer <strong>Sonic</strong> Event Monitor <strong>8.5</strong>.<br />
Upgrading Activation Daemons<br />
Upgrading the container that hosts an activation daemon <strong>and</strong> upgrading the containers that<br />
the daemon can launch effectively upgrades a daemon instance.<br />
If you use activation daemons in your deployments, note that upgrading an activation<br />
daemon’s configuration (through the <strong>Sonic</strong> Management Console), its container, or any<br />
object on the daemon’s activation list forces upgrade of the configuration of all the<br />
containers in its activation list <strong>and</strong> any components that those containers host. If you<br />
cannot manage the volume of changes that could follow from such a set of configuration<br />
installations that require corresponding physical code installations on their respective host<br />
systems, you might want to clear the activation list until the other objects get upgraded,<br />
<strong>and</strong> then upgrade the daemon <strong>and</strong> reconstruct its activation list.<br />
<strong>Progress</strong> <strong>Sonic</strong> <strong>Installation</strong> <strong>and</strong> <strong>Upgrade</strong> <strong>Guide</strong> <strong>8.5</strong> 215