Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Template Reference

The section includes the following topics:

- Defining Configuration and Extension Templates
- Configuration Template Reference
- Extension Template Reference
- Relationships Between Templates

# Defining Configuration and Extension Templates

A template is a Java Archive (JAR) file that contains the files and scripts required to create or update a domain. The Configuration Wizard uses two types of template:

- Configuration template—defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options. This type of template is used to create a domain. BEA delivers a set of predefined configuration templates, which are described in the following sections.
- Extension template—defines applications and services, such as JDBC or JMS components, and startup/shutdown classes, that can be used to extend an existing domain. BEA delivers a set of predefined extension templates, which are described in the following sections.

# Configuration Template Reference

WebLogic Platform provides predefined configuration templates that are installed with the product. You can easily create a WebLogic domain by running the Configuration Wizard in either Express mode or Custom mode, using one of the predefined configuration templates as your selection.

Note: Since the initial product release, there have been changes made to the Basic WebLogic Integration Domain, Basic WebLogic Platform Domain, and Basic WebLogic Portal Domain configuration templates. Because of these changes, when creating a domain using the Configuration Wizard, you should use a configuration template provided with your current installation or a custom template created from a domain or template in your current installation. You must upgrade the domains created using the configuration templates provided with an earlier service pack to the current service pack. For information about upgrading your domains, see the BEA WebLogic Platform Upgrade Planning Guide at http://e-docs.bea.com/platform/docs81/upgrade/index.html.

## Location of Configuration Templates

By default, all the predefined configuration templates provided with your WebLogic Platform installation are located in the following directory:

`WL_HOME``\common\templates\domains`

## Configuration Template Summary

The configuration templates are summarized in the following table.

Note: The availability of predefined configuration templates depends on which WebLogic Platform components are installed; the WebLogic Platform components required for each template are identified in the following table.

Table 16-1 Configuration Template Summary

Template | Required WebLogic Platform Component | Filename | Description
--- | --- | --- | ---
Avitek Medical Records Sample Domain | WebLogic Server | `medrec.jar` | Creates the Avitek Medical Records domain outside the installed kit. This domain is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform.
Basic WebLogic Integration Domain | WebLogic Integration, WebLogic Workshop, WebLogic Server | `wli.jar` | Creates a domain that supports the development of WebLogic Integration solutions. Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension Template.
Basic WebLogic Platform Domain | WebLogic Platform (all components must be installed) | `platform.jar` | Creates a domain that supports the development of applications using all WebLogic Platform components.
Basic WebLogic Portal Domain | WebLogic Portal, WebLogic Workshop, WebLogic Server | `wlp.jar` | Creates a domain that supports the development of WebLogic Portal solutions.
Basic WebLogic Server Domain | WebLogic Server | `wls.jar` | Creates a simple WebLogic Server domain without any sample applications.
Basic WebLogic Workshop Domain | WebLogic Workshop, WebLogic Server | `wlw.jar` | Creates a domain that supports the development of WebLogic Workshop solutions.
WebLogic Server Examples Domain | WebLogic Server | `examples.jar` | Creates the WebLogic Server Examples domain outside the installed kit. This domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs.

The following sections describe the default directory structure and files created by each configuration template.

## Avitek Medical Records Sample Domain

Avitek Medical Records is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform. The Avitek Medical Records Sample Domain configuration template allows you to create an Avitek Medical Records domain outside the installed kit. This configuration template is available when you install WebLogic Server.

By default, the following applications and resources are defined in an Avitek Medical Records Sample Domain:

- Avitek Medical Records example application
- Administration Server
- JDBC connection pools and data source
- JMS server, connection factory, queues, and data store
- Multiple users with group and role assignments
- Entry for the Windows Start menu
- Startup and shutdown classes

