...
For Universal Controller 7.12.x, upgrading refers to the increase of a currently installed 5.2.0 version of the Controller to a 7.12.x version (for example, upgrading Controller 5.2.0.5 to Controller 7.12.0.0).
You can upgrade to Universal Controller 7.12.x only from Universal Controller 5.2.0; you cannot upgrade to 7.12.x from any version earlier than 5.2.0 (for example, 5.1.1).
| Note | ||
|---|---|---|
| ||
To increase a currently installed 6.1.x or later release of the Controller to a 7.12.x release, you do not have to perform an upgrade; you only have to apply maintenance to the 6.1.x or later version. |
...
For Universal Controller 7.12.x, applying maintenance refers to the increase from a currently installed 6.1.x or later release of the Controller to a 7.12.x release of the Controller (for example, increase Controller 6.1.3.1 to Controller 7.12.0.0).
The procedures for upgrading differ from the procedures for applying maintenance (see Applying Maintenance to Universal Controller).
...
Upgrade Controller to... | 1.6.0 | 1.7.0 | 5.1.0 | 5.2.0 | 6.1.x | 6.2.x | 6.3.x | 6.4.x | 6.5.x | 6.6.x | 6.7.x | 6.8.x | 6.9.x | 7.0.x | 7.1.x | 7.2.x |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
From 1.5.0 |
|
|
|
| ||||||||||||
From 1.6.0 |
|
|
| |||||||||||||
From 1.7.0 |
|
| ||||||||||||||
From 5.1.0 |
| |||||||||||||||
From 5.2.0 |
|
|
|
|
|
|
|  | | | | |
Upgrade Procedures
These instructions comprise the following procedures:
1 | Upgrading Universal Controller from 5.2.0#Make Make Sure No Records Are Being Processed |
|---|---|
2 | Upgrading Universal Controller from 5.2.0#Stop Stop OMS |
3 | Upgrading Universal Controller from 5.2.0#Back Back Up Your Database |
4 | Upgrading Universal Controller from 5.2.0#Run Run an Export on the Active Controller |
5 | Upgrading Universal Controller from 5.2.0#Stop Stop Tomcat and Remove All Controllers |
6 | Upgrading Universal Controller from 5.2.0#Prepare Prepare Your Database |
7 | Upgrading Universal Controller from 5.2.0#Download Download the New Controller |
8 | Upgrading Universal Controller from 5.2.0#Install Install the Controller |
9 | Upgrading Universal Controller from 5.2.0#Verify Verify the Active Controller Installation |
10 | Upgrading Universal Controller from 5.2.0#Run Run an Import on the Active Controller |
11 | Upgrading Universal Controller from 5.2.0#Check Check Your Data |
12 | Upgrading Universal Controller from 5.2.0#LDAP LDAP Synchronization |
13 | Upgrading Universal Controller from 5.2.0#Verify Verify the Passive Controller Installations |
14 | Upgrading Universal Controller from 5.2.0#Start Start OMS |
15 | Upgrading Universal Controller from 5.2.0#Verify Verify the Upgrade |
| Note | ||
|---|---|---|
| ||
These instructions assume that you are running a High Availability Universal Controller system: a system configured with Active and Passive Controllers (cluster nodes). If you are running a single Controller, disregard the steps for Passive Controllers. |
...
| Warning | ||
|---|---|---|
| ||
Before upgrading your Controllers, back up your database. The database backup is a fail-safe measure; you will be using the Controller 5.2.0 export and Controller 7.12.x import, as described below, to migrate your data. |
...
Step 1 | From the navigation pane, select Automation Center Administration > Configuration > Maintenance Scripts. The image below shows export script options for Controller 5.2.0. | ||
|---|---|---|---|
Step 2 | Select an export script and click Run. | ||
Step 3 | The Controller prompts for a confirmation. Click Yes. As your data is exported, the output from the script is written to the screen, as shown here. | ||
Step 4 | Check the output for error messages. If there are any, copy the output to a file and email it to Customer Support. | ||
Step 5 | Zip or tar the contents of:
| ||
Step 6 | Copy the zip/tar file to a safe place for use after the upgrade process. | ||
Step 7 | Copy your
| ||
Step 8 | Copy your license key from the Properties list and store it in a safe place. | ||
Step 9 | Copy the LDAP mapping file to a safe place for use after the upgrade process.
|
| Anchor | ||||
|---|---|---|---|---|
|
...
Step 1 | Stop the Tomcat containers in which all Passive Controllers are deployed:
Linux/Unix
| ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Step 2 | Confirm that the Tomcat processes where the Passive Controllers are deployed are not running. | ||||||||||
Step 3 | Back up the Passive Controller deployment directories in any folder other than one under the Tomcat installation.
| ||||||||||
Step 4 | Repeat steps 1 through 3 for the Active Controller. | ||||||||||
Step 5 | Delete the deployment directory and
|
...
Step 1 | Start Tomcat where the Active Controller is deployed.
| ||
|---|---|---|---|
Step 2 | As a precaution, clear the browser cache. | ||
Step 3 | Log in to the Active Controller with |
...
Step 1 | Unzip/untar the backup file that you created earlier using the export. |
|---|---|
Step 2 | Copy the XML files to any directory on the Controller that it has access to. |
Step 3 | From the Administration navigation pane, select Configuration > Server Operations. |
Step 4 | Locate and run the Bulk Import Server Operation. |
Step 5 | The utility prompts for a confirmation. Click Yes. |
Step 6 | As your data is imported, the output from the operation is written to the screen. Look over the output for any error messages. If you see any, copy the output to a file and email it to Customer Support. |
Step 7 | Due to technology and feature changes in Universal Controller 6.7.x, a number of XML files will not be imported. These include but may not be limited to:
|
Step 8 | Apply your 7.12.x license key. |
| Warning |
|---|
If you experiencing problems with the bulk import, do not continue; please contact Customer Support for guidance. |
...
In order to log in to the Controller using LDAP credentials, you must set the LDAP Synchronization Enabled Universal Controller System property (Administration > Configuration > Properties in the Controller user interface) to true.
...