Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Creating Extension Templates Using the WebLogic Configuration Template Builder

An extension template defines applications and services that can be used to extend an existing domain. This type of template is used when you are updating a domain. The applications and services stored in the selected extension templates are imported into the domain using the Configuration Wizard.

The Configuration Template Builder provides a simple means for creating extension templates which can be used as input to the Configuration Wizard. The process used to create an extension template is virtually the same as the process used to create a configuration template except that you are not prompted to define any infrastructure components.

(For information about updating a domain using the Configuration Wizard, see Extending Domains.)

# Overview of Creating an Extension Template Using the Configuration Template Builder

The following table summarizes the procedure for creating an extension template using the Configuration Template Builder.

You can quit the Configuration Template Builder at any time by clicking Exit.

Table 13-1 Steps for Creating Extension Templates

In this step . . . | You . . .
--- | ---
Creating a Configuration or Extension Template | Choose the type of template you want to create: configuration or extension.To create an extension template, choose Create an Extension Template. For details about creating a configuration template, see Creating Configuration Templates Using the WebLogic Configuration Template Builder.
Selecting a Configuration Source for your Extension Template | Choose an extension template or a domain directory from which you want to create a configuration template.
Describing Your Extension Template | Specify a description of the template that will be displayed within the Select a Configuration Extension Template window of the Configuration Wizard. (For more information about the configuration extension template window, see Selecting a Configuration Extension Template.)
Adding Applications to Your Extension Template | Review and modify, if desired, the list of applications to be included in your extension template.
Adding Files to Your Extension Template | Review and modify, if desired, the list of files to be included in your extension template.
Configuring JDBC for Extension Templates | Optionally, customize the Java Database Connectivity (JDBC) settings.
Configuring JMS for Extension Templates | Optionally, define parameters for Java Message Service (JMS).
Configuring Security Options in Your Extension Template | Optionally, create users, groups, and roles, then assign them to groups and global roles.
Preparing Text Files When Creating Extension Templates | Replace specific paths, filenames, and other environment-specific strings with replacement variables in text files contained in the template. Later, when a specific WebLogic configuration domain is being created, the Configuration Wizard replaces these variables with exact strings.
Creating Your Configuration Extension Template | Review the extension template, specify its name and directory for the extension template, and launch the process that creates it.

# Creating a Configuration or Extension Template

The Create a Configuration or Extension Template window prompts you to choose the type of template you want to create: a configuration template or an extension template. To create an extension template, choose Create an Extension Template.

Choose this option . . . | When you want to . . .
--- | ---
Create a Configuration 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 to create a new domain. To learn more about creating a configuration template, see Creating Configuration Templates Using the WebLogic Configuration Template Builder.
Create an Extension Template | Create a template in which you define applications and services that can be used to extend an existing domain.

# Selecting a Configuration Source for your Extension Template

The Select a Template Configuration 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:

1. Select the Select a Template tab.
2. Make sure that the Template Locations field contains the name of the required template extension directory. The templates displayed for selection reside in the specified directory. If you need to change the value in the Template Locations field:

1. Click Browse to invoke the Select a Template Directory dialog box.
2. In the dialog box, navigate to the appropriate directory or manually enter the pathname of the directory in the Location field.

