Using default templates

Applying template using Command Central CLI

Use one of the templates below to provision and register a target installation node:

• New local node
• New remote Linux node
• New remote Windows node
• Existing remote node
• local node that runs Command Central itself. This is only suitable for local development, but the easiest option to get started with

Get the list of runtime templates registered on Command Central:

sagcc list templates composite
Alias                   	Description
sag-um-server           	Universal Messaging Realm server
sag-msc-server          	Microservices container instance
sag-is-server           	Integration Server core
...

Get the list of template specific parameters:

sagcc list templates composite properties <TEMPLATE_ALIAS>

For example, the parameters supported by the sag-um-server template are:

sagcc list templates composite properties sag-um-server
Name                         	Value
um.jmx.port                  	9988
um.memory.init               	64
um.memory.max                	128
um.instance.name             	default
um.realm                     	default
um.numrealmserver.license.key	*_NUMWF_10.*_*_*
um.memory.direct             	1G
um.instance.port             	9000
um.fixes                     	[wMFix.NUMRealmServer, wMFix.NUMspmBundles]

TIP: default values are used if the parameter is not specified when applying the template

Apply the template, passing nodes, repo.product and repo.fix system parameters in addition to template specific parameters:

sagcc exec templates composite apply <TEMPLATE_ALIAS> \
  nodes=<NODE_ALIAS> \
  repo.product=<PRODUCT_REPO_NAME> \
  repo.fix=<FIX_REPO_NAME> \
  ... required parameters defined in the template \
  [ optional parameters defined in the template ] \
  --sync-job --wait <SECONDS_TO_WAIT_FOR_COMPLETION>

Please see README.md in each template folder for details, For example sag-um-server

Creating a new stack using Web UI

• Open Command Central Web UI Stacks
• Add new stack by clicking (+) icon
• Add new Infrastructure layer
  • Select type of the layer
  • Choose the operating system and available bootstrap installer for it
  • Provide required additional parameters
  • Finish the wizard
  • Wait until provision jobs complete. Optionally use Jobs view to monitor
• Add new Runtime layer
  • Select type of the layer
  • Select product and fix repositories
  • Select exactly one node on which to provision the layer runtimes
  • Review and adjust optional parameters as needed
  • Finish the wizard
  • Wait until provision jobs complete. Optionally use Jobs view to monitor
• Add additional Runtime layers as needed to build the stack