1.6 Files Typically Included in a Template

The basic files included in any template are config.xml and template-info.xml. There are additional files in the predefined templates, and a domain is created or extended based on these files. The following table describes the files typically included in a domain or extension template.

Table 1-5 Files Included in a Template

Filename	Description
product component files	Various files used to complete the domain setup for a specific Oracle product component. Such files may provide information for security and default database settings.
*-jdbc.xml	Sets up or extends a domain with JDBC system resources required by a product component. In a template, the *-jdbc.xml files must be located in the config\jdbc directory.
*-jms.xml	Sets up or extends a domain with JMS system resources required by a product component. In a template, the *-jms.xml files must be located in the config\jms directory.
clusters.script	Used to modify the Configuration Wizard framework's default auto-configuration of a cluster. By default, resources are targeted to the cluster. You can unassign a resource from the cluster and then assign it to another component. To specify a target, you can use the following replacement variables: %AManagedServer% — Any Managed Server %AllManagedServers% — Comma-separated list of all Managed Servers %AdminServer% — Administration Server name %Cluster% — Cluster name %ProxyServer% — Proxy server name %HTTPProxyApp% — http proxy application definition Note the following additional considerations: You must use the name attribute of an object that is to be replaced. You can use an asterisk (*) as a wildcard for "All." In a template, the clusters.script file must be located in the script directory.
config.xml	Sets up or extends the domain configuration. In a template, the config.xml file must be located in the config directory.
jdbc.index	Identifies the locations of SQL scripts used to set up a database. The file lists the scripts in the order in which they must be run. If the scripts are not contained in the template, but are located in the product installation directory, that directory can be represented by a tilde ( ~ ) in the pathname for the scripts, as shown in the following example: ~/integration/common/dbscripts/oracle/reporting_runtime.sql Specifically, the tilde represents the directory path identified by the $USER_INSTALL_DIR$ variable in the stringsubs.xml file. In a template, a jdbc.index file must be located in the _jdbc_\dbtype\dbversion directory, where dbtype is the type of database, such as Oracle, and dbversion is the database version, such as 9i. In addition to listing the SQL files related to a data source, the jdbc.index file contains information about the categories associated with the data source. The default dbCategories that are available are: 'Drop/Create P13N Database Objects' category associated with the p13nDataSource data source, which is a part of the p13n.jar domain template 'Drop/Create Portal Database Objects' category associated with the "p13nDataSource" data source, which is a part of the wlp.jar domain template 'Drop/Create GroupSpace Database Objects' category associated with the appsGroupSpaceDataSource data source, which is a part of the wlp_groupspacedb.jar domain template All these template jar files are located in the MW_HOME\wlserver_<version>\common\templates\applications directory.
security.xml	Used to create user groups and roles that establish identity and access to domain resources. You can create the default Admin user only through the security.xml in a domain template. However, you can create user groups and roles through the security.xml included in either a domain or an extension template.
startmenu.xml	Used to create Windows start menu entries.
startscript.xml	Used to create the *.cmd and *.sh files that are placed into a domain's root and bin directories.
stringsubs.xml	Identifies string substitution values and files that will receive string substitutions during domain creation or extension. The files that will receive string substitutions must already be prepared with replacement variables. During domain creation or extension, the Configuration Wizard framework runs macros to replace variables with the appropriate string substitution, using information from WL_HOME\common\lib\macrorules.xml, where WL_HOME is the product installation directory.
template-info.xml	Provides template identification information, such as the template name, software version, type of template (domain or application), author, description, and so on.