This chapter describes the following WebLogic domain templates that are provided with your WebLogic Server installation. You can create or extend domains by selecting these templates on the Select Domain Source or Select Extension Source screens of the Oracle Fusion Middleware Configuration Wizard.
Table 2-1 Oracle WebLogic Server and Workshop for WebLogic Templates
| Template | Description |
|---|---|
|
Creates a base WebLogic Server domain. |
|
|
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 using WS-SecureConversation. |
|
Extends a domain to include the resources required to use SOAP over JMS transport for JAX-WS Web services. |
|
|
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. |
|
Extends the Basic 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 preconfigured, precompiled examples. Resources from this extension template are required for a WebLogic Server Examples domain. |
|
|
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. |
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. You can easily create or extend a domain by using these predefined templates with the Configuration Wizard or WLST.
The following table provides basic information about the Basic WebLogic Server Domain template. Template name is the name of the template as it is shown in the product list on the Configuration Wizard Select Domain Source and Select Extension Source screens.
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 |
|---|---|---|
|
Administration Server |
AdminServer |
The default configuration for the Administration Server is as follows:
When using the Configuration Wizard or WLST Offline to create a domain, 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 applying an extension template. For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating 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 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 |
This is the default (active) WebLogic Server security realm. The administration user account, |
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. You can easily create or extend a domain by using this predefined template with the Configuration Wizard or WLST.
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 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 |
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 |
|---|---|---|
|
Administration Server |
AdminServer |
The default configuration for the Administration Server is as follows:
When using the Configuration Wizard or WLST Offline to create a domain, 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 applying an extension template. For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Creating WebLogic Domains" Creating 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 |
wls_starter |
A sample Web application deployed to the starter domain. |
By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for advanced JAX-RPC Web services. You accomplish this by adding the resources and services provided in the WebLogic Advanced Web Services for JAX-RPC extension template to a base WebLogic Server domain.
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 |
Uncategorized |
|
Template name and version |
WebLogic Advanced Web Services for JAX-RPC Extension—12.1.2.0 |
|
Template Dependencies |
Base WebLogic Server domain template |
|
Template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice.jar |
|
Reconfiguration template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice_reconfig_version.jar |
|
Domain topology profiles |
None defined. The defined application service group is included for both Expanded and Compact domains. |
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:
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, WseeJmsServer. Queues are under JMSModules/module name, these are under 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. |
The WebLogic Advanced Web Services for JAX-WS extension template automatically configures the resources required to support the following advanced Web services features:
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 applying 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.
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 |
Uncategorized |
|
Template name and version |
WebLogic Advanced Web Services for JAX-WS Extension - 12.1.2.0 |
|
Template Dependencies |
Base WebLogic Server domain template |
|
Template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice_jaxws.jar |
|
Reconfiguration template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice_jaxws_reconfig_version.jar |
|
Domain topology profiles |
None defined. The defined application service group is included for both Expanded and Compact domains. |
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:
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. |
|
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 will be 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). |
|
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. |
|
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. |
|
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. |
By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required to use SOAP over JMS transport for JAX-WS Web services. You accomplish this by adding the resources and services provided in the WebLogic Advanced Web Services extension template to a base WebLogic Server domain.
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 |
Uncategorized |
|
Template name and version |
WebLogic JAX-WS SOAP/JMS Extension—12.1.2.0 |
|
Template Dependencies |
Base WebLogic Server domain template |
|
Template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice_soapjms.jar |
|
Reconfiguration template JAR file and location |
WL_HOME\common\templates\wls\wls_webservice_soapjms_reconfig_version.jar |
|
Domain topology profiles |
None defined. The defined application service group is included for both Expanded and Compact domains. |
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 |
|
JMS server management container. |
|
File store |
|
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 |
|
JMS module that defines the JMS resources needed for SOAP over JMS transport. |
|
JMS subdeployment |
|
JMS subdeployment for targeting the JMS resources to the |
|
JMS Connection Factory |
|
Default JMS connection factory used to create connections for SOAP over JMS transport. |
|
JMS Queue |
|
Default JMS request queue. |
|
JMS Queue |
|
Default JMS response queue. |
By 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.
For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.
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 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 |
The following table identifies the resources and services configured in a domain 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 Administration Console. The default configuration for the Administration Server is as follows:
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 |
browser-starter |
Adds the browser-starter Web application and targets it to the Administration Server. |
|
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 |
SamplesSearchWebApp |
Adds a sample search application and targets it to the Administration Server. |
|
JDBC Data Sources |
MedRecGlobalDataSourceXA |
Identifies the JDBC data source as a MedRecGlobalDataSourceXA system resource. |
|
JMS Queues |
com.oracle.medrec.jms.RecordToCreateQueue com.oracle.medrec.jms.PatientNotificationQueue weblogic.wsee.DefaultQueue |
Adds the JMS queue to the JMS server, MedRecWseeJMSServer. |
|
JMS Server |
MedRecJMSServer |
Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server |
|
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. |
|
Mail Session |
mail/MedRecMailSession |
Adds this mail session. |
|
SAF Agent |
WsrmAgent |
Adds this store-and-forward agent, which uses the MedRecWseeFileStorfile store, and targets it to the MedRecServer. |
|
Deployed library |
jsf1.2@1.2.9.0 |
Adds the Java Server Faces Version 1.2 libraries. |
|
Deployed library |
jstl1.2.@1.2.0.2 |
Adds the Java standard tagging (JSTL) Version 1.2 libraries. |
|
WLDF System Resource |
MedRecWLDF |
Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server. |
By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to create an Avitek Medical Records Sample domain in Spring. 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.
For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Understanding Oracle WebLogic Server.
The following table provides basic information about the WebLogic Advanced Web Services Extension template. Template name is the name of the template as it is 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 |
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 Administration Console. The default configuration for the Administration Server is as follows:
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 |
browser-starter |
Adds the browser-starter Web application and targets it to the MedRecServer. |
|
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 Deployment |
SamplesSearchWebApp |
Adds a sample search application and targets it to the Administration Server. |
|
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 Queues |
com.oracle.medrec.jms.RecordToCreateQueue com.oracle.medrec.jms.PatientNotificationQueue weblogic.wsee.DefaultQueue |
Adds these JMS queues to the JMS server, MedRecWseeJMSServer. |
|
JMS Servers |
MedRecJMSServer |
Adds the JMS server as a MedRec-jms system resource and targets it to the MedRecServer. |
|
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. |
|
Mail Session |
mail/MedRecMailSession |
Adds this mail session. |
|
SAF Agent |
WsrmAgent |
Adds this store-and-forward agent, which uses the file store, MedRecWseeFileStore, and targets it to the MedRecServer. |
|
Deployed library |
jsf1.2@1.2.9.0 |
Adds the Java Server Faces Version 1.2 library and targets it to the MedRecServer. |
|
Deployed library |
jstl1.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#10.3.6.0@10.3.6.0 |
Adds the WebLogic Spring Version 10.3.6 library and targets it to the MedRecServer. |
|
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). |
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 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.
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 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 |
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 Administration Console. The default configuration for the Administration Server is as follows:
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 |
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 |
multipartFileHandling |
Adds the multipartFileHandling application and targets it to the examplesServer Administration Server. |
|
Application Deployment |
apache_xbean.jar |
Adds the apache_xbean.jar application and targets it to the examplesServer Administration Server. |
|
Application Deployment |
annotation |
Adds the annotation application and targets it to the examplesServer Administration Server. |
|
JDBC System Resource |
examples-demo |
Identifies this JDBC data source, which has the following configuration:
The connection pool settings are:
|
|
JDBC System Resource |
examples-demoXA |
Identifies this JDBC data source, which has the following configuration:
The connection pool settings are:
|
|
Deployed library |
apache-xbean.jar |
Adds the apache-xbean.jar library dependency to this domain. |
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.
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.
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 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 |
|
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 Administration Console. The default configuration for the Administration Server is as follows:
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 application and targets it to the Administration Server. |
|
JMS Server |
examplesJMSServer |
Adds this JMS server as an examples-jms system resource and targets it to the 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. |
|
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. |
|
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. |
|
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 |
Adds this JMS queue to the WseeJMSServer JMS server. |
|
JMS Topics |
exampleTopic quotes stockTopic |
Adds these JMS topics and targets them to the examplesJMSServer JMS server. |
|
JDBC System Resource |
examples-oracleXA |
Identifies this JDBC data source, which has the following configuration:
The database driver is configured as oracle.jdbc.xa.client.OracleXADataSource. This data source is mapped to the examples-multiDataSource-demoXAPool multi data source. |
|
JDBC System Resource |
examples-demoXA-2 |
Identifies this JDBC data source, which is targeted to the Administration Server and has the following configuration:
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. |
|
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. |