> Domain Template Reference > Domain Template Reference

Domain Template Reference

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Domain Template Reference

This document provides general information about templates in the following topics:

 

Types of Templates

The term template refers to a Java Archive (JAR) file that contains the files and scripts required to create or extend a domain. The types of template include:

 

Location of Installed Templates

The following table identifies the location of the predefined templates provided with your product installation, where BEA_HOME represents the product installation directory.

Table 1 Location of Templates 
Type of Template
Directory Location
Domain
BEA_HOME\common\templates\domains
Extension
BEA_HOME\common\templates\applications

 

Template Tools

The following table identifies the tools with which you can create templates and the tools with which you can use templates to create or extend a domain.

Table 2 Template Tools 
To . . .
Use this tool . . .
Create a new domain
  • Configuration Wizard
  • WLST Offline
  • unpack command
Extend an existing domain
  • Configuration Wizard
  • WLST Offline
Create a new Managed Server domain on a remote machine
unpack command
Create a domain template
  • Domain Template Builder
  • pack command
  • WLST Offline
Create an extension template
Domain Template Builder
Create a Managed Server template
pack command

Note: All the tools used to create or extend a domain leverage a common underlying infrastructure, referred to generically as the Configuration Wizard framework.

 

Template Summary

The following table summarizes the predefined templates that may be provided in your product installation.

Table 3 Summary of AquaLogic Template
Template
Filename
Description
AquaLogic Service Bus Extension
wlsb.jar
Extends the base WebLogic Server domain by providing the resources required to support AquaLogic Service Bus.

Table 4 Summary of WebLogic Server, WebLogic Integration, Portal, and BEA Workshop for WebLogic Platform Templates 
Template
Filename
Description
Domain Template
Basic WebLogic Server Domain
wls.jar
Creates a base WebLogic Server domain.
WebLogic RealTime
wl-realtime.jar
For WebLogic Server 9.1 and 9.2:
Creates a WebLogic Server domain using the BEA JRockit 5.0 R26.4 JDK with the Deterministic Garbage Collection feature enabled.
For WebLogic Server 8.1 (SP2 or later):
Creates a WebLogic Server domain using the BEA JRockit 1.4.2 R26.4 JDK with the Deterministic Garbage Collection feature enabled.
Extension Templates
WebLogic Beehive Extension (AquaLogic Service Bus)
weblogic-beehive.jar
Extends the base WebLogic Server domain to create a WebLogic Beehive domain. Also adds required Beehive libraries to support run-time use of controls.

Note: Resources from the WebLogic Advanced Web Services Extension template are required to create a complete WebLogic Beehive domain.

Advanced Web Services Extension (Platform)
wls_webservice.jar
Extends an existing WebLogic Server domain to add functionality required for advanced Web Services, including WSRM, Buffering, and JMS Transport.
Avitek Medical Records Sample Domain
medrec.jar
Extends the base WebLogic Server domain to create the Avitek Medical Records sample domain. This domain is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform.
BEA Workshop for WebLogic Extension Template
workshop_wl.jar
Extends Basic WebLogic Server domain to create BEA Workshop for WebLogic domain.
WebLogic Server Default Domain
wls_default.jar
Extends the base WebLogic Server domain with a Web application designed to guide new users through an introduction to WebLogic Server. When running the Web application, users can review informative content on various topics, including highlights of WebLogic Server functionality. From the Web application, users can also run several pre-configured, pre-compiled examples. Resources from this extension template are required for a WebLogic Server Examples domain.
WebLogic Server Examples
wls_examples.jar
Extends the WebLogic Server domain containing resources from the base WebLogic Server domain template and the WebLogic Server Default Domain extension template to create a complete WebLogic Server Examples domain. The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE and WebLogic Server APIs.
WebLogic Integration BPM Extension Template
wli_jpd.jar
Imports the resources needed to support the development of WebLogic Integration applications.
WebLogic Integration Worklist Extension Template
wli_worklist.jar
WebLogic Integration Worklist (Compatibility) Extension Template
wli_worklist81x.jar
WebLogic Portal Extension Template
wlp.jar
Extends a WebLogic Server domain to allow for WebLogic Portal application development.
WebLogic Portal GroupSpace Framework
wlp_groupspacedb.jar
Extends a WebLogic Portal domain to allow for development and hosting of GroupSpace applications. This template extends a WebLogic Portal domain by adding additional Datasources and creating an additional database schema.
WebLogic Portal GroupSpace Application
wlp_groupspace.jar
Extends a WebLogic Portal GroupSpace enabled domain by adding a preconfigured Out-of-the-box GroupSpace application to the domain.
WebLogic Personalization Extension
p13n.jar
Extends an existing WebLogic Server domain to add Weblogic Personalization functionality.
WebLogic Simple Producer (Portal) Extension
wsrp-simple-producer.jar
Extends an existing WebLogic domain to add WebLogic Simple Producer (Portal) functionality. Domains extended with this template will support WebLogic Simple Producer functionality. Use this template to enable the development of WebLogic Simple Producer applications in existing domains.

 

Relationships Between Templates

This section provides the following topics:

WebLogic Server Resources as a Prerequisite

WebLogic Server resources must already be set up in your domain before you can add resources from an extension template. When you select an extension template, the Configuration Wizard framework checks to make sure the required resources are available for you.

Relationships Between Templates

You can create a base WebLogic domain using the predefined basic WebLogic Server domain template or you can create a base WebLogic domain and extend it incrementally using the extension templates. The following table shows the relationship between the templates and the domains created.

Table 5 Relationships Between Templates 
This type of domain . . .
Requires resources from these templates . . .
AquaLogic Service Bus
Basic WebLogic Server Domain template, wls.jar
+ WebLogic Beehive extension template,
weblogic-beehive.jar
+ AquaLogic Service Bus Extension template, wlsb.jar
Avitek Medical Records Sample
Basic WebLogic Server Domain template, wls.jar
+ Avitek Medical Records Sample Domain extension template, medrec.jar
WebLogic Server (base)
Basic WebLogic Server Domain template, wls.jar
WebLogic Server Default
Basic WebLogic Server Domain template, wls.jar
+ WebLogic Server Default Domain extension template, wls_default.jar
WebLogic Server Examples
Basic WebLogic Server Domain template, wls.jar
+ WebLogic Server Default Domain extension template, wls_default.jar
+ WebLogic Server Examples extension template, wls_examples.jar
WebLogic Integration Worklist Extension
Basic WebLogic Server Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar + WebLogic Personalization Extension, p13n.jar
+ Worklist Extension Template, wli_worklist.jar.
WebLogic Integration Worklist (Compatibilty) Extension
Basic WebLogic Server Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar + WebLogic Personalization Extension, p13n.jar
+ Worklist Extension Template, wli_worklist.jar
+WebLogic Integration Worklist (Compatibilty) Extension, wli_worklist81x.jar
WebLogic Integration Business Process Management
Basic WebLogic Server Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar,
+ WebLogic Server WebService, wls_webservice.jar,
+ WebLogic Personalization Extension, p13n.jar,
+ WebLogic Integration BPM Extension Templates, wli_jpd.jar.
WebLogic Advanced Web Services Extension
Basic WebLogic Server Domain, wls.jar
+ WebLogic Advanced Web Services Extension, wls_webservice.jar
WebLogic Beehive Extension
Basic WebLogic Server Domain, wls.jar
+ WebLogic Advanced Web Services Extension, wls_webservice.jar
+ WebLogic Beehive Extension, weblogic_beehive.jar
WebLogic Portal
Basic WebLogic Server Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar
+ WebLogic Advanced Web Services Extension, wls_webservice.jar
+ WebLogic Personalization Extension, p13n.jar
+ WebLogic Portal Extension, wlp.jar
WebLogic Portal GroupSpace Framework
Basic WLS Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar
+ WebLogic Advanced Web Services Extension, wls_webservice.jar
+ WebLogic Portal Extension, wlp.jar
+ WebLogic Portal GroupSpace Framework Extension, wlp_groupspacedb.jar
Weblogic Portal GroupSpace Application
Basic WLS Domain, wls.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar
+ WebLogic Advanced Web Services Extension, wls_webservice.jar
+ WebLogic Personalization Extension, p13n.jar
+ WebLogic Portal Extension, wlp.jar
+ WebLogic Portal GroupSpace Framework Extension,
wlp_groupspacedb.jar
+WebLogic Portal GroupSpace Application Extension, wlp_groupspace.jar
BEA Workshop for WebLogic Platform
Basic WLS Domain, wls.jar
+ Advanced Web Services Extension, wls_webservice.jar
+ BEA Workshop for WebLogic Extension, workshop_wl.jar

 

Files Typically Included in a Template

The basic files included in any template are config.xml and template-info.xml. There are additional files in the predefined templates that are the basis for creating or extending a domain. The following table describes the files typically included in a domain or extension template.

Table 6 Files Included in a Template 
Filename
Description
product component files
Various files used to complete the domain setup for a specific BEA product component. Such files may provide information for security and default database settings.
*-jdbc.xml
Sets up or extends a domain with JDBC system resources required by a product component. In a template, the *-jdbc.xml files must be located in the config\jdbc directory.
*-jms.xml
Sets up or extends a domain with JMS system resources required by a product component. In a template, the *-jms.xml files must be located in the config\jms directory.
clusters.script
Used to modify the Configuration Wizard framework's default auto-configuration of a cluster. By default, resources are targeted to the cluster. You can unassign a resource from the cluster and then assign it to another component. To specify a target, you can use the following replacement variables:
  • %AManagedServer% — Any Managed Server
  • %AllManagedServers% — Comma-separated list of all Managed Servers
  • %AdminServer% — Administration Server name
  • %Cluster% — Cluster name
  • %ProxyServer% — Proxy server name
  • %HTTPProxyApp% — http proxy application definition
Note the following additional considerations:
  • You must use the name attribute of an object that is to be replaced.
  • You can use an asterisk (*) as a wildcard for "All."
In a template, the clusters.script file must be located in the script directory.

Note: AquaLogic Service Bus overrides this behavior by retargeting some apps to one of the following:

  • Only admin server
  • Only managed servers in cluster but not http router (preserving the default targeting behavior)
  • Admin and managed servers but not the http router
  • All servers in the domain including the http router.
