Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Creating a New WebLogic Domain

Before you can develop and run WebLogic Platform applications, you must first create a WebLogic Server domain. The Configuration Wizard guides you through the process of creating a new domain using configuration templates. A template is a Java Archive (JAR) file that contains the files and scripts required to create or update a domain.

A configuration template defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options. BEA delivers a set of predefined configuration templates, which are described in the "Template Reference" at the following URL:

http://e-docs.bea.com/platform/docs81/confgwiz/tempref.html

# Overview of Creating a Domain Using the Configuration Wizard

The Configuration Wizard provides two options for creating new domains: express and custom. The express option allows you to create a domain quickly and easily by using the default settings defined in the configuration template you select. The custom option allows you to modify the settings in the configuration template to meet the requirements of your configuration.

## Using the Express Option to Create a New Domain

Table 5-1 summarizes the steps in the procedure for creating a new domain using the express option provided by the Configuration Wizard.

Table 5-1 Steps for Creating a Domain Using the Express Option

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 create a new domain, choose Create a new WebLogic configuration. For details about adding to an existing domain configuration, see Extending Domains.
Selecting a Configuration Template | Choose the configuration template with which you want to create and configure your domain. To determine whether the default settings for a configuration template meet your requirements, see "Template Reference" at the following URL: http://e-docs.bea.com/platform/docs81/confgwiz/tempref.html If necessary, you can update the domain later, as described in Extending Domains.
Choosing Express or Custom Configuration | Select the Express option to create a domain quickly, using the default template settings.
Configuring an Administrative Username and Password | Specify a username and password to be used for starting the Administration Server.
Specifying the Server Start Mode and Java SDK | Select the mode in which to launch your WebLogic domain configuration (development mode or production mode) and the Java Software Development Kit (SDK) that is enabled for the selected Startup mode.
Creating the WebLogic Configuration | Review the domain details, specify the name and directory for the domain, and initiate the creation of the domain.

## Using the Custom Option to Create a New Domain

The custom option allows you to modify configuration information to accommodate your requirements. Table 5-2 summarizes the procedure for creating a domain using the custom configuration option.

Table 5-2 Steps for Creating a Domain Using the Custom Option

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 create a new domain, choose Create a new WebLogic configuration. For details about adding to an existing domain configuration, see Extending Domains.
Selecting a Configuration Template | Choose the configuration template with which you want to create and configure your domain.
Choosing Express or Custom Configuration | Select the Custom option to create a domain with non-default template settings that meet the needs of your domain.
Designating an Administration Server | Designate a server as the Administration Server. This window is displayed automatically only if the selected template includes multiple servers that are not assigned to clusters.
Configuring the Administration Server | Define parameters for the Administration Server, a designated server from which the domain is managed.
Configuring Managed Servers, Clusters, and Machines When Creating a New Domain | Optionally, define parameters for Managed Servers, clusters, and host machines.
Configuring JDBC When Creating a New Domain | Optionally, define parameters for Java Database Connectivity (JDBC).
Configuring JMS When Creating a New Domain | Optionally, define parameters for the Java Message Service (JMS).
Targeting Servers and Clusters When Creating a New Domain | Optionally, target the servers and clusters to which you want to deploy application components (such as Web applications and EJB modules), and application services (such as JDBC or JMS components, and startup/shutdown classes.)
Configuring Security When Creating a New Domain | Specify an administrative username and password. Optionally, you can also configure additional security features by defining users and groups and assigning them to global security roles.
Configuring Windows Options | Optionally, define domain-specific parameters for the Windows operating system.
Specifying the Server Start Mode and Java SDK | Select the mode in which to launch your WebLogic domain configuration (development mode or production mode) and the Java Software Development Kit (SDK) that is enabled for the selected Startup mode.
Creating the WebLogic Configuration | Review the parameters defined for your domain configuration, specify its name and pathname, and initiate its creation.

## Related Topics

Creating and Extending Domains Using the Configuration Wizard

Brief Introduction to Domains

Tutorial: Creating Your First Domain

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

"Overview of WebLogic Server Domains" in Configuring and Managing WebLogic Server at http://e-docs.bea.com/wls/docs81/adminguide/overview_domain.html

# Creating or Extending a Configuration

The Create or Extend a Configuration window prompts you to choose whether you want to create a new domain configuration or extend an existing one by adding applications and services.

