2 WebLogic Server Templates

This chapter describes the following WebLogic domain templates that are provided with your WebLogic Server installation. You can create or extend domains by selecting these templates on the Select Domain Source or Select Extension Source screens of the Oracle Fusion Middleware Configuration Wizard.

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 to create the Avitek Medical Records sample domain for Spring. This domain is a WebLogic Server sample application suite that demonstrates all aspects of the J2EE platform.

Extends the Basic WebLogic Server domain with a web application designed to guide new users through an introduction to WebLogic Server. When running the web application, users can review informative content on various topics, including highlights of WebLogic Server functionality. From the web application, users can also run several preconfigured, precompiled examples. Resources from this extension template are required for a WebLogic Server Examples domain.

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.

Template Details

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

Table 2-2 Basic WebLogic Server Domain Template Information

Template Detail

Information

Template type

Domain

Template name

Basic WebLogic Server Domain

Template JAR file and location

WL_HOME\common\templates\domain\wls.jar

Template Dependencies

None

Resources and Services Configured in a Basic WebLogic Server Domain

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

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

Resource Type

Name

Notes

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

Listen address: All Local Addresses

Listen port: 7001

SSL is disabled

When using the Configuration Wizard or WLST Offline to create a domain, if you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name later when applying an extension template.

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

For information about customizing the Administration Server name while creating a domain with WLST Offline, see "Creating and Configuring WebLogic Domains Using WLST Offline" in Oracle WebLogic Scripting Tool.

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

This is the default (active) WebLogic Server security realm. The administration user account, weblogic, is configured in this security realm.

Generated Domain Output

The Basic WebLogic Server Domain template enables 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 MW_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.

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.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\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."

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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 Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

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.

WebLogic Server Starter Domain Template

Your product installation also provides one predefined WebLogic Server domain template. This template contains the default domain configuration settings and an application that provides a Welcome page to help you get started. You can easily create or extend a domain by using this predefined template with the Configuration Wizard or WLST.

Template Details

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

Table 2-5 WebLogic Server Starter Domain Template Information

Template Detail

Information

Template type

Domain

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\domain\wls_starter.jar

Template Dependencies

None

Resources and Services Configured in a WebLogic Server Starter Domain

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

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

Resource Type

Name

Notes

Administration Server

AdminServer

The default configuration for the Administration Server is as follows:

Listen address: All Local Addresses

Listen port: 7001

SSL is disabled

When using the Configuration Wizard or WLST Offline to create a domain, if you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name later when applying an extension template.

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

Generated Domain Output

The Starter WebLogic Server Domain template enables 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 Starter WebLogic Server Domain template. Unless otherwise specified, by default, the Configuration Wizard framework creates the domain in the MW_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.

user_projects\applications\target\wl_starter\

wls_starter.war

The web application files deployed to the starter domain.

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.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\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."

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\config\jms\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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 Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

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.

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer.

The default configuration for the Administration Server is as follows:

Queues are under JMSModules/module name, these are under WseeJMSModule

JMS Queues

WseeCallbackQueue

Adds the JMS queue to the JMS server, WseeJmsServer.

JMS Server

WseeJmsServer

Adds the JMS server as a system resource and targets it to the Administration Server, AdminServer.

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 MW_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.

user_projects\applications\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\applications\base_domain\

URLs.dat

File containing the URL for the JDBC database.

user_projects\applications\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\applications\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the domain environment on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\applications\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\applications\base_domain\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."

user_projects\applications\base_domain\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).

user_projects\applications\base_domain\config\jms

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).

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.

user_projects\applications\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\applications\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\applications\base_domain\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.

user_projects\applications\base_domain\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.

user_projects\applications\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\applications\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\applications\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\applications\base_domain\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.

user_projects\applications\base_domain\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 Security for Oracle WebLogic Server.

user_projects\applications\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\applications\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

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.

WebLogic Advanced Web Services for JAX-WS Extension Template

