Skip navigation.
Downloads | Product Documentation | Support

Configuring and Managing WebLogic Server

# Creating and Configuring Domains Using the Configuration Wizard

When you are ready to start developing or testing applications, use the Configuration Wizard to create and configure a domain. A domain is a collection of resources, such as servers, clusters, database connections, security services, and J2EE applications, that you manage as a unit. A domain must contain at least a definition for an Administration Server and an administrative user. You can define additional resources as part of the domain-creation process or at any time after creating the domain.

To create a domain, start the Configuration Wizard and choose a domain configuration template. Like a standard template, a domain configuration template provides a basic structure for a domain that you modify as your needs require.

The following sections describe creating and configuring domains:

- Starting the Configuration Wizard
- Choosing a Domain Configuration Template
- Completing the Remaining Steps of the Configuration Wizard
- Example: Creating a Domain with a Single Server Instance
- Example: Creating a Domain with Administration Server and Clustered Managed Servers

For more information, refer to:

- Overview of WebLogic Server Domains
- Domain Restrictions
- "Extending Domains" in the Creating WebLogic Configurations Using the Configuration Wizard guide (adding resources to a domain that is inactive)
- "Creating, Configuring, and Monitoring Servers" in the Administration Console Online Help (adding resources to a domain that is currently active)

# Starting the Configuration Wizard

You can start the Configuration Wizard any time after installing WebLogic Server. The wizard creates domains only on the computer on which it is installed; it cannot connect to remote hosts and create domains there. (After you create the domain, you can log on to a remote WebLogic Server host and use that host to run one or more servers that you created in the domain. For more information about starting servers, refer to "Starting and Stopping Servers" in the Administration Console Online Help.)

The installation program prompts you to start the Configuration Wizard. In addition, you can start the wizard by completing either of the following tasks:

- Starting in a GUI Environment
- Starting in a Text-Based Environment

## Starting in a GUI Environment

To start and run the Configuration Wizard on a Windows computer, select the Configuration Wizard option from the BEA program group in the Windows Start Menu.

To start and run the Configuration Wizard in a GUI environment on a UNIX computer (or from a Windows command prompt):

1. Log in to a Windows or UNIX system on which the WebLogic Server software is installed.
2. Open a command-line shell.
3. Go to the following directory: `WL_HOME/common/bin`

where `WL_HOME` is the directory in which you installed WebLogic Server. For example:

`cd ~/bea/weblogic810/common/bin`

4. Invoke the `config.cmd` or `config.sh` script.

If you try to start the Configuration Wizard on a system that cannot support the graphical display, the wizard automatically starts in console mode.

## Starting in a Text-Based Environment

To start the Configuration Wizard in a text-based environment (console mode):

1. Log in to a Windows or UNIX system on which the WebLogic Server software is installed.
2. Open a command-line shell.
3. Go to the following directory: `WL_HOME/common/bin`

where `WL_HOME` is the directory in which you installed WebLogic Server. For example:

`cd ~/bea/weblogic810/common/bin`

4. Invoke the `config.cmd` or `config.sh` script with the `-mode=console` argument. For example, in a `bash` shell on UNIX:

`. config.sh -mode=console`

# Choosing a Domain Configuration Template

On the first page of the Configuration Wizard, choose Create new WebLogic configuration and then click Next.

The second page of the Configuration Wizard asks you to choose a domain configuration template. A domain configuration template provides a basic structure for a domain that you modify as your needs require. You can choose templates that BEA provides or templates that your organization provides.

## BEA Templates

Table 3-1 provides an overview of the WebLogic Server domain configuration templates. For more information about these and the templates that other BEA products provide, see "Template Reference" in the Creating WebLogic Configurations Using the Configuration Wizard guide.

Table 3-1 WebLogic Server Templates

Template | Description
--- | ---
Basic WebLogic Server Domain | Creates a basic WebLogic Server domain without the installation of any sample applications.
WebLogic Server Examples Domain | Creates the WebLogic Server Examples domain outside the installed kit. The WebLogic Server Examples domain contains a collection of examples that illustrate best practices for coding individual J2EE APIs.
Avitek Medical Records Sample Domain | Creates the Avitek Medical Records domain outside the installed kit. Avitek Medical Records is a WebLogic Server sample application suite that concisely demonstrates all aspects of the J2EE platform.

## Additional Templates

Your organization can provide templates as well. For example, each development team can create a domain configuration template that defines JDBC connection pools and other resources that are specific to the application being developed.

To choose from additional templates, under Template Locations, click the Browse button and choose the directory in which your organization has located additional templates.

For information about creating templates, refer to "Creating Configuration Templates Using the Template Builder" and "Creating Extension Templates Using the Template Builder" in the Creating WebLogic Configurations Using the Configuration Wizard guide.

# Completing the Remaining Steps of the Configuration Wizard

After you choose a domain configuration template, the Configuration Wizard prompts you to choose one of the following:

- Express Configuration, which accepts all default settings in the template.
- Custom Configuration, which enables you to modify the default settings.

For more information about completing the remaining steps, refer to the Configuration Wizard online help or to "Creating a New WebLogic Domain" in the Creating WebLogic Configurations Using the Configuration Wizard guide.