Choose this option . . . | When you want to . . .
--- | ---
Create a new WebLogic configuration | Create a new domain that is configured to meet your requirements. Begin by selecting the configuration template as the basis for your domain. Then modify settings as required.
Extend an existing WebLogic configuration | Add applications and services to an existing domain configuration. Begin by selecting the directory of the domain that you want to update and identifying the extension template you want to use for adding applications. You then have the option of configuring the database (JDBC) and messaging (JMS) services, too. To learn more, see Extending Domains.

## Related Topics

Brief Introduction to Domains

Overview of Creating a Domain Using the Configuration Wizard

# Selecting a Configuration Template

A template is a Java Archive (JAR) file that contains the files and scripts required to create or update a domain. A configuration template defines the full set of resources within a domain, including infrastructure components, applications, services, security features, and general environment and operating system settings.

The Select a Configuration Template window prompts you to choose the configuration template you will use to create and configure your domain. It is important to use the configuration template that best meets the requirements of your domain. A set of predefined configuration templates is provided with your product installation. These templates are described in the "Template Reference" at the following URL:

http://e-docs.bea.com/platform/docs81/confgwiz/tempref.html

Review the descriptions of these templates to determine if one of them meets your needs. You can also define your own custom configuration templates. For more information, see Creating Configuration Templates Using the WebLogic Configuration Template Builder.

Note: Since the initial product release, there have been changes made to the Basic WebLogic Integration Domain, Basic WebLogic Platform Domain, and Basic WebLogic Portal Domain configuration templates. Because of these changes, when creating a domain using the Configuration Wizard, you should use a configuration template provided with your current installation or a custom template created from a domain or template in your current installation. You must upgrade the domains created using the configuration templates provided with an earlier service pack to the current service pack. For information about upgrading your domains, see the BEA WebLogic Platform Upgrade Planning Guide at http://e-docs.bea.com/platform/docs81/upgrade/index.html.

#### To select a configuration template:

1. Review the list of templates displayed in the Templates pane. The templates displayed for selection reside in the directory specified in the Locate Additional Templates field. If you need to select an alternate directory:

1. Click Browse to invoke a dialog box called Select a Template Directory.
2. In the dialog box, navigate to the appropriate directory or manually enter its pathname in the Location field.
3. Click OK to return to the Select a Configuration Template window.

A list of the configuration templates available in the selected directory is displayed in the Templates pane. Templates are organized by category. For example, the predefined configuration templates provided with the product installation are listed together under the heading `BEA`.

2. Select the configuration template that contains the settings you want to use as the basis for your domain.
3. Click Next to proceed to the next configuration window.

# Choosing Express or Custom Configuration

The Choose Express or Custom Configuration window prompts you to select between two types of configuration: express and custom.

Choose this option . . . | When you want to . . .
--- | ---
Express | Create a domain quickly, using the default settings from the configuration template that you selected. Keep in mind that in this mode you cannot modify template settings (for example, server port numbers). If you select this option, see the following sections for information about creating a username and password, specifying the configuration environment, and subsequently creating the domain: Configuring an Administrative Username and Password Specifying the Server Start Mode and Java SDK Creating the WebLogic Configuration
Custom | Create a domain that is customized for your target environment. In this mode you can modify the default settings of the selected configuration template as desired. An overview of the steps involved in creating a custom configuration are presented in Overview of Creating a Domain Using the Configuration Wizard.

## Related Topics

Using the Express Option to Create a New Domain

Using the Custom Option to Create a New Domain

Tutorial: Creating Your First Domain

# Designating an Administration Server

The Choose the Administration Server window prompts you to designate a server as the Administration Server. This window is displayed automatically only if the selected template includes multiple servers that are not assigned to clusters.

#### To choose the Administration Server:

1. From the list of Available Servers, select the server that you want to designate as the Administration Server. The Administration Server cannot be assigned to a cluster.

The Server Details area displays detailed information about the selected server. By default, the currently assigned Administration Server is selected.

2. Select Next to proceed to the next configuration window.

The Configure the Administration Server and Configure Managed Server(s) windows are updated to reflect your changes.

# Configuring the Administration Server

In every domain, one server must be designated the Administration server: the central point from which the whole domain is managed. The Configure the Administration Server window prompts you to define configuration information for the Administration Server. (For details, see Brief Introduction to Domains.) This information is used to access the server in the domain.

Servers can be reached using the following URL: `protocol://listen-address:listen-port`

In this URL, `protocol` can be any of the following:

- `t3`
- `t3s`
- `http`
- `https`