The following table defines the default directory structure and files generated by the Avitek Medical Records Sample Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME\``user_projects\domains\medrec` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-2 Default Directory Structure for Avitek Medical Records Sample Domain

Directory or File | Description
--- | ---
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`applications\` | Directory containing files for any custom applications that you create.
`incoming\` | Directory containing XML file to be used as input to the Avitek Medical Records example.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`DefaultAuthenticatorInit.ldift`, `DefaultAuthorizerInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`log4j.properties` | File containing properties used by Log4j.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`setMedRecEnv.cmd`, `setMedRecEnv.sh` | Scripts that set up the Avitek Medical Records development environment on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startMedRecServer.cmd`, `startMedRecServer.sh` | Scripts used to start the MedRec Administration Server on Windows and UNIX systems, respectively.
`startMedRecServerQS.cmd`, `startMedRecServerQS.sh` | Scripts used internally for the domain. These files can be ignored.
`uninstallService.cmd` | Script used to uninstall Windows services.

For more information about the Avitek Medical Records example, see WebLogic Server Application Examples and Tutorials at the following URL:

http://e-docs.bea.com/wls/docs81/samples.html

## Basic WebLogic Integration Domain

The Basic WebLogic Integration Domain configuration template allows you to create a basic WebLogic Integration domain, without installing sample applications. Domains created from this template support the WebLogic Server, WebLogic Workshop, and WebLogic Integration run-time functionality, including support for J2EE applications, Web applications, Web Services, custom controls, and business processes. You use domains created from this configuration template as the foundations for development of WebLogic Integration applications. The Basic WebLogic Integration Domain configuration template is available when you install WebLogic Integration or when you install all the components of WebLogic Platform.

By default, when using the Basic WebLogic Integration Domain configuration template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension Template.

The following table defines the default directory structure and files generated by the Basic WebLogic Integration Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\integration` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-3 Default Directory Structure for Basic WebLogic Integration Domain

Directory or File | Description
--- | ---
`BEA_HOME``\user_projects\ applications\integration\` | Directory containing the files for the B2BDefaultWebApp application and any custom application files that you create.
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`logs\` | Directory serving as a placeholder for log files.
`rmfilestore\` | Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers.
`script\` | Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster.
`wlai\` | Directory serving as a placeholder for information used by the Application View control.
`wliconfig\` | Directory containing the file used in support of application integration debugging.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`DefaultAuthenticatorInit.ldift`, `DefaultAuthorizerInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
`domain-info.xml` | File containing administrative information about the domain, including version, type, name, author, description, and icon name.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`installService.cmd` | Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: Administration Server (started each time the system is booted) PointBase (if there are PointBase connection pools in the domain) Debugger—if the script is modified to remove the `nodebug` parameter from the following command line: `%USERDOMAIN_HOME%\setDomainEnv.cmd production nodebug`
`jws-config.properties` | File containing WebLogic Workshop-related JMS information.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`setDomainEnv.cmd`, `setDomainEnv.sh` | Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Integration domain, on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startPointBaseConsole.cmd`, `startPointBaseConsole.sh` | Scripts used to start the PointBase Console on Windows and UNIX systems, respectively.
`startWebLogic.cmd`, `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`stopManagedWebLogic.cmd`, `stopManagedWebLogic.sh` | Scripts used to stop a specified Managed Server on Windows and UNIX systems, respectively.
`stopWebLogic.cmd`, `stopWebLogic.sh` | Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall Windows services.
`URLs.dat` | File containing the URL for the JDBC database.
`webapp_build.xml` | File containing the project information used to build a Web application.
`webappCompile.cmd`, `webappCompile.sh` | Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively.
`wli-config.properties` | File containing domain-specific parameters that are used by WebLogic Integration.
`workshop$1.wal` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.dbn` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.properties` | File containing domain-specific parameters that are used by WebLogic Workshop.

## Basic WebLogic Platform Domain

The Basic WebLogic Platform Domain configuration template allows you to create a domain that supports the development of applications using all WebLogic Platform components. This template is available when you install WebLogic Platform.

