WebLogic Server Domain Configuration Wizard

Domain Configuration Wizard

Contents

Overview
boot.properties
Development vs. Production Mode
Changing the JVM that Runs Servers

Overview

To start Configuration Wizard:
config.sh -mode=console

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. Here are the default 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 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.

boot.properties

If you create a domain in development mode, the Configuration Wizard creates a boot.properties file that contains your username and encrypted password. This file enables you to bypass the prompt for username and password during a server's startup cycle.
If the boot.properties file every gives you trouble, just mv/rm it, then stick the username and password inside the start*.sh scripts.

Development vs. Production Mode

To change the runtime mode to production mode, edit StartWebLogic.sh and set PRODUCTION_MODE=TRUE.

SSL Development mode enables use of the bundled demo digital certificates. Production mode warns you if you are using the demonstration digital certificates.

Deploying Applications Development mode enables WebLogic Server instances to automatically deploy and update apps located in:
domain/applications

Production mode disables the auto-deployment feature. Rather, use the console or the weblogic.Deployer tool.

Execute Queues The development default of thread count is 15. The production default thread count is 25.

JDBC Connection Pool Capacity Development default capacity is 15 connections. Production default is 25 connections.

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 Admin server. In a development environment it is acceptable to deploy applications on the Admin server; in a production environment, BEA recommends that you use Admin 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:

Start the Domain Configuration Wizard. The Domain Configuration Wizard displays the Create New Configuration or Add to Existing Configuration page.
On the Create New Configuration or Add to an Existing Configuration page, click Create a new WebLogic configuration button. Then click Next.
On the Select a Configuration Template page, choose the Basic WebLogic Server Domain template. Then click Next.
On the Choose Express or Custom Configuration page, choose Express. Then click next.
On the Configure Username and Password page, enter a user name and password. This user becomes the initial administrative user for the domain.
Click Next and confirm the password.
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 Admin server.
The domain is created for a development environment.
The root directory for the Admin server is located in WL_HOME\user_projects\mydomain.
The domain includes a boot.properties file.

To start the server in this domain, go to $WL_HOME/user_projects/mydomain, and run StartWebLogic.sh
To access the console for the domain, go to:

Example: Creating a Domain with Admin server and Clustered Managed Servers

This type of domain configuration is recommend for production environments that require the improved availability and performance provided by failover and load balancing in a WebLogic Server cluster.
To create a new domain with a cluster of Managed Servers and an Admin server (which is not part of the cluster):

Start the Domain Configuration Wizard. The Domain Configuration Wizard displays the Create New Configuration or Add to Existing Configuration page. Note: The remaining instructions in this section assume that you are running the Domain Configuration Wizard in GUI mode.

On the Create New Configuration or Add to Existing Configuration page, click Create a new WebLogic Configuration button. Then click Next.

On the Select a Configuration Template page, choose the Basic WebLogic Server Domain template. Then click Next.

On the Choose Express or Custom Configuration page, choose Custom. Then click next.

On the Admin server Configuration page, configure the Admin server as follows:

Server 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 console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.

Listen Address Leave this field empty to accept the default behavior, or enter an IP address of the computer that hosts the server, or a DNS name that resolves to the host. Enter localhost only if all Managed Servers are on the same computer as the Admin server. Servers can be reached through the following URL: protocol://listen-address:listen-port

Server Listen Port Enter a numeric value for the listen port. The range is 1 to 65535. The default port is 7001.

Server SSL Listen Port Enter a numeric value for SSL listen port. The range is 1 to 65535. The default port is 7002. By default, the server instance uses demonstration certificates for SSL communication. In a production environment, configure the server to use certificates from a certificate authority.

Click Next.
On the Multiple Servers, Clusters and Machine Options page, click Yes. Then click Next.
On the Managed Servers Configuration 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 Leave this field empty to accept the default behavior, or enter an IP address of the computer that hosts the server, a DNS name that resolves to the host, or localhost. Servers can be reached through the following URL:
protocol://listen-address:listen-port

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

Server SSL Listen Port Enter a numeric value for the SSL listen port. To enable this port, place a check mark in the SSL Enabled box. If you are using SSL, after you create the domain, obtain a private key, digital certificate, and trusted CA. Then use the console to configure the server to use your private key and certificates instead of the demonstration keys and certificates.

Repeat for each additional Managed Server, then click Next to move to the Cluster Configuration page.
On the Cluster Configuration 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.

Cluster MultiCast Address Enter a multicast address for the cluster. This address must begin with 237.xx.xx.xxxx, 238.xx.xx.xxxx, or 239.xx.xx.xxxx.

