4 Creating and Configuring the WebLogic Domain

This section describes how to create and configure the WebLogic Server domain after you successfully install WebLogic Server and Coherence software.

This section includes the following topics:

4.1 Configuring the WebLogic Domain

Use the steps in this topic to create a WebLogic domain using the Configuration Wizard.

For other methods to create a domain, see "Additional Tools for Creating, Extending, and Managing WebLogic Domains" in Creating WebLogic Domains Using the Configuration Wizard.

This section includes the following topics:

4.1.1 Starting the Configuration Wizard

To begin domain configuration, navigate to the ORACLE_HOME/oracle_common/common/bin directory and start the Configuration Wizard.

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

.\config.cmd

4.1.2 Navigating Configuration Wizard Screens to Configure the Domain

Follow the sequence of topics this section to configure the domain with the Configuration Wizard. You can also use this procedure to extend an existing domain.

If your settings don't match those in the procedure, change your selections accordingly or see supporting documentation for additional details.

To configure multiple products in a single domain, see "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middleware.

4.1.2.1 Selecting the Domain Type and Domain Home Location

You specify a Domain type and Domain home directory.

To specify the Domain type and Domain home directory:

  1. On the Configuration Type screen, select Create a New Domain.
  2. In the Domain Location field, specify your Domain home directory.

Oracle recommends that you locate your Domain home in accordance with the directory structure summarized in What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure helps you avoid issues when you upgrade or reinstall your software.

Tip:

For more information about the Domain home directory, see "Choosing a Domain Home" in Planning an Installation of Oracle Fusion Middleware.

For more information about reinstalling the software, see Reinstalling Your Software.

For more information about other options on this screen, see "Configuration Type" in Creating WebLogic Domains Using the Configuration Wizard.

4.1.2.2 Selecting Configuration Templates

You select specific templates so that Managed Servers in the cluster will be managed Coherence servers, and the cluster will be a managed Coherence cluster. This is a starting point to set up your Coherence environment.

On the Templates screen select the following templates for configuration:

  • Basic WebLogic Server Domain (selected by default)

  • WebLogic Coherence Cluster Extension

    For more detailed information and next steps, see Table 6-1.

Tip:

For more information about options on this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.

4.1.2.3 Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

This account is used to boot and connect to the domain's Administration Server.

Tip:

You must make a note of the user name and password you choose to enter here; you will need this in order to be able to start and access the Administration Server.

4.1.2.4 Specifying the Domain Mode and JDK

There are differences between production mode and development mode.

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

  • Select the Oracle Hotspot JDK in the JDK field.

Select Production Mode to give your environment a higher degree of security. You need to enter a user name and password to deploy applications and to start the Administration Server.

Tip:

For details about options on this screen, including differences between development mode and production mode, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

4.1.2.5 Selecting Advanced Configuration

To complete domain configuration for the topology, select these options on the Advanced Configuration screen:

  • Administration Server

    Required to properly configure the Administration Server listen address.

  • Node Manager

  • Managed Servers, Clusters and Coherence

    Required to configure the Managed Servers and cluster, and for configuring the machine and targeting Managed Servers to the machine.

    Tip:

    To configure dynamic clusters, see "Creating Dynamic Clusters" in Administering Clusters for Oracle WebLogic Server.

4.1.2.6 Configuring the Administration Server Listen Address

On the Administration Server screen, select the drop-down list next to Listen Address and select the IP address on the host where the Administration Server will reside.

Do not use "All Local Addresses".

4.1.2.7 Configuring Node Manager

Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Select Per-Domain Default Location as the Node Manager type, then specify Node Manager credentials.

Tip:

See Node Manager in Creating WebLogic Domains Using the Configuration Wizard for details about options on this screen.

See "Node Manager Overview" in Administering Node Manager for Oracle WebLogic Server for details about the types of Node Manager.

4.1.2.8 Configuring Managed Servers

Use the Managed Servers screen to create two new Managed Servers.

  1. Click the Add button to create a new Managed Server.
  2. Specify wls_server_1 in the Server name column.
  3. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on. Do not use "All Local Addresses".
  4. Repeat this process to create a second Managed Server named wls_server_2.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

    For more on the high availability standard topology, see "Understanding the Fusion Middleware Standard HA Topology" in the High Availability Guide.

    For more on the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment For High Availability.

The rest of this document uses the wls_server_1 and wls_server_2 server names; if you choose different names, be sure to substitute wls_server_1 and wls_server_2 with your server names.

Tip:

For more about options on this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

4.1.2.9 Configure a Cluster

You configure a cluster to group Managed Servers.

To create a new cluster:

  1. Click the Add button.
  2. Enter wls_cluster_1 in the Cluster Name field.
  3. Leave the cluster Address field blank.

By default, server instances in a cluster use unicast to communicate with each other. To change your cluster communications to use multicast, see "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.

Tip:

For more about options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.

4.1.2.10 Assigning Managed Servers to the Cluster

To assign wls_server_1 and wls_server_2 to the new cluster wls_cluster_1, use the Assign Servers to Clusters screen.

  1. In the Clusters pane, select the cluster that you want to assign the servers to; in this case, wls_cluster_1.
  2. In the Servers pane, take one of the following steps to assign wls_server_1 to wls_cluster_1:
    • Click once on wls_server_1 to select it, then click on the right arrow to move it beneath the selected cluster (wls_cluster_1) in the Clusters pane.

    • Double-click on wls_server_1 to move it beneath the selected cluster (wls_cluster_1) in the clusters pane.

  3. Repeat to assign wls_server_2 to wls_cluster_1.

