WebLogic Server Templates

2 WebLogic Server Templates

The WebLogic domain templates are provided with your WebLogic Server installation. You can create or extend domains by selecting these templates on the Templates screen of the Oracle Fusion Middleware Configuration Wizard or by using WLST.

Table 2-1 Oracle WebLogic Server and Workshop for WebLogic Templates

Template	Description
Basic WebLogic Server Domain Template	Creates a base WebLogic Server domain.
WebLogic Server Starter Domain Template	Creates a WebLogic Server starter domain.
WebLogic Advanced Web Services for JAX-RPC Extension Template	Extends an existing WebLogic Server domain to add functionality required for advanced JAX-RPC Web services, including Web services reliable messaging, buffering, and JMS transport.
WebLogic Advanced Web Services for JAX-WS Extension Template	Extends a domain to add functional required for advanced Web services, including asynchronous messaging, Web services reliable messaging, message buffering, Web services atomic transactions, and security by using WS-SecureConversation.
WebLogic JAX-WS SOAP/JMS Extension Template	Extends a domain to include the resources required to use SOAP over JMS transport for JAX-WS Web services.
Avitek Medical Records Sample Domain Template	Extends the Basic WebLogic Server domain to create the Avitek Medical Records sample domain. This domain is a WebLogic Server sample application suite that demonstrates all aspects of the J2EE platform.
Avitek Medical Records Sample Domain Template (Spring Version)	Extends the Basic WebLogic Server domain to create the Avitek Medical Records sample domain for Spring. This domain is a WebLogic Server sample application suite that demonstrates all aspects of the J2EE platform.
WebLogic Server Default Domain Extension Template	Extends the Basic WebLogic Server domain with a web application designed to guide new users through an introduction to WebLogic Server. When you run the web application, you can review informative content on various topics, including highlights of WebLogic Server functionality. From the web application, you can also run several preconfigured, precompiled examples. Resources from this extension template are required for a WebLogic Server Examples domain.
WebLogic Server Examples Extension Template	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.

Basic WebLogic Server Domain Template
This template helps you configure resources such as Administration Server and Security realm at the time of creating a domain.
WebLogic Server Starter Domain Template
This template helps you configure resources and services such as Administration Server, Security realm, and Application Deployments at the time of creating a domain.
WebLogic Advanced Web Services for JAX-RPC Extension Template
When you use the Configuration Wizard or WLST, this template helps you include the resources required for advanced JAX-RPC Web services.
WebLogic Advanced Web Services for JAX-WS Extension Template
This template automatically configures the resources required to support the advanced Web services features.
WebLogic JAX-WS SOAP/JMS Extension Template
When you use the Configuration Wizard or WLST, this template helps you include the resources required to use SOAP over JMS transport for JAX-WS Web services.
Avitek Medical Records Sample Domain Template
When you use the Configuration Wizard or WLST, this template helps you to extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain.
Avitek Medical Records Sample Domain Template (Spring Version)
When you use the Configuration Wizard or WLST, this template helps you easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain in the Spring version.
WebLogic Server Default Domain Extension Template
When you use the Configuration Wizard or WLST, this template helps you extend a base WebLogic Server domain to include resources required for a default WebLogic Server domain.
WebLogic Server Examples Extension Template
When you use the Configuration Wizard or WLST, this template helps you easily extend a base WebLogic Server domain to create a WebLogic Server Examples domain.

Basic WebLogic Server Domain Template

This template helps you configure resources such as Administration Server and Security realm at the time of creating a domain.

Your product installation provides one predefined Basic WebLogic Server domain template. All other predefined templates are extension templates that you may use to add resources, services, and applications to a Basic WebLogic Server domain.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the Basic WebLogic Server Domain template. The template name is the name of the template as shown in the product list in the Select Domain Source and Select Extension Source screens of the Configuration Wizard.

Table 2-2 Basic WebLogic Server Domain Template Information

Template Detail	Information
Template type	Domain
Category	Oracle WebLogic Server and Coherence
Template name	Basic WebLogic Server Domain
Template JAR file and location	`WL_HOME/common/templates/wls/wls.jar`
Template dependencies	None

Parent topic: Basic WebLogic Server Domain Template

Resources and Services Configured in a Basic WebLogic Server Domain

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

Table 2-3 Resources Configured in a Basic WebLogic Server Domain

Resource Type Name Notes

