Versions Compared

Old Version 3

changes.mady.by.user IT 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.

...

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:
 

html-bobswift
 Panel
<pre>

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

</pre>

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.
 

html-bobswift
 Panel
<pre>
 
[tomcat directory]/webapps/uc/WEB-INF/properties/users/ldapmap.xml

</pre>
 
You can use this file for reference when creating LDAP mappings on the LDAP Settings page of the Controller 7.2.x user interface.
...
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

 Panel

 Html bobswiftpanel
<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:
 

html-bobswift
 Panel
<pre>

[tomcat-install]\webapps\uc

</pre>

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.

...
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:
 
html-bobswift
 Panel
<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>

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.
...