Domain Template Reference
This document provides general information about templates in the following topics:
This document also provides detailed reference information for each template:
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:
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.
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.
pack
command. Complete details are provided in Creating Templates and Domains Using the pack and unpack Commands.
The following table identifies the location of the predefined templates provided with your product installation, where WL_HOME
represents the product installation directory.
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.
Note: All the tools used to create or extend a domain leverage a common underlying infrastructure, referred to generically as the Configuration Wizard framework.
pack/unpack
commands, see Creating Templates and Domains Using the pack and unpack Commands.
The following table summarizes the predefined templates that may be provided in your product installation.
This section provides the following topics:
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.
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.
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.
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.
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.
Directory designated as the repository for any custom application files that you create. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
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). |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Domain template.
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,
|
||
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.
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.
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.
Directory serving as a placeholder for any custom application files that you create. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
File containing debug parameters for the domain. The default setting for all the parameters is false. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
Global non-XA JDBC data source module for the AquaLogic Service Bus domain. |
||
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). |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
Directory serving as a disk-based file store to store persistent messages and durable subscribers. |
||
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. |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain extended with the AquaLogic Service Bus extension template.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the file store to be used as the persistent store for the JMS server, |
||
Identifies the JDBC data source as a |
||
Identifies the JDBC data source and connection pool setup to be used for JDBC system resources and targets the resources to the Administration Server, |
||
Adds the JMS connection factory as a |
||
Adds the JMS connection factory as a |
||
Adds the JMS connection factory as a |
||
Adds the JMS server as a |
||
Identifies the JMS servers, connection factories, and queues to be used for JMS system resources, and targets the resources to the Administration Server, |
||
Uses the security realm provided by the base WebLogic Server domain. |
||
Adds the inbound Web Services security configuration, including the |
||
Adds the outbound Web Services security configuration, including the |
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 Examples and Tutorials for BEA WebLogic Server 9.1.
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.
Includes Avitek Medical Records split directory deployments. |
||
Includes sub-directories containing various files used to demonstrate extending the WebLogic Server Administration Console with a different look and feel. |
||
Includes sub-directories containing various files of the Avitek Medical Records applications in an exploded (unarchived) directory format. |
||
Directory and files containing the Avitek Medical Records online documentation. |
||
Includes sub-directories containing library files supporting the Avitek Medical Records sample. |
||
Ant build file used with corresponding scripts to set up a database for the Avitek Medical Records sample. |
||
|
SQL scripts used to set up different databases that can be used with the Avitek Medical Records sample. |
|
Includes sub-directories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, etc. |
||
Provides sample SSL protocol support for servers in the domain. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
Configures Avitek Medical Records Log4j implementation including the |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
Diagnostic descriptor information for the Avitek Medical Records diagnostics instrumentation. |
||
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). |
||
Global non-XA JDBC Data Source module for the Avitek Medical Records domain. |
||
Global XA JDBC Data Source module for the Avitek Medical Records domain. |
||
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). |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
Location where XML files containing fictitious patient names are uploaded by the Administration application of the Avitek Medical Records sample application. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
A |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Adds the |
||
Adds the |
||
Adds the |
||
Adds the |
||
Adds the file store and targets the store to the Administration Server, |
||
Adds the file store to be used as the persistent store for the JMS server, |
||
Adds the file store and targets the store to the Administration Server, |
||
Identifies the JDBC data source as a |
||
Identifies the JDBC data source as a |
||
Adds the JDBC store to be used with the JDBC data source, |
||
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, |
||
Adds the JMS server as a |
||
Adds the JMS server as a |
||
Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the Administration Server, |
||
Adds this store-and-forward agent, which uses the file store, |
||
Uses the security realm provided in the base WebLogic Server domain. |
||
Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server, |
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.
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.
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.
Directory serving as a placeholder for any custom application files that you create. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
Global XA JDBC Data Source module for the domain configured for conversational Web services. |
||
Global non-XA JDBC Data Source module for the domain configured for conversational Web services. |
||
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). |
||
Global JMS module for the domain configured for conversational Web services. |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Beehive and WebLogic Conversational Web Services extension templates.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Uses the XA JDBC data source provided by the WebLogic Conversational Web Services extension template. Identifies the XA JDBC data source as a |
||
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 |
||
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, |
||
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, |
||
Uses the JMS connection factory provided by the WebLogic Conversational Web Services extension template. Identifies the JMS connection factory as a |
||
Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, |
||
Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, |
||
Uses the JMS queue provided by the WebLogic Conversational Web Services extension template. Targets the JMS queue to the JMS server, |
||
Uses the JMS server provided by the WebLogic Conversational Web Services extension template. Identifies the JMS server as a |
||
Uses the JMS system resources provided by the WebLogic Conversational Web Services extension template. |
||
Uses the security realm provided by the base WebLogic Server domain. |
||
Adds the WebLogic Beehive Version 1.0 libraries provided by the WebLogic Beehive extension template, and targets them to the Administration Server, |
||
Adds the Apache Beehive NetUI Version 1.0 libraries provided by the WebLogic Beehive extension template, and targets them to the Administration Server, |
||
Adds the Java standard tagging (JSTL) Version 1.1 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, |
||
Adds the Apache Struts Version 1.1 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, |
||
Adds the Apache Struts Version 1.2 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, |
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.
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.
Directory serving as a placeholder for any custom application files that you create. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
Global XA JDBC Data Source module for the domain configured for conversational Web Services. |
||
Global non-XA JDBC Data Source module for the domain configured for conversational Web Services. |
||
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). |
||
Global JMS module for the domain configured for conversational Web Services. |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Conversational Web Services extension template.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Identifies the XA JDBC data source as a |
||
Identifies the non-XA JDBC data source as a |
||
Adds the JDBC store to be used with the JDBC data source, |
||
Identifies the JDBC data source and connection pool setups to be used for JDBC system resources and targets the resources to the Administration Server, |
||
Adds the JMS connection factory as a |
||
Adds the JMS server as a |
||
Identifies the JMS servers, connection factories, and queues to be used for JMS system resources. |
||
Uses the security realm provided by the base WebLogic Server domain. |
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.
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.
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.
Includes sub-directories containing style sheet and graphics files to support the online documentation. |
||
Includes source code and instructions for WebLogic Server examples. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
Global non-XA JDBC Data Source module for the WebLogic Server default domain. |
||
Global XA JDBC Data Source module for the WebLogic Server default domain. |
||
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). |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
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. |
||
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. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Server Default Domain extension template.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Adds the application and targets it to the Administration Server, |
||
Identifies the JDBC data source as an |
||
Identifies the JDBC data source as an |
||
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, |
||
Uses the security realm provided by the base WebLogic Server 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 Examples and Tutorials for BEA WebLogic Server 9.1.
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.
File that opens the WebLogic Server examples online documentation viewer. |
||
Directory and files supporting the WebLogic Server examples online documentation viewer. |
||
Includes sub-directories containing various Java and XML files used to build and work with WebLogic Server examples. |
||
Includes sub-directories containing various Java, XML, and HTML files used to work with WebLogic Server examples. |
||
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used. |
||
File containing initialization information for a PointBase JDBC database. |
||
Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively. |
||
File providing information about the directory, which initially serves as a placeholder for automatic deployments. |
||
Scripts used to set up the development environment on Windows and UNIX systems, respectively. |
||
Scripts used to start a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to start the PointBase console on Windows and UNIX systems, respectively. |
||
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively. |
||
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively. |
||
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration. |
||
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." |
||
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). |
||
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). |
||
Global non-XA JDBC Data Source module for the WebLogic Server Examples domain. |
||
Global XA JDBC Data Source modules for the WebLogic Server Examples domain. |
||
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). |
||
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. |
||
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. |
||
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. |
||
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
||
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. |
||
File used for creating user groups and roles that establish identity and access to domain resources. |
||
File used to create the |
||
File that contains the actual values to substitute for the tokens specified in the start scripts. |
||
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. |
||
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. |
||
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. |
||
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. |
||
Directory to be used for the file store for system resources. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Server Examples extension template.
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Adds the application and targets it to the Administration Server, |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Adds the file store to be used as the persistent store for the JMS server, |
||
Uses the non-XA and XA JDBC data sources provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Adds the XA JDBC data source and targets it to the Administration Server, |
||
Adds the XA JDBC data source and targets it to the Administration Server, |
||
Adds the XA JDBC multi data source and targets it to the Administration Server, |
||
Adds the JDBC store to be used as the persistent store for the JDBC data source, |
||
Uses the JDBC data source and connection pool setups provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
||
Adds the JDBC data source and connection pool setups and targets them to the Administration Server, |
||
Identifies the JMS servers, connection factories, queues, and topics to be used for JMS system resources. |
||
Adds the JMS connection factories as |
||
Adds the JMS server as an |
||
Adds the JMS server as an |
||
Adds the SAF agent and targets it to the Administration Server, |
||
Uses the security realm provided by the base WebLogic Server domain. |