Resource Type	Name	Notes
Administration Server	`AdminServer`	The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is disabled When you use the Configuration Wizard or WLST Offline to create a domain, and if 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 when you apply an extension template. For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see Creating a WebLogic Domain 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 WebLogic Domains Using WLST Offline in Understanding the WebLogic Scripting Tool. The following sample WLST Offline code snippet shows you how to change the default Administration Server name, `AdminServer`, to `MedRecServer`. #-----------------------------------# Read the Basic WebLogic Server Domain template readTemplate('d:/MW_HOME/wlserver/common/templates/wls/wls.jar') #Change the Administration Server name. cd('Servers/AdminServer') set('Name', 'MedRecServer') #-----------------------------------
Security realm	`myrealm`	This realm is the default (active) WebLogic Server security realm. The administration user account, `weblogic`, is configured in this security realm, as well as in all the default groups and roles.

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

Listen address: All Local Addresses
Listen port: 7001
SSL is disabled

When you use the Configuration Wizard or WLST Offline to create a domain, and if 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 when you apply an extension template.

For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see Creating a WebLogic Domain 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 WebLogic Domains Using WLST Offline in Understanding the WebLogic Scripting Tool.

The following sample WLST Offline code snippet shows you how to change the default Administration Server name, AdminServer, to MedRecServer.

