Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Domains Using the Configuration Wizard

# Customizing the Environment

When you are creating a new domain using the Configuration Wizard, you have the option to change the distribution of your domain across servers, clusters, and machines.

The following topics describe the steps required to change the environment for your domain:

- Configure the Administration Server
- Configure Managed Servers
- Configure Clusters
- Assign Managed Servers to Clusters
- Create HTTP Proxy Applications
- Configure Machines
- Assign Servers to Machines
- Review the Domain Settings

## Related Topics

Creating a Domain with Managed Servers and Clusters

# Configure 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. This information is used to access the Administration 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. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Note: Fields marked with an asterisk are required.
Name* | Enter a valid server name: a string of characters that can include spaces. Each server instance in your product 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 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 | 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 | 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. The valid listen port range is from 1 to 65534. For more information, see Specifying Listen Ports.
SSL listen port | 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. The valid listen port range is from 1 to 65534. 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 Securing WebLogic Server at `http://e-docs.bea.com/wls/docs90/secmanage/ssl.html.` For more information, see Specifying Listen Ports.
SSL enabled | 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.

# Configure Managed Servers

The Configure Managed Servers window prompts you to provide the configuration information for one or more Managed Servers. Production environments typically deploy one or more Managed Servers, in addition to the Administration Server, to host enterprise applications. (For details, see Introduction to Domains.) This step is optional.

Note: You can create Managed Servers on remote machines using the `pack` and `unpack` commands. For more information, see "Creating and Starting a Managed Server on a Remote Machine: Main Steps" in Creating Templates and Domains Using the pack and unpack Commands at `http://e-docs.bea.com/common/docs90/pack/tasks.html#remote`.

#### To Configure Managed Servers:

1. Review the current list of Managed Server configurations. Default values may vary, based on the domain source you selected earlier.

Note: The wizard provides two views: a concise tabular view of all the Managed Servers and an individual view of each Managed Server, where each server is represented by a tab—you switch between servers by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your domain, using the guidelines provided in the following table. To delete a Managed Server, select the Managed Server in the list and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Note: Fields marked with an asterisk are required.
Name* | Enter a valid server name: a string of characters that can include spaces. Each server instance in your WebLogic environment must have a unique name, regardless of its function (Managed Server or Administration Server) and the domain or cluster in which it resides. In addition, the name of each Managed Server must be unique among all component names within the domain. The default value in this field is `new_Server_``n`, where `n` specifies a numeric value used to differentiate among default Managed Server names; the value of `n` for the first Managed Server is 1. The value is incremented by 1 for each Managed Server that is added. Note: The server name is included 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 managed server.
Listen address | Select a value for the listen address from the drop-down list. 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 a server instance's listen address 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. If you intend to run the Managed Server on a remote machine, be sure to specify a valid IP address for the machine that will host the Managed Server. To learn more about listen addresses, see Specifying Listen Addresses.
Listen port | 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. The valid listen port range is from 1 to 65534. If you intend to run the Managed Server on a remote machine, be sure to specify a valid listen port for the machine that will host the Managed Server. For more information, see Specifying Listen Ports.
SSL listen port | 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. The valid listen port range is from 1 to 65534. 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 Securing WebLogic Server at`http://e-docs.bea.com/wls/docs90/secmanage/ssl.html.` For more information, see Specifying Listen Ports.
SSL enabled | Select the check box to enable the SSL Listen Port. The default is disabled.

# Configure Clusters

A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. This window is displayed only if your domain contains at least one Managed Server.

The Configure Clusters window prompts you to configure the clusters in your domain. This step is optional.

#### To configure clusters:

1. Review the current list of cluster configurations. Default values may vary, based on the domain source you selected earlier.

Note: The wizard provides two views: a concise tabular view of all the clusters and an individual view of each cluster, where each cluster is represented by a tab—you switch between clusters by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries, as required by your domain, using the guidelines provided in the following table. To delete a cluster, select the cluster in the list and click Delete. When you finish updating your settings, click Next.

Note: If you are creating a domain that includes Service Bus functionality, you can configure only one cluster per domain.

In this field . . . | Enter a . . .
--- | ---
Note: Fields marked with an asterisk are required.
Name* | Valid cluster name: a string of characters that can include spaces. The name of the cluster must be unique among all component names within the domain. The default value in this field is `new_Cluster_``n`, where `n` specifies a numeric value that is used to differentiate among all default cluster names; the value of `n` for the first cluster is 1. The value is incremented by 1 for each cluster that is added.
Multicast address | Multicast address for the cluster. This address is used by cluster members to communicate with each other. The default value is 239.192.0.0. Valid multicast addresses are any valid IP addresses from 224.0.0.1 to 239.255.255.255.
Multicast port | Multicast port for the cluster. The multicast port is used by cluster members to communicate with each other. The default value is 7001. Valid values for multicast ports are from 1 to 65534.
Cluster address | Cluster address that identifies the Managed Servers in the cluster. A cluster address can be one of the following: Comma-separated list of IP addresses or DNS names and ports, for example: `dns_name:port`, `dns_name:port` DNS name that maps to multiple IP addresses `localhost`, DNS name, or IP address if the listen address of all Managed Servers is listening to the same address with unique port numbers The cluster address is used in entity and stateless EJBs to construct the host name portion of URLs. If the cluster address is not set, EJB handles may not work properly.