The following table defines the default directory structure and files generated by the Basic WebLogic Platform Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\platform` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-4 Default Directory Structure for Basic WebLogic Platform Domain

Directory or File | Description
--- | ---
`BEA_HOME``\user_projects\ applications\platform\` | Directory containing the files for the B2BDefaultWebApp application and any custom application files that you create.
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`logs\` | Directory serving as a placeholder for log files.
`rmfilestore\` | Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers.
`script\` | Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster.
`wlai\` | Directory containing information used by the Application View control.
`wliconfig\` | Directory containing the file used in support of application integration debugging.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`create_db.cmd` `create_db.sh` | Scripts used to create database objects on Windows and UNIX systems, respectively. By default, `create_db` creates database objects for PointBase.The scripts are maintained independently from the Configuration Wizard and the Configuration Wizard's Load Database functionality. The scripts provide an alternative method of creating and refreshing WebLogic Portal database objects.
`db_settings.properties` | File containing two types of data used by `create_db`: (a) database properties, including driver, database, user name, and password, and (b) connection properties, and information needed for calling data files for the component-level tables. The file controls which SQL files to process from `WL_HOME``\portal\db`, and is maintained independently from the Configuration Wizard.
`DefaultAuthenticatorInit.ldift`, `DefaultAuthorizerInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
`domain-info.xml` | File containing administrative information about the domain, including version, type, name, author, description, and icon name.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`installService.cmd` | Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: Administration Server (started each time the system is booted) PointBase (if there are PointBase connection pools in the domain) Debugger—if the script is modified to remove the `nodebug` parameter from the following command line: `%USERDOMAIN_HOME%\setDomainEnv.cmd production nodebug`
`jws-config.properties` | File containing WebLogic Workshop-related JMS information.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`set-dbenv.cmd`, `set-dbenv.sh` | Scripts used by `create_db.cmd` and `create_db.sh` to set up the database environment on Windows and UNIX systems, respectively. The Configuration Wizard does not use or maintain these files.
`setDomainEnv.cmd`, `setDomainEnv.sh` | Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Platform domain, on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startPointBaseConsole.cmd`, `startPointBaseConsole.sh` | Script used to start the console for the PointBase database.
`startWebLogic.cmd`, `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`stopManagedWebLogic.cmd`, `stopManagedWebLogic.`sh | Script used to stop a specified Managed Server on Windows and UNIX systems, respectively.
`stopWebLogic.cmd`, `stopWebLogic.sh` | Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall Windows services.
`URLs.dat` | File containing the URL for the JDBC database.
`webapp_build.xml` | File containing the project information used to build a Web application.
`webappCompile.cmd`, `webappCompile.sh` | Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively.
`wli-config.properties` | File containing domain-specific parameters that are used by WebLogic Integration.
`workshop$1.wal` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.dbn` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.properties` | File containing domain-specific parameters that are used by WebLogic Workshop.
`wsrpKeystore.jks` | Java keystore file.

## Basic WebLogic Portal Domain

The Basic WebLogic Portal Domain configuration template allows you to create a basic WebLogic Portal domain, without installing sample applications. Domains created from this template support the WebLogic Server, WebLogic Workshop, and WebLogic Portal run-time functionality, including support for J2EE applications, Web applications, Web Services, custom controls, and portals. You use domains created from this configuration template as the foundations for development of WebLogic Portal applications. The Basic WebLogic Portal Domain configuration template is available when you install WebLogic Portal or when you install all components of WebLogic Platform.

By default, when using the Basic WebLogic Portal Domain configuration template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

The following table defines the default directory structure and files generated by the Basic WebLogic Portal Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\portalDomain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-5 Default Directory Structure for Basic WebLogic Portal Domain

