The process used to create an extension template is virtually the same as the process used to create 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.
The following topics describe the steps you use to create an extension 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. To create an extension template, choose Create 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 to create a new domain. To learn more about creating a domain template, see Creating Extension Templates Using the Domain Template Builder..
|
|
The Select a Template Domain Source window prompts you to choose the application template or domain directory from which you want to create an extension template.
To select an extension template as your extension template source:
A list of the extension templates available in the directory specified in the Locate Additional Templates field is displayed. Templates are organized by category. For example, the predefined extension templates provided with the product installation are listed together under the heading BEA
.
If you need to change directories:
Information about the selected template will be displayed in the Description and Author fields.
To select a domain as your extension template source:
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, do one of the following:
The Add or Omit Applications window prompts you to:
For more information, see Add or Omit Applications.
By default, the Domain Template Builder includes files from the domain or extension template you specified as the source for the extension 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 automatically by the 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 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 want to include other files from your system or network, as required by your application. The Add Files window prompts you to review, add, or remove files in the template.
To add files to the template you are creating:
.cmd
extension, select *.cmd
from the drop-down list.The Add SQL Scripts window prompts you to add SQL scripts for each database that you expect to be used with the domains that you extend using this template. You can also specify the order in which the scripts should be executed. For more information, see Add SQL Scripts.
Optionally, you can configure security parameters for your application—specifically, for the application resources within the domain. You can provide security for an application resource using the following security features:
For example, to leverage individual skills, many Web development teams divide system administration responsibilities into distinct roles. A team may then assign a different level of permission to each role. Each project might give only one or two team members permission to deploy components, but allow all team members to view the WebLogic Server configuration.
WebLogic Server supports such role-based development by providing four default global roles that determine access privileges for system administration operations: Admin, Deployer, Operator, and Monitor.
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). |
The Security Configuration Options window prompts you to set security options for your application. If you choose No, the security settings in the extension template that is created match those defined in the template or domain on which it is based. If you choose Yes, you are prompted, in subsequent windows, to configure the security as described in the following table.
Define users, groups, and global roles for authentication purposes. For instructions, see Configure Users, Groups, and Global Roles.
|
|
Assign users to groups. Groups allow you to manage a number of users at the same time. This is generally more efficient than managing each user individually. For instructions, see Assign Users to Groups.
|
|
Designate a group as a subgroup of another group, to add further granularity to security management. For instructions, see Assign Groups to Groups
|
|
Assign users and groups to predefined WebLogic Server global security roles. For instructions, see Assign Users and Groups to Global Roles.
|
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 variables. The Configuration Wizard can later replace these variables with new hard-coded values during the configuration of a new domain.
If you like, you can prepare additional files that are included with your template by manually inserting replacement variables. For more information, see Prepare Scripts and Files with Replacement Variables.
The Review WebLogic Domain Template window allows you to review the details for your extension template before you initiate its creation.
To review the extension template settings:
Note: | You can limit the type of information displayed in the Domain Summary window by selecting a filter from the View drop-down list |
The Create an Extension Template window prompts you to specify the name and directory for the extension template, and launch the process that creates it.
To create your extension 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 only the applications and services specified in the extension template.