## Related Topics

Configure Managed Servers

"Setting Up WebLogic Clusters" in Using WebLogic Server Clusters at`http://e-docs.bea.com/wls/docs90/cluster/setup.html`

# Assign Managed Servers to Clusters

The Assign Servers to Clusters window prompts you to assign the available Managed Server(s) to a cluster within the domain. This window is displayed only if you have defined at least one cluster.

#### To assign Managed Servers to clusters:

1. In the Cluster pane, select the cluster to which you want to assign a Managed Server.
2. Assign the Managed Server to the designated cluster in one of the following ways:

- Double-click the name of the Managed Server in the Server pane.
- Select the Managed Server and click the right arrow.
- Shift-click to select multiple Managed Servers, then click the right arrow.

The name of the Managed Server is removed from the Server pane and added, below the name of the target cluster, to the Cluster pane.

Note: Only Managed Servers are listed in the Server pane. The Administration Server is not listed because it cannot be assigned to a cluster.

3. Repeat steps 1 and 2 for each Managed Server that you want to assign to a cluster.
4. Review the cluster assignments.

If necessary, you can remove a Managed Server from a cluster in one of the following ways:

- Double-click the name of the Managed Server in the Cluster pane.
- Select the Managed Server and click the left arrow.

The name of the Managed Server is removed from the Cluster pane and restored to the Server pane.

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

# Create HTTP Proxy Applications

The Create HTTP Proxy Applications window prompts you to create an HTTP proxy application on a Managed Server to proxy client requests to the cluster. An HTTP proxy application operates as an intermediary for HTTP requests.

This window is displayed only if both of the following statements are true:

- At least one Managed Server has been assigned to a cluster.
- At least one Managed Server has not been assigned to a cluster.

#### To create HTTP proxy applications:

1. If you have multiple clusters, select the tab corresponding to the cluster for which you want to create HTTP proxy applications.
2. Click Create HTTP proxy for cluster clustername.

A list of the available servers is displayed in the Proxy Server drop-down list.

Note: Only Managed Servers that have not been assigned to a cluster are displayed in the drop-down list.

3. From the Proxy Server list, select a Managed Server onto which the proxy applications can be deployed.

A proxy application named `BEAProxy4_``clustername``_``servername` is created and targeted to the Managed Server.

4. Repeat steps 1 through 3 for each cluster for which you want to create HTTP proxy applications.
5. Click Next to proceed to the next configuration window.

# Configure Machines

The Configure Machines window prompts you to define the configuration information for the Windows and UNIX machines in the domain. This step is optional.

You may want to perform this step in circumstances such as (but not limited to) the following:

- The Administration Server uses the machine definition, in conjunction with the Node Manager application, to start remote servers.
- WebLogic Server uses configured machine names when determining which server in a cluster is best able to handle certain tasks, such as HTTP session replication. WebLogic Server then delegates those tasks to the identified server.

Note: You must create a machine configuration for each product installation that runs a Node Manager process. The machine configuration must include values for the listen address and port number parameters.

#### To configure Windows machines:

Select the Machine tab and review the current list of configurations for Windows machines. Add or modify entries as required by your domain using the guidelines provided in the following table. Default values may vary, based on the domain source you selected earlier. To delete a machine, select the machine in the list and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Note: Fields marked with an asterisk are required.
Name* | Enter a valid machine name: a string of characters that can include spaces. The machine name: Is used to identify the machine within the WebLogic Server domain; it is not required to match the network name for the machine. Must be unique among all component names within the domain. The default value in this field is `new_Machine_``n`, where `n` specifies a numeric value that is used to differentiate among all default machine names; the value of `n` for the first machine is 1. The value is incremented by 1 for each machine that is added.
Node manager listen address | Select a value from the drop-down list for the listen address used by Node Manager to listen for connection requests. By default, the IP addresses defined for the local system and `localhost` are shown in the drop-down list. The default is `localhost`. Valid values for the listen address are as follows: IP address of the computer that hosts the server DNS name that resolves to the host `localhost` `All Local Addresses` If you specify an IP address for a machine that will host the Administration Server and you need to access the WebLogic Server Node Manager, you must disable host name verification. For details and instructions, see "Using Host Name Verification" in "Configuring SSL" in Securing WebLogic Server at the following URL: `http://e-docs.bea.com/wls/docs90/secmanage/ssl.html#host_name_verifier`
Node manager listen port | Enter a valid value for the listen port used by Node Manager to listen for connection requests. The valid Node Manager listen port range is from 1 to 65534. The default value is 5556.

