Skip navigation.
Downloads | Product Documentation | Support

Domain Template Reference

# Domain Template Reference

This document provides general information about templates in the following topics:

- Types of Templates
- Location of Installed Templates
- Template Tools
- Template Summary
- Relationships Between Templates
- Files Typically Included in a Template

This document also provides detailed reference information for each template:

- Basic WebLogic Server Domain Template
- AquaLogic Service Bus Extension Template
- Avitek Medical Records Sample Domain Template
- WebLogic Beehive Extension Template
- WebLogic Conversational Web Services Extension Template
- WebLogic Server Default Domain Extension Template
- WebLogic Server Examples Extension Template

# Types of Templates

The term template refers to a Java Archive (JAR) file that contains the files and scripts required to create or extend a domain. The types of template include:

- Domain template—defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options.

The product installation includes a predefined Basic WebLogic Server Domain template. This template defines the core set of resources within a domain, including an Administration Server and basic configuration information. Complete details are provided in Basic WebLogic Server Domain Template.

You can also create a custom domain template from an existing domain using the Domain Template Builder or the `pack` command. Using the Domain Template Builder, you can also create a custom domain template from an existing template.

- Extension template—defines the applications and services that you can add to an existing domain, including product component functionality and resources such as JDBC or JMS.

The product installation includes several predefined extension templates. For a summary of extension templates, see Template Summary.

You can also create a custom extension template from an existing domain or template using the Domain Template Builder.

- Managed Server template - defines the subset of resources within a domain that are required to create a Managed Server domain directory on a remote machine. You can create a custom Managed Server template using the `pack` command. Complete details are provided in Creating Templates and Domains Using the pack and unpack Commands.

# Location of Installed Templates

The following table identifies the location of the predefined templates provided with your product installation, where `WL_HOME` represents the product installation directory.

Table 1 Location of Templates

Type of Template | Directory Location
--- | ---
Domain | `WL_HOME``\common\templates\domains`
Extension | `WL_HOME``\common\templates\applications`

# Template Tools

The following table identifies the tools with which you can create templates and the tools with which you can use templates to create or extend a domain.

Table 2 Template Tools

To . . . | Use this tool . . .
--- | ---
Create a new domain | Configuration Wizard WLST Offline `unpack` command
Extend an existing domain | Configuration Wizard WLST Offline
Create a new Managed Server domain on a remote machine | `unpack` command
Create a domain template | Domain Template Builder `pack` command WLST Offline
Create an extension template | Domain Template Builder
Create a Managed Server template | `pack` command

Note: All the tools used to create or extend a domain leverage a common underlying infrastructure, referred to generically as the Configuration Wizard framework.

- For information about using the Configuration Wizard, see Creating WebLogic Domains Using the Configuration Wizard.
- For information about using the WLST Offline, see WebLogic Scripting Tool.
- For information about using the `pack/unpack` commands, see Creating Templates and Domains Using the pack and unpack Commands.
- For information about using the Domain Template Builder, see Creating Templates Using the Domain Template Builder.

# Template Summary

The following table summarizes the predefined templates that may be provided in your product installation.

Table 3 Summary of Installed Templates

Template | Filename | Description
--- | --- | ---
Domain Template
Basic WebLogic Server Domain | `wls.jar` | Creates a base WebLogic Server domain.
Extension Templates
AquaLogic Service Bus Extension | `wlsb.jar` | Extends the base WebLogic Server domain by providing the resources required to support AquaLogic Service Bus.
Avitek Medical Records Sample Domain | `medrec.jar` | Extends the base WebLogic Server domain to create the Avitek Medical Records sample domain. This domain is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform.
WebLogic Beehive Extension | `weblogic-beehive.jar` | Extends the base WebLogic Server domain to create a WebLogic Beehive domain. Adds required Beehive libraries to support run-time use of controls. Note: Resources from the WebLogic Conversational Web Services extension template are required to create a complete WebLogic Beehive domain.
WebLogic Conversational Web Services Extension | `wls_conv.jar` | Extends the base WebLogic Server domain to add support for conversational Web services.
WebLogic Server Default Domain | `wls_default.jar` | Extends the base WebLogic Server domain with a Web application designed to guide new users through an introduction to WebLogic Server. When running the Web application, users can review informative content on various topics, including highlights of WebLogic Server functionality. From the Web application, users can also run several pre-configured, pre-compiled examples. Resources from this extension template are required for a WebLogic Server Examples domain.
WebLogic Server Examples | `wls_examples.jar` | Extends the WebLogic Server domain containing resources from the base WebLogic Server domain template and the WebLogic Server Default Domain extension template to create a complete WebLogic Server Examples domain. The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE and WebLogic Server APIs.

