![]() ![]() ![]() ![]() ![]() ![]() |
This section provides information and examples for some common template creation tasks:
The following example explains how to create a custom domain template by using the Avitek Medical Records Sample Domain. A domain template defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system parameters. Once you have created this sample domain, you can then use this template as input to the Configuration Wizard to create a new Medical Records sample domain.
Note: | This example is based on the assumption that you have installed the WebLogic Server samples while installing the product. |
Note: | If the template you are creating is to be used as the source for a new template, the information you provide in this window will be displayed in the Select a Template area of the Select a Template Domain Source window. |
For this example, enter the following information.
Avitek Medical Records Sample Domain
Oracle Corporation
Oracle
Create the Avitek Medical Records domain in a directory outside of the installed kit. The Avitek Medical Records is a WebLogic Server sample application suite that concisely demonstrates all aspects of the Java EE platform.
The applications in this domain are included with the WebLogic Server software; so you cannot change the relative path of the directory into which they are imported. Because these applications already reside on your system, they are not copied into the template.
For this example, leave all applications selected, and click Next.
.cmd
, .sh
, .xml
, .properties
, and .ini
.bin
directorylib
directorysecurity
directory that are not created automatically during domain creation. For example, XACMLAuthenticatorInit.ldift
and XACMLRoleMapperInit.ldift
are not included by default.config
directory that are not included automatically by the Domain Template Builder during template creation. For example, config.xml
and any JDBC and JMS resources defined in config.xml
are not displayed in the Current Template View pane by default because the Domain Template Builder includes them in the template, automatically, during template creation.Note: | Because the applications to be included in this template are provided with the product installation, they are not copied into the template. Therefore, they are not listed under Applications Root Directory in the Current Template View pane. |
If other files exist in your system and are required for deployed applications, you can add them in this window.
For this example, we add a patient data file that is not included by default. To add the required file, do the following:
The Medical Records sample uses the default PointBase demo database included with your product installation; so you do not need to add SQL scripts in this example.
However, you may want to use the Medical Records sample with other databases, such as Oracle or MySQL.
To add database files for Oracle, complete the following procedure.
Oracle
from the Type drop-down list, and Any
from the Version drop-down list.
BEA_HOME
\wlserver_10.3\samples\server\medrec\setup\db
In this pathname, WL_HOME
represents the directory in which you installed WebLogic Server, typically C:\bea\wlserver_10.3
.
The names of the files that you added are displayed in the Selected SQL Files list and the Selected Database Scripts pane.
To add database files for MySQL, complete the following procedure.
MySQL
from the Type drop-down list, and Any
from the Version drop-down list.
BEA_HOME
\wlserver_10.3\samples\server\medrec\setup\db
The names of the files that you added are displayed in the Selected SQL Files list and the Selected Database Scripts pane.
In this example, leave the default values selected and click Next.
By default, the username/password combination for the Medical Records domain is weblogic/weblogic
. You can configure additional users, groups, and global roles.
For this example, accept the default settings, and click Next.
To create a Start menu entry for starting the Medical Records server:
Start Medical Records Server
.bin/startWebLogic.cmd
.It is not necessary to complete the remaining fields for this example.
To create a Start menu entry for stopping the Medical Records server:
Stop Medical Records Server
.bin/stopWebLogic.cmd
. It is not necessary to complete the remaining fields for this example.
In this example, it is not necessary to edit any additional scripts or files.
For this example, enter my_medrec_template
in the Template jar name field.
By default, the template is created in BEA_HOME
\user_templates
, where BEA_HOME
is the directory that contains the product installation. You do not need to change the default in this example.
The following example shows how to create a custom extension template by modifying the Avitek Medical Records Sample Domain extension template provided with your product installation. An extension template defines applications and services that can be used to extend an existing domain. The process for creating an extension template is similar to the process for creating a domain template except that you are not prompted to configure the administration server, assign an administrator username and password, or specify Start menu entries, because these domain settings are already defined in the domain to be extended.
In this example, you create a customized MedRec extension template in which you add support for an additional Medical Records user. Once you have created the sample extension template, you can extend an existing WebLogic domain with the Medical Records sample domain by specifying your new extension template as input to the Configuration Wizard.
To create a customized MedRec extension template, complete the following procedure:
For this example, you do not need to change anything.
For this example, you do not need to add or omit any applications.
In this example, the Avitek Medical Records Sample Domain extension template includes a separately defined applications directory. Therefore, the applications in the template are listed under Applications Root Directory in the Current Template View pane.
For this example, you do not need to add any database scripts.
Because you are going to define an additional user in this example, select Yes, and click Next.
In this example, you are going to define a new physician and assign the physician to an existing group.
In this example, you need to remove joe@md.com
from the Administrators
group and assign to the MedRecPhysicians
group.
Administrators
group is selected.
A list of current assignments for the Administrators
group is displayed in the left pane.
joe@md.com
.MedRecPhysicians
.
A list of current assignments for the MedRec Physicians
group is displayed in the left pane.
joe@md.com
. The list of groups associated with joe@md.com
is updated to reflect the change.In this example, it is not necessary to edit any additional scripts or files. Click Next.
For this example, enter my_medrec_ext_template
in the Template jar name field.
By default, the template is created in BEA_HOME
\user_templates
, where BEA_HOME
is the directory that contains the product installation. You do not need to change the default in this example.
![]() ![]() ![]() |