#-----------------------------------#
Read the Basic WebLogic Server Domain template
readTemplate('d:/MW_HOME/wlserver/common/templates/wls/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Security realm

myrealm

This realm is the default (active) WebLogic Server security realm. The administration user account, weblogic, is configured in this security realm, as well as in all the default groups and roles.

Parent topic: Basic WebLogic Server Domain Template

WebLogic Server Starter Domain Template

This template helps you configure resources and services such as Administration Server, Security realm, and Application Deployments at the time of creating a domain.

Your product installation also provides one predefined WebLogic Server domain template. This template contains the default domain configuration settings and an application that provides a Welcome page to help you get started.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Server Starter Domain template.

Table 2-4 WebLogic Server Starter Domain Template Information

Template Detail	Information
Template type	Domain
Template name in the Configuration Wizard	This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.
Template JAR file and location	`WL_HOME/common/templates/wls/wls_starter.jar`
Template dependencies	Base WebLogic Server domain template

Parent topic: WebLogic Server Starter Domain Template

Resources and Services Configured in a WebLogic Server Starter Domain

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

Table 2-5 Resources Configured in a WebLogic Server Starter Domain

Resource Type Name Notes

Resource Type	Name	Notes
Administration Server	`AdminServer`	The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is disabled When you use the Configuration Wizard or WLST Offline to create a domain, and if 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 later when you apply an extension template. For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating WebLogic Domains Using the Configuration Wizard. For information about customizing the Administration Server name while creating a domain with WLST Offline, see Creating WebLogic Domains Using WLST Offline in Understanding the 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:/MW_HOME/wlserver/common/templates/wls/wls.jar') #Change the Administration Server name. cd('Servers/AdminServer') set('Name', 'MedRecServer') #-----------------------------------
Security realm	`myrealm`	The default (active) WebLogic Server security realm.
Application deployments	`wl_starter`	A sample Web application deployed to the starter domain.

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

Listen address: All Local Addresses
Listen port: 7001
SSL is disabled

For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating WebLogic Domains Using the Configuration Wizard.

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:/MW_HOME/wlserver/common/templates/wls/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Security realm

myrealm

The default (active) WebLogic Server security realm.

Application deployments

wl_starter

A sample Web application deployed to the starter domain.

Parent topic: WebLogic Server Starter Domain Template

WebLogic Advanced Web Services for JAX-RPC Extension Template

When you use the Configuration Wizard or WLST, this template helps you include the resources required for advanced JAX-RPC Web services.

You accomplish this task by adding the resources and services provided in the WebLogic Advanced Web Services for JAX-RPC extension template to a base WebLogic Server domain.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Advanced Web Services for JAX-RPC extension template.

Table 2-6 WebLogic Advanced Web Services for JAX-RPC Extension Template Information

Template Detail	Information
Template type	Extension
Category	Oracle WebLogic Server and Coherence
Template name and version	WebLogic Advanced Web Services for JAX-RPC Extension - 12.2.1.3.0
Template dependencies	Base WebLogic Server domain template
Template JAR file and location	`ORACLE_HOME/oracle_common/common/templates/wls/oracle.wls-webservice-template.jar`

Parent topic: WebLogic Advanced Web Services for JAX-RPC Extension Template

Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services for JAX-RPC extension template.

Table 2-7 Resources Configured in a WebLogic Advanced Web Services for JAX-RPC Domain

Resource Type	Name	Extension Result
Administration Server	`AdminServer`	Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is enabled SSL listen port: 7002 For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the default security realm provided by the Basic WebLogic Server domain.
File store	`WseeFileStore`	Adds the file store to be used as the persistent store for the `WseeJmsServer` JMS server. This file store is targeted to the Administration Server.
SAF agent	`ReliableWseeSAFAgent`	Adds this store-and-forward agent, which uses the `WseeFileStore`, and targets it to the Administration Server. The SAF agent controls receipt and handling of reliable messages.
JMS queues	`WseeMessageQueue`	Adds the JMS queue to the JMS server and `WseeJmsServer`. The queues are located in `JMSModules/module name`, which are located in WseeJMSModule.
JMS queues	`WseeCallbackQueue`	Adds the JMS queue to the JMS server `WseeJmsServer`.
JMS Server	`WseeJmsServer`	Adds the JMS server as a system resource and targets it to the Administration Server `AdminServer`.
Work Manager	`weblogic.wsee.mdb.DispatchPolicy`	Add this Work Manager and targets it to the Administration Server `AdminServer`.

Parent topic: WebLogic Advanced Web Services for JAX-RPC Extension Template

WebLogic Advanced Web Services for JAX-WS Extension Template

This template automatically configures the resources required to support the advanced Web services features.

The following advanced Web services features are supported:

Web services atomic transactions
Security using WS-SecureConversation

Note:

Each of the two Advanced Web Services templates can be used individually or together in a domain. If, however, you apply this template to the same domain to which you applied the WebLogic Advanced Web Services extension template, you must apply the Advanced Web Services template before you apply the Advanced Web Services for JAX-WS template.

For more information, see Configuring Your Domain for Advanced Web Services Features in Developing JAX-WS Web Services for Oracle WebLogic Server.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Advanced Web Services for JAX-WS extension template.

Table 2-8 WebLogic Advanced Web Services for JAX-WS Extension Template Details

Template Detail	Information
Template type	Extension
Category	Oracle WebLogic Server and Coherence
Template name and version	WebLogic Advanced Web Services for JAX-WS Extension - 12.2.1.3.0
Template dependencies	Base WebLogic Server domain template Web Services State Management Memory Provider template
Template JAR file and location	`ORACLE_HOME/oracle_common/common/templates/wls/oracle.wls-webservice-jaxws-template.jar`

Parent topic: WebLogic Advanced Web Services for JAX-WS Extension Template

Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services for JAX-WS extension template.

Table 2-9 Resources Configured in a WebLogic Advanced Web Services for JAX-WS Domain

Resource Type	Name	Extension Result
Administration Server	`AdminServer`	Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is enabled SSL listen port: 7002 For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the default security realm provided by the Basic WebLogic Server domain.
JMS Server	`WseeJaxwsJmsServer`	Adds the JMS server as a system resource and targets it to the Administration Server.
Work Manager	`weblogic.wsee.jaxws.mdb.DispatchPolicy`	Adds this Work Manager and targets it to the Administration Server. The Work Manager defines the thread pool resources.
File store	`WseeJaxwsFileStore`	Adds the file store to be used as the persistent store for the `WseeJaxwsJmsServer` JMS server. This file store is targeted to the Administration Server.
JMS system resource	`WseeJaxwsJmsModule`	Defines a distributed destination for the cluster. All associated targets are used to support JAX-WS Web services. The subdeployment name is `WseeJaxwsJmsServerSub`. Note: By default, a weighted distributed destination (WDD) is configured. In a clustered environment, Oracle strongly recommends that you upgrade the destination to a uniform distributed destination (UDD).
SAF Agent	`ReliableWseeJaxwsSAFAgent`	Adds this store-and-forward agent, which uses the `WseeJaxwsFileStore`, and targets it to the Administration Server. The SAF agent controls receipt and handling of reliable messages.
JMS queues	`weblogic.wsee.BufferedRequest Queue` `weblogic.wsee.BufferedRequestErrorQueue` `weblogic.wsee.BufferedResponseQueue` `weblogic.wsee.BufferedResponseErrorQueue`	Adds these JMS queues to the JMS server, and targets them to `WseeJaxwsJmsServer`. These queues are reserved for future use.

Parent topic: WebLogic Advanced Web Services for JAX-WS Extension Template

WebLogic JAX-WS SOAP/JMS Extension Template

When you use the Configuration Wizard or WLST, this template helps you include the resources required to use SOAP over JMS transport for JAX-WS Web services.

You accomplish this task by adding the resources and services provided in the WebLogic Advanced Web Services extension template to a base WebLogic Server domain.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic JAX-WS SOAP/JMS extension template.

Table 2-10 WebLogic JAX-WS SOAP/JMS Extension Template Details

Template Detail	Information
Template type	Extension
Category	Oracle WebLogic Server and Coherence
Template name and version	WebLogic JAX-WS SOAP/JMS Extension - 12.2.1.3.0
Template dependencies	Base WebLogic Server domain template
Template JAR file and location	`ORACLE_HOME/oracle_common/common/templates/wls/oracle.wls-webservice-soapjms-template.jar`

Parent topic: WebLogic JAX-WS SOAP/JMS Extension Template

Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic JAX-WS SOAP/JMS extension template.

Table 2-11 Resources Configured in a WebLogic JAX-WS SOAP/JMS Domain

Resource Type	Name	Extension Result
JMS Server	`WseeSoapjmsJmsServer`	JMS server management container.
File store	`WseeSoapjmsFileStore`	File store, or physical store, used by the WebLogic Server to handle the I/O operations to save and retrieve data from the physical storage such as file, DBMS, and so on.
JMS module	`WseeSoapjmsJmsModule`	JMS module that defines the JMS resources needed for SOAP over JMS transport.
JMS subdeployment	`WseeSoapjmsJmsServerSub`	JMS subdeployment for targeting the JMS resources to the `WseeSoapJmsServer`.
JMS Connection Factory	`com.oracle.webservices.api.jms.ConnectionFactory`	Default JMS connection factory used to create connections for SOAP over JMS transport.
JMS queues	`com.oracle.webservices.api.jms.RequestQueue`	Default JMS request queue.
JMS queue	`com.oracle.webservices.api.jms.ResponseQueue`	Default JMS response queue.
JMS queue	`com.oracle.webservices.api.jms.ErrorQueue`	Default JMS error queue.

Parent topic: WebLogic JAX-WS SOAP/JMS Extension Template

Avitek Medical Records Sample Domain Template

When you use the Configuration Wizard or WLST, this template helps you to extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain.

You accomplish this task by adding the resources and services provided in the Avitek Medical Records Sample domain extension template to a base WebLogic Server domain.

For more information about the Avitek Medical Records sample application, see Sample Application and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the Avitek Medical Records Sample domain extension template.

Table 2-12 Avitek Medical Records Sample Domain Information

Template Detail	Information
Template type	Extension
Template name in the Configuration Wizard	This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.
Template JAR file and location	`WL_HOME/common/templates/wls/medrec.jar`
Template dependencies	Basic WebLogic Server Domain template

Parent topic: Avitek Medical Records Sample Domain Template

Resources and Services Configured

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

A Work Manager service (weblogic.wsee.mdb.DispatchPolicy) is also available, but it is not targeted to the Administration Server.

Table 2-13 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 is referenced in the template as `@SERVER_NAME`, and appears as `AdminServer` in the WebLogic Server Administration Console. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is enabled SSL port: 7002 For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the default security realm provided in the Basic WebLogic Server domain.
Application deployments	`medrec`	Adds the sample medrec Enterprise application and targets it to the Administration Server.
Application deployments	`physician`	Adds the sample physician Enterprise application and targets it to the Administration Server.
Application deployment	`chat`	Adds the chat Web application, which is used for conversation between the patient and physician, and targets it to the Administration Server.
Application deployments	`browser-starter`	Adds the browser-starter Web application and targets it to the Administration Server.
Application deployment	`SamplesSearchWebApp`	Adds a sample search application and targets it to the Administration Server.
Mail Session	`mail/MedRecMailSession`	Adds this mail session.
JDBC Data Source	`MedRecGlobalDataSourceXA`	Identifies the JDBC data source as a `MedRecGlobalDataSourceXA` system resource.
JDBC Data Source	`BatchDS`	Defines a JDBC data source called BatchDS. This data source is a two-phase commit XA data source with JNDI name `jndi/batchDS`.
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.
JMS Server	`MedRecJMSServer`	Adds the JMS server as a `MedRec-jms` system resource and targets it to the Administration Server
Work Manager	`weblogic.wsee.mdb.DispatchPolicy`	Adds this Work Manager and targets it to the Administration Server. The Work Manager defines the thread pool resources.
WLDF System Resource	`MedRecWLDF`	Adds the WLDF system resource, WLDF harvester for NewUserCoun' and WLDR instrumentation monitors for Dye Injection, and targets them to the Administration Server.
Connection Factory	`MedRecConnectionFactory`	Default JMS connection factory used to create connections over JMS transport.
JMS Queues	`com.oracle.medrec.jms.PatientNotificationQueue`	Adds the JMS queue to the JMS server, `MedRecWseeJMSServer`.

Parent topic: Avitek Medical Records Sample Domain Template

Avitek Medical Records Sample Domain Template (Spring Version)

When you use the Configuration Wizard or WLST, this template helps you easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain in the Spring version.

You accomplish this task by adding the resources and services provided in the Avitek Medical Records Sample domain extension template to a base WebLogic Server domain.

For more information about the Avitek Medical Records sample application, see Sample Application and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Advanced Web Services Extension template. The template name is the name of the template as shown in the product list on the Configuration Wizard Select Domain Source and Select Extension Source screens.

Table 2-14 Avitek Medical Records Sample Domain (Spring) Information

Template Detail	Information
Template type	Extension
Template name	This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.
Template JAR file and location	`WL_HOME/common/templates/wls/medrec_spring.jar`
Template dependencies	Basic WebLogic Server Domain template

Parent topic: Avitek Medical Records Sample Domain Template (Spring Version)

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 for Spring.

Table 2-15 Resources Configured in an Avitek Medical Records Domain for Spring

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 is referenced in the template as `@SERVER_NAME`, and appears as `AdminServer` in the WebLogic Server Administration Console. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is enabled SSL port: 7002 For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the security realm provided in the base WebLogic Server domain.
Application deployments	`medrec`	Adds the sample medrec Enterprise application and targets it to the MedRecServer.
Application deployments	`physician`	Adds the sample physician Enterprise application and targets it to the MedRecServer.
Application deployments	`browser-starter`	Adds the browser-starter Web application and targets it to the MedRecServer.
Application deployment	`SamplesSearchWebApp`	Adds a sample search application and targets it to the Administration Server.
Deployed library	`jsf#1.2@1.2.9.0`	Adds the Java Server Faces Version 1.2 library and targets it to the MedRecServer.
Deployed library	`jstl#1.2.@1.2.0.1`	Adds the Java standard tagging (JSTL) Version 1.2 library and targets it to the MedRecServer.
Deployed library	`weblogic-spring#12.2.1.0.0@12.2.1.0.0`	Adds the WebLogic Spring Version 12.2.1 library and targets it to the MedRecServer.
Mail session	`mail/MedRecMailSession`	Adds this mail session.
JDBC data sources	`MedRecGlobalDataSourceXA`	Identifies the JDBC data source as a `MedRecGlobalDataSourceXA` system resource. Pool capacity (initial): 2 Pool capacity (maximum): 10 Protocol: Two Phase Commit
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 MedRecServer.
JMS Servers	`MedRecJMSServer`	Adds the JMS server as a `MedRec-jms` system resource and targets it to the MedRecServer.
Work Manager	`weblogic.wsee.mdb.DispatchPolicy`	Adds this Work Manager and targets it to the Administration Server. The Work Manager defines the thread pool resources.
WLDF system resource	`MedRecWLDF`	Adds this WLDF system resource, and targets it to the MedRecServer. The WLDF resource defines an instrumentation monitor for dye injection, and a harvester metric `(com.oracle.medrec.admin.AdminReport)`.
SAF Agent	`WsrmAgent`	Adds this store-and-forward agent, which uses the file store, `MedRecWseeFileStore`, and targets it to the MedRecServer.
JMS queues	`com.oracle.medrec.jms.RecordToCreateQueue` `com.oracle.medrec.jms.PatientNotificationQueue` `weblogic.wsee.DefaultQueue`	Adds these JMS queues to the JMS server, `MedRecWseeJMSServer`.
WLDF system resource	`MedRecWLDF`	Adds the WLDF system resource, WLDF harvester for NewUserCoun' and WLDR instrumentation monitors for Dye Injection, and targets them to the Administration Server.

Parent topic: Avitek Medical Records Sample Domain Template (Spring Version)

WebLogic Server Default Domain Extension Template

When you use the Configuration Wizard or WLST, this template helps you extend a base WebLogic Server domain to include resources required for a default WebLogic Server domain.

You accomplish this task by adding the resources and services provided in the WebLogic Server Default Domain extension template to a base WebLogic Server domain.

For more information about the samples that are supported in the WebLogic Server Examples domain, see Sample Application and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Server Default Domain Extension template.

Template Dependencies lists all templates that provide resources required by the WebLogic Server Default Domain extension template.

Table 2-16 WebLogic Server Default Domain Information

Template Detail	Information
Template type	Extension
Template name in the Configuration Wizard	This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.
Template JAR file and location	`WL_HOME/common/templates/wls/wls_default.jar`
Template dependencies	Basic WebLogic Server Domain template

Parent topic: WebLogic Server Default Domain Extension Template

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 2-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 is referenced in the template as `@SERVER_NAME`, and appears as AdminServer in the WebLogic Server Administration Console. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is disabled For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the security realm provided by the base WebLogic Server domain.
Application deployment	`SamplesSearchWebApp`	Adds the `SamplesSearchWebApp` application and targets it to the examplesServer Administration Server.
Application deployment	`mainWebApp`	Adds the `mainWebApp` application and targets it to the examplesServer Administration Server.
Application deployment	`examplesWebApp`	Adds the `examplesWebApp` application and targets it to the examplesServer Administration Server.
Application deployment	`entityBeanValidation`	Adds the `entityBeanValidation` application and targets it to the examplesServer Administration Server.
Application deployment	`jsfBeanValidation`	Adds the `jsfBeanValidation` application and targets it to the examplesServer Administration Server.
Application deployment	`cdi`	Adds the `cdi` application and targets it to the examplesServer Administration Server.
Application deployment	`asyncMethodOfEJB`	Adds the `asyncMethodOfEJB` Enterprise application and targets it to the examplesServer Administration Server.
Application deployment	`calendarStyledTimer`	Adds the `calendarStyledTimer` application and targets it to the examplesServer Administration Server.
Application deployment	`noInterfaceViewInWAR`	Adds the `noInterfaceViewInWAR` application and targets it to the examplesServer Administration Server.
Application deployment	`portableGlobalJNDIName`	Adds the `portableGlobalJNDIName` application and targets it to the examplesServer Administration Server.
Application deployment	`singletonBean`	Adds the `singletonBean` application and targets it to the examplesServer Administration Server.
Application deployment	`jaxrs`	Adds the `jaxrs` application and targets it to the examplesServer Administration Server.
Application deployment	`stockAdapter`	Adds the `stockAdapter` application and targets it to the examplesServer Administration Server.
Application deployment	`stockFrontEnd`	Adds the `stockFrontEnd` application and targets it to the examplesServer Administration Server.
Application deployment	`stockBackEnd`	Adds the `stockBackEnd` application and targets it to the examplesServer Administration Server.
Application deployment	`jdbcDataSource.war`	Adds the `jdbcDataSource.war` application and targets it to the examplesServer Administration Server.
Application deployment	`criteriaQuery`	Adds the `criteriaQuery` application and targets it to the examplesServer Administration Server.
Application deployment	`elementCollection`	Adds the `elementCollection` application and targets it to the examplesServer Administration Server.
Application deployment	`ajaxJSF`	Adds the `ajaxJSF` application and targets it to the examplesServer Administration Server.
Application deployment	`bookmarkingJSF`	Adds the `bookmarkingJSF` application and targets it to the examplesServer Administration Server.
Application deployment	`faceletsJSF`	Adds the `faceletsJSF` application and targets it to the examplesServer Administration Server.
Application deployment	`annotation`	Adds the `annotation` application and targets it to the examplesServer Administration Server.
Application deployment	`asyncServlet30`	Adds the `asyncServlet30` application and targets it to the examplesServer Administration Server.
Application deployment	`programmaticSecurity`	Adds the `progammaticSecurity` application and targets it to the examplesServer Administration Server.
Application deployment	`multipartFileHandling`	Adds the `multipartFileHandling` application and targets it to the examplesServer Administration Server.
Application deployment	`webFragment`	Adds the `webFragment` application and targets it to the examplesServer Administration Server.
Application deployment	`sample-echo`	Adds the `sample-echo` application and targets it to the examplesServer Administration Server.
Application deployment	`sample-cdi`	Adds the `sample-cdi` application and targets it to the examplesServer Administration Server.
Application deployment	`sample-auction`	Adds the `sample-auction` application and targets it to the examplesServer Administration Server.
Application deployment	`message-board`	Adds the `message-board` application and targets it to the examplesServer Administration Server.
Application deployment	`jaxrs-async`	Adds the `jaxrs-async` application and targets it to the examplesServer Administration Server.
Application deployment	`jaxrs-provider`	Adds the `jaxrs-provider` application and targets it to the examplesServer Administration Server.
Application deployment	`jaxrs-sse`	Adds the `jaxrs-sse` application and targets it to the examplesServer Administration Server.
JDBC system resource	`examples-demo`	Identifies this JDBC data source, which has the following configuration: JNDI name: `examples-dataSource-demoPool` Global transaction protocol: Two-Phase Commit The connection pool settings are: Initial capacity: 1 Maximum capacity: 10
JDBC system resource	`examples-demoXA`	Identifies this JDBC data source, which has the following configuration: JNDI Name: `examples-dataSource-demoXAPool` Global transaction protocol: Two-Phase Commit The connection pool settings are: Initial capacity: 2 Maximum capacity: 10
Deployed library	`jax-rs`	Adds the `jax-rs` library dependency to this domain.

Parent topic: WebLogic Server Default Domain Extension Template

WebLogic Server Examples Extension Template

When you use the Configuration Wizard or WLST, this template helps you easily extend a base WebLogic Server domain to create a WebLogic Server Examples domain.

You accomplish this task by adding the resources and services provided in WebLogic Server Examples extension template to a base WebLogic Server domain.

For more information about the samples that are supported in the WebLogic Server Examples domain, see Sample Application and Code Examples in Understanding Oracle WebLogic Server.

Parent topic: WebLogic Server Templates

Template Details

The following table provides basic information about the WebLogic Server Default Domain Extension template.

Template Dependencies lists all templates that provide resources required by the WebLogic Server Examples extension template, in the order in which they must be configured in the domain.

Table 2-18 WebLogic Server Examples Extension Information

Template Detail	Information
Template type	Extension
Template name in the Configuration Wizard	This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.
Template JAR file and location	`WL_HOME/common/templates/wls/wls_examples.jar`
Template dependencies	Basic WebLogic Server Domain template

Parent topic: WebLogic Server Examples Extension Template

Resources and Services Configured

In addition to the resources configured by the WebLogic Server Default Domain extension template (see Table 2-17), the WebLogic Server Examples extension template configures the resources and services listed in the following table.

Table 2-19 Additional Resources Configured by the WebLogic Server Examples Domain

Resource Type	Name	Notes
Administration Server	`AdminServer`	Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is `AdminServer`, unless changed during domain creation. The Administration Server is referenced in the template as `@SERVER_NAME`, and appears as `AdminServer` in the WebLogic Server Administration Console. The default configuration for the Administration Server is as follows: Listen address: All Local Addresses Listen port: 7001 SSL is disabled For information about naming the Administration Server during domain creation, see Resources and Services Configured in a Basic WebLogic Server Domain.
Security realm	`myrealm`	Uses the security realm provided by the base WebLogic Server domain.
Application deployment	`SamplesSearchWebApp`	Adds this application and targets it to the Administration Server.
Application deployment	`mainWebApp`	Adds this application and targets it to the Administration Server.
Application deployment	`examplesWebApp`	Adds this application and targets it to the Administration Server.
Application deployment	`sample-echo`	Adds this application and targets it to the Administration Server.
Application deployment	`sample-cdi`	Adds this application and targets it to the Administration Server.
Application deployment	`sample-auction`	Adds this application and targets it to the Administration Server.
Application deployment	`message-board`	Adds this application and targets it to the Administration Server.
Application deployment	`jaxrs-async`	Adds this application and targets it to the Administration Server.
Application Deployment	`jaxrs-provider`	Adds this application and targets it to the Administration Server.
Application deployment	`jaxrs-sse`	Adds this application and targets it to the Administration Server.
Application deployment	`batch10-joboperator`	Adds this application and targets it to the Administration Server.
Application deployment	`batch10-partition`	Adds this application and targets it to the Administration Server.
Application deployment	`cdi11-event`	Adds this application and targets it to the Administration Server.
Application deployment	`cdi11-transactional`	Adds this application and targets it to the Administration Server.
Application deployment	`cdi11-transaction-scoped`	Adds this application and targets it to the Administration Server.
Application deployment	`concurrency10-executor`	Adds this application and targets it to the Administration Server.
Application deployment	`concurrency10-schedule`	Adds this application and targets it to the Administration Server.
Application deployment	`concurrency10-threads`	Adds this application and targets it to the Administration Server.
Application deployment	`concurrency10-dynamicproxy`	Adds this application and targets it to the Administration Server.
Application deployment	`ejb32-lifecycle`	Adds this application and targets it to the Administration Server.
Application deployment	`ejb32-connector`	Adds this application and targets it to the Administration Server.
Application deployment	`ejb32-mdb`	Adds this application and targets it to the Administration Server.
Application deployment	`mailconnector`	Adds this application and targets it to the Administration Server.
Application deployment	`jsf22-contracts`	Adds this application and targets it to the Administration Server.
Application deployment	`jsf22-fileupload`	Adds this application and targets it to the Administration Server.
Application deployment	`jsf22-flows`	Adds this application and targets it to the Administration Server.
Application deployment	`jsf22-html5`	Adds this application and targets it to the Administration Server.
Application deployment	`jsonp-jaxrs`	Adds this application and targets it to the Administration Server.
Application deployment	`servlet31-httpupgrade`	Adds this application and targets it to the Administration Server.
Application deployment	`servlet31-nonblockread`	Adds this application and targets it to the Administration Server.
Application deployment	`servlet31-nonblockwrite`	Adds this application and targets it to the Administration Server.
Application deployment	`servlet31-sessionidchange`	Adds this application and targets it to the Administration Server.
Application deployment	`servlet31-uncoveredhttpmethod`	Adds this application and targets it to the Administration Server.
Application deployment	`beanvalidation11-cdi`	Adds this application and targets it to the Administration Server.
Application deployment	`jms-ejb`	Adds this application and targets it to the Administration Server.
Application deployment	`jms-servlet`	Adds this application and targets it to the Administration Server.
JDBC system resource	`examples-demo`	Identifies this JDBC data source, which has the following configuration: JNDI name: examples-dataSource-demoPool Global transaction protocol: Two-Phase Commit The database driver is configured as `org.apache.derby.jdbc.ClientDriver`.
JDBC system resource	`examples-demoXA`	Identifies this JDBC data source, which has the following configuration: JNDI name: examples-dataSource-demoXAPool Global transaction protocol: Two-Phase Commit The database driver is configured as `org.apache.derby.jdbc.ClientXADataSource`.
JMS Server	`examplesJMSServer`	Adds this JMS server as an `examples-jms` system resource and targets it to the Administration Server, as listed below: Persistent Store: exampleJDBCStore JMS Message log file: examplesJMSServer
JDBC store	`exampleJDBCStore`	Adds the JDBC store to be used as the persistent store for the examples-demo JDBC data source and the examplesJMSServer JMS server, and targets the store to the examplesServer Administration Server.
JMS system resources	`examples-jms`	Identifies the JMS servers, connection factories, queues, and topics to be used for JMS system resources.
JDBC system resource	`examples-demoXA-2`	Identifies this JDBC data source, which is targeted to the Administration Server and has the following configuration: Connection pool maximum: 100 Global transaction protocol: Two-Phase Commit This data source is mapped to the `examples-multiDataSource-demoXAPool` multi-data source.
JDBC system resource	`examples-multiDataSource-demoXAPool`	Identifies this JDBC multi-data source, which is targeted to the Administration Server. It is configured for failover, and maps to the `examples-oracleXA` and `examples-demo-XA-2` data sources.
File store	`WseeFileStore`	Adds the file store to be used as the persistent store for the `WSEEJMSServer` JMS server and the `ReliableWseeSAFAgent` SAF Agent. This file store is targeted to the examplesServer Administration Server.
JMS Server	`WseeJMSServer`	Adds this JMS server as an `examples-jms` system resource and targets it to the Administration Server. This server is configured to use the `WSeeFileStore` persistent store.
SAF agent	`ReliableWseeSAFAgent`	Adds this store-and-forward agent, which uses the `WseeFileStore` file store, and targets it to the Administration Server.
Work Manager	`weblogic.wsee.mdb.DispatchPolicy`	Adds this Work Manager, but does not target it to any servers.
JMS Connection Factories	`exampleTopic` `exampleTrader` `weblogic.examples.jms.QueueConnectionFactory` `weblogic.examples.ejb30.QueueConnectionFactory`	Adds these connection factories as examples-jms system resources and targets them to the examplesServer server.
JMS queues	`exampleQueue` `jms/MULTIDATASOURCE_MDB_QUEUE` `weblogic.examples.ejb30.ExampleQueue`	Adds these JMS queues to the examplesJMSServer JMS server.
JMS queue	`weblogic.wsee.wseeExamplesDestinationQueue` `WseeBufferedRequestQueue` `WseeBufferedResponseQueue`	Adds these JMS queues to the WseeJMSServer JMS server.
JMS topics	`exampleTopic` `quotes` `stockTopic`	Adds these JMS topics and targets them to the examplesJMSServer JMS server.

Parent topic: WebLogic Server Examples Extension Template