![]() ![]() ![]() ![]() ![]() ![]() |
The following topics describe how to create a domain template:
The Create a New Template window is displayed when you start the Domain Template Builder as described in Starting the Domain Template Builder.
Table 2-1 describes the options that this window provides.
Create a template that defines applications and services that can be used to extend existing domains.
You can import applications and services stored in extension templates into an existing domain by using the Configuration Wizard. For more information, see Creating Extension Templates by Using the Domain Template Builder
|
Select Create a Domain Template and click Next.
The Select a Template Domain Source window is displayed.
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 select an existing domain as the source for the new template:
The Domain Template Builder verifies that the directory you selected contains a valid domain.
Note: | If the directory does not contain a valid domain, an error message is displayed. |
To select a domain template as the source for the new template:
The templates displayed for selection are located in the directory specified in the Locate Additional Templates pane. If you want to change the directory, click Browse, and then navigate to the appropriate directory or enter the path manually.
The Describe the Template window prompts you to provide a description for the template.
Note: | This description will be displayed in the Select a Template pane of the Select a Template Domain Source window. |
Table 2-2 describes the fields in the Describe the Template window.
Note: | Fields marked with an asterisk are required. |
The Add or Omit Applications window is displayed only 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 do the following tasks:
By default, the Domain Template Builder includes applications from the domain or template you specified as the source for the template that you are creating. For example:
Note: | When you create or extend a clustered domain (by using the Configuration Wizard or WLST) based on a template that contains applications with application-scoped JDBC or JMS resources, you may need to perform certain additional steps after creating or extending the domain. These steps are necessary to ensure that the application and its application-scoped resources are targeted and deployed properly. For more information about targeting and deploying application-scoped modules, see Deploying Applications and Modules with weblogic.deployer. |
To add applications in (or omit them from) 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 included with the WebLogic products. 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 by using this template, this path will point to the application files located 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 new template.
.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 Domain 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 Domain 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 must 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 lets you to review, add, or remove files in the template.
.cmd
extension, select *.cmd
from the drop-down list.Note: | You cannot remove files shown in red or their parent directories as they consist of 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 deselect 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. |
After adding and removing files as necessary, click Next.
The Add SQL Scripts window is displayed.
You can add your own SQL scripts to the new template, so that the scripts are available when you create a domain based on the template.
Note: | SQL scripts that are included with the product do not need to be added to 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 based on 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 use a template as basis for the new template, SQL files that are included in the source template are displayed in the Selected Database Scripts pane, organized by database type. |
To add SQL scripts to the template:
The Open dialog box is displayed.
The SQL files that you added are displayed in the Selected SQL Files pane. The Selected Database Scripts pane displays a tree-view of all the databases and associated SQL scripts included in the template.
You can change the order in which the SQL files are executed by using the Up and Down arrow icons. The specified sequence is reflected in the Selected Database Scripts pane.
To remove SQL scripts from the template:
The SQL scripts for the selected database displayed in the Selected Database Scripts pane are listed in the Selected SQL Files pane.
The Configure the Administration Server window is displayed.
Note: | If you are creating an extension template, the next window that is displayed is Security Configuration Options. For more information, see Configuring Security Options. |
In every domain, one server must be designated as the administration server: the central point from which the whole domain is managed.
You can access the administrator server by using the URL protocol://listen-address:listen-port
. The protocol
can be any of the following: t3
, t3s
, http
, https
.
You can define the listen-address
and listen-port
for the administration server in the Configure the Administration Server window of the Domain Template Builder.
For information about the fields of the Configure the Administration Server window, see “Configuring the Administration Server” in Creating WebLogic Domains by Using the Configuration Wizard.
After configuring the administration server, click Next.
The Configure Administrator Username and Password window is displayed.
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 required.
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. |
If you do not want to configure additional users, groups, and global roles, select No, and click Next. The Specify Start Menu Entries window is displayed.
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.
Note: | Depending on the template or domain selected, one or more users, groups, 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 Using Roles and Policies. |
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). |
When you finish updating your settings, click Next.
The Assign Users to Groups window is displayed.
The Assign Users to Groups window prompts you to assign users to groups. It is recommended that you add users to groups, because by managing groups you can manage multiple users more efficiently.
The current assignments for the selected group are displayed in the left pane.
To select all users in the list, click Select All. To deselect all users in the list, click Unselect All.
The list of groups associated with each user is updated to reflect the changes.
The Assign Groups to Groups window prompts you to designate one group as a subgroup of another, as a means of refining 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 . |
The current assignments for the selected group are displayed in the left pane.
To select all groups in the list, click Select All. To unselect all groups in the list, click Unselect All.
The list of subgroups associated with each group is updated to reflect your changes.
The Assign Users and Group to Global Roles window is displayed.
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 Securing WebLogic Resources Using Roles and Policies.
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. |
The current assignments for the selected role are displayed in the left pane.
To select all users and groups in the list, click Select All. To unselect all users and groups in the list, click 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.
The Specify Start Menu Entries window displayed.
Note: | If you are creating an extension template, the next window that is displayed is Prepare Scripts and Files with Replacement Variables. For more information, see Prepare Scripts and Files with Replacement Variables. |
The Specify Start Menu Entries window prompts you to create items to be added to the Windows Start menu.
The next step depends on the source for the new template that you are creating.
Add, modify, or delete entries as required by your domain, by using the guidelines provided in Table 2-4.
To delete an entry, click the tab for the Start menu entry, and click Delete.
When you finish updating your settings, click Next.
The Prepare Scripts and Files with Replacement Variables window is displayed.
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 are selected. |
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 in the Select File pane to revert to the saved version of the file. |
The Review the Domain Template window is displayed.
The following table defines the replacement variables most commonly used in files.
The Review WebLogic Domain Template window allows you to review the settings for the new template before it is created.
Note: | You can limit the type of information displayed in the Template Summary window by using 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.
You can change the location either by clicking Browse and navigating to the appropriate directory or by entering the path manually.
The template directory can be located anywhere in your system. By default, it resides in BEA_HOME
\user_templates
, where BEA_HOME
is the directory that contains the product installation (by default, on Windows, this directory is c:\bea
).
The Creating Template window displays 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.
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 in the Specify Start Menu Entries window, a startmenu.xml
file that contains the specified entries is included in the template. When you create a domain by using this template, Start menu entries are created by using the values specified in this file. For more information, see “Files Typically Included in a Template” in
Domain Template Reference.
![]() ![]() ![]() |