# Example: Creating a Domain with a Single Server Instance

If you are in a development environment and want the simplest possible domain for developing your applications, you can use the Configuration Wizard to create a domain with a single server instance. In this domain, the single server you create is an Administration Server. In a development environment it is acceptable to deploy applications on the Administration Server; in a production environment, BEA recommends that you use Administration Servers only for managing the domain and you deploy applications only on Managed Servers.

To create a new domain with a single WebLogic Server instance:

1. Start the Domain Configuration Wizard. For more information, refer to Starting the Configuration Wizard.

The Domain Configuration Wizard displays the Create or Extend a Configuration page.

Note: The remaining instructions in this section assume that you are running the Domain Configuration Wizard in GUI mode.

2. On the Create or Extend a Configuration page, click Create a new WebLogic configuration button. Then click Next.
3. On the Select a Configuration Template page, choose the Basic WebLogic Server Domain template. Then click Next.
4. On the Choose Express or Custom Configuration page, choose Express. Then click next.
5. On the Configure Administrative Username and Password page, enter a user name and password. This user becomes the initial administrative user for the domain. Then click Next.

See "Specifying an Initial Administrative User for a Domain" in the Administration Console Online Help.

6. On the Configure Server Start Mode and Java SDK page, accept the default selections and click Next.

For information on server modes, see Production and Development Modes.

7. On the Create WebLogic Configuration page, click Create.

By default, the wizard creates a domain with the following characteristics:

- The domain is named mydomain.
- The domain contains a single server named myserver. This server functions as the Administration Server.
- The domain is created for a development environment.
- The root directory for the Administration Server is located in `WL_HOME\user_projects\domains\mydomain`.
- On Windows, you can start the Administration Server from the Start menu.
- The wizard does not install the server as a Windows service.
- The domain includes a `boot.properties` file.

To start the server in this domain, open a command prompt, change to `WL_HOME\user_projects\domains\mydomain`, and run the `startWebLogic.cmd` (Windows) or `startWebLogic.sh` (UNIX) script. For more information about starting servers, refer to "Starting and Stopping Servers" in the Administration Console Online Help.

To access the Administration Console for the domain, use any of the following URLs:

- From the same computer on which the server is running: `http://localhost:7001/console`
- From any computer:
  `http://``DNS-name``:7001/console`
  where `DNS-name` is the DNS name of the computer on which the server is running.
- From any computer:
  `http://``IP=Address``:7001/console`
  where `IP-Address` is an IP address of the computer on which the server is running.

For information about adding resources to this simple domain, refer to:

- "Extending Domains" in the Creating WebLogic Configurations Using the Configuration Wizard guide (adding resources to a domain that is inactive).
- "Creating, Configuring, and Monitoring Servers" in the Administration Console Online Help (adding resources to a domain that is currently active).

# Example: Creating a Domain with Administration Server and Clustered Managed Servers

This type of domain configuration is recommended for production environments that require the improved availability and performance provided by failover and load balancing in a WebLogic Server cluster. For more information about clusters, refer to "Introduction to WebLogic Clustering" in the Using WebLogic Server Clusters guide.

To create a new domain with a cluster of Managed Servers and an Administration Server (which is not part of the cluster):

1. Start the Domain Configuration Wizard. For more information, refer to Starting the Configuration Wizard.

The Domain Configuration Wizard displays the Create or Extend a Configuration page.

Note: The remaining instructions in this section assume that you are running the Domain Configuration Wizard in GUI mode.

2. On the Create or Extend a Configuration page, click Create a new WebLogic configuration button. Then click Next.
3. On the Select a Configuration Template page, choose the Basic WebLogic Server Domain template. Then click Next.
4. On the Choose Express or Custom Configuration page, choose Custom. Then click next.
5. On the Administration Server Configuration page, configure the Administration Server as follows:

- Name: Enter an alphanumeric name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.

This field will not accept spaces.

The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only. The server name displays in the Administration Console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.

- Listen Address—To accept the default behavior, leave the `All Local Addresses` value. By default, remote processes can access server instances through the IP address or DNS name of the host machine. Local processes can access the server with the IP address, DNS name, or the `localhost` string.

To change the default behavior, click in the field and choose a value from the drop-down list. See "Configuring the Listen Address" in the Administration Console Online Help.

- Listen Port: Enter a numeric value for the listen port. The range is 1 to 65535.

See "Configuring the Listen Ports" in the Administration Console Online Help.

- SSL Enabled. Click in this box to enable SSL.

By default, the server instance uses demonstration certificates for SSL communication. In a production environment, you must configure the server to use certificates from a certificate authority. See "Configuring the Listen Ports" in the Administration Console Online Help.

- SSL Listen Port: Enter a numeric value for SSL listen port. The range is 1 to 65535.

6. Click Next.
7. On the Managed Servers, Clusters and Machine Options page, click Yes. Then click Next.
8. On the Configure Managed Servers page, click Add and fill in the fields of the Add Server row as follows:

- Name—Enter an alphanumeric name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.

This field will not accept spaces.

Each server within a domain must have a unique name.