The WebLogic Advanced Web Services for JAX-WS extension template automatically configures the resources required to support the following advanced Web services features:

Web services atomic transactions

Security using WS-SecureConversation

Note:

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

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in this extension template is cgServer.

The default configuration for the Administration Server is as follows:

Adds the JMS server as a system resource and targets it to the Administration Server.

File Store

WseeJaxwsFileStore

Adds the file store to be used as the persistent store for the WseeJaxwsJmsServer JMS server. This file store is targeted to the Administration Server.

JMS System Resource

WseeJaxwsJmsModule

Defines a distributed destination for the cluster. All associated targets will be used to support JAX-WS Web services. The subdeployment name is WseeJaxwsJmsServerSub.

Note: By default, a weighted distributed destination (WDD) is configured. In a clustered environment, Oracle strongly recommends that you upgrade the destination to a uniform distributed destination (UDD).

Adds these JMS queues to the JMS server, and targets them to WseeJaxwsJmsServer.

These queues are reserved for future use.

SAF Agent

ReliableWseeJaxwsSAFAgent

Adds this store-and-forward agent, which uses the WseeJaxwsFileStore, and targets it to the Administration Server. The SAF agent controls receipt and handling of reliable messages.

Work Manager

weblogic.wsee.jaxws.mdb.DispatchPolicy

Adds this Work Manager and targets it to the Administration Server. The Work Manager defines the thread pool resources.

Logical store

WseeStore

Adds this logical store, which specifies BufferingQueueJndiName as weblogic.wsee.BufferedRequestQueue.

This logical store is reserved for future use.

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.

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\applications\medrec.jar

Template Dependencies

Basic WebLogic Server Domain template

Resources and Services Configured

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

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

Table 2-14 Resources Configured in an Avitek Medical Records Domain

Resource Type

Name

Extension Result

Administration Server

AdminServer

Uses the Administration Server provided in the Base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is MedRecServer.

The default configuration for the Administration Server is as follows:

Adds the browser-starter Web application and targets it to the Administration Server.

Application Deployments

medrec

Adds the sample medrec Enterprise application and targets it to the Administration Server.

Application Deployments

physician

Adds the sample physician Enterprise application and targets it to the Administration Server.

JDBC Data Sources

MedRecGlobalDataSourceXA

Identifies the JDBC data source as a MedRecGlobalDataSource system resource.

JMS Queues

com.bea.medrec.jms.RecordToCreateQueue

com.bea.medrec.jms.PatientNotificationQueue

weblogic.wsee.DefaultQueue

Adds the JMS queue to the JMS server, MedRecWseeJMSServer.

JMS Server

MedRecJMSServer

Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server.

JMS System Resources

MedRec-jms

Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the Administration Server.

Mail Session

mail/MedRecMailSession

Adds this mail session.

SAF Agent

WsrmAgent

Adds this store-and-forward agent, which uses the MedRecWseeFileStorfile store, and targets it to the Administration Server.

Deployed library

jsf1.2@1.2.9.0

Adds the Java Server Faces Version 1.2 libraries.

Deployed library

jstl1.2.@1.2.1.0

Adds the Java standard tagging (JSTL) Version 1.2 libraries.

WLDF System Resource

MedRecWLDF

Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server.

Generated Domain Output

The following table defines the default directory structure and files generated after applying the Avitek Medical Records Sample Domain extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_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.

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\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."

user_projects\domains\base_domain\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).

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).

user_projects\domains\base_domain\config\jms\

MedRec-jms.xml

Global JMS module for the Avitek Medical Records domain.

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\console-ext\

diagnostics-console-extension.jar

File used to demonstrate an extension to the WebLogic Server Administration Console that shows diagnostics features.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.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 Security for Oracle WebLogic Server.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

Avitek Medical Records Sample Domain Template (Spring Version)

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

Template Details

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

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

Template Detail

Information

Template type

Extension

Template name

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\applications\medrec_spring.jar

Template Dependencies

Basic WebLogic Server Domain template

Resources and Services Configured

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

Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is MedRecServer.

