Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Command Central | Creating, Managing, or Upgrading Standalone Product Installations | Upgrade a Standalone Product Installation
 
Upgrade a Standalone Product Installation
To see which products support upgrade using Command Central, see the Software AG Command Central Feature Support Matrix.
If you want to upgrade products in one environment using Command Central, follow the instructions in Upgrading Software AG Products On Premises.
If you want to automate product upgrade for multiple similar environments using Command Central, see the composite template instructions in this help. You can reconfigure endpoints such as host names and ports by adding actions in the templates. You will still need to perform the manual tasks in Upgrading Software AG Products On Premises if you cannot script them.
If you do not want to automate the upgrade of Platform Manager, Command Central bootstrapper 10.7 or later enables you to upgrade Platform Manager manually, separately from the products. The bootstrapper migrates these Platform Manager configurations and data:
*Port, SSO, proxy, and JAAS 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 Platform Manager manually.
1. 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.
a. Go to the old Platform Manager machine and stop Platform Manager.
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 Platform Manager.
d. If you want to reduce the size of the ZIP file, move the log files out of the old_Software AG_directory\SPM\logs directory.
e. Enter this command:
jar cfM ZIP_file common\conf profiles\SPM install\products
f. 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.
2. Run the Command Central bootstrapper with the arguments below, where --accept-license means you accept the Software AG product license agreement (available for review at https://documentation.softwareag.com/legal/general_license.txt).
cc-def-release-fixnumber-operating_system.{exe|sh} -D SPM
-m full_path_to_old_Platform Manager_dir_or_ZIP_file
-d full_path_to_new_Platform Manager_dir
-s old_Platform Manager_HTTP_port -S old_Platform Manager_HTTPs_port
--accept-license
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.
Examples
*To migrate the Platform Manager configurations from C:\sag105\cc\PlatformManager to C:\sag107\cc\PlatformManager using HTTP port 8172 and HTTPS port 8173:
cc-def-10.7-fix1-w64.bat -D SPM -d C:\sag107\cc\PlatformManager -m C:\sag105\cc\PlatformManager
-s 8172 -S 8173 --accept-license