Upgrade Command Central

About this task

When you upgrade Command Central, the following configurations and data are migrated for Command Central:

Binary cache.
Composite templates.
Credentials.
Port, SSO, proxy, environment, JAAS, LDAP, and outbound SSL configurations.
HTTPS, LDAP, and SSO certificates.
License reports.
Users, groups, and roles, and password manager data.
Any Java system properties that have been customized from the defaults.
Command Central bootstrap installers.

Important: Repositories are not migrated when you upgrade to Command Central 12.1. After upgrading, recreate connections to webMethods repositories.

The following configurations and data are migrated for the Platform Manager that is installed with Command Central:

Port, SSO, and proxy configurations.
HTTPS and SSO certificates.
Users, groups, and roles, and password manager data.
Any Java system properties that have been customized from the defaults.

Follow the instructions below to upgrade.

Procedure

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 installation. To use the Java Archive tool to create the ZIP file:
1. Go to the machine with the old Command Central installation and stop Command Central.
2. Optionally, move the log files out of the IBMwebMethods_directory \profiles\CCE\logs and IBMwebMethods_directory \SPM\logs directories in order to reduce the size of the ZIP file.
3. In the JAVA_HOME and PATH system variables, specify the location of the Java Archive tool as IBMwebMethods_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.
4. Open a command window or shell and go to the IBM directory that contains the old Command Central installation.
5. Enter the following command:
```
jar cfM ZIP_file common\conf profiles\CCE profiles\SPM install\products
```
6. Copy the ZIP file to any directory on the new Command Central machine.
  
  Important: If you are copying the file using FTP, use the binary file transfer mode\type. If you use another mode\type, the ZIP file might become corrupted.
Use the Command Central bootstrapper to install Command Central and to migrate configuration files from the old installation to the new installation. Follow the instructions in the topic in this help for installing Command Central with the additional guidelines below.
- Specify the -m argument in the following way:
```
- m full_path_to_old_Command Central_dir_or_ZIP_file
```
- You must specify the -p argument by providing the administrator user password of the old Command Central. If you are migrating Platform Manager using the -D SPM option, the -p argument is optional. After completing the upgrade, you can change the password by following the steps in Change or Reset the Command Central Administrator Password. Change the Command Central administrator user password periodically.
- 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.
  Important: You cannot update the source Platform Manager port configurations during upgrade, since this would break the connection to the migrated mirror repositories. Command Central automatically migrates the port configurations of the source Platform Manager. Even if you provide new Platform Manager ports using the -s and -S arguments, Command Central will ignore them.