In this section you specify what type of environments you want to create on the target hosts. The is-layer template defines the following types of environments:

When you define environment properties that apply for all types of environments, you include them under the environments/default section. If an environment property applies only for a particular type of environment, you include it under the respective environment section. For example, the spm.alias property applies only for the dev environment, because it is in the environments/dev section. Conversely, the environments/server section does not have any parameters and the server environment uses the environment properties defined in the environments/default section.

In general, when the is-layer template is used to install a new environment, Command Central determines which values to use for the environment properties in the following order. The composite template applies the apply composite template command arguments first, the environment properties file second, the environment.type sections of the template definition third, and the environments/default section fourth.

For example, the dev environment uses the value of spm.port from the environments/dev section, instead of the environments/default section.

Some of the properties in the environments section have a default value, which you can specify in one place and then refer to that property/value pair from other parameters defined in the template. For example:

indicates that repo.spm refers to the repo.product property, which in the sample.properties file has the default value: repo.product=webMethods-${version}_GA. The version property, included in webMethods-${version}_GA also has a default value: version=9.12. When you apply the template without command arguments, Command Central will use the default value of repo.product from the properties file to determine from which product repository to install products.

Note that if the value of a parameter is specified as follows:

you must provide a value for this parameter in the template definition, a properties file, or a command argument. Otherwise, the template fails to apply successfully.

The environments/default section groups the environment properties, based on which information for the new environment they define:

In the layers/default section, the productRepo and fixRepo refer to the repository parameters, defined in the environments/default section and identify the product and fix repositories from which to install product and fixes for all layers, defined in the section. Each layer has the following purpose and properties:

This section includes the following inline templates:

Command Central uses the map in this section to determine which layers to apply on which target nodes for each environment type. The layers are mapped to the node aliases. When creating the new environment, Command Central applies one layer on all target nodes to which the layer maps before it starts applying the next layer. For example:

In the example, when creating a dev environment, Command Central applies the spm layer on the host of the Platform Manager installation with alias "spm.alias". After applying the spm layer, Command Central applies the dbc layer on the host specified for "dbc.alias", and after the dbc layer is done, the "is" layer gets applied on the host of "spm.alias".

You also have the option to define a list of hosts on which to apply a layer as a parameter and refer to that list, for example:

In the example, when installing a layer environment, the spm and is layers are applied on the list of hosts defined for the is.hosts parameter in the properties file.

The nodes in the list are applied in parallel, based on the thread pool size. For example, if the thread pool size is set to 10 and you have 100 nodes in the list, the nodes are processed 10 at a time in parallel, in the order in which they are listed.

Command Central uses the information from this section to determine how to install Platform Manager on the remote machine. This section includes two sections:

When Platform Manager is installed and running on the remote machine, Command Central skips the bootstrapInfo section, which means that you must only configure the port, host, and secure properties in the nodes/default/default section. Note that by default, spm.secure is set to false. To enable HTTPS, set spm.secure: true.

When Platform Manager is not installed on the remote machine, Command Central uses the properties in the nodes/default/default/bootstrapInfo section to determine how to install Platform Manager. The installDir property specifies the installation directory of Platform Manager on the target machine and repoName identifies from which product repository to install Platform Manager. The platform and port properties refer to the os.platform and os.port parameters, which identify the operating system and the SSH port of the remote machine.

The distribution property specifies how to install Platform Manager. Software AG recommends that you use:

The credentials section includes details about the SSH user account on the remote machine that owns the Software AG installation directory files and can execute Command Central processes and commands. All properties under credentials refer to configuration parameters of the remote operating system, defined in the environments/defaults section. The default value of the os.auth.method parameter is the PASSWORD authentication method for the SSH connection to the remote machine. If you set os.auth.method: CERTIFICATE, you must also specify the location of the RSA private key file as the value of the os.auth.key parameter. For example: os.auth.key: ${user.home}/.ssh/id_rsa

The sample.properties file, included with the is-layer template, contains sample properties that you can configure and use to install Integration Server with an Oracle database. By default, the sample properties are defined for a local development environment. When you want to install a different type of Integration Server environment, you comment out all lines with properties for the environment.type sections that you do not want to use, and uncomment the lines of the environemnt.type section that you want to use. For example, if you want to install an Integration Server cluster, change the environment type sections as follow: