Summary of Default Composite Templates

Template alias	Environment Types	Required Parameters	Description
bpms	dev server cluster	database connection host names database server administrator user credentials license key aliases for Universal Messaging, Terracotta Server Array, Integration Server, Rules Engine	Provisions a typical BPMS environment, configured with the following layers: messaging (Universal Messaging) cache (Terracotta Server Array) bpm (Integration Server/Process Engine/Rules Engine/Monitor) presentation (My webMethods Server/Task Engine/Rules Engine/Monitor Use this template to set up a general purpose BPMS environment. The template requires connection to an external relational database. The database user and schema are created automatically.
dbc	default dev	database connection database server administrator user credentials database components database products	Installs the Database Component Configurator (DBC) on a local or remote installation and uses DBC to create a new database on a supported database server. You must specify the database administrator user credentials to be able to create the new database storage and user. Before using the template, read the readme file located in the dbc template directory.
generic-layer	dev layer	product and fix repository names host names external snapshot templates to apply	DEPRECATED. No replacement. Provisions a generic layer based on external snapshot templates, using the default options defined for each snapshot template in its template.xml file. Use this template to apply a list of snapshot templates to a number of Platform Manager nodes.
is-layer	dev server layer cluster	database connection host names Terracotta Server Array URL database server administrator user credentials license key alias for Integration Server license key alias forTerracotta	Provisions a standalone local or remote Integration Server, or an Integration Server cluster with multiple hosts. Use this template to setup an integration layer based on Integration Server. When provisioning an Integration Server cluster, you must provide an external relational database and an external Terracotta layer. Before using the template, read the readme file located in the is-layer template directory.
mws-layer	dev server cluster	database connection host names database server administrator user credentials	Provisions a standalone local or remote My webMethods Server, or a My webMethods Server cluster with multiple hosts. With this template, you can setup a presentation layer using My webMethods Server. When provisioning a My webMethods Server cluster, you must provide an external relational database.
reference	n/a	n/a	Contains Domain-specific Language (DSL) documentation and reference details. Use this template to understand the syntax and structure of the composite template definition and to refer to examples.
repos	default	Empower user name and password	Contains the public master product and fix repositories of release 9.8 and higher, except the repositories of the latest release. These repositories are required when bootstrapping installations or executing template-provisioning operations. Apply this template first on the master Command Central installation that has Internet access to the Empower Product Support Website.
spm-layer	default dev server layer	SSH connection host names	Bootstraps a single local or remote Platform Manager, or a number of remote Platform Managers on UNIX hosts via an SSH connection. Use this template to setup a base management layer on which to install core products, using composite templates.
tc-layer	dev server cluster	host names license key alias for Terracotta Server	Provisions a standalone local or remote Terracotta Server or a two-server master/slave cluster on remote machines.
um-layer	dev server cluster	host names license key alias for Universal Messaging	Provisions a standalone Universal Messaging realm instance or a two-instance cluster on local or remote machines. Use this template to set up a messaging layer using Universal Messaging.