# Relationships Between Templates

This section provides the following topics:

- WebLogic Server Resources as a Prerequisite
- Relationships Between Templates

## WebLogic Server Resources as a Prerequisite

WebLogic Server resources must already be set up in your domain before you can add resources from an extension template. When you select an extension template, the Configuration Wizard framework checks to make sure the required resources are available for you.

## Relationships Between Templates

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

Table 4 Relationships Between Templates

This type of domain . . . | Requires resources from these templates . . .
--- | ---
AquaLogic Service Bus | Basic WebLogic Server Domain template, `wls.jar` + AquaLogic Service Bus Extension template, `wlsb.jar`
Avitek Medical Records Sample | Basic WebLogic Server Domain template, `wls.jar` + Avitek Medical Records Sample Domain extension template, `medrec.jar`
WebLogic Beehive | Basic WebLogic Server Domain template, `wls.jar` + WebLogic Beehive Extension template, `weblogic-beehive.jar` + WebLogic Conversational Web Services extension template, `wls_conv.jar`
WebLogic Conversational Web Services | Basic WebLogic Server Domain template, `wls.jar` + WebLogic Conversational Web Services extension template, `wls_conv.jar`
WebLogic Server (base) | Basic WebLogic Server Domain template, `wls.jar`
WebLogic Server Default | Basic WebLogic Server Domain template, `wls.jar` + WebLogic Server Default Domain extension template, `wls_default.jar`
WebLogic Server Examples | Basic WebLogic Server Domain template, `wls.jar` + WebLogic Server Default Domain extension template, `wls_default.jar` + WebLogic Server Examples extension template, `wls_examples.jar`

# 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 that are the basis for creating or extending a domain. The following table describes the files typically included in a domain or extension template.

Table 5 Files Included in a Template

Filename | Description
--- | ---
product component files | Various files used to complete the domain setup for a specific BEA 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.
`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 the 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, etc.

# Basic WebLogic Server Domain Template

Your product installation provides one predefined base WebLogic Server domain template. All other predefined templates are extension templates that you may use to add resources, services, and applications to a base WebLogic Server domain. You can easily create or extend a domain by using these predefined templates with the Configuration Wizard or WLST.

- Generated Domain Output
- Resources and Services Configured

## Generated Domain Output

The Basic WebLogic Server Domain template allows you to create a simple WebLogic Server domain. By default, when using the Basic WebLogic Server Domain 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 template. Unless otherwise specified, by default, the Configuration Wizard framework creates the domain in the `BEA_HOME``\user_projects\domains\base_domain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 6 Output Generated from the Basic WebLogic Server Domain Template

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
| n.a. | Directory designated as the repository for any custom application files that you create.
`user_projects\domains\base_domain\`
| `fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Domain template.

Table 7 Resources Configured in a Basic WebLogic Server Domain

Resource Type | Name | Notes
--- | --- | ---
Administration Server | `AdminServer` | When using the Configuration Wizard or WLST Offline to create a new domain, and you want the Administration Server name to be different from the default name, `AdminServer`, you must configure the name manually. You cannot change the name afterwards when applying an extension template. For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Configure the Administration Server" in "Customizing the Environment" in Creating WebLogic Domains Using the Configuration Wizard. For information about customizing the Administration Server name while creating a domain with WLST Offline, see "Creating and Configuring WebLogic Domains Using WLST Offline" in WebLogic Scripting Tool. The following sample WLST Offline code snippet shows how to change the default Administration Server name, `AdminServer`, to `MedRecServer`. `#----------------------------------- #Read the Basic WebLogic Server Domain template` `readTemplate``('d:/bea/weblogic91/commo n/templates/domains/``wls.jar``') #Change the Administration Server name.` `cd('Servers/AdminServer') set('Name', 'MedRecServer')` `#-----------------------------------`
Security realm | `myrealm` | n.a.

# AquaLogic Service Bus Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create an AquaLogic Service Bus domain. You accomplish this by adding the resources and services provided in the AquaLogic Service Bus extension template to a base WebLogic Server domain.

- Generated Domain Output
- Resources and Services Configured