Directory or File | Description
--- | ---
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`rmfilestore\` | Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers.
`script\` | Directory containing a script that targets specified services and applications to the appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`create_db.cmd`, `create_db.sh` | Scripts used to create database objects on Windows and UNIX systems, respectively. By default, `create_db` creates database objects for PointBase.The scripts are independent of the Configuration Wizard and the Configuration Wizard's Load Database functionality. The scripts provide an alternative method of creating and refreshing WebLogic Portal database objects.
`db_settings.properties` | File containing two types of data used by `create_db`: (a) database properties, including driver, database, user name, and password, and (b) connection properties, and information needed for calling the data files for the component-level tables. The file controls which SQL files to process from `WL_HOME``\portal\db`, and is maintained independently from the Configuration Wizard.
`DefaultAuthenticatorInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping including authentication (user and group) and role mapping. These files contain LDAP-specific information.
`domain-info.xml` | File containing administrative information about the domain, including version, type, name, author, description, and icon name.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`installService.cmd` | Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: Administration Server (started each time the system is booted) PointBase (if there are PointBase connection pools in the domain) Debugger—if the script is modified to remove the `nodebug` parameter from the following command line: `%USERDOMAIN_HOME%\setDomainEnv.cmd production nodebug`
`jws-config.properties` | File containing WebLogic Workshop-related JMS information.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`set-dbenv.cmd`, `set-dbenv.sh` | Scripts used by `create_db.cmd` and `create_db.sh` to set up the database environment on Windows and UNIX systems, respectively. The Configuration Wizard does not use or maintain these files.
`setDomainEnv.cmd`, `setDomainEnv.sh` | Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Portal domain, on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startPointBaseConsole.cmd`, `startPointBaseConsole.sh` | Scripts used to start the PointBase Console on Windows and UNIX systems, respectively.
`startWebLogic.cmd`, `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`stopManagedWebLogic.cmd`, `stopManagedWebLogic.sh` | Script used to stop a specified Managed Server on Windows and UNIX systems, respectively.
`stopWebLogic.cmd`, `stopWebLogic.sh` | Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall Windows services.
`URLs.dat` | File containing the URL for the JDBC database.
`webappCompile.cmd`, `webappCompile.sh` | Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively.
`workshop$1.wal` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.dbn` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.properties` | File containing domain-specific parameters that are used by WebLogic Workshop.
`wsrpKeystore.jks` | Java keystore file.

## Basic WebLogic Server Domain

The Basic WebLogic Server Domain configuration template allows you to create a simple WebLogic Server domain without installing any sample applications. This template is available when you install WebLogic Server.

By default, when using the Basic WebLogic Server Domain configuration template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

The following table defines the default directory structure and files generated by the Basic WebLogic Server Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\mydomain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-6 Default Directory Structure for Basic WebLogic Server Domain

Directory or File | Description
--- | ---
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`applications\` | Directory serving as a placeholder for any custom application files that you create.
`rmfilestore\` | Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`DefaultAuthenticatorInit.ldift`, `DefaultAuthorizerInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`installService.cmd` | Script used to install the Administration Server as a Windows service. The script creates an entry for the service in the Windows Registry. As a result, the Windows system starts the service each time the system boots.
`SerializedSystemIni.dat` | File containing encrypted security information.
`setEnv.cmd`, `setEnv.sh` | Scripts that set up the development environment on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startWebLogic.cmd`, `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`stopWebLogic.cmd`, `stopWebLogic.sh` | Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall the Administration Server as a Windows service.

## Basic WebLogic Workshop Domain

The Basic WebLogic Workshop Domain configuration template allows you to create a basic WebLogic Workshop domain, without installing sample applications. Domains created from this template support the WebLogic Server and WebLogic Workshop run-time functionality, including support for J2EE applications, Web applications, Web Services, and custom controls. Use domains created from this template as the foundations for development of WebLogic Workshop applications. This template is available when you install WebLogic Server, WebLogic Integration, WebLogic Portal, and WebLogic Platform.

By default, when using the Basic WebLogic Workshop Domain configuration template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.

By default, the following applications and resources are defined in a Basic WebLogic Workshop Domain:

- Administration Server
- JDBC connection pool and data source
- JMS servers, connection factory, queues, and data stores
- Administrative user
- Entry for the Windows Start menu
- Startup and shutdown classes

