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. On the bootstrapper command, specify the -m argument and set the argument to the Software AG directory that contains the old Command Central installation or the ZIP file you made in the previous step. The table below lists the files and assets that are migrated.
File or Asset | 9.7 and lower | 9.8 | 9.9 and higher |
Binary cache | Yes | Yes | Yes |
Composite templates | N/A | Yes | Yes |
Environment configuration data | Yes | Yes | Yes |
JAAS configuration and password manager data | No | Yes | Yes |
LDAP configuration | Yes | Yes | Yes |
License reports | N/A | Yes | Yes |
Local mirror repositories | N/A | No | Yes |
Port configuration data | No | No | No |
Users, groups, and roles | Yes | Yes | Yes |
3. Go to the Software AG_directory\profiles\CCE\configuration \com.softwareag.platform.config.propsloader directory in the old and new installations and open the com.softwareag.sso.pid.properties. If a value in the old file is different from the corresponding value in the new file, copy the old value over the new value. In addition, update any absolute file system paths in the new files to point to the new installation. Do not update paths that use tokens (for example, do not update @path\:sag.install.area\common\conf\platform_truststore.jks).
4. 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.