Note: Using the Configuration Wizard in graphical mode, you can easily create a new AquaLogic Service Bus domain by checking the AquaLogic Service Bus check box in the Select Domain Source window. The result is the same as creating a base WebLogic Server domain first and then extending that domain with the AquaLogic Service Bus extension template. For more information about the templates required to create an AquaLogic Service Bus domain, see Relationships Between Templates.

## Generated Domain Output

The following table defines the default directory structure and files generated after applying the AquaLogic Service Bus extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\base_domain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 8 Base Domain After Applying AquaLogic Service Bus Extension Template

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
| n.a. | Directory serving as a placeholder for any custom application files that you create.
`user_projects\domains\base_domain\`
| `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.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`URLs.dat` | File containing the URL for the JDBC database.
`wlidebug.XML` | File containing debug parameters for the domain. The default setting for all the parameters is false.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`wlsbjmsrpDataSource-jdbc.xml` | Global non-XA JDBC data source module for the AquaLogic Service Bus domain.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`xbusResources-jms.xml` | Global JMS module for the AquaLogic Service Bus domain.
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`rmfilestore\` |  | Directory serving as a disk-based file store to store persistent messages and durable subscribers.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultAuthorizerInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLAuthorizerInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the AquaLogic Service Bus extension template.

Table 9 Resources Configured in an AquaLogic Service Bus Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `xbusServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
Application Deployments | `ALSB Configuration System` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Logging` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Publish` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Resource` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Routing` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Test Framework` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB Transform` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ALSB UDDI Manager` | Adds the application and targets it to the Administration Server, `AdminServer`.
Application Deployments (continued) | `Email Transport Provider` | Adds the application and targets it to the Administration Server, `AdminServer`.
`File Transport Provider` | Adds the application and targets it to the Administration Server, `AdminServer`.
`Ftp Transport Provider` | Adds the application and targets it to the Administration Server, `AdminServer`.
`JMS Reporting Provider` | Adds the application and targets it to the Administration Server, `AdminServer`.
`Message Reporting Purger` | Adds the application and targets it to the Administration Server, `AdminServer`.
`ServiceBus_Console` | Adds the application and targets it to the Administration Server, `AdminServer`.
`WLI Aggregator` | Adds the application and targets it to the Administration Server, `AdminServer`.
`WLI Common` | Adds the application and targets it to the Administration Server, `AdminServer`.
`XBus Kernel` | Adds the application and targets it to the Administration Server, `AdminServer`. The application includes the `/` (slash) WAR and `kerneladmin` EJB modules, which are also targeted to `AdminServer`.
File Stores | `FileStore` | Adds the file store to be used as the persistent store for the JMS server, `wlsbJMSServer`.
JDBC Data Source | `wlsbjmsrpDataSource` | Identifies the JDBC data source as a `wlsbjmsrpDataSource` system resource.
JDBC System Resources | `wlsbjmsrpDataSource` | Identifies the JDBC data source and connection pool setup to be used for JDBC system resources and targets the resources to the Administration Server, `AdminServer`.
JMS Connection Factories | `weblogic.wlsb.jms.transporttask.QueueConnectionFactory` | Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
`wli.reporting.jmsprovider.NonXAConnectionFactory` | Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
`wli.reporting.jmsprovider.XAConnectionFactory` | Adds the JMS connection factory as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
JMS Queues | `QueueIn` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wlsb.internal.transport.task.queue.email` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wlsb.internal.transport.task.queue.file` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wlsb.internal.transport.task.queue.ftp` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wli.reporting.jmsprovider.queue` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wli.reporting.jmsprovider_error.queue` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
`wli.reporting.purge.queue` | Adds the JMS queue to the JMS server, `wlsbJMSServer`.
JMS Servers | `wlsbJMSServer` | Adds the JMS server as a `jmsResources` system resource and targets it to the Administration Server, `AdminServer`.
JMS System Resources | `jmsResources` | Identifies the JMS servers, connection factories, and queues to be used for JMS system resources, and targets the resources to the Administration Server, `AdminServer`.
Security realm | `myrealm` | Uses the security realm provided by the base WebLogic Server domain.
Web Services Security | `__SERVICE_BUS_INBOUND_WEB_SERVICE_SECURITY_MBEAN__` | Adds the inbound Web Services security configuration, including the `default_x509_handler` and `default_ut_handler` token handlers and the `ServiceBusProviderUNT` and `ServiceBusProviderX509` credential providers.
`__SERVICE_BUS_OUTBOUND_WEB_SERVICE_SECURITY_MBEAN__` | Adds the outbound Web Services security configuration, including the `default_x509_handler` and `default_ut_handler` token handlers and the `ServiceBusProviderUNT`, `ServiceBusProviderX509`, `and alsb_saml_credential_provider` credential providers.

