...
For Universal Controller 7.23.x, applying maintenance refers to the increase from a currently installed 6.1.x or later release of the Controller to a 7.23.x release of the Controller (for example, increase Controller 6.2.0.1 to Controller 7.23.0.0).
If you want to increase Controller 5.2.0 to Controller 7.2.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).
...
For Universal Controller 7.23.x, upgrading refers to the increase of its currently installed 5.2.0 version to a 7.23.x version (for example, upgrading Controller 5.2.0.5 to Controller 7.23.0.0).
You cannot upgrade to Controller 7.23.x from versions prior to 5.2.0 (for example, 5.1.1).
...
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: Windows Use an appropriate archiving / unzipping product. Linux/Unix Panel |
---|
Html bobswift |
---|
<pre>tar -xvf universal-controller-N.N.N.N.tar</pre> |
|
|
---|
Step 4 | Stop the Tomcat container in which the Passive cluster node is deployed. Windows Use the services application to stop Tomcat. You also can issue the stop command on a command line: Panel |
---|
Html bobswift |
---|
<pre>
net stop [name of Tomcat service]
</pre> |
|
UNIX Stop the daemon using the script found in the /etc/init.d directory for Tomcat. Panel |
---|
Html bobswift |
---|
<pre>
service [name of Tomcat service] stop
</pre> |
|
Windows or UNIX Stop the service using the $CATALINA_HOME/bin/shutdown.bat or $CATALINA_HOME/bin/shutdown.sh scripts: Windows Panel |
---|
Html bobswift |
---|
<pre>
cd $CATALINA_HOME\bin
shutdown</pre> |
|
Linux/Unix Panel |
---|
Html bobswift |
---|
<pre>
cd $CATALINA_HOME/bin
./shutdown </pre> |
|
|
---|
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: html-bobswift<ol>
<li> - Delete
- the
existing <b>deployment directory</b> and <b>war</b> file from your <b>webapps</b> directory.
<br><br>
The Controller installation process renamed the unpacked <b>war</b> file (<b><code>universal- existing deployment directory and war file from your webapps directory.
The Controller installation process renamed the unpacked war file (universal-controller-N.N.N.N-build.N. war</code></b>war ) - as
<b><code>uc.war</code></b>, so the following would be your <b>deployment directory</b> and <b>war</b> file:
<br><br>
uc.war , so the following would be your deployment directory and war file:
Panel |
---|
Html bobswift |
---|
<pre>
[tomcat-install]\webapps\uc
[tomcat-install]\webapps\uc.war
</pre> |
|
Note |
---|
| If you want to rename the deployment directory and uc.war for back-up, you must do so outside of the Tomcat folder. | Html bobswift | <li> Copy the <b>war</b> file from the new downloaded package to your <b>webapps</b> directory and rename the <b>war</b> file <b><code>uc.war</code></b>.
<li> Start the Tomcat container in which the <b><i>Active</i></b> cluster node is deployed.
2. Copy the war file from the new downloaded package to your webapps directory and rename the war file uc.war . 3. Start the Tomcat container in which the Active cluster node is deployed. Note |
---|
| We recommend that all Universal Controller users clear their browser cache and close their browser prior to re-opening and navigating back to the Universal Controller URL to ensure that the most recent client updates are loaded. | Html bobswift | <li>
Log in to the <b><i>Active</i></b> cluster node deployment with user <b>ops.admin</b> or a user with equivalent authorization and verify the installation (see <b>Verify the Installation</b>, below).\
the Active cluster node deployment with user ops.admin or a user with equivalent authorization and verify the installation (see Verify the Installation, below). Note |
---|
| If you have deployed any JDBC driver jar files (or in the case of DB2, a JDBC driver license jar file) to the $CATALINA_HOME/webapps/uc/WEB-INF/lib directory, you must recopy these files to this directory and restart Tomcat after your initial validation. | Html bobswift |
---|
</ol> |
|
---|
Step 7 | Repeat Step 6 for the Passive cluster node deployment. |
---|
...