config.xml
Sets up or extends the domain configuration. In a template, the config.xml file must be located in the config directory.
jdbc.index
Identifies the locations of SQL scripts used to set up a database. The file lists the scripts in the order in which they must be run. If the scripts are not contained in the template, but are located in the product installation directory, that directory can be represented by a tilde ( ~ ) in the pathname for the scripts, as shown in the following example:
~/integration/common/dbscripts/oracle/reporting_runtime.sql
Specifically, the tilde represents the directory path identified by the $USER_INSTALL_DIR$ variable in the stringsubs.xml file.
In a template, a jdbc.index file must be located in the _jdbc_\dbtype\dbversion directory, where dbtype is the type of database, such as Oracle, and dbversion is the database version, such as 9i.
In addition to listing the SQL files related to a data source, the jdbc.index file contains information about the categories associated with the data source. The default dbCategories that are available are:
  • `Drop/Create P13N Database Objects' category associated with the p13nDataSource dataSource, which is a part of the p13n.jar domain template
  • `Drop/Create Portal Database Objects' category associated with the "p13nDataSource" dataSource, which is a part of the wlp.jar domain template
  • `Drop/Create GroupSpace Database Objects' category associated with the appsGroupSpaceDataSource dataSource, which is a part of the wlp_groupspacedb.jar domain template
All these templates jar files are located in the BEA_HOME\weblogic92\common\templates\applications directory.
security.xml
Used to create user groups and roles that establish identity and access to domain resources. You can create the default Admin user only through the security.xml in a domain template. However, you can create user groups and roles through the security.xml included in either a domain or an extension template.
startmenu.xml
Used to create Windows start menu entries.
startscript.xml
Used to create the *.cmd and *.sh files that are placed into a domain's root and bin directories.
stringsubs.xml
Identifies string substitution values and the files that will receive string substitutions during domain creation or extension. The files that will receive string substitutions must already be prepared with replacement variables. During domain creation or extension, the Configuration Wizard framework runs macros to replace variables with the appropriate string substitution, using information from BEA_HOME\common\lib\macrorules.xml, where BEA_HOME is the product installation directory.
template-info.xml
Provides template identification information, such as the template name, software version, type of template (domain or application), author, description, etc.

 

Basic WebLogic Server Domain Template

Your product installation provides one predefined base WebLogic Server domain template. All other predefined templates are extension templates that you may use to add resources, services, and applications to a base WebLogic Server domain. You can easily create or extend a domain by using these predefined templates with the Configuration Wizard or WLST.

Generated Domain Output

The Basic WebLogic Server Domain template allows 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 BEA_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 7 Output Generated from the Basic WebLogic Server 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\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.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server 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.
startManagedWebLogic.cmd
startManagedWebLogic.sh
Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
startPointBaseConsole.cmd
startPointBaseConsole.sh
Scripts used to start the PointBase console on Windows and UNIX systems, respectively.
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
stopManagedWebLogic.cmd
stopManagedWebLogic.sh
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
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 Understanding Domain Configuration.
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\jms\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing global JMS modules that can be configured directly from JMX (as opposed to JSR-88).
config\lib\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing JAR files that are added to the system classpath of the server when the server's Java virtual machine starts.
config\nodemanager\
nm_password.properties
File containing Node Manager password property values.
config\security\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules for the security framework. The directory contains one security provider configuration extension for each type of security provider in the domain's current realm.
config\startup\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.
console-ext\
readme.txt
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.
init-info\
domain-info.xml
File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.
security.xml
File used for creating user groups and roles that establish identity and access to domain resources.
startscript.xml
File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.
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 Understanding WebLogic Security at http://e-docs.bea.com/wls/docs92/secintro/archtect.html#archtect_0111.
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 boot 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 Starting and Stopping Servers in Managing Server Startup and Shutdown at
http://edocs.bea.com/wls/docs92/server_start/overview.html.
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.

Resources and Services Configured for WebLogic Server Domain Template

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

Table 8 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 new domain, and you want the Administration Server name to be different from the default name, AdminServer, you must configure the name manually. You cannot change the name afterwards when applying an extension template.
For information about customizing the Administration Server name while creating a domain with the Configuration Wizard, see "Configure the Administration Server" in "Customizing the Environment" in Creating WebLogic 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 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:/bea/weblogic92/common/templates/domains/wls.jar')
#Change the Administration Server name.
cd('Servers/AdminServer')
set('Name', 'MedRecServer')
#-----------------------------------

Security realm
myrealm
n.a.

 

WebLogic Integration BPM Extension Template

Using the Configuration Wizard, you can extend a base WebLogic Server Domain to create a WebLogic Integration Domain. You accomplish this by adding the resources and services provided in the WebLogic Integration .

Generated Domain output

The following table defines the default directory structure and files generated after applying the WebLogic Integration Extension template to a base WebLogic Server domain. Unless otherwise specified, by default, the Configuration Wizard creates the domain in the BEA_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 9 Output Generated from WebLogic Integration BPM Extension Template 
Directory
File
Description
user_projects\domains\base_domain\
 
   
Directory serving as a placeholder for any custom application files that you create
user_projects\domains\base_domain\
 
 
fileRealm.properties
File containing ACL, users, and groups that can be used for the default security realm when Compatibility security is used
 
pointbase.ini
File containing initialization information for a PointBase JDBC database.
 
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
 
apacheLog4jCfg.xml
File specifying the WebLogic Integration BPM logging configuration and logging levels for WebLogic Server
 
wli-config.properties
File containing domain-specific parameters that are used by Business Processes.
 
workshop.properties
File containing domain-specific parameters for compatibility with 8.1 Web Services Stack.
 
jws-config.properties
File containing Business Process Management-related JMS information used for compatibility with 8.1 Web Services Stack.
 
URLs.dat
File containing the URL for the Pointbase 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.
 
startManagedWebLogic.cmd
startManagedWebLogic.sh
Scripts used to start a Managed Server on Windows and UNIX systems, respectively.
 
startPointBaseConsole.cmd
startPointBaseConsole.sh
Scripts used to start the PointBase console on Windows and UNIX systems, respectively.
 
startWebLogic.cmd
startWebLogic.sh
Scripts used to start the Administration Server on Windows and UNIX systems, respectively.
 
stopManagedWebLogic.cmd
stopManagedWebLogic.sh
Scripts used to stop a Managed Server on Windows and UNIX systems, respectively.
 
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 Understanding Domain Configuration.
config\deployments\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is then used for staging an application when the staging mode of the application is staged.
config\deployments\
readme.txt
File providing information about the directory, which initially serves as a placeholder, and is then used for staging an application when the staging mode of the application 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).
 
cgDataSource-jdbc.xml
Global XA JDBC Data Source module for the domain configured for advanced Web services and Business Process Management
 
cgDataSource-nonXA-jdbc.xml
Global non-XA JDBC Data Source module for the domain configured for Business Process Management.
 
bpmArchDataSource-jdbc.xml
Global XA JDBC Data Source module for the domain configured for Business Process management archiving.
config\jms\
conversational-jms.xml
Global JMS module for the domain configured for Business Process Management.
 
wseejmsmodule-jms.xml
Global JMS module for the domain configured for advanced Web Services.
config\lib\
readme.txt
 
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.
 
security.xml
File used for creating user groups and roles that establish identity and access to domain resources.
 
startscript.xml
File used to create the *.cmd and *.sh files that are placed into the domain's root and bin directories.
 
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\
DefaultAuthorizerInit.ldift
DefaultAuthenticatorInit.ldift
DefaultRoleMapperInit.ldift
XACMLRoleMapperInit.ldift
XAMLAuthorizerInit.ldift
Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see WebLogic Security Providers in Understanding WebLogic Security at http://e-docs.bea.com/wls/docs92/secintro/archtect.html#archtect_0111.
 
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 boot 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.
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\
 
Directory to be used for the file store for system resources.
wliconfig\
 
Directory to be used for the file storing Event Generator and Application Integration information.
 
AIConfiguration.xml
File containing information about the Application views created in the domain.
 
EmailEventGen.xml
File containing information about the email Event Generators created in the domain.
 
FileEventGen.xml
File containing information about the file Event Generators created in the domain.
 
HttpEventGen.xml
File containing information about the http Event Generators created in the domain.
 
JMSEventGen.xml
File containing information about the jms Event Generators created in the domain.
 
MQEventGen.xml
File containing information about the mq Event Generators created in the domain.
 
RDBMSEventGen.xml
File containing information about the rdbms Event Generators created in the domain.
 
TibRVEventGen.xml
File containing information about the tibcoRv Event Generators created in the domain.
 
TimerEventGen.xml
File containing information about the timerEvent Generators created in the domain.

Resources and Services Configured

The following table identifies the resources and services configured in a domain extended with the WebLogic Integration BPM extension template. Prior to extending the domain, the WebLogic Integration BPM extension Template requires the WebLogic Advanced Web Services (wls_webservices) and Workshop for WebLogic extension (workshop_wl) template to be applied on the domain.

Table 10 Resources and Services Configured in WebLogic BPM Extension 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.
For information about naming the Administration Server during domain creation, see Resources and Services Configured for WebLogic Server Domain Template on page 1-19
Application Deployments
WLI System EJBs
WLI System EAR :
Adds the following EJBs Module:
  • wliadmin: Adds WLI Admin EJB module
  • adminhelper :Adds WLI Admin Helper EJB module
  • tracking: Adds WLI Process Tracking EJB module
  • proxydispatcher: Adds WLI Process Proxy Dispatcher EJB module
  • wlai-processors-ejb.jar: Adds WLI AI Message Processors EJB module
  • wlai-rarupload-ejb.jar: Adds WLI AI RAR Upload EJB module (upload utilities for AI)
  • rosettanet: Adds WLI RosettaNet EJB module
  • ebxml : Adds WLI ebXML EJB module
  • message-tracking : Adds WLI Message Tracking EJB module
  • transport/responsehandler: Adds Sync/Async Transport EJB module
  • Adds the following Web applications:
    • sync2AsyncIM: adds the Sync Async Web Application with module name transport/http
    • TransportServlet : Adds B2B HTTP Transport Web Application with module name b2btransport-webapp
 
WLI Console
Adds the WLI BPM Console Web application
 
wlai-designtime
Defines the Application View design console needed to define new Application Views and publish them to a Workshop application.
 
B2BDefaultWebAppApplication
Adds a web application for B2B messages to work, targets to AdminServer and Cluster.
 
JWSQueueTransport
Adds the KNEX.bean.QueueTransport Message Driven Bean used by the Business Process to support JMS Transport
 
rdbmsEG_ear
Adds WLI RDBMSEG EAR for creating and managing rdbms Event Generators.
 
tibRVEG_ear
Adds WLI TIBCORVEG EAR for creating and managing tibcoRV Event Generators.
 
httpEG_ear
Adds WLI HTTPEG EAR for creating and managing http Event Generators.
 
mqEG_ear
Adds WLI MQEG EAR for creating and managing MQ Event Generators.
FileStore
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.
 
conversational-jms
Uses the JMS system resources provided by the WebLogic Integration BPM extension template.
JDBC Data Source
cgDataSource
Uses the XA JDBC data source provided by the Workshop for WebLogic extension template. Identifies the XA JDBC data source as a cgDataSource system resource.
cgDataSource-nonXA
Uses the non-XA JDBC data source provided by the Workshop For WebLogic extension template. Identifies the non-XA JDBC data source as a cgDataSource-nonXA system resource.
JDBC Store
cgJMSStore
Uses the JDBC store provided by the WebLogic Integration BPM extension template. The JDBC store is to be used with the JDBC data source, cgDataSource-nonXA, and the JMS server, cgJMSServer, as a persistent store, and is targeted to the Administration Server, AdminServer.
JDBC System Resources
cgDataSource
cgDataSource-nonXA
Uses the JDBC data source and connection pool setups provided by the Workshop For WebLogic extension template. These JDBC system resources are targeted to the Administration Server, AdminServer.
 
samplesDataSource
Uses the JDBC data source and connection pool setups provided by the Workshop For WebLogic extension template. These JDBC system resources are targeted to the Administration Server, AdminServer.
SAF Agent
ReliableWseeSAFAgent
Adds the SAF agent and targets it to the Administration Server, AdminServer.
JMS Connection Factory
cgQueue
Uses the JMS connection factory provided by the WebLogic Integration BPM extension template with JNDI Name weblogic.jws.jms.QueueConnectionFactory Identifies the JMS connection factory as a conversational-jms system resource and targets it to the Administration Server, AdminServer.
 
com.bea.wli.b2b.server.TopicConnectionFactory
JMS connection factory for B2B events, targeted to AdminServer.
 
wli.internal.egrdbms.XAQueueConnectionFactory
Uses the JMS connection factory provided by the WebLogic Integration BPM extension template with JNDI Name wli.internal.egrdbms.XAQueueConnectionFactory. Identifies the JMS connection factory as a conversational-jms system resource and targets it to the AdminServer
WS Reliable Delivery Policy
RMDefaultPolicy
Adds the Default Reliable Message Policy provided by the WebLogic Integration BPM extension.
JMS Queues
cgJWSQueue
Adds the JMS queue with JNDI name jws,queue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
wlwJWSBuffer
Adds the JMS queue with JNDI name jws.bufferqueue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
wlwJWSErrors
Adds the JMS queue with JNDI name jws.errorqueue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
 
WSInternaljms.internal.queue.WSStoreForwardQueuecgServer
Adds the JMS queue with local JNDI name WSInternaljms.internal.queue.WSStoreForwardQueuecgServer provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, WSStoreForwardInternalJMSServercgServer.
 
WSInternaljms.internal.queue.WSDupsEliminationHistoryQueuecgServer
Adds the JMS queue with local JNDI name WSInternaljms.internal.queue.WSDupsEliminationHistoryQueuecgServer provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, WSStoreForwardInternalJMSServercgServer.
 
WSInternaljms.internal.queue.WSDupsEliminationMessageQueuecgServer
Adds the JMS queue with local JNDI name WSInternaljms.internal.queue.WSDupsEliminationMessageQueuecgServer provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, WSStoreForwardInternalJMSServercgServer.
 
wli.internal.b2b.rosettanetencoder.queue
Adds the JMS queue for outbound RosettaNet messages with local JNDI name wli.internal.b2b.rosettanetencoder.queue and targets it to cgJMSServer.
 
wli.b2b.mt.event.stream_error
Adds the JMS queue for reporting (archiving) errors with local JNDI name wli.b2b.mt.event.stream_error and targets it to cgJMSServer.
 
wli.internal.msgtracking.queue
Adds the internal JMS queue with JNDI name wli.internal.msgtracking.queue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
 
wli.process.event.stream_error
Adds the JMS queue with JNDI name wli.process.event.stream_error provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
 
wli.internal.scheduling.queue
Uses the JMS queue with JNDI name wli.internal.scheduling.queue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
 
wli.internal.scscheduling.queue_error
Adds the internal JMS queue with JNDI name wli.process.event.stream_error provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.
 
wli.internal.ai.event_suspend
A queue that holds any event that was accepted from an AI event generator, but was suspended because of an ApplicationView being suspended. This queue is drained when the ApplicationView is resumed.
 
wli.internal.egfile.queue
Adds the internal JMS queue with JNDI name wli.internal.egfile.queue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer. Used by file Event Generator for holding events.
 
wli.b2b.failedmessage.queue
Adds the JMS queue for failed B2B messages with JNDI name wli.b2b.failedmessage.queue and targets it to cgJMSServer.
 
wli.internal.egmq.queue
Adds the internal JMS queue with JNDI name wli.internal.egmq.queue provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer. Used by mq EG for holding events.
 
wli.internal.instance.info.buffer_error
Adds the JMS queue with JNDI name wli.internal.instance.info.buffer_error provided by the WebLogic Integration BPM extension template. Identifies the JMS queue as a conversational-jms system resource and targets it to the JMS server, cgJMSServer.