Creating WebLogic Configurations Using the Configuration Wizard
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.)
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.
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. |
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.) |
|
Review and modify, if desired, the list of applications to be included in your extension template. |
|
Review and modify, if desired, the list of files to be included in your extension template. |
|
Optionally, customize the Java Database Connectivity (JDBC) settings. |
|
Optionally, define parameters for Java Message Service (JMS). |
|
Optionally, create users, groups, and roles, then assign them to groups and global roles. |
|
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. |
|
Review the extension template, specify its name and directory for the extension template, and launch the process that creates it. |
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.
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 a template in which you define applications and services that can be used to extend an existing domain. |
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 choose the directory of the domain from which you want to create an 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:
The Add Applications window prompts you to:
For more information, see Adding Applications to Your Configuration 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.
.cmd
extension, select *.cmd
from the drop-down list.
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.
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:
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.
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://download.oracle.com/docs/cd/E13222_01/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:
For more information about configuring WebLogic JMS, see Configuring a Java Messaging Service.
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:
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.
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.
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.
You can limit the information displayed in this window by selecting a filter from the Summary View drop-down list.
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.
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.