Migrating Platform Manager Using a Template
You can migrate Platform Manager version 10.7 and higher through a composite template. For example, you can migrate the Platform Manager configurations (such as the proxy server configuration, SSL certificates, and user management settings) from a source installation into a target installation of the same or higher release version. For more information about the Platform Manager configurations and data that you can migrate, see
Upgrade a Standalone Product
Installation.
Before you migrate the Platform Manager configurations from the source to the target installation, make sure that:
If Platform Manager is installed on the target machine, it has not been started yet.
The Command Central bootstrap installer for the target Platform Manager version is added in the target Command Central.
If using a source archive to migrate the Platform Manager configurations to a different host, copy the ZIP source file to the target Platform Manager machine.
To migrate the Platform Manager configurations from the source installation to the target installation:
1. In the composite template, set the Platform Manager bootstrap parameters in the nodes:default:default:bootstrapInfo: section as follows:
nodes:
default:
default:
port: ${nodes.spm.port} # The port of the source Platform Manager.
bootstrapInfo:
installer: ${cc.installer} # The file name of the Command Central bootstrap installer to use for
# the target Platform Manager version.
installDir: ${install_dir} # The installation directory of the target Platform Manager.
port: ${nodes.ssh.port}
credentials: spm.SSH.credentials
Important:
Do not change the Platform Manager port when migrating Platform Manager configurations, because the source and target Platform Managers must have the same port number and type.
2. Import the composite template in Command Central.
3. Apply the composite template in migration mode by running the apply composite templates command with the environment.mode=migration argument.
The Command Central bootstrap installer (specified in the installer: parameter in the template) will run the Platform Manager migration utility, which migrates all the configurations from the source Platform Manager installation to the target Platform Manager installation.
Example
To use the template with alias "spm-migration" to migrate the Platform Manager configurations from a 10.5 source installation to the target Platform Manager with version 10.7, located in the "C:\sag107\cc" directory:
1. Define the following bootstrap parameters in the "spm-migration" template:
...
nodes:
default:
default:
...
bootstrapInfo:
installer: cc-def-10.7-fix1-w64.exe # The file name of the bootstrap installer to use for the
# target Platform Manager version 10.7.
installDir: C:\sag107\cc # The installation directory of the target Platform Manager.
credentials: defaultSSHCredentials
port: 22
2. Import the "spm-migration" template in Command Central and run the following command to apply the template in migration mode:
sagcc exec templates composite apply spm-migration
environment.mode=migration spm.port=8093 src.install.dir=C:\sag105\cc
install.dir=C:\sag107\cc -s rubicon
When applying a composite template in migration mode, if the installer: parameter points to a bootstrap installer with version 10.5 or lower, or the installDir: parameter points to a target Platform Manager installation with version 10.5 or lower, Command Central does not migrate the Platform Manager configurations. You can only migrate Platform Manager 10.5 or lower by running the Command Central bootstrap installer 10.7 or higher at the command line.