Exporting the Platform Manager of an Installation to a Template
You can export the Platform Manager of an installation managed by Command Central to an infrastructure micro template. Command Central generates a template with the Platform Manager data, imports the generated template automatically, and creates a layer type definition for the template in the local Command Central installation. You can use the layer definition for the template to create an infrastructure layer in an existing stack.
In the Command Central web user interface, you access the Export wizard from the Overview page of an SPM instance by selecting the Export infrastructure option. By default, Command Central generates a template that includes the following data about the Platform Manager instance:
Products, which includes the
Platform Manager components and the product plugins installed on the SPM instance
Fixes
Configurations of the SPM instance
If you select the Include Hostname checkbox, the generated template will also include the hostname of the Platform Manager node, from which you export Platform Manager.
Note that the sections and parameters included in the generated template will depend on the release version of the
Platform Manager installation from which you export the
Platform Manager instance. For details about the template that
Command Central generates based on the selected infrastructure data and the release version of the
Platform Manager instance, see the "Usage Notes for Exporting a Platform Manager Instance" in
sagcc exec templates composite generate.
By default, if you choose to include configurations, Command Central exports all configuration instances for all configuration types from the selected Platform Manager instance and its child components. In the Select Configuration Types step of the wizard, you can select which configuration types for the Platform Manager instance and its child components to include in the generated template.
You can view the exported template in the Templates view of the Command Central web user interface. If you want to modify the template, you can download and edit it in a text editor, and then re-import the template in Command Central.
Considerations when Exporting Platform Manager
When exporting a Platform Manager instance to an infrastructure template, you should consider the following:
If you want to export a
Platform Manager instance to a different host, but keep the same node alias name, select
Include Hostname to include the hostname of the
Platform Manager node in the exported template. You can use this approach when migrating a node.
When exporting a
Platform Manager instance with fixes, you must check the version of the
Command Central boostrapper that you will specify in the
cc.installer: ${} parameter in the generated template. If you specify a bootstrapper that contains fixes with a higher version than the ones listed in the generated template, the fixes from the bootstrapper will get installed and will replace the ones from the template.
You cannot apply an exported template with configurations on the same
Platform Manager installation from which you exported the configurations. Software AG recommends using one virtual machine for the
Platform Manager installation from which to export and another virtual machine for the
Platform Manager installation in which to apply the exported template with configurations.
If any of the configurations you export use full file paths, you must review the generated template and parameterize the configurations that include full file paths.
Example
The log4j.configurationFile property in the following COMMON-SYSPROPS configuration uses a full installation directory path that gets exported as follows:
COMMON-JAVASYSPROPS:
COMMON-JAVASYSPROPS:
osgi.install.area: '"%OSGI_INSTALL_AREA%"'
log4j.configurationFile.stripquotes: 'TRUE'
java.util.Arrays.useLegacyMergeSort: 'true'
osgi.install.area.stripquotes: 'TRUE'
log4j.configurationFile: '"C:\SoftwareAG105\profiles\SPM\configuration\logging\log4j2.properties"'
java.io.tmpdir.stripquotes: 'TRUE'
You can replace the hardcoded installation directory by referencing the nodes.install.dir parameter, which is defined in the generated template:
log4j.configurationFile:
'"${nodes.install.dir}/profiles/SPM/configuration/logging/log4j2.properties"'
If you replace all hardcoded full file paths in the exported template with parameters, you can apply the template on another machine and in a different installation directory from the source installation directory. If you do not replace the full file paths in the exported template, you must apply the template on another machine and in the same installation directory as the source installation.