Upgrade Platform Manager

About this task

Follow the instructions below to upgrade Platform Manager manually.

Procedure

If you are going to install the new Platform Manager on a different machine than the old Platform Manager, create a ZIP file of the old Platform Manager. These instructions use the Java Archive tool to create the ZIP file.
1. Go to the old Platform Manager machine and stop Platform Manager.
2. 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.
3. Open a command window or shell and go to the IBM directory that contains the old Platform Manager.
4. If you want to reduce the size of the ZIP file, move the log files out of the old_ IBMwebMethods_directory \SPM\logs directory.
5. Enter this command:
```
jar cfM ZIP_file common\conf profiles\SPM install\products
```
6. Copy the ZIP file to any directory on the new Platform Manager 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.
Run the Command Central bootstrapper in one of these ways according to the location of the new Platform Manager:
- If the new Platform Manager is on a different machine than the old Platform Manager, specify the ZIP file of the old Platform Manager as the value of the -m argument:
```
cc-def-release-fixnumber-operating_system.{exe|sh} -D SPM 
-m full_path_to_old_Platform Manager_ZIP_file
-d full_path_to_new_Platform Manager_dir 
-s old_Platform Manager_HTTP_port -S old_Platform Manager_HTTPS_port 
[-p old_SPM_password | --base64-pass old_SPM_base64_encoded_password] 
```
- If the new and the old Platform Manager installations are on the same machine, specify the full path to the old Platform Manager as the value of the -m argument:
```
cc-def-release-fixnumber-operating_system.{exe|sh} -D SPM 
-m full_path_to_old_Platform Manager_dir
-d full_path_to_new_Platform Manager_dir 
-s old_Platform Manager_HTTP_port -S old_Platform Manager_HTTPS_port
[-p old_SPM_password | --base64-pass old_SPM_base64_encoded_password]
```
Note: If for some reason you have to specify ports that are different from the old ports, Command Central will disable the specified ports after the upgrade and will communicate with the new Platform Manager using the ports used by the old Platform Manager.
Note: When upgrading from release 11.1 or earlier, the bootstrapper automatically migrates the outbound SSL connection configuration for Command Central. The migration performs the following actions:
- Renames the configuration file from com.softwareag.platform.management.ssl.connection.properties to com.webmethods.platform.management.ssl.connection.properties.
- Transforms the trust.store.location property value to a path-token format compatible with the new installation layout.
- Merges the certificates from the old truststore into the new truststore, skipping any certificates that already exist in the new truststore.

Example

To migrate the Platform Manager configurations from C:\webMethods105\cc\PlatformManager to C:\webMethods121\cc\PlatformManager using HTTP port 8172 and HTTPS port 8173:

cc-def-12.1-fix1-w64.bat -D SPM -d C:\webMethods121\cc\PlatformManager -m C:\webMethods105\cc\PlatformManager 
-s 8172 -S 8173 -p old_SPM_password