# Avitek Medical Records Sample Domain Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain. You accomplish this by adding the resources and services provided in the Avitek Medical Records Sample domain extension template to a base WebLogic Server domain.

- Generated Domain Output
- Resources and Services Configured

For more information about the Avitek Medical Records sample application, see Sample Application Examples and Tutorials for BEA WebLogic Server 9.1.

## Generated Domain Output

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

Table 10 Base Domain After Applying the Avitek Medical Records Sample Extension Template

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
`build\` | Various | Includes Avitek Medical Records split directory deployments.
`console-extension\` | Various | Includes sub-directories containing various files used to demonstrate extending the WebLogic Server Administration Console with a different look and feel.
`dist\` | Various | Includes sub-directories containing various files of the Avitek Medical Records applications in an exploded (unarchived) directory format.
`doc\` | Various | Directory and files containing the Avitek Medical Records online documentation.
`lib\` | Various | Includes sub-directories containing library files supporting the Avitek Medical Records sample.
`setup\` | `build.xml` | Ant build file used with corresponding scripts to set up a database for the Avitek Medical Records sample.
`setup\db\` | `medrec_mysql.ddl medrec_mysql_data.sql medrec_oracle.ddl medrec_oracle_data.sql medrec_pointbase.ddl medrec_pointbase_data.sql` | SQL scripts used to set up different databases that can be used with the Avitek Medical Records sample.
`src\` | Various | Includes sub-directories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, etc.
`user_projects\domains\base_domain\`
| `democa.pem` | Provides sample SSL protocol support for servers in the domain.
`fileRealm.properties` | File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
`log4jConfig.xml` | Configures Avitek Medical Records Log4j implementation including the `MedRecApp.log` file.
`pointbase.ini` | File containing initialization information for a PointBase JDBC database.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`MedRecWLDF.xml` | Diagnostic descriptor information for the Avitek Medical Records diagnostics instrumentation.
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`MedRecGlobalDataSource-jdbc.xml` | Global non-XA JDBC Data Source module for the Avitek Medical Records domain.
`MedRecGlobalDataSourceXA-jdbc.xml` | Global XA JDBC Data Source module for the Avitek Medical Records domain.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`MedRec-jms.xml` | Global JMS module for the Avitek Medical Records domain.
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`incoming\` | `StJohnHospital.xml` | Location where XML files containing fictitious patient names are uploaded by the Administration application of the Avitek Medical Records sample application.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`log4j.jar` `wllog4j.jar` | Libraries used by the Avitek Medical Records domain.
`medrecWseeFileStore\` |  | File store used by the Avitek Medical Records application.
`physicianFileStore\` |  | File store used by the Physician application.
`rmfilestore\` |  | File store used by system resources.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultAuthorizerInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLAuthorizerInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`MedRecDBMSPlugin.jar` | A `CustomDBMSAuthenticatorPlugin` used to validate a user/password against a DBMS for the Avitek Medical Records sample application.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template.

Table 11 Resources Configured in an Avitek Medical Records Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `MedRecServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
Application Deployments | `InitEAR` | Adds the `InitEAR` Web application and targets it to the Administration Server, `AdminServer`.
`MedRecEAR` | Adds the `MedRecEAR` Web application and targets it to the Administration Server, `AdminServer`.
`PhysicianEAR` | Adds the `PhysicianEAR` Web application and targets it to the Administration Server, `AdminServer`.
`StartBrowserEAR` | Adds the `StartBrowserEAR` Web application and targets it to the Administration Server, `AdminServer`.
File Stores | `FileStore` | Adds the file store and targets the store to the Administration Server, `AdminServer`.
`MedRecWseeFileStore` | Adds the file store to be used as the persistent store for the JMS server, `MedRecWseeJMSServer`, and targets the store to the Administration Server, `AdminServer`.
`PhysicianFileStore` | Adds the file store and targets the store to the Administration Server, `AdminServer`.
JDBC Data Sources | `MedRecGlobalDataSource` | Identifies the JDBC data source as a `MedRecGlobalDataSource` system resource.
`MedRecGlobalDataSourceXA` | Identifies the JDBC data source as a `MedRecGlobalDataSourceXA` system resource.
JDBC Store | `MedRecJMSJDBCStore` | Adds the JDBC store to be used with the JDBC data source, `MedRecGlobalDataSource`, and as the persistent store for the JMS server, `MedRecJMSServer`, and targets the store to the Administration Server, `AdminServer`.
JDBC System Resources | `MedRecGlobalDataSource` `MedRecGlobalDataSourceXA` | Identifies the JDBC data source and connection pool setups to be used for non-XA and XA JDBC system resources, and targets the resources to the Administration Server, `AdminServer`.
JMS Queues | `weblogic.wsee.reliability.wseeMedRecDestinationQueue` | Adds the JMS queue to the JMS server, `MedRecWseeJMSServer`.
JMS Servers | `MedRecJMSServer` | Adds the JMS server as a `MedRec-jms` system resource and targets it to the Administration Server, `AdminServer`.
`MedRecWseeJMSServer` | Adds the JMS server as a `MedRec-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS System Resources | `MedRec-jms` | Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the Administration Server, `AdminServer`.
Mail Session | `mail/MedRecMailSession` | Adds the mail session.
SAF Agent | `MedRecSAFAgent` | Adds this store-and-forward agent, which uses the file store, `MedRecWseeFileStore`, and targets it to the Administration Server, `AdminServer`.
Security realm | `myrealm` | Uses the security realm provided in the base WebLogic Server domain.
WLDF System Resource | `MedRecWLDF` | Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server, `AdminServer`.

# WebLogic Beehive Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for using WebLogic Beehive. You accomplish this by adding the resources and services provided in the WebLogic Beehive and WebLogic Conversational Web Services extension templates to a base WebLogic Server domain.

- Generated Domain Output
- Resources and Services Configured

Note: Using the Configuration Wizard in graphical mode, you can easily create a new WebLogic Beehive domain by checking the Apache Beehive check box in the Select Domain Source window. The result is the same as creating a base WebLogic Server domain first and then extending that domain with both the WebLogic Beehive and WebLogic Conversational Web Services extension templates. For more information about the templates required to create a WebLogic Beehive domain, see Relationships Between Templates.

## Generated Domain Output

The following table defines the default directory structure and files generated after applying the WebLogic Beehive and WebLogic Conversational Web Services extension templates to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\base_domain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 12 Base Domain After Applying the WebLogic Beehive and WebLogic Conversational Web Services Extension Templates

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
| n.a. | Directory serving as a placeholder for any custom application files that you create.
`user_projects\domains\base_domain\`
| `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.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`URLs.dat` | File containing the URL for the JDBC database.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`cgDataSource-jdbc.xml` | Global XA JDBC Data Source module for the domain configured for conversational Web services.
`cgDataSource-nonXA-jdbc.xml` | Global non-XA JDBC Data Source module for the domain configured for conversational Web services.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`conversational-jms.xml` | Global JMS module for the domain configured for conversational Web services.
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Beehive and WebLogic Conversational Web Services extension templates.

