Creating WebLogic Domains Using the Configuration Wizard

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Customizing the Environment

While creating a domain, you can (optionally) specify the RDBMS security store settings, configure the distribution of your domain across servers, clusters, and machines, specify JDBC data sources, define JMS file store settings.

This section describes how you can configure the domain environment while creating a domain.

To configure the domain environment, you must select Yes in the Customize Environment and Services Settings window. The Configuration Wizard guides you through the following series of steps.

Configuring the RDBMS Security Store Database

You can define RDBMS security store settings in the Configure RDBMS Security Store Database window, which is displayed when you select Yes in the Customize Environment and Services Settings window of the Configuration Wizard.

If RDBMS security store data already exists in config.xml, the data is displayed in read-only mode in the Configure RDBMS Security Store Database window.

After specifying the RDBMS security store settings, click Next.

Notes: You can test the connection to the database by clicking Test Connection.
Note: Before starting the server, you must load the necessary SQL scripts for the RDBMS security store.
Note: If you use an RDBMS security store in a clustered domain, it is recommended that you use it with JMS configuration (JNDI name and JMS topic). For more information, see the WebLogic Server Administration Console Online Help.

Configuring the Administration Server

In every domain, one server must be designated as the administration server: the central point from which the whole domain is managed.

You can access the administrator server by using the URL protocol://listen-address:listen-port. The protocol can be any of the following: t3, t3s, http, https.

You can define the listen-address and listen-port in the Configure the Administration Server window of the Configuration Wizard.

Note: The Configure the Administration Server window is displayed when you select Next in the Configure RDBMS Security Store Database window of the Configuration Wizard.

Table 4-2 describes the fields in the Configure the Administration Server window. Specify the appropriate values, and then click Next to proceed.

Note: Fields marked with an asterisk are required.
Table 4-2 Configuring the Administration Server
In this field...
Do the following...
Name*
Enter a valid server name: a string of characters that can include spaces.
Each server instance in the product environment must have a unique name, regardless of the domain or cluster in which it resides, and regardless of 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.
If you select localhost as the listen address for a server instance, non-local processes cannot connect to that 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.
For more information, see Specifying the Listen Address.
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 the Listen Port.
SSL enabled
Select this check box to enable the SSL listen port. By default, SSL is disabled for all new servers.
SSL listen port
This field is enabled only if the SSL enabled check box is selected.
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 65535.

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.

For more information, see Specifying the Listen Port.

Specifying the Listen Address

Table 4-3 provides guidelines for specifying the listen address for a server.

Table 4-3 Specifying Listen Address
If the listen address is set to...
Then...
All Local Addresses or a DNS name
On multi-homed Windows machines, a server instance binds to all available IP addresses.
An IP address or a 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 attempts to resolve the DNS name, but if it cannot access DNS name mapping, the request fails.

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 the Listen Port

Note the following guidelines when specifying the listen ports and secure listen port:

Configuring Managed Servers

In production environments, enterprise applications are hosted, typically, on one or more managed servers, in addition to the administration server.

You can add and delete managed servers in the Configure Managed Servers window, which is displayed when you click Next in the Configure the Administration Server window of the Configuration Wizard.

Note: You can create managed servers on remote machines by using the pack and unpack commands. For more information, see Creating and Starting a Managed Server on a Remote Machine.
  1. Review the current managed server configurations. Default values may vary, based on the domain source you selected earlier.
  2. 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.
  3. Add or delete managed servers, or change the settings for existing managed servers, as required for your domain.
  4. After configuring the managed servers, click Next to proceed.

Configuring Clusters

A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. By creating clusters, you can group managed servers such that they operate as a single unit for hosting applications and resources.

You can add, configure, and delete clusters in the Configure Clusters window of the Configuration Wizard. This window is displayed when you click Next in the Configure Managed Servers window, only if the domain contains at least one managed server.

  1. Review the current cluster configuration. Default values may vary, based on the domain source you selected earlier.
  2. 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.
  3. Add or delete clusters, or change the settings for existing clusters, as required for your domain.
Note: Fields marked with an asterisk are required.
Table 4-4 Configuring Clusters
Field
Action
Name*
Enter a valid name for the cluster: 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 is a numeric value that is used to differentiate among all the default cluster names; the value of n for the first cluster is 1. The value is incremented by 1 for each cluster that you add.
Multicast address
Enter the 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.
The valid multicast address range is 224.0.0.1 to 239.255.255.255.
Multicast port
Enter the 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
Enter the addresses to identify 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.
  1. After configuring the clusters, click Next to proceed.

