This chapter discusses the following topics:
Note:
As of WebLogic Server 11g Release 1 Patch Set 1 (10.3.2), Workshop no longer ships with WebLogic Server. Oracle recommends that you use JDeveloper instead.The Workshop templates will be present only if you are upgrading a previous installation of WebLogic Server 11g Release 1 and you installed Workshop in that release.
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.
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.
Table 2-1 Output Generated from the Basic WebLogic Server Domain Template
| Directory | File/s | 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. |
|
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\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 |
|
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. |
|
user_projects\domains\base_domain\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. |
The following table identifies the resources and services configured in a domain created with the Basic WebLogic Server Domain template.
Table 2-2 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 domain, and you want the Administration Server name to be different from the default name, 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 and Configuring 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')
#-----------------------------------
|
|
Security realm |
myrealm |
n.a. |
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.
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\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 |
|
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. |
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 |
|---|---|---|
|
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, 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. |
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.
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.
Table 2-5 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\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\ |
pointbase.ini |
File containing initialization information for a PointBase JDBC database. |
|
user_projects\applications\base_domain\ |
startWebLogic.cmd startWebLogic.sh |
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
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 development 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\ |
startPointBaseConsole.cmd startPointBaseConsole.sh |
Scripts used to start the PointBase console 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 Oracle Fusion Middleware 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). |
|
user_projects\applications\base_domain\config\jms |
wseejmsmodule-jms.xml |
Global JMS module for the domain configured for advanced Web Services. |
|
user_projects\applications\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\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 Oracle Fusion Middleware 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. 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_projects\applications\base_domain\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. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Advanced Web Services extension template.
Table 2-6 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. For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
JMS Queues |
WseeMessageQueue |
Adds the JMS queue to the JMS server, WseeJmsServer. |
|
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. |
|
Security realm |
myrealm |
Uses the security realm provided by the base WebLogic Server domain. |
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.
For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Oracle Fusion Middleware Information Roadmap for Oracle WebLogic Server.
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.
Table 2-7 Base Domain After Applying the Avitek Medical Records Sample Extension Template
| Directory | File | Description |
|---|---|---|
|
user_projects\applications\base_domain\dist\ |
Various |
Includes sub-directories containing various distributions of the Avitek Medical Records applications. |
|
user_projects\applications\base_domain\doc\ |
Various |
Directory and files containing the Avitek Medical Records online documentation. |
|
user_projects\applications\base_domain\lib\ |
Various |
Includes sub-directories containing library files supporting the Avitek Medical Records sample. |
|
user_projects\applications\base_domain\modules\ |
Various |
Includes sub-directories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, and so on. |
|
user_projects\applications\base_domain\ |
build.xml |
Ant build file used with corresponding scripts to set up a database for the Avitek Medical Records sample. |
|
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\ |
log4j.properties |
Configures Avitek Medical Records Log4j implementation including the MedRecApp.log file. |
|
user_projects\domains\base_domain\ |
pointbase.ini |
File containing initialization information for a PointBase JDBC database. |
|
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\diagnostics\ |
MedRecWLDF.xml |
Diagnostic descriptor information for the Avitek Medical Records diagnostics instrumentation. |
|
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\jdbc\ |
MedRec-jdbc.xml |
Global XA JDBC Data Source module for the Avitek Medical Records domain. |
|
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\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 Oracle Fusion Middleware 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. 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. |
The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template.
Table 2-8 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 For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
Application Deployments |
browser-starter |
Adds the browser-starter application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
medrec |
Adds the medrec application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
physician |
Adds the physician application and targets it to the Administration Server, AdminServer. |
|
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 Servers |
MedRecJMSServer |
Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server, AdminServer. |
|
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, AdminServer. |
|
Mail Session |
mail/MedRecMailSession |
Adds the mail session. |
|
SAF Agent |
WsrmAgent |
Adds this store-and-forward agent, which uses the file store, MedRecWseeFileStore, and targets it to the Administration Server, AdminServer. |
|
Security realm |
myrealm |
Uses the security realm provided in the base WebLogic Server domain. |
|
WLDF System Resource |
MedRecWLDF |
Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server, AdminServer. |
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.
For more information about the Avitek Medical Records sample application, see "Sample Application and Code Examples" in Oracle Fusion Middleware Information Roadmap for Oracle WebLogic Server.
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.
Table 2-9 Base Domain After Applying the Avitek Medical Records Sample Extension Template (Spring Version)
| Directory | File | Description |
|---|---|---|
|
user_projects\applications\base_domain\dist\ |
Various |
Includes sub-directories containing various distributions of the Avitek Medical Records applications. |
|
user_projects\applications\base_domain\doc\ |
Various |
Directory and files containing the Avitek Medical Records online documentation. |
|
user_projects\applications\base_domain\lib\ |
Various |
Includes sub-directories containing library files supporting the Avitek Medical Records sample. |
|
user_projects\applications\base_domain\modules\ |
Various |
Includes sub-directories containing Avitek Medical Records source code including various Java, XML, JSP, HTML files, and so on. |
The following table identifies the resources and services configured in a domain extended with the Avitek Medical Records Sample extension template for Spring.
Table 2-10 Resources Configured in an Avitek Medical Records Domain for Spring
| Resource Type | Name | Extension Result |
|---|---|---|
|
Administration Server |
AdminServer |
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
Application Deployments |
browser-starter |
Adds the browser-starter application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
medrec |
Adds the medrec application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
physician |
Adds the physician application and targets it to the Administration Server, AdminServer. |
|
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 Servers |
MedRecJMSServer |
Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server, AdminServer. |
|
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, AdminServer. |
|
Mail Session |
mail/MedRecMailSession |
Adds the mail session. |
|
SAF Agent |
WsrmAgent |
Adds this store-and-forward agent, which uses the file store, MedRecWseeFileStore, and targets it to the Administration Server, AdminServer. |
|
Security realm |
myrealm |
Uses the security realm provided in the base WebLogic Server domain. |
|
WLDF System Resource |
MedRecWLDF |
Adds the WLDF system resource and defined WLDF instrumentation monitors for dye injection, and targets them to the Administration Server, AdminServer. |
|
Administration Server |
AdminServer |
Uses the Administration Server provided in the base WebLogic Server domain. The default name is For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
Application Deployments |
browser-starter |
Adds the browser-starter application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
medrec |
Adds the medrec application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
physician |
Adds the physician application and targets it to the Administration Server, AdminServer. |
|
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 Servers |
MedRecJMSServer |
Adds the JMS server as a MedRec-jms system resource and targets it to the Administration Server, AdminServer. |
|
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, AdminServer. |
Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include resources required for a default WebLogic Server domain. You accomplish this by adding the resources and services provided in the WebLogic Server Default Domain extension template to a base WebLogic Server domain.
Note:
Applying the WebLogic Server Default Domain extension template to a base WebLogic domain is a prerequisite to using the WebLogic Server Examples extension template. For information about the relationship between templates, see Relationships Between Templates.For more information about the samples that are supported in the WebLogic Server Examples domain, see "Sample Application and Code Examples" in Oracle Fusion Middleware Information Roadmap for Oracle WebLogic Server.
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.
Table 2-11 Base Domain After Applying the WebLogic Server Default Domain Extension Template
| Directory | File | Description |
|---|---|---|
|
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. |
|
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. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Server Default Domain extension template.
Table 2-12 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. For information about naming the Administration Server during domain creation, see 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. |
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 Oracle Fusion Middleware Information Roadmap for Oracle WebLogic Server.
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. See Relationships Between Templates for more details.
Table 2-13 Base Domain After Applying the WebLogic Server Default and WebLogic Server Examples Extension Templates
| Directory | File | Description |
|---|---|---|
|
user_projects\applications\base_domain\ |
empty |
empty |
|
server\ |
wls_samples_overview.html |
File that opens the WebLogic Server examples online documentation viewer. |
|
server\docs\ |
Various |
Directory and files supporting the WebLogic Server examples online documentation viewer. |
|
server\examples\build\ |
Various |
Includes sub-directories containing various Java and XML files used to build and work with WebLogic Server examples. |
|
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\ |
empty |
empty |
|
empty |
client2certs.pem clientkey.pem |
Demo certificate and keystore files. |
|
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 Examples domain. |
|
config\jdbc\ |
examples-demoXA-2-jdbc.xml examples-demoXA-jdbc.xml examples-multiDataSource-demoXAPool-jdbc.xml examples-oracleXA-jdbc.xml |
Global XA JDBC Data Source modules for the WebLogic Server Examples 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\jms\ |
examples-jms.xml |
Global JMS module for the WebLogic Server Examples 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. |
|
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. |
|
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. |
|
WseeFileStore\ |
n.a. |
Directory to be used for the file store for system resources. |
The following table identifies the resources and services configured in a domain extended with the WebLogic Server Examples extension template.
Table 2-14 Resources Configured in a WebLogic Server Examples 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. For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
Application Deployments |
ejb20BeanMgedEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
examplesWebApp |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
jdbcRowSetsEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
jspSimpleTagEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
mainWebApp |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
SamplesSearchWebApp |
Adds the application and targets it to the Administration Server, AdminServer. |
|
Application Deployments |
webappCachingEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
webservicesJwsSimpleEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
Application Deployments |
xmlBeanEar |
Uses the application provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
File Store |
WseeFileStore |
Adds the file store to be used as the persistent store for the JMS server, WseeJMSServer, and the SAF Agent, ReliableWseeSAFAgent, and targets the store to the Administration Server, AdminServer. |
|
JDBC Data Sources |
examples-demo examples-demoXA |
Uses the non-XA and XA JDBC data sources provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
JDBC Data Sources |
examples-oracleXA |
Adds the XA JDBC data source and targets it to the Administration Server, AdminServer. |
|
JDBC Data Sources |
examples-demoXA-2 |
Adds the XA JDBC data source and targets it to the Administration Server, AdminServer. |
|
JDBC Data Sources |
examples-multiDataSource-demoXAPool |
Adds the XA JDBC multi data source and targets it to the Administration Server, AdminServer. Maps to examples-demoXA and examples-demoXA-2 data sources. |
|
JDBC Store |
exampleJDBCStore |
Adds the JDBC store to be used as the persistent store for the JDBC data source, examples-demo, and the JMS server, examplesJMSServer, and targets the store to the Administration Server, AdminServer. |
|
JDBC System Resources |
examples-demo examples-demoXA |
Uses the JDBC data source and connection pool setups provided by the WebLogic Server Default extension template applied to the base WebLogic Server domain. |
|
JDBC System Resources |
examples-demoXA-2 examples-oracleXA examples-multiDataSource-demoXAPool |
Adds the JDBC data source and connection pool setups and targets them to the Administration Server, AdminServer. |
|
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 |
Adds the JMS connection factories as examples-jms system resources and targets them to the Administration Server, AdminServer. |
|
JMS Servers |
examplesJMSServer |
Adds the JMS server as an examples-jms system resource and targets it to the Administration Server, AdminServer. |
|
JMS Servers |
WseeJMSServer |
Adds the JMS server as an examples-jms system resource and targets it to the Administration Server, AdminServer. |
|
JMS Queues |
exampleQueue |
Adds the JMS queue to the JMS server, examplesJMSServer. |
|
JMS Queues |
jms/MULTIDATASOURCE_MDB_QUEUE |
Adds the JMS queue to the JMS server, examplesJMSServer. |
|
JMS Queues |
weblogic.wsee.wseeExamplesDestinationQueue |
Adds the JMS queue to the JMS server, WseeJMSServer. |
|
JMS Topics |
exampleTopic |
Adds the JMS topic to the JMS server, examplesJMSServer. |
|
JMS Topics |
quotes |
Adds the JMS topic to the JMS server, examplesJMSServer. |
|
SAF Agent |
ReliableWseeSAFAgent |
Adds the SAF agent and targets it to the Administration Server, AdminServer. |
|
Security realm |
myrealm |
Uses the security realm provided by the base WebLogic Server domain. |
Note:
As of WebLogic Server 11g Release 1 Patch Set 1 (10.3.2), Workshop no longer ships with WebLogic Server. Oracle recommends that you use JDeveloper instead.The Workshop templates will be present only if you are upgrading a previous installation of WebLogic Server 11g Release 1 and you installed Workshop in that release.
Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for using Workshop for WebLogic. You accomplish this by adding the resources and services provided in the Workshop for WebLogic template to a base WebLogic Server domain.
Note:
Using the Configuration Wizard in graphical mode, you can easily create a Workshop for WebLogic domain by checking the Workshop for WebLogic check box in the Select Domain Source window. The result is the same as creating a base WebLogic Server domain first and then extending that domain with both the Oracle Workshop for WebLogic extension template. For more information about the templates required to create a Oracle Workshop for WebLogic domain, see Relationships Between Templates.The following table defines the default directory structure and files generated after applying the Workshop for WebLogic 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.
Table 2-15 Base Domain After Applying the Oracle Workshop for WebLogic 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\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\ |
pointbase.ini |
File containing initialization information for a PointBase JDBC database. |
|
user_projects\applications\base_domain\ |
startWebLogic.cmd startWebLogic.sh |
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
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 development 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\ |
startPointBaseConsole.cmd startPointBaseConsole.sh |
Scripts used to start the PointBase console 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 Oracle Fusion Middleware 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\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\applications\base_domain\config\jdbc\ |
cgDataSource-jdbc.xml |
Global XA JDBC Data Source module for the domain configured for advanced Web services. |
|
user_projects\applications\base_domain\config\jdbc\ |
cgDataSource-nonXA-jdbc.xml |
Global non-XA JDBC Data Source module for the domain configured for advanced Web services. |
|
user_projects\applications\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\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 Oracle Fusion Middleware 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. 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_projects\applications\base_domain\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. |
The following table identifies the resources and services configured in a domain extended with the Oracle Workshop for WebLogic template.
Table 2-16 Resources Configured in a Oracle Workshop for WebLogic 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. For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
JDBC Data Source |
cgDataSource |
Defines an XA JDBC data source including its associated jdbc connection pool. The data source is named cgDataSource. |
|
JDBC Data Source |
cgDataSource-nonXA |
Includes the JDBC data source and connection pool setups defined as cgDataSource in the domain and targets them to the correct server(s). |
|
JDBC Store |
cgJMSStore |
Uses the JDBC store provided by the Oracle Workshop for WebLogic extension template. The JDBC store is to be used with the JDBC data source, cgDataSource-nonXA, and the JMS server, WseeJmsServer, as a persistent store, and is targeted to the Administration Server, AdminServer. |
|
JDBC System Resources |
cgDataSource cgDataSource-nonXA |
Identifies the JDBC data source and connection pool setups to be used for JDBC system. |
|
JMS Server |
WseeJmsServer |
Uses the JMS server provided by the Workshop for WebLogic extension template. Identifies 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. |
|
Commons-Logging Bridge |
wls-commonslogging-bridge#1.0@1.0 |
Hooks commons-logging into the WLS logging mechanism. |
|
Libraries Deployed |
beehive-netui-1.0#1.0@1.0 |
Adds the Apache Beehive NetUI Version 1.0 libraries. These libraries support pageflow development, and depend upon the libraries contained in struts-1.1.war and weblogic-beehive-1.0.ear. |
|
Libraries Deployed |
jstl#1.1@1.1.2 |
Adds the Java standard tagging (JSTL) Version 1.1 libraries. |
|
Libraries Deployed |
jsf-ri#1.1@1.1.1 |
Adds the Java Server Faces Reference Implementation libraries. |
|
Libraries Deployed |
jsf-myfaces#1.1@1.1.1 |
Adds the Apache MyFaces libraries. |
|
Libraries Deployed |
struts-1.1#1.1@1.0 |
Adds the Apache Struts Version 1.1 libraries. |
|
Libraries Deployed |
struts-1.2#1.2@1.0 |
Adds the Apache Struts Version 1.2 libraries. |
|
Libraries Deployed |
weblogic-controls-10.0#10.0@10.0 |
Adds the Oracle Workshop for WebLogic controls extensions, including additional system controls (such as service control and timer control) and support for adding transactions, security, and message buffering to existing controls. Packaged for EARs. |
|
Libraries Deployed |
weblogic-controls-10.0-war#10.0@10.0 |
Adds the Oracle Workshop for WebLogic controls extensions including additional system controls (such as service control) and support for adding transactions, security, and message buffering to existing controls. Excludes those features which require EAR support such as timer control. Packaged for WARs. |
|
Libraries Deployed |
beehive-controls-1.0#1.0@1.0 |
Adds the Apache Beehive Controls 1.0.1 libraries to the domain. This includes the control run time and the Beehive system controls - JdbcControl, JMSControl, and EJBControl. |
Note:
As of WebLogic Server 11g Release 1 Patch Set 1 (10.3.2), Workshop no longer ships with WebLogic Server. Oracle recommends that you use JDeveloper instead.The Workshop templates will be present only if you are upgrading a previous installation of WebLogic Server 11g Release 1 and you installed Workshop in that release.
Using the Configuration Wizard or WLST, you can easily extend a base WebLogic Server domain to include the resources required for using Workshop for WebLogic 10.3. You accomplish this by adding the resources and services provided in the Workshop for WebLogic 10.3 template to a base WebLogic Server domain.
Note:
Using the Configuration Wizard in graphical mode, you can easily create an Oracle Workshop for WebLogic domain by checking the Workshop for WebLogic 10.3 check box in the Select Domain Source window. The result is the same as creating a base WebLogic Server domain first and then extending that domain with both the Workshop for WebLogic 10.3 extension template. For more information about the templates required to create a Workshop for WebLogic 10.3 domain, see Relationships Between Templates.The following table defines the default directory structure and files generated after applying the Workshop for WebLogic 10.3 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.
Table 2-17 Base Domain After Applying the Workshop for WebLogic 10.3 Template
| Directory | File | Description |
|---|---|---|
|
user_projects\applications\base_domain\ |
empty |
empty |
|
empty |
n.a. |
Directory serving as a placeholder for any custom application files that you create. |
|
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 |
startWebLogic.cmd startWebLogic.sh |
Scripts used to start the Administration Server on Windows and UNIX systems, respectively. |
|
empty |
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. |
|
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\ |
cgDataSource-jdbc.xml |
Global XA JDBC Data Source module for the domain configured for advanced web services. |
|
config\jdbc\ |
cgDataSource-nonXA-jdbc.xml |
Global non-XA JDBC Data Source 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. |
|
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. |
|
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 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. |
|
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. |
The following table identifies the resources and services configured in a domain extended with the Workshop for WebLogic 10.3 template.
Table 2-18 Resources Configured in a Workshop for WebLogic 10.3 template
| 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. For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template. |
|
JDBC Data Source |
cgDataSource |
Defines an XA JDBC data source including its associated jdbc connection pool. The data source is named cgDataSource. |
|
JDBC Data Source |
cgDataSource-nonXA |
Includes the JDBC data source and connection pool setups defined as cgDataSource in the domain and targets them to the correct server(s). |
|
JDBC Store |
cgJMSStore |
Uses the JDBC store provided by the Workshop for WebLogic 10.3 extension template. The JDBC store is to be used with the JDBC data source, cgDataSource-nonXA, and the JMS server, WseeJmsServer, as a persistent store, and is targeted to the Administration Server, AdminServer. |
|
JDBC System Resources |
cgDataSource cgDataSource-nonXA |
Identifies the JDBC data source and connection pool setups to be used for JDBC system. |
|
JMS Server |
WseeJmsServer |
Uses the JMS server provided by the Workshop for WebLogic 10.3 extension template. Identifies 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. |
|
Commons-Logging Bridge |
wls-commonslogging-bridge#1.0@1.0 |
Hooks commons-logging into the WLS logging mechanism. |
|
Libraries Deployed |
beehive-netui-1.0#1.0@1.0 |
Adds the Apache Beehive NetUI Version 1.0 libraries. These libraries support pageflow development, and depend upon the libraries contained in struts-1.1.war and weblogic-beehive-1.0.ear. |
|
Libraries Deployed |
jstl#1.1@1.1.2 |
Adds the Java standard tagging (JSTL) Version 1.1 libraries. |
|
Libraries Deployed |
jsf-ri#1.1@1.1.1 |
Adds the Java Server Faces Reference Implementation libraries. |
|
Libraries Deployed |
jsf-myfaces#1.1@1.1.1 |
Adds the Apache MyFaces libraries. |
|
Libraries Deployed |
struts-1.1#1.1@1.0 |
Adds the Apache Struts Version 1.1 libraries. |
|
Libraries Deployed |
struts-1.2#1.2@1.0 |
Adds the Apache Struts Version 1.2 libraries. |
|
Libraries Deployed |
weblogic-controls-10.0#10.0@10.0 |
Adds the Workshop for WebLogic 10.3 controls extensions, including additional system controls (such as service control and timer control) and support for adding transactions, security, and message buffering to existing controls. Packaged for EARs. |
|
Libraries Deployed |
weblogic-controls-10.0-war#10.0@10.0 |
Adds the Workshop for WebLogic 10.3 controls extensions including additional system controls (such as service control) and support for adding transactions, security, and message buffering to existing controls. Excludes those features which require EAR support such as timer control. Packaged for WARs. |
|
Libraries Deployed |
beehive-controls-1.0#1.0@1.0 |
Adds the Apache Beehive Controls 1.0.1 libraries to the domain. This includes the control run time and the Beehive system controls - JdbcControl, JMSControl, and EJBControl. |