The following table defines the default directory structure and files generated by the Basic WebLogic Workshop Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\workshop` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-7 Default Directory Structure for Basic WebLogic Workshop Domain

Directory or File | Description
--- | ---
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`logs\` | Directory serving as a placeholder for log files.
`rmfilestore\` | Directory serving as a disk-based JMS file store to store persistent messages and durable subscribers.
`script\` | Directory containing a script that targets specified services and applications to their appropriate servers or clusters. This script supplements the Configuration Wizard's auto-targeting of services and applications to a cluster.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`DefaultAuthenticatorInit.ldift`, `DefaultRoleMapperInit.ldift` | Files used for bootstrapping including authentication (user and group) and role mapping. These files contain LDAP-specific information.
`domain-info.xml` | File containing administrative information about the domain, including version, type, name, author, description, and icon name.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`installService.cmd` | Script used to install Windows services. The script creates an entry for such services in the Windows Registry. As a result, the Windows system starts the specified service each time the system boots. This script can install the following services: Administration Server (started each time the system is booted) PointBase (if there are PointBase connection pools in the domain) Debugger—if the script is modified to remove the `nodebug` parameter from the following command line: `%USERDOMAIN_HOME%\setDomainEnv.cmd production nodebug`
`jws-config.properties` | File containing WebLogic Workshop-related JMS information.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`setDomainEnv.cmd`, `setDomainEnv.sh` | Scripts used to set up all the environment variables and Java options required to run WebLogic Server, in the WebLogic Workshop domain, on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`startPointBaseConsole.cmd`, `startPointBaseConsole.sh` | Scripts used to start the PointBase Console on Windows and UNIX systems, respectively.
`startWebLogic.cmd`, `startWebLogic.sh` | Script used to start the Administration Server on Windows and UNIX systems, respectively.
`stopManagedWebLogic.cmd`, `stopManagedWebLogic`.sh | Script used to stop a specified Managed Server on Windows and UNIX systems, respectively.
`stopWebLogic.cmd` `stopWebLogic.sh` | Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall Windows services.
`URLs.dat` | File containing the URL for the JDBC database.
`webapp_build.xml` | File containing the project information used to build a Web application.
`webappCompile.cmd`, `webappCompile.sh` | Scripts used to compile a Web application into an EAR file on Windows and UNIX systems, respectively.
`workshop$1.wal` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.dbn` | File containing domain-specific PointBase database information for the default database named `workshop`.
`workshop.properties` | File containing domain-specific parameters that are used by WebLogic Workshop.

For more information about WebLogic Workshop, see the following URL:

http://e-docs.bea.com/workshop/docs81/index.html

## WebLogic Server Examples Domain

The WebLogic Server Examples Domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs, and a set of scripts to run those examples. The WebLogic Server Examples Domain configuration template allows you to create the WebLogic Server Examples domain outside the installed kit. This template is available when you install WebLogic Server.

By default, the following applications and resources are defined in a WebLogic Server Examples Domain:

- Two simple Web applications:

- The Main Web Application is the default Web application; it simply forwards requests to the Examples Web Application
- The Examples Web Application contains code samples for programming with various J2EE APIs

- Administration Server
- JDBC connection pools and data sources
- JMS server, connection factories, queues, topics, and data store
- Administrative user with group and role assignments
- Entry for the Windows Start menu
- Startup and shutdown classes

After creating a domain with the template, you can start the server. When the server is started, the PointBase database server is also started.

