|
|
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.
The following topics describe the steps for creating an extension template:
The Create a New Template window is displayed when you start the Domain Template Builder as described in Starting the Domain Template Builder.
Select Create an Extension 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 application template or domain directory from which you want to create an extension template.
To select an extension template as the source for the new extension template:
The templates are grouped by category.
The extension 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.
To select a domain as the source for the new extension template:
The Describe the Template window prompts you to provide a description for the template.
| Note: | The description that you provide here will be displayed in the Select a Template pane of the Select a Template Domain Source window. |
For information about the fields in the Describe the Template window, see Table 3-2.
The Add or Omit Applications window is displayed.
In this window, you can do the following:
For more information, see Add or Omit Applications.
After performing the required steps, click Next. The Add Files window is displayed.
By default, the Domain Template Builder includes files from the domain or extension template that you specified as the source for the new extension template. In the Add Files window, you can review, add, and remove files in the template.
For more information, see Add Files.
After performing the required steps, click Next. The Add SQL Scripts window is displayed.
In the Add SQL Scripts window, you can 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.
After performing the required steps, click Next. The Security Configuration Options window is displayed.
Optionally, you can configure security parameters for the application resources within the domain. You can provide security for an application resource by 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). |
In the Security Configuration Options window, you can set security options for your application.
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 want to, you can prepare additional files to be included with your template by manually inserting replacement variables. For more information, see Prepare Scripts and Files with Replacement Variables.
After performing the required steps, click Next. The Review WebLogic Domain Template window is displayed.
In the Review WebLogic Domain Template window, you can review the settings for the new extension 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 an Extension Template window prompts you to specify the name and directory for the extension 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 only the applications and services specified in the extension template.
|
icon.