Complete Installation and Upgrade Information for Software AG Products : Command Central : Automation and Template-based Provisioning : Using Composite Templates : Understanding the Composite Template Definition : Nodes
The nodes section defines the managed installations, also called nodes, to which the layers in the composite template are mapped.
The nodes included in this section are identified by their global node alias. You can define a list of nodes in a nodes/nodeAlias section, for each environment.type included in a composite template. All parameters that you specify for a node are optional. When you do not specify parameters for a node in a nodeAlias section:
*The node uses the properties specified in the nodes/default/default section and the node alias is also used as a host name for that node. This section specifies the properties of the default node definition.
*If the properties are not specified in the nodes/default/default section, the node uses the system default parameters.
Defining the local node in the nodes section is optional. Even when the local node is not defined in the nodes section, you can map the local node to layers in the provision section.
If Platform Manager is already bootstrapped on the target node and you use a custom password for the administrator user account, you must include the custom administrator user credentials in the nodes section of the composite template. In the following template snippet, the credentials parameter refers to the spm.credentials.alias parameter.
        port: ${spm.port}     
        secure: ${}     
        credentials: ${spm.credentials.alias}
You can specify the value of the spm.credentials.alias parameter in the environments/default section, a separate properties file, or as argument of the apply composite template command. The spm.credentials.alias parameter maps to the alias of the common credentials configuration instance you created for your custom administrator user, for example: spm.credentials.alias: SECURE_ADMINISTRATOR
where SECURE_ADMINISTRATOR is the alias of the custom COMMON-CREDENTIALS-SECURE_ADMINISTRATOR configuration instance. For information about creating common credentials configuration instances, see Configuration Types for Command Central and Platform Manager OSGI ENGINE.
In the following example, the installations with aliases “node1” and “node2” are installed only when creating an environment with type “envType1”. The two nodes are installed on the local host with unique port numbers and installation directories.
The definition for “node1” and “node2” does not specify user credentials. The two nodes use the “DEFAULT_ADMINISTRATOR” user credentials specified in the credentials parameter in the nodes/default/default section. For information about the default common credentials configuration instances, see COMMON-CREDENTIALS Usage Notes.
The nodes/default/default section does not provide a value for the HTTPS port and all nodes in the template use the system default value for the HTTPS port.
Platform Manager is installed on both nodes using the Command Central bootstrap installer specified in the cc.installer parameter in the nodes/default/default/bootstrapInfo section.
        port: 8093     
        secure: false     
        credentials: DEFAULT_ADMINISTRATOR     
          cc.installer: ${}     
          installDir: /opt/softwareag     
          platform: lnxamd64     
        port: 8192     
          installer: ${cc.installer}
installDir: /opt/softwareag/n1     
        host: localhost     
        port: 8292     
          installer: ${cc.installer}
          installDir: /opt/softwareag/n2
In the nodes/default/default section, you can add an optional section with bootstrap information that enables you to bootstrap Platform Manager to a local or remote installation.
Usage Notes
Command Central attempts to connect to the Platform Manager host and port of the node, which Command Central wants to use, with the user credentials specified for the node. If Platform Manager is running and responds, Command Central uses the node. If Platform Manager does not respond, Command Central attempts to connect to the remote host using the SSH protocol and the user credentials defined in the bootstrapInfo section. If the connection is successful Command Central bootstraps and starts Platform Manager, and waits until Platform Manager becomes responsive and available to establish an HTTP/S connection.
The remote host must have Java 8 installed and available for the SSH user. You can specify the location of Java on the remote host by adding a javaPath property in the bootstrapInfo section as follows:
javaPath: /path/to/java
You can specify the following parameters in the nodes/default/default/bootstrapInfo section:
installer: ${cc.installer} #The Command Central bootstrap installer to use
#for bootstrapping Platform Manager.
installDir: ${install.dir} #The installation directory of Platform Manager.
credentials: ${os.credentials.alias} #For remote bootstrap: The SSH credentials
#to use to connect to the remote hosts.
version: "${release}" #The release version of the Platform Manager node.
#For backward compatibity when "cc.installer"
#is not available.
In the nodes/default/default/bootstrapInfo section, the following parameters are deprecated beginning with release 10.1:
*The "repo.spm" and "platform" parameters are replaced by the "installer" parameter.
*The "username" and "password" parameters are replaced by the "credentials: ${os.credentials.alias}" parameter.
The following template snippet shows how to define a composite template that you can use to bootstrap Platform Manager to a local node. The alias of the new Platform Manager installation, “dev8192”, is specified in the “spm-alias” parameter in the environments/default subsection. The “cc.installer” parameter is the Command Central bootstrap installer to use to install Platform Manager. The “install.dir” parameter is the path to the Platform Manager target installation directory. The “cc.installer”and “install.dir”parameters are required and their values depend on your operating system. You must provide values for those parameters at the time of applying the template. The “install.dir” value should point to a directory that does not exist on the target node and for which the Command Central user account that you use to bootstrap Platform Manager has write access. The “spm.port” default value is unique and is not used by any other local process, including Command Central and Platform Manager.
The parameters in the nodes/default/default/bootstrapInfo section refer to the values for Command Central bootstrap installer and Platform Manager installation directory specified in the environments/default section. The nodes section also defines an “spm.alias” node with host “localhost”. The layers section defines a single Platform Manager “management” layer that maps to the “spm.alias” node in the provision section.
description: Bootstrapping local nodes
      cc.installer: ${}
install.dir:  ${}
      spm.port: 8192
      spm.alias: dev${spm.port}
        secure: false
          installer: ${cc.installer}
installDir: ${install.dir}
     host: localhost
description: management layer of SPM
templates: spm-tuneup

      management: ${spm.alias}
Copyright © 2007-2017 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback