2.9 WebLogic Server Default Domain Extension Template

user_projects\applications\base_domain\

empty

empty

server\docs\

Various

Includes sub-directories containing style sheet and graphics files to support the online documentation.

server\examples\build\

Various

Includes WebLogic Server examples deployments.

server\examples\src\

Various

Includes source code and instructions for WebLogic Server examples.

user_projects\domains\base_domain\

empty

empty

empty

fileRealm.properties

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

empty

pointbase.ini

File containing initialization information for a PointBase JDBC database.

empty

setExamplesEnv.cmd

setExamplesEnv.sh

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

empty

startWebLogic.cmd

startWebLogic.sh

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

empty

startWebLogicEx.cmd

startWebLogicEx.sh

Scripts used to start the Administration Server for the WebLogic Server Examples domain 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.

bin\

startManagedWebLogic.cmd

startManagedWebLogic.sh

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

bin\

startPointBaseConsole.cmd

startPointBaseConsole.sh

Scripts used to start the PointBase console on Windows and UNIX systems, respectively.

bin\

startWebLogic.cmd

startWebLogic.sh

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

bin\

stopManagedWebLogic.cmd

stopManagedWebLogic.sh

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

bin\

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 Oracle Fusion Middleware Understanding Domain Configuration for Oracle WebLogic Server.

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\jdbc\

examples-demo-jdbc.xml

Global non-XA JDBC Data Source module for the WebLogic Server default domain.

config\jdbc\

examples-demoXA-jdbc.xml

Global XA JDBC Data Source module for the WebLogic Server default 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).

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.

config\nodemanager\

nm_password.properties

File containing Node Manager password property values.

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.

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.

init-info\

security.xml

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

init-info\

startscript.xml

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

init-info\

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

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 Oracle Fusion Middleware Understanding Security for Oracle WebLogic Server.

security\

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 start 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 Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_staged_config\

readme.txt

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.

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.

For information about naming the Administration Server during domain creation, see Section 2.1.2, "Resources and Services Configured for WebLogic Server Domain Template."

Application Deployments

ejb20BeanMgedEar

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

examplesWebApp

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

jdbcRowSetsEar

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

jspSimpleTagEar

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

mainWebApp

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

webappCachingEar

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

webservicesJwsSimpleEar

Adds the application and targets it to the Administration Server, AdminServer.

Application Deployments

xmlBeanEar

Adds the application and targets it to the Administration Server, AdminServer.

JDBC Data Sources

examples-demo

Identifies the JDBC data source as an examples-demo system resource.

JDBC Data Sources

examples-demoXA

Identifies the JDBC data source as an examples-demoXA system resource.

JDBC System Resources

examples-demo

examples-demoXA

Identifies the JDBC data source and connection pool setups to be used for non-XA and XA JDBC system resources and targets them to the Administration Server, AdminServer.

Security realm

myrealm

Uses the security realm provided by the base WebLogic Server domain.