Installer 10.11 | Complete Installation and Upgrade Information for Software AG Products | Command Central | Bootstrapping Platform Manager on a Remote Machine Using a Template | Bootstrapping Platform Manager Using the Default SSH and WinRM Templates
 
Bootstrapping Platform Manager Using the Default SSH and WinRM Templates
The method you choose to boostrap Platform Manager on a remote machine depends on whether the remote machine has an SSH server. With Command Central 10.5 and higher, you can bootstrap Platform Manager on a remote machine using:
*The sag-spm-boot-ssh infrastructure micro template. Read the template readme and ensure that the Command Central host machine and the remote machine(s) meet the requirements described in the readme.
*A custom infrastructure micro template, generated by exporting an existing Platform Manager instance. For details about generating a custom infrastructure template see, "Exporting the Platform Manager of an Installation to a Template".
Before you apply an infrastructure micro template that bootstraps Platform Manager, you must:
*Define a credentials alias for the SSH user account that you use to connect to the remote machine, for example by using the sag-cc-creds-dev. Note that Command Central supports only the PKCS #1 definition of the ASN.1 syntax for representing the SSH private keys.
*When using a generated infrastructure micro template, ensure that the target machine is compatible with the source machine, from which you exported the template. The target machine should run on the same operating system as the source machine.
*When using the "sag-spm-boot-ssh" template, read the template readme and ensure that the Command Central host machine and the remote machine(s) meet the requirements described in the readme.
*Ensure that the UNIX or Windows operating system on the target machine has a Secure Shell (SSH) server running and the system is configured for remote access with the user account for the Software AG products. If your version of Windows has out-of-the-box SSH support, use the default SSH server on the Windows machine. If your version of Windows does not support SSH by default, set up OpenSSH on the Windows machine using a third-party tool, for example Cygwin. For information about how to install Cygwin, go to https://cygwin.com/install.html or follow the instructions in the Using Cygwin to Configure OpenSSH When Installing Platform Manager on a Remote Windows Machine article located on the TECHcommunity.
Important:
The instructions in the article also apply when you want to use a composite template to bootstrap Platform Manager on a remote Windows machine.
If the target machine does not have an SSH server, you must download the Command Central bootstrapper to the target machine and install only Platform Manager on the remote machine as described in . For a Windows remote machine, you can also use the sag-spm-boot-winrm infrastructure micro template, which uses the Windows Remote Management (WinRM) service. Note that the Command Central host machine, from which you run the "sag-spm-boot-winrm" template, must have a Windows operating system and meet the requirements listed in the template readme.
Note that with Command Central 10.3 and lower, you can only bootstrap Platform Manager on a remote Windows machine using the "sag-spm-boot-winrm" template.