`listen-address` and `listen-port` are defined in the Configure the Administration Server window.

#### To configure the Administration Server:

Review the values displayed in the window and modify them as necessary, using the guidelines provided in the following table. (Fields marked with an asterisk are required.) When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid server name: a string of characters that can include spaces. Each server instance in your WebLogic Platform environment must have a unique name, regardless of the domain or cluster in which it resides, or whether it is an Administration Server or a Managed Server. In addition, the name of the Administration Server must be unique among all configuration component names within the domain. Note: This value is specified for identification purposes only; it is not used as part of the URL for applications that are deployed on the server. The server name is displayed in the WebLogic Server Administration Console. In addition, if you use WebLogic Server command-line utilities or APIs, you must specify this name to identify the server.
Listen address (Optional) | From the drop-down list, select a value for the listen address. Valid values for the listen address are as follows: `All Local Addresses` (default) IP address of the computer that hosts the server DNS name that resolves to the host `localhost` (valid only for requests that are issued from the computer on which the server is running) If you identify the listen address for a server instance as `localhost`, non-local processes cannot connect to the server instance. Only processes on the machine that hosts the server instance can connect to the server instance. If the server instance must be accessible as `localhost` (for example, if you create administrative scripts that connect to `localhost`), and it must also be accessible by remote processes, select `All Local Addresses`. The server instance determines the address of the machine and listens on it. To learn more about Listen Addresses, see Specifying Listen Addresses.
Listen port (Optional) | Enter a valid value for the listen port to be used for regular, non-secure requests (via protocols such as HTTP and T3). The default value is 7001. If you leave this field blank, the default value is used. Any number between 1 and 65535 is a valid value. For more information, see Specifying Listen Ports.
SSL listen port (Optional) | Enter a valid value to be used for secure requests (via protocols such as HTTPS and T3S). The default value is 7002. If you leave this field blank, the default value is used. Any number between 1 and 65535 is a valid value. Note: By default, a server instance uses demonstration certificates to authenticate requests from a secure port. In a production environment, you must configure SSL to use certificates from a certificate authority. For more information, see "Configuring SSL" in Managing WebLogic Security at http://e-docs.bea.com/wls/docs81/secmanage/ssl.html. For more information, see Specifying Listen Ports.
SSL enabled (Optional) | Select the check box in this field to enable the SSL listen port. By default, the SSL is disabled for all new servers.

## Specifying Listen Addresses

If you want to limit the valid listen address for a server, use the guidelines for specifying listen addresses provided in the following table.

If the listen address is set to . . . | Then the following is true . . .
--- | ---
`All Local Addresses` or DNS name | On multi-homed Windows machines, a server instance binds to all available IP addresses.
IP Address or DNS name | To connect to the server instance, processes can specify either the IP address or the corresponding DNS name. Processes that specify `localhost` fail to connect. You must update existing processes that use `localhost` to connect to the server instance. For connections that specify the IP address for the listen address and a secured port for the listen port, host name verification must be disabled. Note: To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for the listen address and then a client request specifies a DNS name, WebLogic Server will attempt to resolve the DNS name, but if it cannot access DNS name mapping, the request will fail.
`localhost` | Processes must specify `localhost` to connect to the server instance. Only processes that reside on the machine that hosts the server instance (local processes) will be able to connect to the server instance.

## Specifying Listen Ports

Refer to the following guidelines when specifying listen ports and secure listen ports:

- Although you can specify any valid port number, if you specify port 80, you can omit the port number from the HTTP request used to access resources over HTTP. For example, if you define port 80 as the listen port, you can use the URL `http://``hostname``/myfile.html` instead of `http://``hostname``:``portnumber``/myfile.html`.
- On some operating systems, port 80 can be accessed only by processes run under a privileged user or group ID. In this case, you can assign the server instance to a UNIX machine on which a Post-Bind UID or GID is defined.
- In a development environment, you might want to run multiple instances of WebLogic Server on a single computer. If you do so, each instance must use a unique listen port/listen address combination. On a multi-homed computer, you can use the same listen port but you must configure each server to use a unique IP address as its listen address. If your computer does not support multiple IP addresses, you must use a different listen port for each active instance.

# Configuring Managed Servers, Clusters, and Machines When Creating a New Domain

The minimum requirement for your domain is a single Administration Server on a single machine. In addition, however, you have the option of configuring other resources to be managed by the Administration Server and distributing them across multiple machines. Specifically, you can:

- Add, change, or delete Managed Servers
- Add, change, or delete clusters
- Group Managed Servers into clusters, or change current groupings
- Assign servers to machines, or change current assignments

The Managed Servers, Clusters, and Machines Options window prompts you to specify whether you want to distribute your WebLogic configuration across Managed Servers, clusters, and physical machines. For more information, see Configuring Managed Servers, Clusters, and Machines.

# Configuring JDBC When Creating a New 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 your 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

Because WebLogic Server applications usually require some database access, most templates created for use with the Configuration Wizard contain JDBC configuration information. When using the Configuration Wizard, you can accept these settings, modify them, or add JDBC configuration information, as described in Configuring a Database Service.

# Configuring JMS When Creating a New Domain

WebLogic JMS gives you 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 Configuration Wizard gives you the option of setting up JMS messaging services for a domain. To set up a messaging service, 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.

Because JMS is often required by WebLogic Server applications, the templates created for use with the Configuration Wizard typically contain JMS configuration information. You can accept these settings when using the Configuration Wizard, or you can modify or add JMS configuration information as described in Configuring a Java Messaging Service.

# Targeting Servers and Clusters When Creating a New Domain

If you have configured your domain to be distributed 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. Typically, applications provided in templates are targeted to the appropriate server(s). You can accept these settings when using the Configuration Wizard, or you can modify or add targeting information as described in Configuring Targets.

# Configuring Security When Creating a New Domain

To make sure that your domain is secure when you boot it for the first time, the Configuration Wizard provides basic security features. Whenever you create a domain, regardless of whether you do so using the express or custom option, you are prompted to define an administrative username and password. (See Configuring an Administrative Username and Password.)

If you are customizing a configuration, you can provide additional security by setting up two other security mechanisms:

- Users and groups
- Global security roles

For information about configuring basic security when creating a new domain, see Configuring Security.

# Configuring Windows Options

The Windows Options window prompts you to define operating system configuration information for Windows platforms. This window is displayed only if you are running on a Windows platform.

#### To configure Windows Options:

Specify your options as defined in the following table. Then click Next.

In this pane . . . | Do the following . . .
--- | ---
Create Start Menu | Specify whether you want to create a shortcut for the domain on the Windows Start menu. If you choose Yes (the default), you are prompted, in the next window, to define the Start menu entries.
Install Administrative Server as a Service | Specify whether you want the Administration server installed as a Windows service. When a server is installed as a Windows service, it starts automatically each time you boot your Windows system.You must have Administrator privileges to install the server as a Windows service. If you are creating a domain with an Administration Server and Managed Servers, a Windows service is created only for the Administration Server. The wizard also creates a server-specific script that you can modify and use to install other servers as Windows services. The script is named `domain-name``\installService.cmd`, where `domain-name` is the name of the domain that you created.

## Related Topics

"Setting Up a WebLogic Server Instance as a Windows Service" in Configuring and Managing WebLogic Server at http://e-docs.bea.com/wls/docs81/adminguide/winservice.html

# Building Start Menu Entries

The Build Start Menu Entries window prompts you to build entries for the Windows Start Menu. This window is displayed in the Configuration Wizard only if you:

- Are running on a Windows platform.
- Set the Create Windows Start Menu option to Yes in the Configure Windows Options window.

#### To build the Start Menu entries:

Review the current list of Start Menu entries. Add, modify, or delete entries as required by your configuration, using the guidelines provided in the following table. To delete an entry, select the Start Menu entry tab and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Shortcut link name | Enter a name for the shortcut to be displayed in the Start menu. The name can be any string of characters, including spaces.
Program | Specify the name of the program to be run when the shortcut is selected. Do one of the following: Select a program from the drop-down list. By default, a list of the programs defined by the configuration template is displayed in the drop-down list. Click Browse to navigate through the local installation directory. Select the desired program.
Argument | Enter any parameter that you want to pass to the shortcut program.
Working directory | Enter the pathname of the directory from which the shortcut is executed, or click Browse to navigate through the local installation directory so you can find and select the desired directory. The specified pathname must exist. If, in the Program field, you select a program from the drop-down list that is defined by the configuration template, then this field is grayed out. In this case, the program script is executed in the root directory of the domain.
Description | Enter a description for the shortcut.

# Specifying the Server Start Mode and Java SDK

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

- Configuration startup mode for your domain
- SDK to be used for the domain