Table 13 Resources Configured in a WebLogic Beehive Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `cgServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
JDBC Data Source | `cgDataSource` | Uses the XA JDBC data source provided by the WebLogic Conversational Web Services extension template. Identifies the XA JDBC data source as a `cgDataSource` system resource.
`cgDataSource-nonXA` | Uses the non-XA JDBC data source provided by the WebLogic Conversational Web Services extension template. Identifies the non-XA JDBC data source as a `cgDataSource-nonXA` system resource.
JDBC Store | `cgJMSStore` | Uses the JDBC store provided by the WebLogic Conversational Web Services extension template. The JDBC store is to be used with the JDBC data source, `cgDataSource-nonXA`, and the JMS server, `cgJMSServer`, as a persistent store, and is targeted to the Administration Server, `AdminServer`.
JDBC System Resources | `cgDataSource` `cgDataSource-nonXA` | Uses the JDBC data source and connection pool setups provided by the WebLogic Conversational Web Services extension template. These JDBC system resources are targeted to the Administration Server, `AdminServer`.
JMS Connection Factory | `cgQueue` | Uses the JMS connection factory provided by the WebLogic Conversational Web Services extension template. Identifies the JMS connection factory as a `conversational-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS Queues | `cgJWSQueue` | Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, `cgJMSServer`.
`wlwJWSBuffer` | Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, `cgJMSServer`.
`wlwJWSErrors` | Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, `cgJMSServer`.
JMS Server | `cgJMSServer` | Uses the JMS server provided by the WebLogic Conversational Web Services extension template. Identifies the JMS server as a `conversational-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS System Resources | `conversational-jms` | Uses the JMS system resources provided by the WebLogic Conversational Web Services extension template.
Security realm | `myrealm` | Uses the security realm provided by the base WebLogic Server domain.
Libraries Deployed | `weblogic-beehive-1.0#1.0@1.0` | Adds the WebLogic Beehive Version 1.0 libraries provided by the WebLogic Beehive extension template, and targets them to the Administration Server, `AdminServer`. The libraries include Beehive and system controls.
`beehive-netui-1.0#1.0@1.0` | Adds the Apache Beehive NetUI Version 1.0 libraries provided by the WebLogic Beehive extension template, and targets them to the Administration Server, `AdminServer`. These libraries support pageflow development, and depend upon the libraries contained in `struts-1.1.war` and `weblogic-beehive-1.0.ear`.
`jstl-1.1#1.1@1.0` | Adds the Java standard tagging (JSTL) Version 1.1 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, `AdminServer`.
`struts-1.1#1.1@1.0` | Adds the Apache Struts Version 1.1 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, `AdminServer`.
`struts-1.2#1.2@1.0` | Adds the Apache Struts Version 1.2 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, `AdminServer`.

