...
For Universal Controller 7.4.x, applying maintenance refers to the increase from a currently installed 6.1.x or later release of the Controller to a 7.4.x release of the Controller (for example, increase Controller 6.2.0.1 to Controller 7.3.0.0).
If you want to increase Controller 5.2.0 to Controller 7.4.x, you must perform an upgrade. The procedures for upgrading differ from the procedures for applying maintenance (see Upgrading Universal Controller from 5.2.0).
Applying Maintenance vs. Upgrading
For Universal Controller 7.4.x, upgrading refers to the increase of its currently installed 5.2.0 version to a 7.4.x version (for example, upgrading Controller 5.2.0.5 to Controller 7.3.0.0).
You cannot upgrade to Controller 7.4.x from versions prior to 5.2.0 (for example, 5.1.1).
The procedures for upgrading differ from the procedures for applying maintenance (see Upgrading Universal Controller from 5.2.0).
Universal Controller Maintenance
...
To apply maintenance to the currently installed release of Universal Controller:
Step 1 | From the Stonebranch Customer Portal, download the Universal Controller 7.1.x package (for instructions, see /wiki/spaces/UC71x/pages/5178154). | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 2 | If any JDBC drivers have been added to the Controller installation, these should be backed up prior to the application of maintenance and then copied back after the application. Instructions for adding drivers can be found here. | |||||||||||||||||
Step 3 | Unpack the Universal Controller distribution file, using the following method appropriate for your platform:
| |||||||||||||||||
Step 4 | Stop the Tomcat container in which the Passive cluster node is deployed.
| |||||||||||||||||
Step 5 | Stop the Tomcat container in which the Active cluster node is deployed, using one of the methods shown in Step 4. | |||||||||||||||||
Step 6 | For the Active cluster node deployment:
2. Copy the war file from the new downloaded package to your webapps directory and rename the war file 3. Start the Tomcat container in which the Active cluster node is deployed.
4. Log in to the Active cluster node deployment with user ops.admin or a user with equivalent authorization and verify the installation (see Verify the Installation, below).
| |||||||||||||||||
Step 7 | Repeat Step 6 for the Passive cluster node deployment. |
Anchor | ||||
---|---|---|---|---|
|
...