Cluster MultiCast Port Enter a numeric value for the multicast port. The range of values is 1 to 65535.

Cluster Address Enter the cluster address. 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.

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.

Click Next to display the Servers to Cluster Assignments page.
On the Servers to Cluster Assignments page:

In the Targets list, select the cluster you created.
In the Sources list, select Managed Servers. Admin servers cannot be part of a cluster.
Click the right arrow button to assign the server to the cluster.
Click Next to display the Machine Configuration page.

On the Machine Configuration page, complete the following steps for each WebLogic Server host that will run servers in the domain:

Click the Add button.
In the Machine row, in Name column provide a name that identifies the computer that will run a server instance.
If you plan to use the Node Manager on the computer, in the Listen Address column, enter the DNS name of the computer. In Listen Port, enter the port on which the Node Manager listens for requests.
The Admin server uses the listen address and listen port to connect to the Node Manager running on the remote computer. The Admin 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.
Click Next to display the Machine to Server Associations page.
On the Servers to Machine Assignments page:

In the Targets list, select a Machine that you created.
In the Sources list, select a server.
Click the right arrow to assign the server to the machine.
When you complete all server associations, click Next.

Skip subsequent pages until the wizard displays the Configure Username and Password page.
On the Configure Username and Password page, enter a user name and password. This user becomes the initial administrative user for the domain.
Click Next and confirm the password.

On the Domain Environment Configuration page, select Production Mode. Then click Next.

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 Admin server is named myserver.
The root directory for the Admin server is located in WL_HOME\user_projects\mydomain.

To start the server in this domain, open a command prompt, change to WL_HOME\user_projects\mydomain, and run the StartWebLogic.cmd (Windows) or StartWebLogic.sh (UNIX) script.

Changing the JVM that Runs Servers

When you create a domain, if you choose to customize the configuration, the Configuration Wizard presents a list of SDKs that WebLogic Server installed. From this list, you choose the JVM that you want to run your domain and the wizard configures the server start scripts based on your choice.
After you create a domain, if you want to use a different JVM, you can modify the start scripts as follows:

domain/StartWebLogic.sh and/or domain/StartManagedWebLogic.sh
Change the value for the JAVA_HOME variable.
Change the value for the JAVA_VENDOR variables.

BEA indicates that you are using the JRockit SDK. It is valid only on platforms that support JRockit.
Sun indicates that you are using the Sun SDK.
HP and IBM indicate that you are using SDKs that Hewlett Packard or IBM have provided. These values are valid only on platforms that support HP or IBM SDKs.

Bounce servers

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

SSL	Development mode enables use of the bundled demo digital certificates. Production mode warns you if you are using the demonstration digital certificates.
Deploying Applications	Development mode enables WebLogic Server instances to automatically deploy and update apps located in: domain/applications Production mode disables the auto-deployment feature. Rather, use the console or the weblogic.Deployer tool.
Execute Queues	The development default of thread count is 15. The production default thread count is 25.
JDBC Connection Pool Capacity	Development default capacity is 15 connections. Production default is 25 connections.

Server 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 console, and if you use WebLogic Server command-line utilities or APIs, you use this name to identify the server.
Listen Address	Leave this field empty to accept the default behavior, or enter an IP address of the computer that hosts the server, or a DNS name that resolves to the host. Enter localhost only if all Managed Servers are on the same computer as the Admin server. Servers can be reached through the following URL: protocol://listen-address:listen-port
Server Listen Port	Enter a numeric value for the listen port. The range is 1 to 65535. The default port is 7001.
Server SSL Listen Port	Enter a numeric value for SSL listen port. The range is 1 to 65535. The default port is 7002. By default, the server instance uses demonstration certificates for SSL communication. In a production environment, configure the server to use certificates from a certificate authority.

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	Leave this field empty to accept the default behavior, or enter an IP address of the computer that hosts the server, a DNS name that resolves to the host, or localhost. Servers can be reached through the following URL: protocol://listen-address:listen-port
Listen Port	Enter a numeric value for the listen port. The range is 1 to 65535.
Server SSL Listen Port	Enter a numeric value for the SSL listen port. To enable this port, place a check mark in the SSL Enabled box. If you are using SSL, after you create the domain, obtain a private key, digital certificate, and trusted CA. Then use the console to configure the server to use your private key and certificates instead of the demonstration keys and certificates.

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.
Cluster MultiCast Address	Enter a multicast address for the cluster. This address must begin with 237.xx.xx.xxxx, 238.xx.xx.xxxx, or 239.xx.xx.xxxx.
Cluster MultiCast Port	Enter a numeric value for the multicast port. The range of values is 1 to 65535.
Cluster Address	Enter the cluster address. 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. 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.