The term template refers to a Java Archive (JAR) file that contains the files and scripts required to create or extend a domain. The types of template include:
Domain template—defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options.
The product installation includes a predefined Basic WebLogic Server Domain template. This template defines the core set of resources within a domain, including an Administration Server and basic configuration information. For more information on Basic WebLogic Server Domain template, see
Basic WebLogic Server Domain Template on page 1-13.
You can also create a custom domain template from an existing domain by using the Domain Template Builder or the pack command. By using the Domain Template Builder, you can also create a custom domain template from an existing template.
Extension template—defines the applications and services that you can add to an existing domain, including product component functionality and resources such as JDBC or JMS.
The product installation includes several predefined extension templates. For a summary of extension templates, see Template Summary.
You can also create a custom extension template from an existing domain or template using the Domain Template Builder.
Managed Server template – defines the subset of resources within a domain that are required to create a Managed Server domain directory on a remote machine. You can create a custom Managed Server template by using the pack command. Complete details are provided in Creating Templates and Domains Using the pack and unpack Commands.
Location of Installed Templates
The following table identifies the location of the predefined templates provided with your product installation, where BEA_HOME represents the product installation directory.
Table 1 Location of Templates
Type of Template
Directory Location
Domain
BEA_HOME\common\templates\domains
Extension
BEA_HOME\common\templates\applications
Template Tools
The following table identifies the tools with which you can create templates and the tools with which you can use templates to create or extend a domain.
Table 2 Template Tools
To . . .
Use this tool . . .
Create a new domain
Configuration Wizard
WLST Offline
unpack command
Extend an existing domain
Configuration Wizard
WLST Offline
Create a new Managed Server domain on a remote machine
unpack command
Create a domain template
Domain Template Builder
pack command
WLST Offline
Create an extension template
Domain Template Builder
Create a Managed Server template
pack command
Note:
All the tools used to create or extend a domain leverage a common underlying infrastructure, referred to as the Configuration Wizard framework.
The following tables summarizes the predefined templates that may be provided in your product installation.
Table 3 Summary of AquaLogic Template
Template
Filename
Description
AquaLogic Service Bus Extension Template
wlsb.jar
Extends the base WebLogic Server domain by providing the resources required to support AquaLogic Service Bus. For more information on the AquaLogic Service Bus Extension template, see the AquaLogic Service Bus Deployment Resources in the Deployment Guide.
Table 4 Summary of WebLogic Server, WebLogic Integration, Portal, and BEA Workshop for WebLogic Platform Templates
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.
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.
Extends a WebLogic Portal domain to allow for development and hosting of GroupSpace applications. This template extends a WebLogic Portal domain by adding additional Datasources and creating an additional database schema.
Extends a WebLogic Portal GroupSpace enabled domain by adding a preconfigured GroupSpace application to the domain.
WebLogic Personalization Extension
p13n.jar
Extends an existing WebLogic Server domain to add Weblogic Personalization functionality.
WebLogic Content Extension
content.jar
Extends an existing WebLogic Server domain to add WebLogic Content Management functionality.
WebLogic Simple Producer (Portal) Extension
wsrp-simple-producer.jar
Extends an existing WebLogic domain to add WebLogic Simple Producer (Portal) functionality. Domains extended with this template support WebLogic Simple Producer functionality. Use this template to enable the development of WebLogic Simple Producer applications in existing domains.
WebLogic Server resources must be set up in your domain before you can add resources from an extension template. When you select an extension template, the Configuration Wizard framework checks to make sure the required resources are available for you.
Relationships Between Templates
You can create a base WebLogic domain by using the predefined Basic WebLogic Server domain template, or you can create a Basic WebLogic domain and extend it incrementally using the extension templates. The following table shows the relationships between the templates and the domains created.
Table 5 Relationships Between Templates
This type of domain . . .
Requires resources from these templates . . .
AquaLogic Service Bus
For more information on the AquaLogic Service Bus Extension template, see the AquaLogic Service Bus Deployment Resources in the Deployment Guide.
Avitek Medical Records Sample
Basic WebLogic Server Domain template, wls.jar + Avitek Medical Records Sample Domain extension template, medrec.jar
WebLogic Server (base)
Basic WebLogic Server Domain template, wls.jar
WebLogic Server Default
Basic WebLogic Server Domain template, wls.jar + WebLogic Server Default Domain extension template, wls_default.jar
WebLogic Server Examples
Basic WebLogic Server Domain template, wls.jar + WebLogic Server Default Domain extension template, wls_default.jar + WebLogic Server Examples extension template, wls_examples.jar
WebLogic Integration Worklist Extension
Basic WebLogic Server Domain, wls.jar + WebLogic Advanced Web Services Extension, wls_webservice.jar, + BEA Workshop for WebLogic Extension, workshop_wl_10_2.jar + WebLogic Personalization Extension, p13n.jar + Worklist Extension Template, wli_worklist.jar.
Basic WebLogic Server Domain, wls.jar + Advanced Web Services Extension, wls_webservice.jar + BEA Workshop for WebLogic Extension, workshop_wl.jar
Workshop for WebLogic Platform 10.2
Basic WebLogic Server Domain, wls.jar + Advanced Web Services Extension, wls_webservice.jar + Workshop for WebLogic 10.2, workshop_wl_10_2.jar
Files Typically Included in a Template
The basic files included in any template are config.xml and template-info.xml. There are additional files in the predefined templates, and a domain is created or extended based on these files. The following table describes the files typically included in a domain or extension template.
Table 6 Files Included in a Template
Filename
Description
product component files
Various files used to complete the domain setup for a specific BEA product component. Such files may provide information for security and default database settings.
*-jdbc.xml
Sets up or extends a domain with JDBC system resources required by a product component. In a template, the *-jdbc.xml files must be located in the config\jdbc directory.
*-jms.xml
Sets up or extends a domain with JMS system resources required by a product component. In a template, the *-jms.xml files must be located in the config\jms directory.
clusters.script
Used to modify the Configuration Wizard framework’s default auto-configuration of a cluster. By default, resources are targeted to the cluster. You can unassign a resource from the cluster and then assign it to another component. To specify a target, you can use the following replacement variables:
%AManagedServer% — Any Managed Server
%AllManagedServers% — Comma-separated list of all Managed Servers
You must use the name attribute of an object that is to be replaced.
You can use an asterisk (*) as a wildcard for “All.”
In a template, the clusters.script file must be located in the script directory.
Note:
AquaLogic Service Bus overrides this behavior. For more information on the AquaLogic Service Bus Extension template, see the AquaLogic Service Bus Deployment Resources in the Deployment Guide.
config.xml
Sets up or extends the domain configuration. In a template, the config.xml file must be located in the config directory.
jdbc.index
Identifies the locations of SQL scripts used to set up a database. The file lists the scripts in the order in which they must be run. If the scripts are not contained in the template, but are located in the product installation directory, that directory can be represented by a tilde ( ~ ) in the pathname for the scripts, as shown in the following example:
Specifically, the tilde represents the directory path identified by the $USER_INSTALL_DIR$ variable in the stringsubs.xml file.
In a template, a jdbc.index file must be located in the _jdbc_\dbtype\dbversion directory, where dbtype is the type of database, such as Oracle, and dbversion is the database version, such as 9i.
In addition to listing the SQL files related to a data source, the jdbc.index file contains information about the categories associated with the data source. The default dbCategories that are available are:
‘Drop/Create P13N Database Objects’ category associated with the p13nDataSource data source, which is a part of the p13n.jar domain template
‘Drop/Create Portal Database Objects’ category associated with the "p13nDataSource" data source, which is a part of the wlp.jar domain template
‘Drop/Create GroupSpace Database Objects’ category associated with the appsGroupSpaceDataSource data source, which is a part of the wlp_groupspacedb.jar domain template
All these template jar files are located in the BEA_HOME\wlserver_10.2\common\templates\applications directory.
security.xml
Used to create user groups and roles that establish identity and access to domain resources. You can create the default Admin user only through the security.xml in a domain template. However, you can create user groups and roles through the security.xml included in either a domain or an extension template.
startmenu.xml
Used to create Windows start menu entries.
startscript.xml
Used to create the *.cmd and *.sh files that are placed into a domain’s root and bin directories.
stringsubs.xml
Identifies string substitution values and files that will receive string substitutions during domain creation or extension. The files that will receive string substitutions must already be prepared with replacement variables. During domain creation or extension, the Configuration Wizard framework runs macros to replace variables with the appropriate string substitution, using information from BEA_HOME\common\lib\macrorules.xml, where BEA_HOME is the product installation directory.
template-info.xml
Provides template identification information, such as the template name, software version, type of template (domain or application), author, description, and so on.
Basic WebLogic Server Domain Template
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.
Generated Domain Output
The Basic WebLogic Server Domain template allows you to create a simple WebLogic Server domain. By default, when using the Basic WebLogic Server Domain template, you generate a domain that contains only the required components: an Administration Server and a single administrative user. Any required applications must be created and configured within the domain.
The following table defines the default directory structure and files generated by the Basic WebLogic Server Domain template. Unless otherwise specified, by default, the Configuration Wizard framework creates the domain in the BEA_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
Table 7 Output Generated from the Basic WebLogic Server Domain Template
Directory
File
Description
user_projects\applications\base_domain\
n.a.
Directory designated as the repository for any custom application files that you create.
user_projects\domains\base_domain\
fileRealm.properties
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
autodeploy\
readme.txt
File providing information about the directory, which initially serves as a placeholder for automatic deployments.
bin\
setDomainEnv.cmd
setDomainEnv.sh
Scripts used to set up the development environment on Windows and UNIX systems, respectively.
startManagedWebLogic.cmd
startManagedWebLogic.sh
Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
startPointBaseConsole.cmd
startPointBaseConsole.sh
Scripts used to start the PointBase console on Windows and UNIX systems, respectively.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
stopManagedWebLogic.cmd
stopManagedWebLogic.sh
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
stopWebLogic.cmd
stopWebLogic.sh
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
config\
config.xml
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
config\deployments\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application’s staging mode is “staged.”
config\diagnostics\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
config\jdbc\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
config\jms\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
config\lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server’s Java virtual machine starts.
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain’s current realm.
config\startup\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
console-ext\
readme.txt
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
init-info\
domain-info.xml
File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
security.xml
File used for creating user groups and roles that establish identity and access to domain resources.
startscript.xml
File used to create the *.cmd and *.sh files that are placed into the domain’s root and bin directories.
tokenValue.properties
File that contains the actual values to substitute for the tokens specified in the start scripts.
lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder for the domain’s libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
security\
DefaultAuthenticatorInit.ldift
DefaultRoleMapperInit.ldift
XACMLRoleMapperInit.ldift
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
Note:
WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security at http://e-docs.bea.com/wls/docs100/secintro/archtect.html#archtect_0111.
SerializedSystemIni.dat
File containing encrypted security information.
servers\AdminServer\security\
boot.properties
File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode.
This file enables you to bypass the prompt for user name and password during a server’s startup cycle. For more information, see “Provide User Credentials to Start and Stop Servers” in Starting and Stopping Servers in Managing Server Startup and Shutdown at
File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.
Resources and Services Configured for WebLogic Server Domain Template
The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Domain template.
Table 8 Resources Configured in a Basic WebLogic Server Domain
Resource Type
Name
Notes
Administration Server
AdminServer
When using the Configuration Wizard or WLST Offline to create a new domain, and you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name later when applying an extension template.
For information about customizing the Administration Server name while creating a domain with WLST Offline, see “Creating and Configuring WebLogic Domains Using WLST Offline” in WebLogic Scripting Tool.
The following sample WLST Offline code snippet shows how to change the default Administration Server name, AdminServer, to MedRecServer.
#----------------------------------- #Read the Basic WebLogic Server Domain template readTemplate('d:/bea/wlserver_10.2/common/templates/domains/wls.jar') #Change the Administration Server name. cd('Servers/AdminServer') set('Name', 'MedRecServer') #-----------------------------------
Security realm
myrealm
n.a.
WebLogic Beehive Extension Template
By 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 Advanced Web Services extension templates to a base WebLogic Server domain.
Generated Domain Output
The following table defines the default directory structure and files generated after applying the WebLogic Beehive and WebLogic Advanced Web Services extension templates to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
Table 9 Base Domain After Applying the WebLogic Beehive and WebLogic Advanced Web Services Extension Templates
Directory
File
Description
user_projects\applications\base_domain\
n.a.
Directory serving as a placeholder for any custom application files that you create.
user_projects\domains\base_domain\
fileRealm.properties
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
pointbase.ini
File containing initialization information for a PointBase JDBC database.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
URLs.dat
File containing the URL for the JDBC database.
autodeploy\
readme.txt
File providing information about the directory, which initially serves as a placeholder for automatic deployments.
bin\
setDomainEnv.cmd
setDomainEnv.sh
Scripts used to set up the development environment on Windows and UNIX systems, respectively.
startManagedWebLogic.cmd
startManagedWebLogic.sh
Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
startPointBaseConsole.cmd
startPointBaseConsole.sh
Scripts used to start the PointBase console on Windows and UNIX systems, respectively.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
stopManagedWebLogic.cmd
stopManagedWebLogic.sh
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
stopWebLogic.cmd
stopWebLogic.sh
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
config\
config.xml
File containing the configuration information used by the Administration Server. For more information, see Domain Configuration Files in Understanding Domain Configuration.
config\deployments\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application’s staging mode is “staged.”
config\diagnostics\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
config\jdbc\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JDBC modules that can be configured directly from JMX (as opposed to JSR-88).
cgDataSource-jdbc.xml
Global XA JDBC Data Source module for the domain configured for conversational Web services.
cgDataSource-nonXA-jdbc.xml
Global non-XA JDBC Data Source module for the domain configured for conversational Web services.
config\jms\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
conversational-jms.xml
Global JMS module for the domain configured for conversational Web services.
config\lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server’s Java virtual machine starts.
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain’s current realm.
config\startup\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
console-ext\
readme.txt
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
init-info\
domain-info.xml
File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
security.xml
File used for creating user groups and roles that establish identity and access to domain resources.
startscript.xml
File used to create the *.cmd and *.sh files that are placed into the domain’s root and bin directories.
tokenValue.properties
File that contains the actual values to substitute for the tokens specified in the start scripts.
lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder for the domain’s libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
security\
DefaultAuthenticatorInit.ldift
DefaultRoleMapperInit.ldift
XACMLRoleMapperInit.ldift
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
Note:
WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security at http://e-docs.bea.com/wls/docs100/secintro/archtect.html#archtect_0111.
SerializedSystemIni.dat
File containing encrypted security information.
servers\AdminServer\security\
boot.properties
File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode.
This file enables you to bypass the prompt for user name and password during a server’s startup cycle. For more information, see “Provide User Credentials to Start and Stop Servers” in Starting and Stopping Servers in Managing Server Startup and Shutdown at
File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.
Resources and Services Configured
The following table identifies the resources and services configured in a domain extended with the WebLogic Beehive and WebLogic Advanced Web Services extension templates.
Table 10 Resources Configured in a WebLogic Beehive Domain
Resource Type
Name
Extension Result
Administration Server
AdminServer
Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is cgServer.
Uses the security realm provided by the base WebLogic Server domain.
Libraries Deployed
beehive-netui-1.0#1.0@1.0
Adds the Apache Beehive NetUI Version 1.0 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, AdminServer. These libraries support pageflow development, and depend on the libraries contained in struts-1.1.war and weblogic-beehive-1.0.ear.
struts-1.1#1.1@1.0
Adds the Apache Struts Version 1.1 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, AdminServer.
struts-1.2#1.2@1.0
Adds the Apache Struts Version 1.2 libraries provided by the WebLogic Beehive extension template and targets them to the Administration Server, AdminServer.
WebLogic Advanced Web Services Extension Template
By using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for advanced 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.
Generated Domain Output
The following table defines the default directory structure and files generated after applying the WebLogic Advanced Web Services extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
Table 11 Base Domain After Applying the WebLogic Advanced Web Services Extension Template
Directory
File
Description
user_projects\applications\base_domain\
n.a.
Directory serving as a placeholder for any custom application files that you create.
user_projects\domains\base_domain\
fileRealm.properties
File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.
pointbase.ini
File containing initialization information for a PointBase JDBC database.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
URLs.dat
File containing the URL for the JDBC database.
autodeploy\
readme.txt
File providing information about the directory, which initially serves as a placeholder for automatic deployments.
bin\
setDomainEnv.cmd
setDomainEnv.sh
Scripts used to set up the development environment on Windows and UNIX systems, respectively.
startManagedWebLogic.cmd
startManagedWebLogic.sh
Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
startPointBaseConsole.cmd
startPointBaseConsole.sh
Scripts used to start the PointBase console on Windows and UNIX systems, respectively.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
stopManagedWebLogic.cmd
stopManagedWebLogic.sh
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
stopWebLogic.cmd
stopWebLogic.sh
Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.
config\
config.xml
File containing the configuration information used by the “Domain Configuration Files” Administration Server. For more information, see in Understanding Domain Configuration.
config\deployments\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for staging an application when the application’s staging mode is “staged.”
config\diagnostics\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing the system modules associated with instrumentation in the WebLogic Diagnostic Framework (WLDF).
config\jms\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
wseejmsmodule-jms.xml
Global JMS module for the domain configured for advanced Web Services.
config\lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server’s Java virtual machine starts.
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain’s current realm.
config\startup\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
console-ext\
readme.txt
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
init-info\
domain-info.xml
File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
security.xml
File used for creating user groups and roles that establish identity and access to domain resources.
startscript.xml
File used to create the *.cmd and *.sh files that are placed into the domain’s root and bin directories.
tokenValue.properties
File that contains the actual values to substitute for the tokens specified in the start scripts.
lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder for the domain’s libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.
security\
DefaultAuthenticatorInit.ldift
DefaultRoleMapperInit.ldift
XACMLRoleMapperInit.ldift
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.
Note:
WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security at http://e-docs.bea.com/wls/docs100/secintro/archtect.html#archtect_0111
SerializedSystemIni.dat
File containing encrypted security information.
servers\AdminServer\security\
boot.properties
File containing server startup properties, including the user name and password required to boot the server (in encrypted format). It is generated only when you select development startup mode.
This file enables you to bypass the prompt for user name and password during a server’s startup cycle. For more information, see “Provide User Credentials to Start and Stop Servers” in Starting and Stopping Servers in Managing Server Startup and Shutdown at
File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.
Resources and Services Configured
The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services extension template.
Table 12 Resources Configured in a WebLogic Advanced Web Services Domain
Resource Type
Name
Extension Result
Administration Server
AdminServer
Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is cgServer.
Adds the JMS queue to the JMS server, WseeJmsServer.
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.
Security realm
myrealm
Uses the security realm provided by the base WebLogic Server domain.
Avitek Medical Records Sample Domain Template
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.
The following table defines the default directory structure and files generated after applying the Avitek Medical Records Sample Domain extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_HOME\user_projects\domains\base_domain directory. If you modify the default configuration settings, the output directory structure may be different from the structure described here.
Table 13 Base Domain After Applying the Avitek Medical Records Sample Extension Template
Directory
File
Description
user_projects\applications\base_domain\
build\
Various
Includes Avitek Medical Records split directory deployments.
console-extension\
Various
Includes sub-directories containing various files used to demonstrate extending the WebLogic Server Administration Console with a different look and feel.
dist\
Various
Includes sub-directories containing various files of the Avitek Medical Records applications in an exploded (unarchived) directory format.
