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 Oracle Fusion Middleware Avitek Medical Records Development Tutorials 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-9 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\config\startup\ |
readme.txt |
File providing information about the directory, which initially serves as a placeholder, and is later used for storing system modules that contain startup plans. Startup plans are used to generate shell scripts that can be used as part of server startup. |
|
user_projects\domains\base_domain\console-ext\ |
readme.txt |
File providing information about the directory, which initially serves as a placeholder for custom extensions to the WebLogic Server Administration Console. |
|
user_projects\domains\base_domain\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-10 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 Section 2.1.2, "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. |