## Choosing 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 and advanced features, such as clusters, may be used.To auto-deploy applications in this mode, you must first put the exploded directory structure or archive file in the `domain` directory.

Notes: The PointBase Server included in the WebLogic Platform distribution is provided solely for evaluation purposes. Non-evaluation development or other use of the PointBase Server requires that a separate PointBase Server license be obtained by the end user directly from DataMirror. For more information about contacting DataMirror, see http://www.pointbase.com/. For more information about databases supported on your platform and any associated restrictions or limitations, see "Supported Database Configurations" in Supported Configurations for WebLogic Platform 8.1 at http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/supported_db.html.

When you deploy applications automatically, the server automatically adds an entry for each application or module to the `config.xml` file for the domain. You do not need to edit the `config.xml` file manually.

To learn more about choosing between development and production modes, see Differences Between Configuration Startup Modes.

## Selecting the SDK for the Domain

The Java SDK Selection pane prompts you to select the Java SDK for the startup mode you selected in the WebLogic Configuration Startup Mode pane. The Configuration Wizard presents a list of the SDKs supplied by BEA and installed with the product, including:

- Sun SDK

Provided by Sun Microsystems.

- BEA WebLogic JRockit SDK

First commercial server-side SDK developed uniquely for server-side applications and optimized for Intel architectures to ensure reliability, scalability, manageability, and flexibility for Java applications.

You can choose one of the SDKs provided by BEA or another SDK that you have installed on your system. The Configuration Wizard will create server startup scripts that invoke the Java SDK you select.

Select only those Java SDKs that are supported on the platform you are using. For a list of the Java SDKs that are supported for a specific platform, see WebLogic Platform 8.1 Supported Configurations. The default selection reflects the Java SDK 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 WebLogic JRockit SDK in production mode, BEA recommends that you develop and test your applications using WebLogic JRockit early in your project cycle. For information about migrating your application to WebLogic JRockit, see "Migrating to WebLogic JRockit" in Developing Applications at http://e-docs.bea.com/wljrockit/docs142/devapp/migrate.html.

#### To select the Java SDK:

1. Perform one of the following steps:

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

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

2. Click Next to proceed to the next configuration window.

## Differences Between Configuration Startup Modes

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

Table 5-3 Differences Between Development and Production Modes

Function | In development mode . . . | In production mode . . .
--- | --- | ---
SSL | You can use the demonstration digital certificates 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 Managing WebLogic Security at the following URL: http://e-docs.bea.com/wls/docs81/ secmanage/ssl.html | A warning message is displayed if you use the demonstration digital certificates.
Deploying Applications | WebLogic Server instances can automatically deploy and update applications that reside in the `domain_name``/applications` directory (where `domain_name` is the name of a domain). | The auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console or the `weblogic.Deployer` tool. For more information, see Deploying WebLogic Server Applications at the following URL: http://e-docs.bea.com/wls/ docs81/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 500 kilobytes.
Execute Queues | The default number of threads available to Execute Queues is 15. The thread count determines the number of simultaneous operations that can be performed by applications that use the specified execute queue. By default, all applications use the execute queue named default. You can create additional queues to exercise more control over the resources that your applications use. | The default number of threads available to Execute Queues is 25.
JDBC Connection Pool Capacity | The default capacity is 15 connections. | The default capacity is 25 connections.

## Related Topics

For information on changing the run-time mode after you have created a domain, see "Changing the Runtime Mode" in the WebLogic Server Administration Console Online Help at http://e-docs.bea.com/wls/docs81/ConsoleHelp/servers.html#ChangingRuntimeMode

# Creating the WebLogic Configuration

The Create WebLogic Configuration window prompts you to review the details for your configuration, specify the name and pathname for the domain, and initiate its creation.

#### To create the WebLogic configuration:

1. Review the 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 window.
2. Make sure that the Configuration Location and Domain Name 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 a WebLogic Configuration Directory dialog box.
2. In the dialog box, navigate to the appropriate directory or manually enter its pathname in the Location field. Click OK.

The configuration 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 configuration template.

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

Note: Do not create a domain named `weblogic`. This name is reserved for internal use by WebLogic Server.

4. After you verify the information displayed in the window, click Create.

The Creating Configuration 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 configuration directory that you specify.

## Related Topics

"Domain Restrictions" in Configuring and Managing WebLogic Server at http://e-docs.bea.com/wls/docs81/adminguide/overview_domain.html#DomainRestrictions

# Creating Configuration

The Creating Configuration 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.