#### To configure UNIX machines:

Select the UNIX Machine tab and review the current list of UNIX machine configurations. Add or modify entries as required by your domain, using the guidelines provided in the following table. Default values may vary, based on the domain source you selected earlier. To delete a machine, select the machine in the list and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Note: Fields marked with an asterisk are required.
Name* | Enter a valid machine name: a string of characters that can include spaces. The machine name: Is used to identify the machine within the WebLogic Server domain; it is not required to match the network name for the machine. Must be unique among all component names within the domain. The default value in this field is `new_UnixMachine_``n`, where `n` specifies a numeric value that is used to differentiate among all default machine names; the value of `n` for the first machine name is 1. The value is incremented by 1 for each machine that is added.
Post bind GID enabled | Select the check box to enable a server running on this machine to bind to a UNIX group ID (GID) after it finishes all privileged startup actions (see Post bind GID). The default is Disabled (unchecked).
Post bind GID | Enter a valid UNIX group ID (GID) that a server running on this machine will run under after it finishes all privileged startup actions. Otherwise, the server continues to run under the group from which it was started. (Requires that you enable Post-Bind GID.)
Post bind UID enabled | Select the check box to enable a server running on this machine to bind to a UNIX user ID (UID) after it finishes all privileged startup actions (see Post bind UID). The default is Disabled (unchecked).
Post bind UID | Enter a valid UNIX user ID (UID) that a server running on this machine will run under after it finishes all privileged startup actions. Otherwise, the server continues to run under the account from which it was started. (Requires that you enable Post-Bind UID.)
Node manager listen address | Select a value from the drop-down list for the listen address used by Node Manager to listen for connection requests. By default, the IP addresses defined for the local system and `localhost` are shown in the drop-down list. The default is `localhost`. Valid values for the listen address are as follows: IP address of the computer that hosts the server DNS name that resolves to the host `localhost` `All Local Addresses` If you specify an IP address for a machine that will host the Administration Server and need to access the WebLogic Server Node Manager, you must disable host name verification. For details and instructions, see "Using Host Name Verification" in "Configuring SSL" in Securing WebLogic Server at the following URL: `http://e-docs.bea.com/wls/docs90/secmanage/ssl.html#host_name_verifier`
Node manager listen port | Enter a valid value for the listen port used by Node Manager to listen for connection requests. The valid Node Manager listen port range is from 1 to 65534. The default value is 5556.

## Related Topics

"Using Node Manager to Control Servers" in Managing Server Startup and Shutdown at`http://e-docs.bea.com/wls/docs90/server_start/nodemgr.html`

# Assign Servers to Machines

The Assign Servers to Machines window prompts you to assign WebLogic Server instances to the machines on which they run. This window is displayed only if you have defined at least one machine.

#### To assign WebLogic Server instances to machines:

1. In the Machine pane, select the Windows or UNIX machine to which you want to assign a WebLogic Server instance.
2. Assign the appropriate WebLogic Server instance to the designated machine in one of the following ways:

- Double-click the WebLogic Server instance in the Server pane.
- Select the appropriate WebLogic Server instance in the Server pane and click the right arrow.
- Shift-click to select multiple Servers in the Server pane, then click the right arrow.

The name of the WebLogic Server instance is removed from the Server pane and added, below the name of the target machine, to the Machine pane.

3. Repeat steps 1 and 2 for each WebLogic Server instance that you want to assign to a machine.
4. Review the machine assignments.

If necessary, you can remove a WebLogic Server instance from a machine in one of the following ways:

- Double-click the name of the appropriate WebLogic Server instance in the Machine pane
- Select the appropriate WebLogic Server instance in the Machine pane and click the left arrow

The name of the WebLogic Server instance is removed from the Machine pane and restored to the Server pane.

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

If the domain source on which you are basing your domain contains JDBC data source and JMS file store definitions, you are presented with the option to modify them as described in Customizing Existing JDBC and JMS Settings. Otherwise, you are presented with the option to review the domain settings and create the domain.

# Review the Domain Settings

The Review WebLogic Domain window allows you to review the detailed configuration settings of your domain before the Configuration Wizard creates it.

#### To review the domain settings:

1. Select an item in the Domain Summary pane on the left and review the associated details in the Details pane on the right. You can make limited adjustments by clicking Previous to return to a prior window.

Note: You can limit the type of information displayed in the Domain Summary pane by selecting a filter from the View drop-down list.

2. Click Next to proceed to the next configuration window, Create the WebLogic Domain.