Tip:

See Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard for details on options in this screen.

4.1.2.11 Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the default port number 0 as the Coherence cluster listen port.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that can be assigned to a Managed Server port number is 60535, instead of 65535.

See Table 6-2 for more information and next steps for configuring Coherence. For Coherence licensing information, see "Oracle Coherence" in Oracle Fusion Middleware Licensing Information.

4.1.2.12 Creating a New Machine

To create a new machine in the domain, use the Machines screen. Node Manager requires a machine to be able to start and stop servers.

Tip:

If you plan to create a high availability environment and know the list of machines that your target topology requires, you can follow the steps in this topic to create all machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.

To create a new machine in the domain:

  1. Click the Add button to create a new machine.
  2. Specify wls_machine_1 in the Name field.
  3. In the Node Manager Listen Address field, select the IP address of the machine where you are configuring Managed Servers.

    You must select a specific interface and not "localhost." This allows Coherence cluster addresses to be dynamically calculated.

  4. Verify the port in the Node Manager Listen Port field.

    Other examples in the documentation may refer to the port number 5556. Replace this port number with your own port number as needed.

    Note:

    If you extend an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.

    Tip:

    See "Machines" in Creating WebLogic Domains Using the Configuration Wizard for more about this screen.

    If you plan to create a high availability environment and know the list of machines required for your target topology, you can create all machines at this time. For more information, see "Optional Scale Out Procedure" in High Availability Guide.

4.1.2.13 Assigning Servers to Machines

You assign both Managed Servers to a machine.

To assign the Administration Server and Managed Servers to the new machine you just created:

  1. In the Machines pane, select the machine you want to assign the servers to; in this case, wls_machine_1.

  2. In the Servers pane, assign AdminServer to wls_machine_1 by doing one of the following:

    • Click once on AdminServer to select it, then click on the right arrow to move it beneath the selected machine (wls_machine_1) in the Machines pane.

    • Double-click on AdminServer to move it beneath the selected machine (wls_machine_1) in the Machines pane.

  3. Repeat to assign both wls_server_1 and wls_server_2 to wls_machine_1.

Tip:

See Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard for more on options on this screen.

4.1.2.14 Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen has detailed configuration information for the domain you are about to create. Review this screen to verify that the information is correct.

To make any changes, go back to a screen by using the Back button or selecting the screen in the navigation pane.

Domain creation does not start until you click Create.

Tip:

See Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard for more on options in this screen.

4.1.2.15 Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows two important items about the domain you just configured.

The Configuration Success screen shows:

  • Domain Location

  • Administration Server URL

You must make a note of both items; you need them to start the servers and access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

4.2 Starting the Servers

After you finish configuration, Oracle recommends that you take the following steps to access tools that you use to manage your domain

4.2.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start Node Manager as shown below, using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > nm.out&

On Windows operating systems, run:

startNodeManager.cmd

Note:

If you use Windows, Oracle recommends that you install Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted. (Node Manager is not required to start servers, Oracle recommends it over other methods.)

For more information, see "Running Node Manager as a Startup Service" in Administering Node Manager for Oracle WebLogic Server.

4.2.2 Starting the Administration Server

To start the Administration Server, go the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen in Specifying the Domain Mode and JDK, you see a prompt for Administrator login credentials, shown on the Administrator Account screen in Configuring the Administrator Account.

Tip:

For more about starting the Administration Server, see "Starting and Stopping Servers" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

In production mode, you can create a boot identity file to bypass the need to provide a user name and password when starting the Administration Server. For more information, see "Creating a Boot Identity File for an Administration Server" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

4.2.3 Starting Managed Servers

To start Managed Servers, go the DOMAIN_HOME/bin directory and run the command:

On UNIX operating systems:

./startManagedWebLogic.sh managed_server_name admin_server_url

On Windows operating systems:

startManagedWebLogic.cmd managed_server_name admin_server_url

Replace managed_server_name with the names of Managed Server you want to start. For this topology, Managed Server names are wls_server_1 and wls_server_2 (defined on the Managed Server screen in Configuring Managed Servers). You must run this command twice, once for each Managed Server.

Replace admin_server_url with the Administration Server's full URL, as shown in the Configuration Success screen in Reviewing Your Configuration Specifications and Configuring the Domain.

The following examples show commands to start wls_server_1 and wls_server_2 on a UNIX operating system:

./startManagedWebLogic.sh wls_server_1 t3:\\examplehost.exampledomain.com:7001 &
./startManagedWebLogic.sh wls_server_2 t3:\\examplehost.exampledomain.com:7001 &

Tip:

For more on starting Managed Servers, see "Starting and Stopping Servers" in Administering Server Startup and Shutdown for Oracle WebLogic Server.

4.3 Verifying the Configuration

You want to verify that your domain is configured properly.

To verify configuration, see Performing Basic Administrative Tasks. Oracle recommends that you familiarize yourself with the tasks that this section describes and perform them to verify that your domain is properly configured.