Upgrade Command Central
When you upgrade Command Central, these configurations, data, and assets are migrated:
Binary cache.
Composite templates.
Credentials.
Environment, JAAS, LDAP, port, and proxy configurations.
HTTPS and SSO certificates.
License reports.
Primary and image repositories.
Users, groups, and roles, and password manager data.
Follow the instructions below to upgrade.
1. If you are going to install the new Command Central on a different machine than the old Command Central, create a ZIP file of the old Command Central. These instructions use the Java Archive tool to create the ZIP file.
a. Go to the old Command Central machine.
b. In the JAVA_HOME and PATH system variables, specify the location of the Java Archive tool as Software AG_directory\jvm\jvm\bin.
Note: On some systems, the lower-level jvm directory name includes additional information, such as \jvm\jvm160_32, or \jvm\jvm170, or \jvm\jvm_64.
c. Open a command window or shell and go to the Software AG directory that contains the old Command Central.
d. If you want to reduce the size of the ZIP file, move the log files out of the old_Software AG_directory\profiles\CCE\logs and SPM\logs directories.
e. Enter this command:
jar cfM ZIP_file_name common\conf profiles\CCE profiles\SPM install\products
f. Copy the ZIP file to any directory on the new Command Central machine.
Important: If using FTP to copy, use the binary file transfer mode\type. If you use another mode\type, the ZIP file might become corrupted.
2. Use the Command Central bootstrapper to install Command Central and to migrate configuration files and assets from the old installation to the new installation. Follow the instructions in the topic in this help for installing Command Central with these additional guidelines:
Specify the argument
-m old_Command_Central, as follows:
If old_Command_Central is on... | Specify... |
Same machine as new installation | Software AG directory that contains the old Command Central installation. |
Different machine than new installation | ZIP file you created in the previous step. |
You must specify the argument
-p password. As always, if you are installing in a production environment,
Software AG strongly recommends you replace the default with a strong, custom password.
9.12 and higher: If you want to use the same ports for the new
Command Central that you used for the old one, do not specify the -c and -C port arguments; the bootstrapper will migrate the port configurations and HTTPS and SSO certificates. If you want to use new ports for the new
Command Central, specify the -c and -C port arguments; the bootstrapper will not migrate any port information.
If the old Command Central used non-default ports to communicate with the local Platform Manager, specify the non-default ports on the -s and -S port arguments.
Note: If you do not specify the non-default ports in this scenario, the local Platform Manager will use the default ports. However, the migrated Command Central configuration contains the non-default ports, so Platform Manager will appear offline and you will have to specify the non-default ports in the new Command Central.
3. 9.7 upgrade: If you set a custom password for Platform Manager, set the custom password for the new Platform Manager. To do so, in the new Command Central, on the Instances tab, click the new Platform Manager (SPM), then click 
next to Authentication on the Overview tab.