The following table defines the default directory structure and files generated by the WebLogic Server Examples Domain configuration template. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\examples` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 16-8 Default Directory Structure for WebLogic Server Examples Domain

Directory or File | Description
--- | ---
`_cfgwiz_donotdelete\` | Directory containing files used by the Configuration Wizard in support of creating and extending the domain.
`applications\` | Directory serving as a placeholder for any custom application files that you create.
`examplesWebApp\` | Directory containing the files for an example Web application.
`mainWebApp\` | Directory containing the files for an example Web application.
`boot.properties` | File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode. This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Providing Usernames and Passwords to Start and Stop a Server" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ ConsoleHelp/startstop.html# Providing_Usernames_and_Passwords_to_Start_a_Server
`config.xml` | File containing the configuration information used by the Administration Server. For more information, see the WebLogic Server Configuration Reference at the following URL: http://e-docs.bea.com/wls/docs81/config_xml/index.html
`DefaultAuthenticatorInit.ldift`, `DefaultAuthorizerInit.ldift`, `DefaultCredentialMapper.ldift` `DefaultRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, credential mapping, and role mapping. These files contain LDAP-specific information.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`SerializedSystemIni.dat` | File containing encrypted security information.
`setExamplesEnv.cmd`, `setExamplesEnv.sh` | Scripts that set up the WebLogic Server Examples development environment on Windows and UNIX systems, respectively.
`startExamplesServer.cmd`, `startExamplesServer.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`startManagedWebLogic.cmd`, `startManagedWebLogic.sh` | Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
`uninstallService.cmd` | Script used to uninstall Windows services.

For more information about the samples that are supported in the WebLogic Server Examples domain, see WebLogic Server Application Examples and Tutorial at the following URL:

http://e-docs.bea.com/wls/docs81/samples.html

# Extension Template Reference

WebLogic Platform provides predefined extension templates that are installed with the product. You can easily extend an existing WebLogic domain by using the Configuration Wizard's Extend an existing WebLogic configuration option and selecting one or more of the predefined extension templates. For information about template dependencies, see Relationships Between Templates

## Location of Extension Templates

By default, all the predefined extension templates provided with your WebLogic Platform installation are located in the following directory:

`WL_HOME``\common\templates\applications`

## Extension Template Summary

The extension templates are summarized in the following table.

Note: The availability of predefined extension templates depends on which WebLogic Platform components are installed; the WebLogic Platform components required for each template are shown in the table.

Table 16-9 Extension Template Summary

Template | Required WebLogic Platform Component | Filename | Description
--- | --- | --- | ---
DefaultWebApp | Any Platform component | `DefaultWebApp.jar` | Imports the static resources for a basic Web application, including an HTML file, image files, and required XML descriptors. Use the Default Web Application as a launching point from which to develop your own Web applications.
WebLogic Integration Extension | WebLogic Integration WebLogic Workshop WebLogic Server | `wli.jar` | Imports the resources needed to support the development of WebLogic Integration applications. Support for WebLogic Integration application development is already provided in the following configuration templates: Basic WebLogic Integration Domain Basic WebLogic Platform Domain Note: To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension template.
WebLogic Portal Extension | WebLogic Portal WebLogic Workshop WebLogic Server | `wlp.jar` | Imports the resources needed to support the development of WebLogic Portal applications. Support for WebLogic Portal application development is already provided in the following configuration templates: Basic WebLogic Portal Domain Basic WebLogic Platform Domain
WebLogic Workshop Extension | WebLogic Workshop WebLogic Server | `wlw.jar` | Imports the resources needed to support the development of WebLogic Workshop applications. Support for WebLogic Workshop application development is already provided in the following configuration templates: Basic WebLogic Workshop Domain Basic WebLogic Integration Domain Basic WebLogic Portal Domain Basic WebLogic Platform Domain

## Relationships Between Templates

This section provides the following topics:

- Relationships between domains created with predefined configuration templates and domains extended with extension templates
- WebLogic Workshop resources as prerequisites for extension templates

### Relationships Between Templates

You can create a basic WebLogic domain using the predefined configuration templates or you can create a basic WebLogic domain and extend it incrementally using the extension templates. The following table shows the relationship between the templates and the domains created.

Table 16-10 Relationships Between Templates

A domain created using this configuration template . . . | Is equivalent to a domain created using . . .
--- | ---
Basic WebLogic Workshop Domain | Basic WebLogic Server Domain configuration template + WebLogic Workshop extension template
Basic WebLogic Integration Domain | Basic WebLogic Server Domain configuration template + WebLogic Workshop extension template + WebLogic Integration extension template Basic WebLogic Workshop Domain configuration template + WebLogic Integration extension template
Basic WebLogic Portal Domain | Basic WebLogic Server Domain configuration template + WebLogic Workshop extension template + WebLogic Portal extension template Basic WebLogic Workshop Domain configuration template + WebLogic Portal extension template
Basic WebLogic Platform Domain | Basic WebLogic Server Domain configuration template + WebLogic Workshop extension template + WebLogic Integration extension template + WebLogic Portal extension template Basic WebLogic Server Domain configuration template + WebLogic Workshop extension template + WebLogic Portal extension template + WebLogic Integration extension template Basic WebLogic Workshop Domain configuration template + WebLogic Integration extension template + WebLogic Portal extension template Basic WebLogic Workshop Domain configuration template + WebLogic Portal extension template + WebLogic Integration extension template Basic WebLogic Integration Domain configuration template + WebLogic Portal extension template Basic WebLogic Portal Domain configuration template + WebLogic Integration extension template

### WebLogic Workshop Resources as a Prerequisite

WebLogic Workshop resources must already be set up in your domain before you can start importing resources from the WebLogic Integration or WebLogic Portal extension template. When you select an extension template, the Configuration Wizard checks to make sure the required resources are available for you. If desired, the Configuration Wizard allows you to import the WebLogic Workshop, WebLogic Integration, and WebLogic Portal extensions simultaneously. (Note that there are no prerequisites for using the DefaultWebApp extension template.)

## Default WebApp Extension Template

You can extend your domain to support a basic Web application quickly and easily by using the Configuration Wizard to import resources from the Default WebApp extension template. For more information about developing Web applications, see Developing Web Applications for WebLogic Server at the following URL:

http://e-docs.bea.com/wls/docs81/webapp/index.html

The following table shows the application resources and services, provided by the Default WebApp extension template, that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.

Table 16-11 Default WebApp Extension Template Resources and Services

Resource Type | Name | Extension Result
--- | --- | ---
JMS Services | FileStore | No change to the JMS JDBC Store provided by WebLogic Server
wsStoreForwardInternalJMSServer<myserver> | No change to the JMS Server provided by WebLogic Server
Application Deployments | DefaultWebApp | Adds the DefaultWebApp Web application

## WebLogic Integration Extension Template

To extend your domain to support WebLogic Integration, use the Configuration Wizard to import resources and services from the WebLogic Integration extension template.

Note: WebLogic Workshop resources must already be set up in your domain before you can start importing the WebLogic Integration extension template, unless you import the WebLogic Workshop and WebLogic Integration extensions at the same time.

To create a domain that supports the development of WebLogic Server Process Edition solutions, use the Basic WebLogic Integration Domain template. If you have an existing WebLogic Server-based domain, you can extend it to include the resources required for WebLogic Server Process Edition by using the WebLogic Integration Extension template.

The following table shows the application resources and services provided by the WebLogic Integration extension template that can be imported into an existing domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.

Table 16-12 WebLogic Integration Extension Template Resources and Services

Resource Type | Name | Extension Result
--- | --- | ---
Startup Classes | WLI Startup Class | Adds the startup class
WLI Post-Activation Startup Class | Adds the startup class
Shutdown Classes | WLI Shutdown Class | Adds the shutdown class
JDBC Services | bpmArchPool | Adds the JDBC connection pool
cgPool | Uses the JDBC connection pool provided by WebLogic Workshop to accommodate the additional data sources
bpmArchDataSource | Adds the JDBC Tx Data Source that uses the bpmArchPool JDBC connection pool
cgDataSource | Uses the JDBC Tx Data Source provided by WebLogic Workshop
JMS Services | cgQueue | Uses the JMS connection factory provided by WebLogic Workshop
WLI-B2B System Topic Factory | Adds the JMS connection factory
cgJMSStore | Uses the JMS JDBC Store provided by WebLogic Workshop
FileStore | No change to the JMS JDBC Store provided by WebLogic Server
cgJMSServer | Uses the JMS Server provided by WebLogic Workshop
wsStoreForwardInternalJMSServer<myserver> | No change to the JMS Server provided by WebLogic Server
cgJWSQueue | Uses the JMS queue provided by WebLogic Workshop
Application Deployments | JWSQueueTransport | Uses the QueueTransportEJB EJB module provided by WebLogic Workshop
WLI-AI Design-time | Adds the WLI-AI Manager EJBs EJB module Adds the wlai Web application
WLI System EJBs | Adds the following EJBs: WLI Admin WLI Admin Helper WLI Process Tracking WLI Calendar Persistence WLI Worklist Persistence WLI Worklist Selection WLI Process Proxy Dispatcher WLI AI Message Processors WLI AI RAR Upload WLI RosettaNet WLI ebXML WLI Message Tracking Adds the WLI-B2B HTTP Transport Web Application
WLI Console | Adds the WLI Console Web application
WLI Worklist | Adds the following EJBs: `.workshop/worklist/EJB/ProjectBeans` `.workshop/worklist/EJB/GenericState less` EJBs Adds the Worklist Web application
B2BDefaultWebAppApplication | Adds the B2BDefaultWebApp Web application module
BEA_WLS_DBMS_ADK | Adds the BEA_WLS_DBMS_ADK_Web Web application Adds the BEA_WLS_DBMS_ADK and BEA_WLS_DBMS_ADK_LOCALTX connector modules

## WebLogic Portal Extension Template

To extend your domain to support WebLogic Portal, use the Configuration Wizard to import resources and services from the WebLogic Portal extension template.

Note: WebLogic Workshop resources must already be set up in your domain before you can start importing the WebLogic Portal extension template, unless you import the WebLogic Workshop and WebLogic Portal extensions at the same time.

The following table shows the application resources and services provided by the WebLogic Portal extension template that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.

Table 16-13 WebLogic Portal Extension Template Resources and Services

Resource Type | Name | Extension Result
--- | --- | ---
JDBC Services | cgPool | Uses the JDBC connection pool provided by WebLogic Workshop to accommodate the additional data sources
cgDataSource | Uses the JDBC Tx Data Source provided by WebLogic Workshop
commercePool | Adds the JDBC Tx Data Source
contentDataSource | Adds the JDBC Tx Data Source
ebusinessPool | Adds the JDBC Tx Data Source
portalFrameworkPool | Adds the JDBC Tx Data Source
p13n_trackingDataSource | Adds the JDBC data source
p13n_sequencerDataSource | Adds the JDBC data source
p13n_dataSyncDataSource | Adds the JDBC data source
JMS Services | cgQueue | Uses the JMS Connection Factory provided by WebLogic Workshop
cgJMSServer | Uses the JMS Server provided by WebLogic Workshop
FileStore | No change to the JMS JDBC Store provided by WebLogic Server
cgJMSStore | Uses the JMS JDBC Store provided by WebLogic Workshop
wsStoreForwardInternalJMSServer<myserver> | No change to the JMS Server provided by WebLogic Server
cgJWSQueue | Uses the JMS queue provided by WebLogic Workshop
Application Deployments | JWSQueueTransport | Uses the QueueTransportEJB EJB module provided by WebLogic Workshop
paymentWSApp | Adds the payment EJB and the payws Web service
taxWSApp | Adds the tax EJB and taxws Web service

## WebLogic Workshop Extension Template

To extend your domain to support WebLogic Workshop, use the Configuration Wizard to import resources and services from the WebLogic Workshop extension template. WebLogic Workshop resources are required before you can extend a domain to support WebLogic Integration, WebLogic Portal, or both (that is, a full Platform domain).

The following table shows the application resources and services provided by the WebLogic Workshop extension template that can be imported into an existing WebLogic domain. The information is based on the assumption that the existing WebLogic domain was created using the Basic WebLogic Server Domain template.

Table 16-14 WebLogic Workshop Extension Template Resources and Services

Resource Type | Name | Extension Result
--- | --- | ---
JDBC Services | cgPool | Adds the JDBC connection pool
cgDataSource | Adds the JDBC Tx Data Source
JMS Services | cgQueue | Adds the JMS connection factory
cgJMSStore | Adds the JMS JDBC Store
FileStore | No change to the JMS JDBC Store provided by WebLogic Server
cgJMSServer | Adds the JMS Server
wsStoreForwardInternalJMSServer<myserver> | No change to the JMS Server provided by WebLogic Server
cgJWSQueue | Adds the JMS queue
Application Deployments | JWSQueueTransport | Adds the QueueTransportEJB EJB Module