# WebLogic Conversational Web Services Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for conversational Web services. You accomplish this by adding the resources and services provided in the WebLogic Conversational Web Services extension template to a base WebLogic Server domain.

- Generated Domain Output
- Resources and Services Configured

## Generated Domain Output

The following table defines the default directory structure and files generated after applying the WebLogic Conversational Web Services extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the `BEA_HOME``\user_projects\domains\base_domain` directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.

Table 14 Base Domain After Applying the WebLogic Conversational Web Services Extension Template

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
| n.a. | Directory serving as a placeholder for any custom application files that you create.
`user_projects\domains\base_domain\`
| `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.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`URLs.dat` | File containing the URL for the JDBC database.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`cgDataSource-jdbc.xml` | Global XA JDBC Data Source module for the domain configured for conversational Web Services.
`cgDataSource-nonXA-jdbc.xml` | Global non-XA JDBC Data Source module for the domain configured for conversational Web Services.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`conversational-jms.xml` | Global JMS module for the domain configured for conversational Web Services.
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Conversational Web Services extension template.

Table 15 Resources Configured in a WebLogic Conversational Web Services Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `cgServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
JDBC Data Source | `cgDataSource` | Identifies the XA JDBC data source as a `cgDataSource` system resource.
`cgDataSource-nonXA` | Identifies the non-XA JDBC data source as a `cgDataSource-nonXA` system resource.
JDBC Store | `cgJMSStore` | Adds the JDBC store to be used with the JDBC data source, `cgDataSource-nonXA`, and the JMS server, `cgJMSServer`, as a persistent store, and targets it to the Administration Server, `AdminServer`.
JDBC System Resources | `cgDataSource` `cgDataSource-nonXA` | Identifies the JDBC data source and connection pool setups to be used for JDBC system resources and targets the resources to the Administration Server, `AdminServer`.
JMS Connection Factory | `cgQueue` | Adds the JMS connection factory as a `conversational-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS Queues | `cgJWSQueue` | Adds the JMS queue to the JMS server, `cgJMSServer`.
`wlwJWSBuffer` | Adds the JMS queue to the JMS server, `cgJMSServer`.
`wlwJWSErrors` | Adds the JMS queue to the JMS server, `cgJMSServer`.
JMS Server | `cgJMSServer` | Adds the JMS server as a `conversational-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS System Resources | `conversational-jms` | Identifies the JMS servers, connection factories, and queues to be used for JMS system resources.
Security realm | `myrealm` | Uses the security realm provided by the base WebLogic Server domain.

# WebLogic Server Default Domain Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include resources required for a default WebLogic Server domain. You accomplish this by adding the resources and services provided in the WebLogic Server Default Domain extension template to a base WebLogic Server domain.

Note: Applying the WebLogic Server Default Domain extension template to a base WebLogic domain is a prerequisite to using the WebLogic Server Examples extension template. For information about the relationship between templates, see Relationships Between Templates.

- Generated Domain Output
- Resources and Services Configured

For more information about the samples that are supported in the WebLogic Server Examples domain, see Sample Application Examples and Tutorials for BEA WebLogic Server 9.1.

## Generated Domain Output

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

Table 16 Base Domain After Applying the WebLogic Server Default Domain Extension Template

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
`server\docs\` | Various | Includes sub-directories containing style sheet and graphics files to support the online documentation.
`server\examples\build\` | Various | Includes WebLogic Server examples deployments.
`server\examples\src\` | Various | Includes source code and instructions for WebLogic Server examples.
`user_projects\domains\base_domain\`
| `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.
`setExamplesEnv.cmd` `setExamplesEnv.sh` | Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`startWebLogicEx.cmd` `startWebLogicEx.sh` | Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`examples-demo-jdbc.xml` | Global non-XA JDBC Data Source module for the WebLogic Server default domain.
`examples-demoXA-jdbc.xml` | Global XA JDBC Data Source module for the WebLogic Server default domain.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultAuthorizerInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLAuthorizerInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Server Default Domain extension template.

