2.2 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 these predefined template with the Configuration Wizard or WLST.

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

Table 2-3 Output Generated from the WebLogic Server Starter 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\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\	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\	startPointBaseConsole.cmd startPointBaseConsole.sh	Scripts used to start the PointBase console 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 Oracle Fusion Middleware 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\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.
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 Oracle Fusion Middleware 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. 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.

2.2.2 Resources and Services Configured for WebLogic Server Starter Domain Template

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

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

Resource Type Name Notes

Resource Type	Name	Notes
Administration Server	AdminServer	When using the Configuration Wizard or WLST Offline to create a 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 the Configuration Wizard, see "Creating WebLogic Domains" Oracle Fusion Middleware Creating Domains Using the Configuration Wizard. For information about customizing the Administration Server name while creating a domain with WLST Offline, see "Creating WebLogic Domains Using WLST Offline" in Oracle Fusion Middleware Oracle WebLogic Scripting Tool. The following sample WLST Offline code snippet shows how to change the default Administration Server name, AdminServer, to MedRecServer. #-----------------------------------# Read the Basic WebLogic Server Domain template readTemplate('d:/MW_HOME/wlserver_10.3/common/templates/domains/wls.jar') #Change the Administration Server name. cd('Servers/AdminServer') set('Name', 'MedRecServer') #-----------------------------------
Application Deployments	wls_starter	The web application deployed to the starter domain.
Security realm	myrealm	n.a.

Administration Server

AdminServer

When using the Configuration Wizard or WLST Offline to create a 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 the Configuration Wizard, see "Creating WebLogic Domains" Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

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

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

#-----------------------------------#
Read the Basic WebLogic Server Domain template
readTemplate('d:/MW_HOME/wlserver_10.3/common/templates/domains/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Application Deployments

wls_starter

The web application deployed to the starter domain.

Security realm

myrealm

n.a.