Creating WebLogic Domains Using the Configuration Wizard

Creating a New WebLogic Domain

Before you can develop and run WebLogic-based applications, you must first create a domain. The Configuration Wizard guides you through the process of creating a new domain quickly and easily, by selecting the product components you want to include in your domain, or by using domain templates.

The following topics describe the steps required to create a new domain using the Configuration Wizard:

Create or Extend a Domain

The Welcome window prompts you to choose whether you want to create a new domain or extend an existing one.

Choose this option . . .	When you want to . . .
Create a new WebLogic domain	Create a new domain that is configured to meet your requirements. Begin by selecting the product components you want to include in your domain, or a domain template to be used as the basis for your domain. Then modify settings as required.
Extend an existing WebLogic domain	Add product component functionality or support for additional applications and services to an existing domain. Begin by selecting the directory of the domain that you want to update. Then specify the product components you want to add, or identify the extension template you want to use for adding applications and services. You then have the option of customizing the JDBC connections to your database and the JMS file store, if defined. To learn more, see Extending Domains.

Choose this option . . .

When you want to . . .

Create a new WebLogic domain

Create a new domain that is configured to meet your requirements. Begin by selecting the product components you want to include in your domain, or a domain template to be used as the basis for your domain. Then modify settings as required.

Extend an existing WebLogic domain

Add product component functionality or support for additional applications and services to an existing domain. Begin by selecting the directory of the domain that you want to update. Then specify the product components you want to add, or identify the extension template you want to use for adding applications and services. You then have the option of customizing the JDBC connections to your database and the JMS file store, if defined. To learn more, see Extending Domains.

Select a Domain Source

The Select a Domain Source window prompts you to select the source from which to create the domain. You can select the product components to include in your domain, or select a custom template on which to base your domain.

Choose one of the following options for selecting the source for your domain:

Generate a domain configured automatically to support the following BEA products:

To use this option, select the check boxes associated with the components you want to include, and click Next.

Base this domain on an existing template

To use this option, manually enter the full pathname to the template in the Template location field and click Next, or click Browse to navigate to the directory containing the desired template. Select the domain template that contains the settings you want to use as the basis for your domain.

Note: While using the Configuration Wizard or WLST Offline to create or extend a clustered domain with a template that has applications containing application-scoped JDBC and/or JMS resources, you may need to perform additional steps (after the domain is created or extended) to make sure that the application and its application-scoped resources are targeted and deployed properly in a clustered environment. For more information on the targeting and deployment of application-scoped modules, see "Deploying Applications and Modules" in Deploying Applications to WebLogic Server at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs90/deployment/deploy.html

Configure an Administrator Username and Password

The Configure Administrator Username and Password window prompts you to specify a username and password to be used for starting the Administration Server.

To configure an administrator username and password:

Enter a valid value in the Username field. This name is used to boot the Administration Server and connect to it.

Do not use commas, tabs, or any characters in the following comma-separated list: < >, #, |, &, ?, ( ), { }. User names are case sensitive.

Enter a valid value in the User password field: a string of at least 8 case-sensitive characters. The password value is encrypted.

Note: Do not use the name/password combination weblogic/weblogic in a production environment.

Reenter the password in the Confirm user password field.

Optionally, enter a login description for this username.

Click Next to proceed to the next configuration window.

Specify the Server Start Mode and JDK

The Configure Server Start Mode and JDK window prompts you to specify the:

Choose the Startup Mode

Specify the startup mode for your domain as shown in the following table.

Choose this mode . . .	When . . .
Development	You are creating your applications. In this mode, the configuration of security is relatively relaxed, allowing you to auto-deploy applications.
Production	Your application is running in its final form. In this mode, security is fully configured.

Differences Between Domain Startup Modes

The following table describes the differences between development and production modes in terms of key functions.

Table 3-1 Differences Between Development and Production Modes

Function	In development mode . . .	In production mode . . .
SSL	You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL. For more information about managing security, see "Configuring SSL" in Securing WebLogic Server at the following URL: `http://download.oracle.com/docs/cd/E13222_01/wls/docs90/ secmanage/ssl.html`	You should not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed.
Deploying Applications	WebLogic Server instances can automatically deploy and update applications that reside in the `domain_name/autodeploy` directory (where `domain_name` is the name of a domain). It is recommended that this method be used only in a single-server development environment. For more information, see "Auto-Deploying Applications in Development Domains" in Deploying Applications to WebLogic Server at the following URL: `http://download.oracle.com/docs/cd/E13222_01/wls/ docs90/deployment/deploy.html#autodeploy`	The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the `weblogic.Deployer` tool, or the WebLogic Scripting Tool (WLST). For more information, see Deploying Applications to WebLogic Server at the following URL: `http://download.oracle.com/docs/cd/E13222_01/wls/ docs90/deployment/index.html`
Log File Rotation	When you start a server, the server automatically renames (rotates) its local server log file as `server-name.log.n`. For the remainder of the server session, the server rotates its local log file whenever the size of the file reaches 500 kilobytes.	A server rotates its local log file after the size of the file reaches 5000 kilobytes. When the server is configured for production mode, by default, all versions of the log files are retained. Administrators may want to customize the number of log files retained.

Function

In development mode . . .

In production mode . . .

SSL

You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL.

For more information about managing security, see "Configuring SSL" in Securing WebLogic Server at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs90/ secmanage/ssl.html

You should not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed.

Deploying Applications

WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain).

It is recommended that this method be used only in a single-server development environment.

For more information, see "Auto-Deploying Applications in Development Domains" in Deploying Applications to WebLogic Server at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/ docs90/deployment/deploy.html#autodeploy

