Software AG Command Central 10.0 | Automation and Template-based Provisioning | Using Composite Templates | Using the is-layer Default Template | Applying the is-layer Default Template
 
Applying the is-layer Default Template
To apply the is-layer template, using only the parameter values defined in the template definition or an external properties file, run the apply composite templates command with the input file option, for example:
sagcc exec templates composite apply is-layer -i env.properties
where env.properties is your custom properties file.
You can also provision just one or more of the environments defined in the template by adding command arguments, or using as many different .properties files as your target environments.
Examples
*To install a dev environment in the new installation directory "C:\sag912\mydevenv", located on the local machine, add the environment.type=dev argument:
sagcc exec templates composite apply is-layer environment.type=dev
repo.product=webMethods-9.12 repo.fix=Empower
is.license.key.alias=Integration_Server912 tc.license.key.alias=Terracotta
install.dir=C:\sag912\mydevenv
Command Central uses the product and fix repositories, and the Integration Server license key specified in the command arguments.
*To install an environment with a single Integration Server that uses an Oracle database on the "rubicon2" target node, add the environment.type=server and is.host=rubicon2 arguments:
sagcc exec templates composite apply is-layer -i sample.properties
environment.type=server is.host=rubicon2
Command Central uses the connection details of the Oracle database from the sample.properties file.
*To install an environment with several instances of Integration Server, which are not configured in a cluster, on two Linux target nodes, add the environment.type=layer and is.hosts=[rubicon1,rubicon2] arguments:
sagcc exec templates composite apply is-layer -i sample.properties
environment.type=layer is.hosts=[rubicon1,rubicon2] os.platform=lnxamd64
*To install an environment with a cluster of Integration Server instances that uses a Terracotta Server, add the environment.type=cluster and is.hosts=[rubicon1,rubicon2] arguments:
sagcc exec templates composite apply is-layer -i sample.properties
environment.type=cluster is.hosts=[rubicon1,rubicon2] os.platform=lnxamd64
is.tsa.url=rubicon3:9910 tc.license.key.alias=Terracotta
In the example, theis.tsa.url argument specifies the URL that Integration Server must use to connect to the Terracotta Server and the tc.license.key.alias specifies the license key to use for the Terracotta Server.
If applying the template fails, see Correcting a Failed Composite Template Apply Operation.

Copyright © 2013-2017 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release