Table 17 Resources Configured in a WebLogic Server Default Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `examplesServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
Application Deployments | `ejb20BeanMgedEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
`examplesWebApp` | Adds the application and targets it to the Administration Server, `AdminServer`.
`jdbcRowSetsEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
`jspSimpleTagEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
`mainWebApp` | Adds the application and targets it to the Administration Server, `AdminServer`.
`webappCachingEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
`webservicesJwsSimpleEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
`xmlBeanEar` | Adds the application and targets it to the Administration Server, `AdminServer`.
JDBC Data Sources | `examples-demo` | Identifies the JDBC data source as an `examples-demo` system resource.
`examples-demoXA` | Identifies the JDBC data source as an `examples-demoXA` system resource.
JDBC System Resources | `examples-demo` `examples-demoXA` | Identifies the JDBC data source and connection pool setups to be used for non-XA and XA JDBC system resources and targets them to the Administration Server, `AdminServer`.
Security realm | `myrealm` | Uses the security realm provided by the base WebLogic Server domain.

.

# WebLogic Server Examples Extension Template

Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create a WebLogic Server Examples domain. You accomplish this by adding the resources and services provided in both the WebLogic Server Default and WebLogic Server Examples extension templates to a base WebLogic Server domain.

- Generated Domain Output
- Resources and Services Configured

For more information about the samples that are supported in the WebLogic Server Examples domain, see Sample Application Examples and Tutorials for BEA WebLogic Server 9.1.

## Generated Domain Output

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. Once the WebLogic Server Default extension template has been applied to a base domain, applying the WebLogic Server Examples extension template allows you to create the WebLogic Server Examples domain. See Relationships Between Templates for more details.

Table 18 Base Domain After Applying the WebLogic Server Default and WebLogic Server Examples Extension Templates

