Upgrade Command Central
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 as described below. 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 exceptions:
Also specify the argument
-m. Set the argument as follows:
If old Command Central installation is on... | Set argument to... |
Same machine as new installation | Software AG directory that contains the old Command Central installation. |
Different machine than new installation | ZIP file you made in the previous step. |
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 port arguments -c and -C; 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 arguments; the bootstrapper will not migrate any port information.
The table below lists the files, configurations, and assets that are migrated and the releases from which they will be migrated.
File or Asset | 9.6 and higher | 9.7 and higher | 9.8 and higher | 9.9 and higher | 9.12 and higher |
Binary cache | | | | | |
Composite templates | | | | | |
Environment configurations | | | | | |
JAAS configurations and password manager data | | | | | |
LDAP configurations | | | | | |
License reports | | | | | |
Local mirror repositories | | | | | |
Port configurations | | | | | |
HTTPS and SSO certificates | | | | | |
Users, groups, and roles | | | | | |
3. 9.0, 9.5, 9.6, or 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. 