Creating and Configuring the WebLogic Domain

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:

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

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 Domain Type and Domain Home Location

You specify a Domain type and Domain home directory.

To specify the Domain type and Domain home directory:

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

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.

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 IP address of the host.

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.

Do not specify any server groups for the Administration Server.

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 two new Managed Servers.

Click the Add button to create a new Managed Server.
Specify wls_server_1 in the Server name column.
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.
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.

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

To continue configuring the domain, click Next.

For steps to create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.

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 High Availability Guide.

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.

In the Clusters pane, select the cluster that you want to assign the servers to; in this case, wls_cluster_1.
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.
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.

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:

Click the Add button to create a new machine.
Specify wls_machine_1 in the Name field.
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.
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. See Optional Scale Out Procedure in High Availability Guide.

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

Virtual Targets

If you have a WebLogic Server Multitenant (MT) environment, you use the Virtual Targets screen to add or delete virtual targets. For this installation (not a WebLogic Server MT environment), you do not enter any values; just select Next.

For details about this screen, see Virtual Targets in Creating WebLogic Domains Using the Configuration Wizard.

Note:

WebLogic Server Multitenant virtual targets are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.

Partitions

The Partitions screen is used to configure partitions for virtual targets in WebLogic Server Multitenant (MT) environments. Select Next without selecting any options.

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

Note:

WebLogic Server Multitenant domain partitions are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.

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.

Configuring the WebLogic Domain With JRF on an Oracle Autonomous Transaction Processing-Shared (ATP-S) Database

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

This section includes the following topics:

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

Navigating Configuration Wizard Screens to Configure the Domain

Follow the sequence of topics in this section to configure the JRF domain with the Configuration Wizard.

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

After you have the desired selections in the configuration wizard, click Next to proceed to the next screen.

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:

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

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 the specific templates to create a JRF domain.

On the Templates screen select the following templates for configuration:

Basic WebLogic Server Domain (selected by default)
Oracle JRF SOAP/JMS Web Services
Oracle WSM Policy Manager
Oracle JRF

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

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.

Specifying the Database Configuration Type

Use the Database Configuration type screen to specify details about the database and database schema.

On the Database Configuration type screen, select the RCU Data option only. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.

After selecting RCU Data, specify the connection credentials using the Connection URL String option only and specify the following details:

Field Description

Field	Description
URL	Enter the connect string in the following format: `jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>` In the connect string, you must pass `TNS_alias` as the database name found in `tnsnames.ora`, and `TNS_ADMIN` property to the location of the wallet files, `ojdbc.properties`, and `tnsnames.ora`. Example: `jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/`
Schema Owner Schema Password	Enter the username and password for connecting to the database's Service Table schema. This is the schema user name and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Schema Passwords in Creating Schemas with the Repository Creation Utility). The default username is `prefix_STB`, where `prefix` is the custom prefix that you defined in the RCU.

URL

Enter the connect string in the following format:

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example:

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

Schema Owner

Schema Password

Enter the username and password for connecting to the database's Service Table schema. This is the schema user name and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Schema Passwords in Creating Schemas with the Repository Creation Utility).

The default username is prefix_STB, where prefix is the custom prefix that you defined in the RCU.

Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

For more information about the schema installed when the RCU is run, see About the Service Table Schema in Creating Schemas with the Repository Creation Utility.

See Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard .

Specifying JDBC Component Schema Information

Use the JDBC Component Schema screen to verify or specify details about the database schemas.

Verify that the values populated on the JDBC Component Schema screen are correct for all schemas.

Specify the connection credentials using the Connection URL String option only, and enter the connect string in the following format:

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database service name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example:

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

See JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.

Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections.

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.

For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard.

Selecting Advanced Configuration

To complete domain configuration, select the required option on the Advanced Configuration screen:

Select Deployment and Services to customize how application deployments and services are targeted to servers and clusters.

Deploying an Application

You can target applications to additional servers and clusters.

Under the DeploymentTargets column, select the target, AdminServer. Then under the Deployments column, select the application, wsm-psm and click the right arrow. wsm-psm is now added to the AdminServer in the DeploymentTargets column.

Deploying a Service

You can target services to additional servers and clusters.

Under the DeploymentTargets column, select the target, AdminServer. Then under the Services column, select the service, WLSSchemaDataSource and click the right arrow. WLSSchemaDataSource is now added to the AdminServer in the DeploymentTargets column.

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.

Click Create to start the domain creation. Next, the Configuration Progress screen shows the progress of the domain creation.

Tip:

See Configuration Summary and Configuration Progress 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 End of Configuration screen shows information about the domain you just configured.

Make a note of the following items because you need them later:

Domain Location
Administration Server URL

You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to 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:

If you restart the server and encounter the following error, then follow the instructions in Doc ID 2691299.1 to solve the issue.

<BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password
      from the boot identity file (boot.properties) is not valid.

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.

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 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. See Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.

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.

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.