3 Creating and Configuring the WebLogic Domain
This section includes the following topics:
- Configuring the WebLogic Domain
Use the steps in this topic to create a WebLogic domain using the Configuration Wizard. - 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 - Verifying the Configuration
This section explains how to verify that your domain is configured properly.
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:
- Starting the Configuration Wizard
To begin domain configuration, navigate to theORACLE_HOME
/oracle_common/common/bin
directory and start the Configuration Wizard. - Navigating Configuration Wizard Screens to Configure the Domain
Follow the sequence of topics in this section to configure the domain with the Configuration Wizard. You can also use this procedure to extend an existing domain.
Parent topic: Creating and Configuring the WebLogic Domain
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
Parent topic: Configuring the WebLogic Domain
Navigating Configuration Wizard Screens to Configure the Domain
Follow the sequence of topics in 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.
- Selecting the Configuration Type and Domain Home Location
Use this screen to select a configuration type and domain home directory. - Selecting Configuration Templates
You can 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. - Configuring the Administrator Account
On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain. - Specifying the Domain Mode and JDK
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK) for your production environment. - Selecting Advanced Configuration
To complete domain configuration for the topology, select these options on the Advanced Configuration screen: - Configuring the Administration Server Listen Address
Use the Administration Server screen to select the Listen Address and configure the Administration Server ports. - 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. - Configuring Managed Servers
Use the Managed Servers screen to create a new Managed Server. - Configure a Cluster
You configure a cluster to group Managed Servers. - Defining Server Templates
If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for the domain. - Configuring Dynamic Servers
If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers. - Assigning Managed Servers to the Cluster
To assignwls_server_1
andwls_server_2
to the new clusterwls_cluster_1
, use the Assign Servers to Clusters screen. - 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 7574 as the Coherence cluster listen port. - 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. - Assigning Servers to Machines
You assign both Managed Servers to a machine. - 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. - Writing Down Your Domain Home and Administration Server URL
The Configuration Success screen shows two important items about the domain you just configured.
Parent topic: Configuring the WebLogic Domain
Selecting the Configuration Type and Domain Home Location
Use this screen to select a configuration type and domain home directory.
To specify the type of domain configuration to perform:
- On the Configuration Type screen, select Create a New Domain.
- 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 on the Domain home directory, see Choosing a Domain Home in Planning an Installation of Oracle Fusion Middleware.
For more about reinstalling the software, see Reinstalling Your Software.
For more about other options on this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Selecting Configuration Templates
You can 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
Tip:
See Templates in Creating WebLogic Domains Using the Configuration Wizard for details about options on this screen.
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.
Specifying the Domain Mode and JDK
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK) for your production environment.
On the Domain Mode and JDK screen:
-
Select Production in the Domain Mode field.
Note:
As of WebLogic Server 14.1.2.0.0, when you select Production mode, WebLogic Server automatically sets some of the security configurations of Secured Production to more secure values. However, there are certain security configurations (such as SSL/TLS) that require manual configuration. See Using Secured Production Mode in .
If you want to disable the more secure default settings, then you may select Disable Secure Mode. This will enable the non-SSL listen ports.
If you want to retain the more secure default settings of Secured Production mode in general, but want to change which ports (listen ports, SSL listen ports, or administration ports) will be enabled by default in your domain, then you may:- Leave Disable Secure Mode unselected, and
- Change the default port selections under Enable or Disable Default Ports for Your Domain
For more information, see Understand How Domain Mode Affects the Default Security Configuration in .
-
Select the Oracle HotSpot JDK in the JDK field.
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
-
Topology
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.
Configuring the Administration Server Listen Address
Use the Administration Server screen to select the Listen Address and configure the Administration Server ports.
Note:
The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.
- Provide a name for the Administration Server. The name field must not be null or empty and cannot contain any special characters.
- Select the drop-down list next to Listen Address and select the IP
address of the host where the Administration Server will reside or use the system name or
DNS name that maps to a single IP address. Do not use
All Local Addresses
. - Verify the port settings. When the domain type is set to Production, then
the Enable SSL Listen Port option is enabled by default. Do not specify any
server groups for the Administration Server.
Note:
You can change the port values as needed, but they must be unique. If the same port numbers are used for different ports, you will not be able to navigate to the next step in the Configuration Wizard.
For more information, see Specifying the Listen Address in .
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.
Configuring Managed Servers
Use the Managed Servers screen to create a new Managed Server.
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. The port numbers will be auto-incremented.
Tip:
For more options on this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Configure a Cluster
You configure a cluster to group Managed Servers.
To create a new cluster:
- Click the Add button.
- Enter
wls_cluster_1
in the Cluster Name field. - 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.
Defining Server Templates
If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for the domain.
Note:
The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.
- Click Add to create
new_ServerTemplate_1
. The server template name will increment automatically when an additional server template is added (new_ServerTemplate_2
). - For Secure Production Mode, verify that the
Enable SSL Port option is selected. The
default SSL Listen Port does not increment automatically
when a new server template is added. You can change the
default to Enable Listen Port, but Oracle recommends that
retain the default to enable SSL. Enabling Listen Port
disables SSL Listen Port.
Note:
You can change the port values as needed using an integer in the range of 1 and 65535, but they must be unique. If the same port numbers are used for different ports, you will receive a port conflict error and you will not be able to start the server.
- The Administration Port does not increment when an
additional server template is added.
Note:
If the Listen ports are disabled, then instead of seeing a number you will see
Disabled
.
For steps to create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in .
Configuring Dynamic Servers
If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.
If you are not configuring a dynamic cluster, click Next to continue configuring the domain.
Note:
When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.To create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in .
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.
Tip:
See Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard for details on options in this screen.
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 7574 as the Coherence cluster listen port.
Note:
Setting the unicast listen port to 7574 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 Performing Additional Configuration Tasks for next steps for configuring Coherence. For Coherence licensing information, see Oracle Coherence in Oracle Fusion Middleware Licensing Information.
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. See Optional Scale Out Procedure in High Availability Guide.
To create a new machine in the domain:
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:
-
In the Machines pane, select the machine you want to assign the servers to; in this case,
wls_machine_1
. -
In the Servers pane, assign
AdminServer
towls_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.
-
-
Repeat to assign both
wls_server_1
andwls_server_2
towls_machine_1
.
Tip:
See Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
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.
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.
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
Note:
Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console.
- Starting the Node Manager
To start your per-domain Node Manager, go to theDOMAIN_HOME
/bin
directory. - Starting the Administration Server
To start the Administration Server, go theDOMAIN_HOME
/bin
directory. - Starting Managed Servers
To start Managed Servers, go theDOMAIN_HOME
/bin
directory and run the command:
Parent topic: Creating and Configuring the WebLogic Domain
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.)
See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.
Parent topic: Starting the Servers
Starting the Administration Server
To start the Administration Server, go the DOMAIN_HOME
/bin
directory.
On UNIX operating systems:
./startWebLogic.sh
On Windows operating systems:
startWebLogic.cmd
If you selected Production Mode on the Domain Mode and JDK screen, then you will 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. See Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Parent topic: Starting the Servers
Starting Managed Servers
To start Managed Servers, go the DOMAIN_HOME
/bin
directory and run the command:
Note:
Depending on your existing security settings, you may need to perform additional configuration before you can start managed servers in a domain with secured production mode enabled. For more information see Starting Managed Servers using WebLogic Remote Console in Administering Security for Oracle WebLogic Server
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 https:\\examplehost.exampledomain.com:8003 & ./startManagedWebLogic.sh wls_server_2 https:\\examplehost.exampledomain.com:8004 &
Tip:
For more on starting Managed Servers, see Starting and Stopping Servers in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Parent topic: Starting the Servers
Verifying the Configuration
This section explains how 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.
Parent topic: Creating and Configuring the WebLogic Domain