Directory | File | Description
--- | --- | ---
`user_projects\applications\base_domain\`
`server\` | `wls_samples_overview.html` | File that opens the WebLogic Server examples online documentation viewer.
`server\docs\` | Various | Directory and files supporting the WebLogic Server examples online documentation viewer.
`server\examples\build\` | Various | Includes sub-directories containing various Java and XML files used to build and work with WebLogic Server examples.
`server\examples\src\` | Various | Includes sub-directories containing various Java, XML, and HTML files used to work with WebLogic Server examples.
`user_projects\domains\base_domain\`
| `client2certs.pem` `clientkey.pem` | Demo certificate and keystore files.
`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.
`setExamplesEnv.cmd` `setExamplesEnv.sh` | Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.
`startWebLogic.cmd` `startWebLogic.sh` | Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
`startWebLogicEx.cmd` `startWebLogicEx.sh` | Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.
`autodeploy\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for automatic deployments.
`bin\` | `setDomainEnv.cmd` `setDomainEnv.sh` | Scripts used to 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.
`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 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.
`config\` | `config.xml` | File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
`config\deployments\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application's staging mode is "staged."
`config\diagnostics\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
`config\jdbc\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
`examples-demo-jdbc.xml` | Global non-XA JDBC Data Source module for the WebLogic Server Examples domain.
`examples-demoXA-2-jdbc.xml` `examples-demoXA-jdbc.xml` `examples-multiDataSource-demoXAPool-jdbc.xml` `examples-oracleXA-jdbc.xml` | Global XA JDBC Data Source modules for the WebLogic Server Examples domain.
`config\jms\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
`examples-jms.xml` | Global JMS module for the WebLogic Server Examples domain.
`config\lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
`config\nodemanager\` | `nm_password.properties` | File containing Node Manager password property values.
`config\security\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
`config\startup\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
`console-ext\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
`init-info\` | `domain-info.xml` | File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
`security.xml` | File used for creating user groups and roles that establish identity and access to domain resources.
`startscript.xml` | File used to create the `*.cmd` and `*.sh` files that are placed into the domain's root and `bin` directories.
`tokenValue.properties` | File that contains the actual values to substitute for the tokens specified in the start scripts.
`lib\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
`security\` | `DefaultAuthenticatorInit.ldift` `DefaultAuthorizerInit.ldift` `DefaultRoleMapperInit.ldift` `XACMLAuthorizerInit.ldift` `XACMLRoleMapperInit.ldift` | Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information. Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security.
`SerializedSystemIni.dat` | File containing encrypted security information.
`servers\AdminServer\security\` | `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 "Provide User Credentials to Start and Stop Servers" in Starting and Stopping Servers in Managing Server Startup and Shutdown.
`user_staged_config\` | `readme.txt` | File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.
`WseeFileStore\` |  | Directory to be used for the file store for system resources.

## Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Server Examples extension template.

Table 19 Resources Configured in a WebLogic Server Examples Domain

Resource Type | Name | Extension Result
--- | --- | ---
Administration Server | `AdminServer` | Uses the Administration Server provided in the base WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in the extension template is `examplesServer`. For information about naming the Administration Server during domain creation, see Resources and Services Configured.
Application Deployments | `ejb20BeanMgedEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`examplesWebApp` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`jdbcRowSetsEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`jspSimpleTagEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`mainWebApp` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`SamplesSearchWebApp` | Adds the application and targets it to the Administration Server, `AdminServer`.
`webappCachingEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`webservicesJwsSimpleEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`xmlBeanEar` | Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
File Store | `WseeFileStore` | Adds the file store to be used as the persistent store for the JMS server, `WseeJMSServer`, and the SAF Agent, `ReliableWseeSAFAgent`, and targets the store to the Administration Server, `AdminServer`.
JDBC Data Sources | `examples-demo` `examples-demoXA` | Uses the non-XA and XA JDBC data sources provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`examples-oracleXA` | Adds the XA JDBC data source and targets it to the Administration Server, `AdminServer`.
`examples-demoXA-2` | Adds the XA JDBC data source and targets it to the Administration Server, `AdminServer`.
`examples-multiDataSource-demoXAPool` | Adds the XA JDBC multi data source and targets it to the Administration Server, `AdminServer`. Maps to `examples-demoXA` and `examples-demoXA-2` data sources.
JDBC Store | `exampleJDBCStore` | Adds the JDBC store to be used as the persistent store for the JDBC data source, `examples-demo`, and the JMS server, `examplesJMSServer`, and targets the store to the Administration Server, `AdminServer`.
JDBC System Resources | `examples-demo` `examples-demoXA` | Uses the JDBC data source and connection pool setups provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain.
`examples-demoXA-2` `examples-oracleXA` `examples-multiDataSource-demoXAPool` | Adds the JDBC data source and connection pool setups and targets them to the Administration Server, `AdminServer`.
JMS System Resources | `examples-jms` | Identifies the JMS servers, connection factories, queues, and topics to be used for JMS system resources.
JMS Connection Factories | `exampleTopic` `exampleTrader` `weblogic.examples.jms.QueueConnectionFactory` | Adds the JMS connection factories as `examples-jms` system resources and targets them to the Administration Server, `AdminServer`.
JMS Servers | `examplesJMSServer` | Adds the JMS server as an `examples-jms` system resource and targets it to the Administration Server, `AdminServer`.
`WseeJMSServer` | Adds the JMS server as an `examples-jms` system resource and targets it to the Administration Server, `AdminServer`.
JMS Queues | `exampleQueue` | Adds the JMS queue to the JMS server, `examplesJMSServer`.
`jms/MULTIDATASOURCE_MDB_QUEUE` | Adds the JMS queue to the JMS server, `examplesJMSServer`.
`weblogic.wsee.wseeExamplesDestinationQueue` | Adds the JMS queue to the JMS server, `WseeJMSServer`.
JMS Topics | `exampleTopic` | Adds the JMS topic to the JMS server, `examplesJMSServer`.
`quotes` | Adds the JMS topic to the JMS server, `examplesJMSServer`.
SAF Agent | `ReliableWseeSAFAgent` | Adds the SAF agent and targets it to the Administration Server, `AdminServer`.
Security realm | `myrealm` | Uses the security realm provided by the base WebLogic Server domain.