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 Section 1.5, "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-15 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. |
|
config\startup\ |
readme.txt |
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup. |
|
console-ext\ |
readme.txt |
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
|
init-info\ |
domain-info.xml |
File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain. |
|
init-info\ |
security.xml |
File used for creating user groups and roles that establish identity and access to domain resources. |
|
init-info\ |
startscript.xml |
File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories. |
|
init-info\ |
tokenValue.properties |
File that contains the actual values to substitute for the tokens specified in the start scripts. |
|
lib\ |
readme.txt |
File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup. |
|
security\ |
DefaultAuthenticatorInit.ldift 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-16 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 Section 2.1.2, "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. |