The following topics describe each step required to create a new domain template:
The Create a New Template window prompts you to choose the type of template you want to create: a domain template or an extension template.
Create a template that defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system parameters. You can then use this template as input to the Configuration Wizard, WLST Offline, or the unpack command to create a new domain. \
|
||
Create a template that defines applications and services that can be used to extend an existing dominies applications and services stored in the selected extension templates are imported into an existing domain using the Configuration Wizard. To learn more about creating an extension template, see Creating Extension Templates Using the Domain Template Builder.
|
The Select a Template Domain Source window prompts you to choose the domain or domain template from which you want to create a domain template.
To choose a domain as the source for your template:
The Domain Template Builder verifies that the directory you selected contains a valid domain. If it does not, an error message is displayed.
To choose a domain template as the source for your template:
A list of the domain templates available in the selected directory is displayed in the Templates pane. Templates are organized by category. For example, the predefined domain templates provided with your product installation are listed together under the heading BEA
.
The Describe the Template window prompts you to provide a description that will be displayed in the Select a Template area of the Select a Template Domain Source window.
To enter template description information:
Enter a description of the domain template. A valid description consists of a string of characters that can include spaces.
|
Note: | The Add or Omit Applications window is displayed if applications are included in the template or domain selected in Select a Template Domain Source. |
The Add or Omit Applications window allows you to:
By default, the Domain Template Builder includes applications from the domain or template you specified as the source for the template you are creating. For example:
config.xml
file using the app-deployment
element that are not considered internal applications in your product installation are included by default.Note: | If you create a template that contains applications with application-scoped JDBC and/or JMS resources, and subsequently use the template as input to the Configuration Wizard or WLST Offline to create or extend a clustered domain, you may need to perform additional steps (after the domain is created or extended) to make sure that the application and its application-scoped resources are targeted and deployed properly in a clustered environment. For more information on the targeting and deployment of application-scoped modules, see "Deploying Applications and Modules" in Deploying Applications to WebLogic Server at the following URL: |
Note: |
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/deployment/deploy.html |
To add or omit applications in the template:
The applications displayed reside in the directory specified in the Current Application Path field. The applications are copied into your template from this location.
Note: | Some of the applications listed in the Applications pane may be provided with your WebLogic software. You cannot change the relative paths for these applications. When you select these applications in the Applications pane, the Imported Application Path field is replaced by an Internal Application Path. Because these files are installed on your system during your product installation, they are not copied into the template at template creation time. When you create a domain using this template, this path will point to the application files contained in your product installation directory. |
By default, the Domain Template Builder includes files from the domain or template you specified as the source for the template you are creating. For example:
.cmd
, .sh
, .xml
, .properties
, and.ini
..pem
extension defined in the SSL configuration for your domainbin
directorylib
directorysecurity
directory that are not created automatically during domain creation. For example in WebLogic, XACMLRoleMapperInit.ldift
is not created automatically, and therefore is included in the template by default when creating a template. The XACMLAuthenticatorInit.ldift
file is included by default while creating a domain in AquaLogic Service Bus. config
directory that are not included by the Template Builder automatically 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 Template Builder includes them in the template, automatically, during template creation.Note: | The servers directory is not included in the template by default. If you have configured additional security data such as users, groups, or roles, through the WebLogic Server Administration Console or other online tools, it has been stored in the LDAP server and will not be included in the template. You will need to export the data first and then import it into the target domain. |
You may also need to include other files from your domain or file system that are required by the applications.
The Add Files window prompts you to review, add, or remove files in the template. To add files into the template you are creating:
.cmd
extension, select *.cmd
from the drop-down list.Note: | You cannot remove files shown in red or their parent directories as they comprise the applications defined in the config.xml file in the template source. These files will be included by default in the template being created. If you do not want these files included in your template, you must remove the application with which they are associated. To do so, click Previous to return to the Add or Omit Applications window and clear the appropriate check box for the application. |
Note: | If you attempt to add a file that is created automatically by the Configuration Wizard at domain creation time, an error message is displayed. |
SQL scripts that are created by the user can be added to your template. Adding SQL scripts to your template is optional. You can add SQL scripts that you have created to the template, so that they are available when you create a domain using the template.
Note: | SQL scripts that are provided by the product do not need to be added to the template. An example of SQL scripts provided by WebLogic Portal, are located in weblogic_home/portal/db. Since you can access these scripts as part of the product installation, you do not need to include the scripts inside the template. |
The Add SQL Scripts window prompts you to add SQL scripts for each database that you expect to be used with the domains created from this template. You can also specify the order in which the scripts are executed. When you create a domain using this template, the databases and associated SQL scripts that you include are displayed in the Run Database Scripts window of the Configuration Wizard.
Note: | If you are using a template as your template source, any SQL files that are included in the template source are displayed in the Selected Database Scripts pane, organized by database type. If desired, you can remove specified SQL scripts. For instructions, see To remove SQL scripts from your template:. |
To add SQL scripts to your template:
The Add SQL File(s) dialog box is displayed.
The SQL files that you added are displayed in the Selected SQL Files list and the Selected Database Scripts pane of the Add SQL Scripts window. The Selected Database Scripts pane displays a tree-view of all the databases and associated SQL scripts included in the template.
The specified sequence is reflected in the Selected Database Scripts pane. When you create a domain based on this template, this information is displayed in the Run Database Scripts window of the Configuration Wizard.
To remove SQL scripts from your template:
The SQL scripts for the selected database displayed in the Selected Database Scripts pane are listed in the Selected SQL Files pane.
Note: | If you are creating an extension template, the next configuration window displayed is Security Configuration Options. For more information, see Configuring Security Options in Your Extension Template. |
In every domain, one server must be designated the Administration server: the central point from which the whole domain is managed. The Configure the Administration Server window prompts you to define configuration information for the Administration Server. This information is used to access the Administration Server in the domain.
Servers can be reached using the following URL: protocol://listen-address:listen-port
In this URL, protocol
can be any of the following:
listen-address
and listen-port
are defined in the Configure the Administration Server window.
To configure the Administration Server:
Review the values displayed in the window and modify them as necessary, using the guidelines provided in the following table. When you finish updating your settings, click Next.
Each server instance in your product environment must have a unique name, regardless of the domain or cluster in which it resides, and regardless of whether it is an Administration Server or a Managed Server. In addition, the name of the Administration Server must be unique among all component names within the domain.
This value is specified for identification purposes only; it is not used as part of the URL for applications that are deployed on the server. The server name is displayed in the WebLogic Server Administration Console. In addition, if you use WebLogic Server command-line utilities or APIs, you must specify this name to identify the server.
|
||||
From the drop-down list, select a value for the listen address. Valid values for the listen address are as follows:
localhost (valid only for requests that are issued from the computer on which the server is running)
If you identify the listen address for a server instance as localhost, non-local processes cannot connect to the server instance. Only processes on the machine that hosts the server instance can connect to the server instance. If the server instance must be accessible as localhost (for example, if you create administrative scripts that connect to localhost), and it must also be accessible by remote processes, select All Local Addresses. The server instance determines the address of the machine and listens on it.
To learn more about Listen Addresses, see Specifying Listen Addresses
|
||||
Enter a valid value for the listen port to be used for regular, non-secure requests (via protocols such as HTTP and T3). The default value is 7001. If you leave this field blank, the default value is used.
For more information, see Specifying Listen Ports
|
||||
Enter a valid value to be used for secure requests (via protocols such as HTTPS and T3S). The default value is 7002. If you leave this field blank, the default value is used.
For more information, see Specifying Listen Ports.
|
||||
If you want to limit the valid listen address for a server, use the guidelines for specifying listen addresses provided in the following table.Specifying Listen Addresses
Refer to the following guidelines when specifying listen ports and secure listen ports:
http://
hostname
/myfile.html
instead of http://
hostname
:
portnumber
/myfile.html
.When you create a domain template, the administrator username and password from the original domain or template are included in your new template. You can modify this username and password if desired. In addition, you can provide extra security for application resources using the following security features:
To modify the administrator username and password:
Do not use commas or any characters in the following comma-separated list: \t
, < >
, #
, |
, &
, ?
, ( )
, { }
. User names are case sensitive.
Note: | Do not use the password=weblogic in a production environment. |
The Configure Users, Groups and Global Roles window is displayed in the Domain Template Builder in the following circumstances:
Users, groups, and global roles are defined as follows:
The Configure Users, Groups and Global Roles window prompts you to define users, groups, and roles for authentication purposes. You must define at least one user.
Depending on the template or domain selected, one or more users, groups, and/or roles may be defined already. In addition, WebLogic Server defines a default set of groups and roles. For a list of the default groups and roles defined in WebLogic Server, see "Users, Groups, and Security Roles" in Securing WebLogic Resources at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/secwlres/secroles.html
To configure users, groups, and global roles:
WARNING: | Do not make the default global security roles for Administrative and Server resources more restrictive. If you eliminate any existing security roles, you risk degrading WebLogic Server operation. You can, however, make the default security roles more inclusive (for example, by adding new security roles). |
"Users, Groups, and Security Roles" in Securing WebLogic Resources at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/secwlres/secroles.html
The Assign Users to Groups window prompts you to assign users to groups. BEA recommends adding users to groups because by managing groups you can manage multiple users simultaneously.
The current assignments for the selected group are displayed in the left pane.
To select all users in the list, choose Select All. To unselect all users in the list, choose Unselect All.
The list of groups associated with each user is updated to reflect your changes.
The Assign Groups to Groups window prompts you to designate one group as a subgroup of another group, as a means of refining the management of security for your domain.
Note: | You should not assign groups recursively. For example, do not assign groupA as a subgroup of groupB and groupB as a subgroup of groupA . WebLogic Server does not support this type of recursion. |
To assign groups to other groups:
The current assignments for the selected group are displayed in the left pane.
To select all groups in the list, choose Select All. To unselect all groups in the list, choose Unselect All.
The list of subgroups associated with each group is updated to reflect your changes.
The Assign Users and Groups to Global Roles window prompts you to assign users and groups to the global security roles defined by WebLogic Server. For a list of the default roles and the privileges that users or groups in these security roles are granted, see "Default Global Roles" in "Users, Groups, and Security Roles" in Securing WebLogic Server at
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/secwlres/secroles.html#default_roles
.
Note: | You must assign one or more users or groups (containing one or more users) to the Administrator role to ensure that there is at least one user who can boot WebLogic Server. |
To assign users and groups to global security roles:
The current assignments for the selected role are displayed in the left pane.
To select all users and groups in the list, choose Select All. To unselect all users and groups in the list, choose Unselect All.
The Role list corresponding to each user and group is updated to reflect the global roles to which the user and group are assigned.
Note: | If you are creating an extension template, the next configuration window displayed is Prepare Scripts and Files with Replacement Variables. For more information, see Prepare Scripts and Files with Replacement Variables. |
"Users, Groups, and Security Roles" in Securing WebLogic Resources at
http://download.oracle.com/docs/cd/E13222_01/wls/docs100/secwlres/secroles.html
The Specify Start Menu Entries window prompts you to create items to be added to the Windows Start Menu. How you proceed depends on what you have chosen as the source for your custom template.
To specify Start Menu entries:
Add, modify, or delete entries as required by your domain, using the guidelines provided in the following table. To delete an entry, click the tab for the Start Menu entry and click Delete. When you finish updating your settings, click Next.
Specify the program to be run when the shortcut is selected. A list of the programs defined by the template source is shown in the drop-down list. To use a predefined program, select it from the drop-down list.
|
||
When you are creating a template, you want the scripts and files that you are packaging with your template to be free of local domain environment settings and ready for use by the Configuration Wizard. The Domain Template Builder automatically updates any standard scripts included in a template, such as start scripts, by replacing hard-coded values for various domain environment settings with replacement variables. The Configuration Wizard can later replace these variables with new hard-coded values during the configuration of a new domain.
The Prepare Scripts and Files with Replacement Variables window allows you to replace hard-coded strings with replacement variables in files that have not been updated by the Domain Template Builder.
Note: | The check boxes of files that were automatically updated by the Domain Template Builder contain a check. |
To insert replacement variables into your files:
The replacement variable replaces the selected string. The Configuration Wizard later substitutes literal strings for the replacement variables to set up a specific WebLogic domain. For definitions of the available replacement variables, see Replacement Variable Definitions.
Note: | You can also click Reset within the Select File area to revert to the saved version of the file. |
The following table defines the replacement variables most commonly used in files.
The Review WebLogic Domain Template window allows you to review a detailed specification for your domain template before you start creating it.
To review the domain template settings:
Note: | You can limit the type of information displayed in the Template Summary window by selecting a filter from the View drop-down list. |
The Create a Template window prompts you to specify the name and directory for the domain template, and launch the process that creates it.
To create your domain template:
The template directory can be located anywhere on your system. By default, it resides in BEA_HOME
\user_templates
, where BEA_HOME
is the directory that contains the product installation (by default, this directory is c:\bea
on Windows).
The Creating Template window is opened to display status messages during the template creation process. The Domain Template Builder generates a JAR file that contains all the components required to generate a new domain, including the template settings that you provided.
Note: | The files included in a template vary, depending on the domain or template on which the template is based. For example, if you specify any Start Menu entries using the Specify Start Menu Entries window, a startmenu.xml file that contains the specified entries is included in your template. When you create your domain using this template, Start Menu entries are created using the values specified in this file. For more information, see "Files Typically Included in a Template" in Domain Template Reference at the following URL: |
Note: |
http://download.oracle.com/docs/cd/E13179_01/common/docs100/tempref/tempref.html |