The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the weblogic.Deployer tool, or the WebLogic Scripting Tool (WLST). For more information, see Deploying Applications to WebLogic Server at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/ docs90/deployment/index.html

Log File Rotation

When you start a server, the server automatically renames (rotates) its local server log file as server-name.log.n. For the remainder of the server session, the server rotates its local log file whenever the size of the file reaches 500 kilobytes.

A server rotates its local log file after the size of the file reaches 5000 kilobytes.

When the server is configured for production mode, by default, all versions of the log files are retained. Administrators may want to customize the number of log files retained.

Select the JDK for the Domain

The JDK Selection pane prompts you to select the J2SE Development Kit (JDK) for the startup mode you selected in the WebLogic Domain Startup Mode pane. The Configuration Wizard presents a list of the JDKs supplied by BEA and installed with the product, including:

Sun JDK

From Sun Microsystems.

BEA JRockit JDK

From BEA Systems, Inc.

You can choose one of the JDKs supplied by BEA or another JDK that you have installed on your system. If you select a JDK supplied by BEA, the Configuration Wizard will create server startup scripts that invoke the JDK you select.

Select only those JDKs that are supported on the platform you are using. For a list of the JDKs that are supported for a specific platform, see Supported Configurations. The default selection reflects the JDK that best meets the requirements of your environment, based on the platform on which you are installing the domain.

Note: If you plan to use the JRockit JDK in production mode, BEA recommends that you develop and test your applications using BEA JRockit early in your project cycle. For information about BEA JRockit, see the BEA JRockit JDK documentation at the following URL:

http://download.oracle.com/docs/cd/E13188_01/jrockit/docs50/index.html

To select the JDK:

Perform one of the following steps:

To use a JDK supplied by BEA, select BEA Supplied JDKs and then select a JDK from the list.
To use a JDK that is not installed with the product, select Other JDK, click Browse, and navigate to the appropriate directory.

Note: The Configuration Wizard does not configure the start scripts to use this type of JDK. You must change the start scripts manually.

Click Next to proceed to the next configuration window.

Customize Environment and Services Settings

The Customize Environment and Services Settings window gives you the option to change the distribution of your domain across servers, clusters, and machines, and to modify existing JDBC and JMS file store settings.

If you choose not to customize any environment or services settings by accepting the default (No), you proceed directly to creating the domain.

The following topics summarize the settings you can change.

Customize the Environment

You can customize the environment of your domain as follows:

Change the configuration of the Administration Server, including listen address and listen ports
Add or delete Managed Servers, or change the configuration of existing Managed Servers defined in the selected template
Group the Managed Servers into clusters, which allows multiple Managed Servers to operate as a single unit to host applications and resources. To group the Managed Servers into clusters, you have the option of performing the following steps:

Add or delete clusters, or change the configuration of existing clusters
Assign the Managed Servers to a cluster in the domain
Create an HTTP proxy for each cluster within the domain

Assign WebLogic Server instances to host machines. In a domain, machine definitions identify a particular, physical piece of hardware and are used to associate a computer with the Managed Servers it hosts. To map WebLogic Server instances to host machines, you have the option of performing the following steps:

Add or delete machines, or change the configuration of existing machines
Assign each instance of WebLogic Server to the machine on which it runs.

For more information, see Customizing the Environment.

Customize Existing JDBC and JMS Settings

If the domain source on which you are basing your domain contains a database configuration, you have the option to do the following:

Modify JDBC Data Source settings, including database type and drivers
Test the connections to the database
Load the database

If a JMS file store has been defined in the domain source, you can also change the file store definition.

For more information, see Customizing Existing JDBC and JMS Settings.

Create the WebLogic Domain

The Create WebLogic Domain window prompts you to specify the name and pathname for the domain, and initiate its creation.

To create the WebLogic domain:

Make sure that the Domain Name field contains the name of the required domain. If you need to change the value in this field, click within the field and modify the string displayed there.

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

Click Browse to invoke the Select a WebLogic Domain Directory dialog box.

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

The domain directory can be located anywhere on your system. By default, it resides in BEA_HOME\user_projects\domains\domain, where BEA_HOME is the directory that contains the product installation, and domain is the name of the domain directory defined by the selected domain template.

Click Create.

Note: You cannot overwrite an existing domain. If a domain with the name you specify already exists in the selected location, you must either delete the existing domain, or specify a different name or location for this domain.

The Creating Domain window is opened to display status messages during the domain creation process.
The Configuration Wizard stores the config.xml file and all other generated components in the domain directory that you specify.

Creating Domain

The Creating Domain window displays status messages during the domain creation process. When the process is complete, the new domain is ready for use.

On this platform . . .	Perform the following task . . .
UNIX and Linux	Click Done.
Windows	Do one of the following: If you want to start the server immediately, select the Start Admin Server check box and click Done. If you do not want to start the server at this time, click Done.

On this platform . . .

Perform the following task . . .

UNIX and Linux

Click Done.

Windows

Do one of the following:

If you want to start the server immediately, select the Start Admin Server check box and click Done.

If you do not want to start the server at this time, click Done.

Creating a New WebLogic Domain

Related Topics

Create or Extend a Domain

Related Topics

Select a Domain Source

Configure an Administrator Username and Password

To configure an administrator username and password:

Specify the Server Start Mode and JDK

Choose the Startup Mode

Differences Between Domain Startup Modes

Select the JDK for the Domain

To select the JDK:

Related Topics

Customize Environment and Services Settings

Customize the Environment

Customize Existing JDBC and JMS Settings

Create the WebLogic Domain

To create the WebLogic domain:

Creating Domain