...
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. |
...
In this procedure, you are performing a bulk export of data that you will import to your upgraded system in a later procedure using the bulk import.
| Anchor | ||||
|---|---|---|---|---|
|
...
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.
|
...
| Warning | ||
|---|---|---|
| ||
Make sure you have copied to a safe location all of the exported files from the bulk export before continuing here, where you will stop Tomcat and remove the Controller. |
...
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
|
...
| Warning | ||
|---|---|---|
| ||
Before dropping your existing database, make sure you have created a backup, as mentioned earlier in these procedures. |
| Anchor | ||||
|---|---|---|---|---|
|
...
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 |
...
In this procedure, you are performing a bulk import of the data that you exported earlier using a bulk export.
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.23.x license key. |
| Warning |
|---|
If you experiencing problems with the bulk import, do not continue; please contact Customer Support for guidance. |
...
The start/stop procedure for Universal Agent components (such as OMS) may differ depending on your platform. For instructions, see Starting and Stopping Agent Components.
| Anchor | ||||
|---|---|---|---|---|
|
...
Verify that your Agent components are communicating with the Active Controller (see Verifying Universal Agent Installation).