A list of the extension templates available in the selected directory 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`.

3. Select an extension template from the list.
4. Click Next to proceed to the next configuration window.

## Choose a Domain Directory

To choose the directory of the domain from which you want to create an extension template:

1. Select the Select a Domain Directory tab.
2. Navigate to the domain directory from which you want to create an extension template.
3. Click Next to proceed to the next configuration window.

# Describing Your Extension Template

The Describe the Template window prompts you to provide a description that will be displayed in the Select a Configuration Extension Template window of the Configuration Wizard.

To enter template description information, do one of the following:

- If you selected a template in the Select a Template Configuration Source window, the information from the selected template is displayed here. Review the information and, if necessary, modify it to meet the needs of your extension template, as described in Describing the Template. Then click Next.
- If you selected a domain directory in the Select a Template Configuration Source window, enter the information required for your extension template, as described in Describing the Template. Then click Next.

# Adding Applications to Your Extension Template

The Add Applications window prompts you to:

- Review the list of applications that are currently defined
- Review the pathnames of the current and imported applications
- If necessary, change the relative directory into which applications are imported
- If necessary, omit applications from the list of files to be imported

For more information, see Adding Applications to Your Configuration Template.

# Adding Files to Your Extension Template

Extension templates generated from the designated template or domain directory include files from that configuration source. You may also want to include other files from your system or network. The Add Files window prompts you to review, add, or remove files in the template.

#### To add files to the template you are creating:

1. To view a current list of files that currently reside in your template, expand the Domain Root Directory and Applications Root Directory in the Current Template View pane.
2. To add or remove files, perform the following steps:

- In the Current Template View, select the destination directory to which you want to add a file.
- To add a file, navigate to the file within the File System View area and select Add File. You can limit the files displayed in this view by selecting a filter from the Show File Types drop-down list. For example, to display only files with the `.cmd` extension, select `*.cmd` from the drop-down list.
- To remove a file, select the file that you want to delete from the Current Template View pane, and select Remove File.

3. Repeat steps 1 and 2 for each file that you want to add or remove.
4. Click Next to proceed to the next configuration window.

# Importing SQL Scripts Into Your Extension Template

The Import 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 should be executed. For more information, see Adding SQL Scripts Into Your Configuration Template.

# Configuring JDBC for Extension Templates

All JDBC services included in the original domain or template are also included in the extension template you are creating. If you want to customize the extension template further, you may do so by adding, modifying, or removing these services.

WebLogic JDBC enables Java programmers to interact with common database management systems (DBMS) such as Oracle, Microsoft SQL Server, Sybase, and others. The WebLogic Configuration Template Builder gives you the option of configuring a database service for the domain by defining several WebLogic JDBC components:

- Connection pools—Ready-to-use groups of connections to your DBMS
- MultiPools—Groups of connection pools
- Data sources—Interfaces between applications and connection pools

The Database (JDBC) Options window prompts you to specify whether you want to define a database service. For more information, see Configuring a Database Service.

# Configuring JMS for Extension Templates

All JMS services included in the original domain or template are also included in the extension template you are creating. If you want to customize the extension template further, you may do so by adding, modifying, or removing these services.

WebLogic JMS provides access to enterprise messaging systems that enable applications to communicate with one another. To familiarize yourself with the features of WebLogic JMS, see Programming WebLogic JMS at the following URL:

http://e-docs.bea.com/wls/docs81/jms/index.html

The wizard allows you to change JMS attributes, especially those affected by changes to the JDBC configuration. Specifically, you can:

- Create and/or customize JMS connection factories
- Create JMS templates
- Create JMS destination keys and assign them to JMS templates
- Designate destinations and persistent stores
- Create and/or customize distributed destinations
- Create and/or customize JMS servers and assign them to specific WebLogic Server instances

For more information about configuring WebLogic JMS, see Configuring a Java Messaging Service.

# Configuring Security Options in Your Extension Template

Optionally, you can configure security parameters for your application—specifically, options to secure the application resources within the domain. You can provide security for an application resource using the following security features:

- Users and groups—Classification of individuals and collections of individuals who may be granted a security role. Typically, a group is a collection of users who share a role or function within a company, such as working in the same department.
- Global security roles—Dynamically computed privileges that are used to restrict access to WebLogic resources. These privileges are granted to or withheld from users according to which roles they are assigned.

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 created 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.

Task | Description
--- | ---
Configuring Users, Groups, and Global Roles | Define users, groups, and global roles for authentication purposes.
Assigning Users to Groups | 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.
Assigning Groups to Groups | Assign a group as a subgroup of another group, to add further granularity to security management
Assigning Users and Groups to Global Roles | Assign users and groups to the predefined WebLogic Server global security roles

# Preparing Text Files When Creating Extension Templates

The Configuration Template Builder automatically updates any standard scripts included in a template, such as start scripts, by replacing hard-coded values for various configuration 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 Preparing Scripts and Files With Replacement Variables.

# Creating Your Configuration Extension Template

The Create Template window prompts you to review details about the extension template, specify the name and directory for the extension template, and launch the process that creates it.

#### To create your extension template:

1. Review details about the configuration in the Configuration Summary and Configuration Details areas. If you need to modify any information, select Previous to return to the desired configuration windows.

You can limit the information displayed in this window by selecting a filter from the Summary View drop-down list.

2. Make sure that the Configuration Template Location field contains the name of the required configuration directory. If you need to change the value in this field:

1. Click Browse to invoke the Select the Template Creation Directory dialog box.
2. In the dialog box, navigate to the appropriate directory or manually enter the pathname of the directory in the Location field and click OK.

The configuration directory can be located anywhere on your system. By default, it resides in `BEA_HOME``\user_templates\``template``.jar`, where `BEA_HOME` is the directory that contains the product installation (by default, this directory is `c:\bea` on Windows), and `template``.jar` is the name that you specified for the JAR file.

3. Specify a name for the template in the Template Jar Name field by clicking within the field and modifying the contents.
4. After you verify the information displayed in the window, click Create.

The Creating Configuration window is displayed, indicating the status of template creation process. The Configuration Template Builder generates a JAR file that consists of all components required by the Configuration Wizard to generate a new domain, including the configuration settings that you provided.

5. Click Done on the Creating Configuration window.