Product Documentation

Upgrading Command Center

Mar 30, 2016

Command Center offers new features and improved functionality of existing features. For more information, see

Upgrading the Command Center server to release requires the installation of the Command Center service pack. This service pack installs the upgraded Command Center platform, installs JRE 1.6, and upgrades your data.

You can download the service pack for both Windows and Linux from the Citrix portal Web site: http://mycitrix.com.

Note: You cannot downgrade a Command Center software or appliance.
Important: Please see the database upgrade requirements and the upgrade scenarios and steps before you begin upgrading your Command Center server.

Database Upgrade Requirements

For Command Center release , the MySQL database version supported is 5.0 and higher with InnoDB storage engine. Also, Command Center 4.0 and later no longer supports internal MySQL that was packaged with earlier releases of Command Center.

If you are using Command Center release 3.x with internal or external MySQL database version earlier than 5.1.x and/or with MyISAM storage engine, you must migrate your data to a MySQL database running 5.1.x with InnoDB storage engine before you upgrade to Command Center .

Upgrade Scenarios and Procedures

The following table summarizes four scenarios and the upgrade steps you would follow to upgrade your Command Center in each scenario.
 

Scenario

Upgrade Steps

Upgrading from Command Center release 3.x with one of the following databases:

o    MS SQL database

o    Oracle database

o    External MySQL 5.1.x with InnoDB storage engine

1.      Upgrade to Command Center 4.0 by installing the service pack CC_SP4.exe (for Windows) or, CC_SP4.bin (for Linux)

For information about the installation steps, see Installing the Service Pack.

2.      Upgrade to Command Center 4.1 by installing the latest version of the service pack with file naming convention: CC_SP_ReleaseNumber_BuildNumber.exe (for Windows) or, CC_SP_ReleaseNumber_BuildNumber.bin (for Linux)

3.      Upgrade to Command Center 5.x by installing the latest version of the service pack with file naming convention: CC_SP_ReleaseNumber_BuildNumber.exe (for Windows) or, CC_SP_ReleaseNumber_BuildNumber.bin (for Linux)

For information about the installation steps, see Installing the Service Pack.

Upgrading from Command Center release 3.x with one of the following MySQL database versions:

o    Internal MySQL

o    External MySQL running a version earlier than 5.1.x

o    External MySQL running version 5.1.x and with MyISAM storage engine.

1.      Migrate to an external MySQL database running version 5.1.x with InnoDB storage engine.

For information about the migration executable and the migration steps, see Migrating MySQL Database.

2.      Upgrade to Command Center 4.0 by installing the service pack CC_SP4.exe (for Windows) or, CC_SP4.bin (for Linux).

For information about the installation steps, see Installing the Service Pack.

3.      Upgrade to Command Center 4.1 by installing the latest version of the service pack with file naming convention: CC_SP_ReleaseNumber_BuildNumber.exe (for Windows) or, CC_SP_ReleaseNumber_BuildNumber.bin (for Linux)

4.      Upgrade to Command Center 5.x by installing the latest version of the service pack with file naming convention: CC_SP_ReleaseNumber_BuildNumber.exe (for Windows) or, CC_SP_ReleaseNumber_BuildNumber.bin (for Linux)

For information about the installation steps, see Installing the Service Pack.

Upgrading within Command Center release 5.x

Install only the latest version of the 5.1 service pack with file naming convention: CC_SP_ReleaseNumber_BuildNumber.exe (for Windows) or, CC_SP_ReleaseNumber_BuildNumber.bin (for Linux)

For information on the installation steps, see Installing the Service Pack.

Upgrading Command Center software in a High Availability (HA) setup

To upgrade Command Center software in an HA setup:

1.      Stop the Secondary Command Center service.

2.      Stop the Primary Command Center service.

3.      Upgrade the Primary Command Center server as described in the scenarios above.

4.      Upgrade the Secondary Command Center server as described in the scenarios above.

5.      Start the Primary Command Center service (Make sure that all the processes in <CC_HOME>/logs/wrapper.log are in the Started state)

6.      Start the Secondary Command Center service. (Verify that the Command Center server  in <CC_HOME>/logs/wrapper.log comes up as a secondary server)