Related Topics

Setting Up WebLogic Clusters in Using WebLogic Server Clusters

Assigning Managed Servers to Clusters

You can assign the available managed servers to clusters within the domain in the Assign Servers to Clusters window.

This window is displayed when you click Next in the Configure Clusters window, only if you have defined at least one cluster.

  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 in 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.
  5. 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.

  6. Click Next to proceed.

Creating HTTP Proxy Applications

An HTTP proxy application acts as an intermediary for HTTP requests.

In the Create HTTP Proxy Applications window of the Configuration Wizard, you can create an HTTP proxy application for each cluster, and specify the managed server on which the proxy application must be deployed.

This window is displayed when you click Next in the Assign Servers to Clusters window, only if both of the following statements are true:

To create HTTP proxy applications:

  1. If multiple clusters are defined, select the tab corresponding to the cluster for which you want to create HTTP proxy applications.
  2. Select the Create HTTP proxy for cluster <cluster_name> check box.
  3. A list of the managed servers that are not assigned to any cluster is displayed in the Proxy Server drop-down list.

  4. From the Proxy Server list, select a managed server on which the proxy applications must be deployed.
  5. A proxy application named BEAProxy4_clustername_servername is created and targeted at the managed server.

  6. Repeat steps 1 through 3 for each cluster for which you want to create HTTP proxy applications.
  7. Click Next to proceed.

Configuring Machines

In a domain, the machine definitions identify physical units of hardware and are used to associate computers with the managed servers that they host.

You might want to create machine definitions in situations such as (but not limited to) the following:

Note: You must configure machines for each product installation that runs a node manager process. The machine configuration must include values for the listen address and port number parameters.

You can create machine definitions in the Configure Machines window, which is displayed when you click Next in the Create HTTP Proxy Applications window of the Configuration Wizard.

  1. Select the Machine tab (for Windows) and Unix Machine tab for (UNIX)
  2. Review the current list of configurations, and add or change entries as required for your domain.
    • To add a machine, click Add.
    • To delete a machine, select the machine in the list and click Delete.
    • Table 4-5 describes the configuration settings that you can define. Default values may vary based on the domain source that you selected earlier.

      Note: Fields marked with an asterisk are required.
      Table 4-5 Configure Windows Machine
      Field
      Description
      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.
      The name must be unique among all component names within the domain.
      The default value in this field is new_Machine_n, where n is 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 you add.
      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 value is localhost.
      If you specify an IP address for a machine that hosts the administration server and you need to access the WebLogic Server node manager, you must disable host name verification. For more information, see Using Host Name Verification in Securing WebLogic Server.
      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.
      Post bind GID enabled
      This field is displayed only in the Unix Machine tab.
      Select this 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). By default, this check box is not selected.
      Post bind GID
      This field is displayed only in the Unix Machine tab.
      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
      This field is displayed only in the Unix Machine tab.
      Select this 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). By default, this check box is not selected.
      Post bind UID
      This field is displayed only in the Unix Machine tab.
      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.)
  3. After updating the settings, click Next.

Assigning Servers to Machines

After configuring servers and defining machines, you can assign WebLogic Server instances to machines in the Assign Servers to Machines window.

This window is displayed only if you have defined at least one machine. It is displayed when you click Next in the Configure Machines window.

  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, in 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.
  5. 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.

  6. Click Next.
  7. 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 JDBC and JMS Settings in WebLogic Domains. Otherwise, you are presented with the option to review the domain settings and create the domain.

Review the Domain Settings and Create the Domain

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

  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 previous window.
  2. Note: You can limit the type of information displayed in the Domain Summary pane by selecting a filter from the Summary View drop-down list.
  3. After reviewing the domain settings, click Next.
  4. The Create WebLogic Domain window is displayed

  5. Enter the name of the domain and specify the domain location.
    • Domain names must not start with a number. This restriction prevents potential conflicts with internally-generated JDBC store table names, which must begin with a letter.
    • The domain directory can be located anywhere in the 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 template.
    • The Configuration Wizard stores the config.xml file and all other generated components in the domain directory that you specify.

  6. Click Create.
  7. Note: You cannot overwrite an existing domain. If a domain with the name you specified already exists in the selected location, you must either delete the existing domain, or specify a different name or location for the new 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.


  Back to Top       Previous  Next