2.10 WebLogic Server Examples Extension Template

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.

config\startup\

readme.txt

File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup.

console-ext\

readme.txt

File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console.

init-info\

domain-info.xml

File used to identify domain creation and extension information. Such information includes the identity of the components in the domain, the location of the JDK and applications directory used by the domain, and the templates used to create and extend the domain.

init-info\

security.xml

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

init-info\

startscript.xml

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

init-info\

tokenValue.properties

File that contains the actual values to substitute for the tokens specified in the start scripts.

lib\

readme.txt

File providing information about the directory, which initially serves as a placeholder for the domain's libraries. The JAR files in this directory are added dynamically to the end of the server classpath at server startup.

security\

DefaultAuthenticatorInit.ldift

DefaultAuthorizerInit.ldift

DefaultRoleMapperInit.ldift

XACMLAuthorizerInit.ldift

XACMLRoleMapperInit.ldift

Files used for bootstrapping tasks, including authentication (user and group), authorization, and role mapping. These files contain LDAP-specific information.

Note: WebLogic domains created with this release use the XACML providers, by default. These XACML security providers are compatible with policies and roles created using the WebLogic Authorization provider (DefaultAuthorizer) and WebLogic Role Mapping provider (DefaultRoleMapper). For more information, see "WebLogic Security Providers" in Oracle Fusion Middleware Understanding Security for Oracle WebLogic Server.

security\

SerializedSystemIni.dat

File containing encrypted security information.

servers\AdminServer\security\

boot.properties

File containing server startup properties, including the user name and password required to start the server (in encrypted format). It is generated only when you select development startup mode.

This file enables you to bypass the prompt for user name and password during a server's startup cycle. For more information, see "Provide User Credentials to Start and Stop Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

user_staged_config\

readme.txt

File providing information about the directory, which initially serves as a placeholder for configuration information optionally staged by an administrator to be copied to managed servers in the domain.

WseeFileStore\

n.a.

Directory to be used for the file store for system resources.

Administration Server

AdminServer

Uses the Administration Server provided in the base WebLogic Server domain. The default name is AdminServer, unless changed during domain creation. The Administration Server referenced in the extension template is examplesServer.

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

Application Deployments

ejb20BeanMgedEar

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.