Command Central syntax:Command Central syntax:With input parameters:With input properties file:Not supported on Platform Manager.Argument or Option | Description |
template_alias | Required. The alias for the template to apply. You can determine the template alias using the sagcc list templates composite command. |
environment.mode= {provision | migrate | migration} | Optional for the provisioning operation, but required when migrating an environment. Indicates the type of operation the apply command will execute. Valid values: provision - the command installs a new environmentmigrate | migration - the command migrates an existing environment |
param1=v1 param2=v2 [param3=v3...paramn=vn] | Required. The input parameters declared in the template_alias YAML file. |
{--input | -i} filename.properties | Required. A properties file that contains the input parameters declared in the template_alias YAML file |
[options] | Optional. The command allows all options supported by the Command Line Interface. For a description of the options, see Common Options. |
You can include both the param1=v1 param2=v2 [param3=v3...paramn=vn] argument and an input properties file in the same command. The values of the input parameters from the argument will override the values of the same parameters specified in the properties file.When applying a composite template on the local installation, Command Central and Platform Manager will restart and the apply composite template job does not show on the jobs list.If one of the target nodes defined in a composite template is the localhost node, Command Central does not get restarted during the composite template application on the local node.When you include the environment.mode=migrate parameter, the apply command migrates the environment, but does not create new product instances. The product instances get created by the product migration utilities as described in Upgrading Software AG Products.When applying a composite template, the main composite template apply job returns DONE status even when a sub-job in the composite template that Command Central applies fails. However, the main composite template apply job also returns customStatus=WARNING to indicate that a sub-job has failed.The composite template with alias “myTemplate” is already imported in a Command Central installation. The template provisions an environment with type “dev” and installs a Platform Manager with alias “dev2” and port “7292” in the specified installation directory:To apply a template with alias “myTemplate”, which is already imported in a Command Central installation, using the input parameters specified in the “mydevenv.properties” file:The composite template with alias “myTemplate” does not include a migration section and uses default migration settings. The template is applied on the “is1” and “is3” hosts:The “myTemplate” composite template uses default migration settings and is applied on the “is1” and “is3” hosts. The apply command migrates “myTemplate” from the “/opt/sag98” source directory to the “/opt/sag910” target installation directory:The command applies a template with alias “myTemplate”, which is already imported in a Command Central installation, using the input parameters specified in the “env.properties” file. The command waits for Command Central to become online for 120 seconds and submits the apply template request, then starts monitoring the job. If Command Central gets restarted at some point in the apply template operation, the command waits for Command Central to come online for 120 seconds. If Command Central does not come online for 120 seconds, the job fails. If Command Central does come online withing 120 seconds, the command is resubmitted. The command fails if it is not executed within 3600 seconds, or 1 hour.