The default configuration for the Administration Server is as follows:

Adds the browser-starter Web application and targets it to the Administration Server.

Application Deployments

medrec

Adds the sample medrec Enterprise application and targets it to the Administration Server.

Application Deployments

physician

Adds the sample physician Enterprise application and targets it to the Administration Server.

JDBC Data Sources

MedRecGlobalDataSourceXA

Identifies the JDBC data source as a MedRecGlobalDataSource system resource.

Pool capacity (initial): 2

Pool capacity (maximum): 10

Protocol: Two Phase Commit

JMS Queues

com.bea.medrec.jms.RecordToCreateQueue

com.bea.medrec.jms.PatientNotificationQueue

weblogic.wsee.DefaultQueue

Adds these JMS queues to the JMS server, MedRecWseeJMSServer.

JMS Servers

MedRecJMSServer

Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server.

JMS System Resources

MedRec-jms

Adds the JMS servers, connection factories, and queues to be used as JMS system resources, and targets the resources to the Administration Server.

Mail Session

mail/MedRecMailSession

Adds this mail session.

SAF Agent

WsrmAgent

Adds this store-and-forward agent, which uses the file store, MedRecWseeFileStore, and targets it to the Administration Server.

Deployed library

jsf1.2@1.2.9.0

Adds the Java Server Faces Version 1.2 library and targets it to the Administration Server.

Deployed library

jstl1.2.@1.2.1.0

Adds the Java standard tagging (JSTL) Version 1.2 library and targets it to the Administration Server.

Deployed library

weblogic-spring#10.3.2.0@10.3.2.0

Adds the WebLogic Spring Version 10.3.2 library and targets it to the Administration Server.

WLDF System Resource

MedRecWLDF

Adds this WLDF system resource, and targets it to the Administration Server. The WLDF resource defines an instrumentation monitor for dye injection, and a harvester metric (com.oracle.medrec.admin.AdminReport).

Generated Domain Output

The following table defines the default directory structure and files generated after applying the Avitek Medical Records Sample Domain extension template for Spring to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_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.

WebLogic Server Default Domain Extension Template

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

Note:

Applying the WebLogic Server Default Domain extension template to a base WebLogic domain is a prerequisite to using the WebLogic Server Examples extension template.

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

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\applications\wls_webservice.jar

Template Dependencies

Basic WebLogic Server Domain template

Resources and Services Configured

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

Table 2-20 Resources Configured in a WebLogic Server Default Domain

Resource Type

Name

Extension Result

Administration Server

AdminServer

Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is examplesServer.

The default configuration for the Administration Server is as follows:

Adds the mainWebApp application and targets it to the examplesServer Administration Server.

Application Deployment

examplesWebApp

Adds the examplesWebApp application and targets it to the examplesServer Administration Server.

Application Deployment

ejb20BeanMgedEar

Adds the ejb20BeanMgedEar application and targets it to the examplesServer Administration Server.

Application Deployment

ejb30

Adds the ejb30 application and targets it to the examplesServer Administration Server.

Application Deployment

stockEar

Adds the stockear application and targets it to the examplesServer Administration Server.

Application Deployment

asyncServletEar

Adds the asyncServletEar Enterprise application and targets it to the examplesServer Administration Server.

Application Deployment

extServletAnnotationsEar

Adds the extServletAnnotationsEar application and targets it to the examplesServer Administration Server.

Application Deployment

jdbcRowSetsEar

Adds the jdbcRowSetsEar application and targets it to the examplesServer Administration Server.

Application Deployment

jspSimpleTagEar

Adds the jspSimpleTagEar application and targets it to the examplesServer Administration Server.

Application Deployment

webservicesJwsSimpleEar

Adds the webservicesJwsSimpleEar application and targets it to the examplesServer Administration Server.

Application Deployment

xmlBeanEar

Adds the xmlBeanEar application and targets it to the examplesServer Administration Server.

JDBC System Resource

examples-demo

