Creating WebLogic Configurations Using the Configuration Wizard

Extending Domains

In some situations, you may need to extend an existing domain with the addition of a predefined application, a WebLogic Platform component product, or a set of services such as JDBC or JMS. For example, if you need to develop a WebLogic Workshop application for a domain in which you are already running a WebLogic Server application, you must extend the functionality of the domain by adding WebLogic Workshop to it.

The Configuration Wizard simplifies the task of extending an existing domain by using extension templates. An extension template defines applications and services that can be added to an existing domain. BEA delivers a set of predefined extension templates, which are described in "Template Reference" at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/tempref.html

Overview of Extending a Domain Using the Configuration Wizard

Note: Make sure that the domain is not active; you cannot update an active domain.

The following table summarizes the procedure for extending an existing domain using the Configuration Wizard.

Note: The following instructions are based on the assumption that you are running the Configuration Wizard in graphical mode. You can quit the Configuration Wizard at any time by clicking Exit.

Table 11-1 Steps for Extending Domains

In this step . . .	You . . .
Creating or Extending a Configuration	Choose whether to create a new WebLogic domain configuration or add to an existing domain configuration. To extend an existing domain configuration, choose Extend an existing WebLogic configuration. For details about creating a new WebLogic domain configuration, see Creating a New WebLogic Domain.
Choosing a WebLogic Configuration Directory	Select the host directory for the domain you want to update.
Selecting a Configuration Extension Template	Specify an extension (or application) template that allows you to add applications and services to an existing domain.
Configuring JDBC When Extending a Domain	Optionally, define parameters for Java Database Connectivity. (JDBC).
Configuring JMS When Extending a Domain	Optionally, define parameters for Java Message Service (JMS).
Targeting Applications and Services to Servers and Clusters When Extending a Domain	Optionally, define parameters for the target servers and clusters onto which you want to deploy application components, such as Web applications and EJB modules, and application services, such as JDBC or JMS components, or startup and shutdown classes.
Configuring Security Options When Extending a Domain	Optionally, create users, groups, and roles, then assign them to groups and global roles.
Creating Your WebLogic Configuration	Review your current configuration settings and launch the process that updates the domain.

Choosing a WebLogic Configuration Directory

The Choose a WebLogic Configuration Directory window prompts you to select an existing domain that you want to update with additional applications or services.

To choose a WebLogic configuration directory:

Use the navigation tree to select a valid domain directory: a directory that contains a config.xml file in the root directory of the domain and is indicated by the

icon.

Click Next to proceed to the next configuration window.

Selecting a Configuration Extension Template

The Select a Configuration Extension Template window prompts you to specify one or more extension templates to be included when the domain is updated. You must select at least one extension template. A set of predefined configuration extension templates is provided with WebLogic Platform. (For a description of these extension templates, see "Template Reference" at the following URL: http://download.oracle.com/docs/cd/E13196_01/platform/docs81/confgwiz/tempref.html.)

To select a configuration extension template:

Make sure that the Template Locations field contains the name of the required extension template directory. The templates displayed for selection reside in the specified directory. To change the value in the Template Locations field:

Click Add Location to invoke the Select a Template Directory dialog box.

Navigate to the appropriate directory or manually enter the pathname for it in the Location field. Click OK.

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 WebLogic Platform are grouped together under the heading BEA.

In the Configuration Extensions pane, select the check box for one or more extension templates that contain the applications or services that you want to import into your domain.

Click Next to proceed to the next configuration window.

Configuring JDBC When Extending a Domain

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

Connection pools—Ready-to-use group 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 configure a database service. For details about configuring JDBC, see Configuring a Database Service.

Configuring JMS When Extending a Domain

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 Configuration Wizard gives you the option of configuring JMS for your domain. To set up JMS, you define the following components:

Connection factory—Encapsulated connection configuration information that enables JMS applications to create a connection.
File and JDBC stores—Disk-based file stores and JDBC-accessible database stores, respectively, used to store persistent messages.
Destination Keys and JMS Templates—Keys to define the sort order for messages that arrive at a destination and templates to define multiple destinations with similar attribute settings.
JMS Servers—Servers that manage connections and message requests on behalf of clients.
Destinations—Queues (in point-to-point models) or topics (in publish/subscribe models) that serve as destinations and distributed destinations for a JMS server.

The Messaging (JMS) Options window prompts you to configure the WebLogic Java Message Service (JMS). For details, see Configuring a Java Messaging Service.

Targeting Applications and Services to Servers and Clusters When Extending a Domain

If you configure your domain for distribution across servers or clusters, it is a good idea to target the servers and clusters onto which you want to deploy applications, such as Web applications, or services, such as JMS and JDBC component services. The Targeting Options window prompts you to specify the servers and clusters onto which you want to deploy applications and services. For details, see Configuring Targets.

Note: The Configuration Wizard automatically modifies your existing configurations to support applications and services running in a clustered or non-clustered multi-server environment. For more information, see Autoconfiguration of Applications and Services.

Configuring Security Options When Extending a Domain

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 extended domain match those defined in the configuration source. 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

Creating Your WebLogic Configuration

The Create WebLogic Configuration window prompts you to review the details for your extension, and launch the process that updates the domain.

To create the extended domain:

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

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

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

Click Browse to invoke the Select the Applications Directory dialog box.

In the dialog box, navigate to the appropriate directory or manually enter its pathname in the Location field. Click OK.

After you verify the information displayed in the window, click Import to update the domain with the applications, services, and settings provided from the specified extension template.

The Creating Configuration window is opened to display status messages during the update process. The Configuration Wizard updates the config.xml file and other application-specific components in the configuration directory, as defined by the configuration template.
When the process is complete, the updated domain is ready.

Click Done in the Creating Configuration window.