Validating a Composite Template
After you run the apply composite templates command,
Command Central validates the composite template as a first processing step. You can also validate a composite template before applying the template, using
sagcc exec templates composite
validate.
The validation of the composite template either triggers a new job, or gets executed as part of the main composite template job. In both cases, when you view the job (from Jobs in the
Command Central web user interface), you can access a filtered default.log that shows only the validation report entries. If you set the log level of the com.softwareag.platform.management.client.template.composite.impl.validate logger to TRACE, the validation report also includes the full composite template with resolved reference values. For information about changing the logging level, see
Changing the Log Configuration Settings.
Command Central checks the template validity as follows:
Tests the connection to the product and fix repositories.
Verifies the content of the product and fix repositories and checks if the products and fixes defined in the template and their dependencies are available in the respective repositories.
If the template installs products with version 10.11 or higher, validates that:
The ADMINISTRATOR or custom credentials alias defined in the template for the product administrator user has a password value.
The
nodes:default:default:credentials: parameter uses the ADMINISTRATOR credentials alias or a custom credentials alias.
Tests the connection to the remote nodes and checks if:
The remote nodes are accessible over SSH.
The authentication credentials for the remode nodes are correct.
Platform Manager is already installed.
The validation of a remode node is successful when either the remote node is accessible over SSH, or Platform Manager is installed on the remote node.
Validates the installation directory. Checks if the installation directory is valid and different from the installation directory of other
Platform Managers installed on the same node.
If the DSL version of the template is 1.0, checks if the alias mapping policy defined in
nodes:default:aliasMapping:policy: is
HOSTNAME.
Validates that the node aliases are resolved successfully depending on the alias mapping policy defined in
nodes:default:aliasMapping:policy:.
Validates that the node aliases are resolved successfully depending on the alias mapping policy defined in
nodes:default:aliasMapping:policy:.
Validates the
Platform Manager node as follows:
If the template does not include a
bootstrapInfo: section for the node, checks if the node already exists in the
Command Central landscape.
If the template includes a
bootstrapInfo: section for the node, verifies that the node does not exist in the
Command Central landscape and the alias of the infrastructure layer does not contain unresolved variables.
If the mapping policy defined for the node in
nodes:default:aliasMapping:policy: is
EXISTING, verifies that the node already exists in the
Command Central landscape.
Validates that the bootstrap installer defined in the
installer: instruction is registered in
Command Central.
If an inline template contains the patches: section, checks that the DSL version of the template is 1.1 or higher.
If the template contains the options: section, checks that the DSL version of the template is set to 1.2.
If a remote action is defined in the template, checks that the SSH credentials for the remote node are also defined in the template.
Writes the validation report to the default.log.