Identifies this JDBC data source, which has the following configuration:

JNDI name: examples-dataSource-demoPool

Global transaction protocol: Two Phase Commit

The connection pool settings are:

Initial capacity: 1

Maximum capacity: 10

JDBC System Resource

examples-demoXA

Identifies this JDBC data source, which has the following configuration:

JNDI Name: examples-dataSource-demoXAPool

Global transaction protocol: Two Phase Commit

The connection pool settings are:

Initial capacity: 2

Maximum capacity: 10

Deployed library

pubsub#1.0@1.4.0.0

Adds the HTTP PublisherSubscriber Version 1.4.0.0 library and targets it to the examplesServer Administration Server.

Deployed library

weblogic-sca#1.0@1.0.0.0

Adds the WebLogic SCA Version 1.0.0.0 library and targets it to the examplesServer Administration Server.

Deployed library

apache-xbean.jar

Adds the apache-xbean.jar library dependency to this domain.

Generated Domain Output

The following table defines the default directory structure and files generated after applying the WebLogic Server Default Domain extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the MW_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 the style sheet and graphics files to support the online documentation.

user_projects\applications\base_domain\server\examples\build\

Various

Includes WebLogic Server examples deployments.

user_projects\applications\base_domain\server\examples\src\

Various

Includes source code and instructions for WebLogic Server examples.

user_projects\domains\base_domain\

fileRealm.properties

File containing ACLs, users, and groups that can be used for the default security realm when Compatibility security is used.

user_projects\domains\base_domain\

setExamplesEnv.cmd

setExamplesEnv.sh

Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogicEx.cmd

startWebLogicEx.sh

Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\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."

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\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).

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).

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

DefaultRoleMapperInit.ldift

XACMLAuthorizerInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

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.

WebLogic Server Examples Extension Template

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

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

Template Details

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

Table 2-22 WebLogic Server Examples Extension Information

Template Detail

Information

Template type

Extension

Template name in Configuration Wizard

This template is not available from the list of products in the Configuration Wizard. You can select it only by using the Browse option on the Select Domain Source or Select Extension Source screens, and navigating to the JAR file location.

Template JAR file and location

WL_HOME\common\templates\applications\wls_examples.jar

Template Dependencies

Basic WebLogic Server Domain template

+ WebLogic Server Default Domain Extension template

Resources and Services Configured

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

Uses the Administration Server provided in the Basic WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is examplesServer.

The default configuration for the Administration Server is as follows:

Adds this JMS server as an examples-jms system resource and targets it to the Administration Server.

Persistent Store: exampleJDBCStore

JMS Message log file: examplesJMSServer

JMS Server

WseeJMSServer

Adds this JMS server as an examples-jms system resource and targets it to the Administration Server.

This server is configured to use the WSeeFileStore persistent store.

File Store

WseeFileStore

Adds the file store to be used as the persistent store for the WSEEJMSServer JMS server and the ReliableWseeSAFAgent SAF Agent. This file store is targeted to the examplesServer Administration Server.

JDBC Store

exampleJDBCStore

Adds the JDBC store to be used as the persistent store for the examples-demo JDBC data source and the examplesJMSServer JMS server, and targets the store to the examplesServer Administration Server.

JMS System Resources

examples-jms

Identifies the JMS servers, connection factories, queues, and topics to be used for JMS system resources.

JMS Connection Factories

exampleTopic

exampleTrader

weblogic.examples.jms.QueueConnectionFactory

weblogic.examples.ejb30.QueueConnectionFactory

Adds these connection factories as examples-jms system resources and targets them to the examplesServer server.

JMS Queues

exampleQueue

jms/MULTIDATASOURCE_MDB_QUEUE

weblogic.examples.ejb30.ExampleQueue

Adds these JMS queues to the examplesJMSServer JMS server.

JMS Queue

weblogic.wsee.wseeExamplesDestinationQueue

Adds this JMS queue to the WseeJMSServer JMS server.

JMS Topics

exampleTopic

quotes