- Listen Address—To accept the default behavior, leave the `All Local Addresses` value. By default, remote processes can access server instances through the IP address or DNS name of the host machine. Local processes can access the server with the IP address, DNS name, or the `localhost` string.

To change the default behavior, choose a value from the drop-down list.

For guidelines on supplying addressing information for a cluster and its members, see Identify Names and Addresses in the Using WebLogic Server Clusters guide.

- Listen Port: Enter a numeric value for the listen port. The range is 1 to 65535.

See "Configuring the Listen Ports" in the Administration Console Online Help.

- SSL Enabled. Click in this box to enable SSL.

By default, the server instance uses demonstration certificates for SSL communication. In a production environment, you must configure the server to use certificates from a certificate authority. See "Configuring the Listen Ports" in the Administration Console Online Help.

- SSL Listen Port: Enter a numeric value for SSL listen port. The range is 1 to 65535.

9. Repeat step 8. to add additional Managed Servers, then click Next to move to the Cluster Configuration page.
10. On the Configure Clusters page, click Add and fill in the fields of the Add Cluster row as follows:

- Cluster Name: Enter an alphanumeric name that is unique for all configuration objects in the domain. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain. This field will not accept spaces.
- MultiCast Address: Enter a multicast address for the cluster. A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255.
- MultiCast Port: Enter a numeric value for the multicast port. The range of values is 1 to 65535.
- Cluster Address: (Optional) Enter the cluster address. The cluster address forms the host name portion of URLs for requests directed to the cluster. If the cluster address is not set, EJB handles may not work properly. See "Cluster Address" in Using WebLogic Server Clusters.

For production use, enter a DNS name that maps to the individual IP addresses of the Managed Servers in the cluster.

For testing or development purposes, use a comma-separated list of the IP addresses and ports assigned to the Managed Servers (this is the default entry). For example `IPaddress1``:``port1``,``IPaddress2``:``port2``,``IPaddress3``:``port3`

11. Click Next to display the Assign Servers to Clusters page.
12. On the Assign Servers to Clusters page:

1. In the Target list, select the cluster you created.
2. In the Source list, select Managed Servers.

Administration Servers cannot be part of a cluster.

3. Click the right arrow button to assign the server to the cluster.
4. Click Next to display the Configure Machines page.

13. On the Configure Machines page, complete the following steps for each WebLogic Server host that will run servers in the domain:

1. Click the Add button.
2. In the Name column provide a name that identifies the computer that will run a server instance.
3. If you plan to use the Node Manager on the computer, in the Node Manager Listen Address column, enter the DNS name of the computer. In Node Manager Listen Port, enter the port on which the Node Manager listens for requests.

The Administration Server uses the listen address and listen port to connect to the Node Manager running on the remote computer. The Administration Server can then ask the Node Manager to start a server instance on the computer.

For servers that are in a cluster, WebLogic Server uses the Machines that you configure to determine the optimum server to which certain tasks, such as HTTP session replication, are delegated.

14. Click Next to display the Assign Servers to Machines page.
15. On the Assign Servers to Machines page:

1. In the Target list, select a Machine that you created.
2. In the Source list, select a server.
3. Click the right arrow to assign the server to the machine.
4. When you complete all server associations, click Next.

16. Skip subsequent pages until the wizard displays the Configure Administrative Username and Password page.
17. On the Configure Administrative Username and Password page, enter a user name and password. This user becomes the initial administrative user for the domain. Then click Next.

See "Specifying an Initial Administrative User for a Domain" in the Administration Console Online Help.

18. For Windows systems, the Configuration Wizard prompts you to create an item on the Windows Start menu. Click Yes if you want the wizard to lead you through the process of configuring a shortcut for the servers in your domain.
19. For Windows systems, the wizard also prompts you to install the Administration Server as a Windows service. Select Yes if you want the Administration Server to start automatically when you boot the Windows computer. See Setting Up a WebLogic Server Instance as a Windows Service.

Click Next to continue.

20. On the Configure Server Start Mode and Java SDK page, select Production Mode. Then click Next.

For information on server modes, see Production and Development Modes.

21. On the Create WebLogic Configuration page, click Create.

By default, the wizard creates a domain with the following characteristics:

- The domain is named mydomain.
- The domain's Administration Server is named myserver.
- The root directory for the Administration Server is located in `WL_HOME`\`user_projects\domains\mydomain`.

To start the Administration Server in this domain, open a command prompt, change to `WL_HOME`\`user_projects\domains\mydomain`, and run the `startWebLogic.cmd` (Windows) or `startWebLogic.sh` (UNIX) script. To start Managed Servers, use the Node Manager or the `startManagedWebLogic` script. See "Starting and Stopping Servers" in the Administration Console Online Help.

To access the Administration Console for the domain, use any of the following URLs:

- From the same computer on which the server is running: `http://localhost:7001/console`
- From any computer:
  `http://``DNS-name``:7001/console`
  where `DNS-name` is the DNS name of the computer on which the server is running.
- From any computer:
  `http://``IP=Address``:7001/console`
  where `IP-Address` is an IP address of the computer on which the server is running.