Versions Compared

Old Version 6

changes.mady.by.user Stonebranch

Saved on

compared with

New Version Current

changes.mady.by.user Stonebranch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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
Export Scripts
Export Scripts
Export Scripts

...

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:
 

<pre> 
[tomcat directory]/webapps/uc/WEB-INF/plugins/com.uc/backup/unload
/ <
/
pre>
 Panel
 Html bobswift

Step 6
Copy the zip/tar file to a safe place for use after the upgrade process.
Step 7
Copy your glide.properties file to a safe place. You may need to consult this file later. The file is located here:
 
<pre>

[tomcat directory]/webapps/uc/WEB-INF/properties

</pre>
 Panel
 Html bobswift

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.
 
<pre>
 
[tomcat directory]/webapps/uc/WEB-INF/properties/users/ldapmap.xml

</pre>
 Panel
 Html bobswift
 
You can use this file for reference when creating LDAP mappings on the LDAP Settings page of the Controller 7.2.x user interface.
...
 Warning
titleImportant
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:
 
Windows
Use the services application to stop Tomcat. You also can issue the stop command on a command line:
 

<pre>
 
net stop [name of Tomcat service]

</pre>
 Panel
 Html bobswift
 
UNIX
Stop the daemon using the script found in the /etc/init.d directory for Tomcat.
 

<pre>
 
service [name of Tomcat service] stop

</pre>
 Panel
 Html bobswift
 
Windows or UNIX
Stop the service using the $CATALINA_HOME\bin\shutdown.bat or $CATALINA_HOME/bin/shutdown.sh scripts:
 
Windows

<pre>

cd $CATALINA_HOME\bin

shutdown</pre>
shutdown
 Panel
 Html bobswift
Linux/Unix

html-bobswift
 Panel
<pre>

cd $CATALINA_HOME/bin
./shutdown 
</pre>

Step 2
Confirm that the Tomcat processes where the Passive Controllers are deployed are not running.
 
Windows
Use the Windows Task Manager.
 
Linux/Unix
Use the ps command.
Step 3
Back up the Passive Controller deployment directories in any folder other than one under the Tomcat installation.
 
The Controller installation process renamed the unpacked war file (universal-controller-N.N.N.N-build.N.war) as uc.war, so the following would be your deployment directory:
 

<pre>

[tomcat-install]\webapps\uc

</pre>
 Panel
 Html bobswift

Step 4
Repeat steps 1 through 3 for the Active Controller.
Step 5
Delete the deployment directory and uc.war file for all Controllers.
 
The following would be your deployment directory and uc.war:
 

<pre>

[tomcat-install]\webapps\uc
[tomcat-install]\webapps\uc.war

</pre>
 Panel
 Html bobswift

 Note
titleNote
If you want to rename the deployment directory and uc.war for back-up, you must do so outside of the Tomcat folder.

...
 Warning
titleImportant
Before dropping your existing database, make sure you have created a backup, as mentioned earlier in these procedures.
 Anchor
Download the New Controller
Download the New Controller
Download the New Controller
...
Step 1
Start Tomcat where the Active Controller is deployed.
 
When the database initialization is complete and the Controller is running, you will see the following (for example) in the log:
 
<pre>

2012-09-12-12:53:07:339   INFO [Ops.Cluster.Monitor.0] Server is now Running in Active mode. Previous mode was Passive. 
2012-09-12-12:53:07:339   INFO [Ops.Cluster.Monitor.0] Setting server to ACTIVE.

</pre>
 Panel
 Html bobswift

Step 2
As a precaution, clear the browser cache.
Step 3
Log in to the Active Controller with ops.admin (password is not set). On the Universal Controller Home Dashboard, verify that the Overview specifies the correct release.
...
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:
  • Activity
  • History
  • Audit
  • Reports
  • Cluster nodes
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.
...