stockTopic

Adds these JMS topics and targets them to the examplesJMSServer JMS server.

JDBC System Resource

examples-oracleXA

Identifies this JDBC data source, which has the following configuration:

JNDI name: examples-dataSource-oracleXAPool

Global transaction protocol: Two Phase Commit

The database driver is configured as oracle.jdbc.xa.client.OracleXADataSource.

This data source is mapped to the examples-multiDataSource-demoXAPool multi data source.

JDBC System Resource

examples-demoXA-2

Identifies this JDBC data source, which is targeted to the Administration Server and has the following configuration:

Connection pool maximum: 100

Global transaction protocol: Two Phase Commit

This data source is mapped to the examples-multiDataSource-demoXAPool multi data source.

JDBC System Resource

examples-multiDataSource-demoXAPool

Identifies this JDBC multi data source, which is targeted to the Administration Server. It is configured for failover, and maps to the examples-oracleXA and examples-demo-XA-2 data sources.

SAF Agent

ReliableWseeSAFAgent

Adds this store-and-forward agent, which uses the WseeFileStore file store, and targets it to the Administration Server.

Work Manager

weblogic.wsee.mdb.DispatchPolicy

Adds this Work Manager, but does not target it to any servers.

Generated Domain Output

The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs, and a set of scripts to run those examples. Once the WebLogic Server Default extension template has been applied to a base domain, applying the WebLogic Server Examples extension template enables you to create the WebLogic Server Examples domain.

Includes sub-directories containing various Java and XML files used to build and work with WebLogic Server examples.

user_projects\applications\base_domain\server\examples\src\

Various

Includes sub-directories containing various Java, XML, and HTML files used to work with WebLogic Server examples.

user_projects\domains\base_domain\

client2certs.pem

clientkey.pem

Demo certificate and keystore files.

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.

user_projects\domains\base_domain\

setExamplesEnv.cmd

setExamplesEnv.sh

Scripts that set up the environment to use the WebLogic Server Examples on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\

startWebLogicEx.cmd

startWebLogicEx.sh

Scripts used to start the Administration Server for the WebLogic Server Examples domain on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\autodeploy\

readme.txt

File providing information about the directory, which initially serves as a placeholder for automatic deployments.

user_projects\domains\base_domain\bin\

setDomainEnv.cmd

setDomainEnv.sh

Scripts used to set up the development environment on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

Scripts used to start a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

startWebLogic.cmd

startWebLogic.sh

Scripts used to start the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\bin\

stopWebLogic.cmd

stopWebLogic.sh

Scripts used to stop the Administration Server on Windows and UNIX systems, respectively.

user_projects\domains\base_domain\config\

config.xml

File containing the configuration information used by the Administration Server. For more information, see "Domain Configuration Files" in Understanding Domain Configuration for Oracle WebLogic Server.

user_projects\domains\base_domain\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."

user_projects\domains\base_domain\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).

user_projects\domains\base_domain\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).

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).

user_projects\domains\base_domain\config\jms\

examples-jms.xml

Global JMS module for the WebLogic Server Examples domain.

user_projects\domains\base_domain\config\lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java Virtual Machine starts.

user_projects\domains\base_domain\config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

user_projects\domains\base_domain\config\security\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\init-info\

security.xml

File used for creating user groups and roles that establish identity and access to domain resources.

user_projects\domains\base_domain\init-info\

startscript.xml

File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.

user_projects\domains\base_domain\init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

user_projects\domains\base_domain\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.

user_projects\domains\base_domain\security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

DefaultRoleMapperInit.ldift

XACMLAuthorizerInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Understanding Security for Oracle WebLogic Server.

user_projects\domains\base_domain\security\

SerializedSystemIni.dat

File containing encrypted security information.

user_projects\domains\base_domain\servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

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.

user_projects\domains\base_domain\WseeFileStore\

Not applicable.

Directory to be used for the file store for system resources.

Scripting on this page enhances content navigation, but does not change the content in any way.