Layers

A layer in a composite template is a collection of instances that have the same logical role. For example, an Integration Server cluster is a layer.

The layers section of the composite template contains the definition of the layers that will be installed on a set of nodes. A composite template should include at least one layer. Each layer is identified by a unique alias name and includes an ordered list of inline templates. The inline templates are applied on all nodes that map to the layer, following the exact order of the list. The inline templates are defined in line, in the same composite template that contains the layer definition.

Note:
If the templates list is empty, Command Central does not apply any inline templates to the nodes that map to this layer.

The layers section includes an optional default subsection in which you can specify a product or fix repository from which to install the products or fixes for all layers defined in the composite template. You can also define a product or fix repository from which to install products or fixes for each layer. When a product or fix repository is defined for each individual layer, Command Central installs products and fixes from the layer specific repositories and ignores the repository details provided in the default subsection.

You can add an optional description for each layer.

The templates for each layer are listed in the templates section.

In the following example, the composite template includes two layers with alias names “layer1” and “esb”. The inline templates under “layer1” and “esb” are applied on the nodes that each layer maps to, but both layers use the product and fix repositories specified in the default section:

layers:
    default:
      productRepo:  webMethods-9.10
      fixRepo:  Empower
    layer1:
      templates:
         - myTemplate2
    esb:
      description: generic Integration Server layer
      templates:
         - is-server
         - is-config