5 Configuration Wizard Screens

The Configuration Wizard helps you create and update a WebLogic domain. During the process, it takes you through a sequence of screens depending on your domain requirements and your customization needs.

This chapter includes the following sections:

Configuration Type

The CONFIG_JVM_ARGS environment variable enables you to pass additional arbitrary command line arguments to the java command that initiates the Configuration Wizard. To enable the selection of the profile type, use CONFIG_JVM_ARGS to set the System Property com.oracle.cie.config.showProfile. For example, CONFIG_JVM_ARGS="-Dcom.oracle.cie.config.showProfile=true".

There are two versions of this screen:

Configuration Type - No Profiles

This Configuration Type - No Profiles screen helps you create a domain or update an existing domain.

Option/Field Description

Create a new domain

Select this option if you want to create a new domain. Typically, the new domain is based on the WebLogic Server Basic Domain, which includes an Administration Server and the default security realm myrealm. You may, however, choose to use your own domain template to create the domain; your domain template must contain at least an Administration Server.

Update an existing domain

Select this option if you already have a WebLogic domain, and you want to add resources to that domain.

Note: You can only update domains that were created or reconfigured using the WebLogic Server installation from which you ran the Configuration Wizard. You cannot update domains that were created using other installations of WebLogic Server. If you specify a domain that was not created with the current installation, an error appears when you click Next.

Domain Location

If you select the Create option, enter the full path for the domain or use the Browse button to navigate to the directory in which your domains are located. If you do so, you must enter a unique directory name for the new domain at the end of the path.

Note: Oracle recommends that you create your domain directories outside of the Oracle home directory.

If you selected the Update option, use the Browse button to navigate to the domain that you want to update. If multiple domains exist in this installation, this field contains a drop-down list of the domains, and you can select the domain that you want to update.

Configuration Type - Profiles

In the Configuration Type - Profiles screen, you select whether to create a domain (expanded or compact) or update an existing domain. When you create a domain, the selection you make is permanent. The default is an expanded domain. Compact domains, if defined in a product template, are typically used only for development environments with limited hardware resources. Compact domains may also be used for some Fusion Middleware product domains such as OHS domains.

Note:

If you create a domain that does not include Fusion Middleware components installed with WebLogic Server, always create an expanded domain. Compact domain profiles are defined only for some Fusion Middleware components.

Compact domains are not available for all WebLogic domains that include Fusion Middleware components. If these domain types are defined in the templates that you are using to create the domain, your selection determines the server groups that are available for your Managed Servers and the applications and services that are mapped to those server groups. When you create your domain, some of the templates you select may have expanded and compact profiles defined, while others may not.

For more information about domain profiles and server groups, see Domain Profile Types in Domain Template Reference.
Option/Field Description

Create new expanded domain

Select this option for production environments to create a new expanded domain, which includes clusters and Managed Servers. Typically, the new domain is based on the WebLogic Server Basic Domain, which includes an Administration Server and the default security realm myrealm. You may, however, choose to use your own domain template to create the domain; your domain template must contain at least an Administration Server.

You can add as many clusters and Managed Servers to an expanded domain as needed.

Create new compact domain

Select this option if you want to create a new compact domain. Compact domains contain only a single-server instance (the Administration Server) and cannot be expanded to include clusters and Managed Servers.

Some Fusion Middleware templates define a compact domain topology profile. If used to create a compact domain, some or all the application service groups defined in the template are targeted to the Administration Server.

Update existing domain

Select this option if you already have a WebLogic domain, and you want to add resources to that domain.

Note: You can only update domains that were created or reconfigured using the WebLogic Server installation from which you ran the Configuration Wizard. You cannot update domains that were created using other installations of WebLogic Server. If you specify a domain that was not created with the current installation, an error appears when you click Next.

Domain Location

If you select the Create option, enter the full path for the domain, or use the Browse button to navigate to the directory in which your domains are located. If you do so, you must enter a unique directory name for the new domain at the end of the path.

Note:

Oracle recommends that you create your domain directories outside of the Oracle home directory.

If you select the Update option, use the Browse button to navigate to the domain that you want to update. If multiple domains exist in this installation, this field contains a drop-down list of the domains. You can then select the domain that you want to update.

Configuration

The Configuration screen helps you configure the WebLogic Server sample domains. This screen appears only if you run the Quick Start Configuration Wizard at the end of the WebLogic Server installation process or if you run the wizard from the command line.

Configure the following fields for the sample domains.

Field Description

Name

The login username for the WebLogic Administrator account.

The username must not contain commas, tabs, or any of the following characters:

< > # | & ? ( ) { }

Password

The password for the WebLogic Administrator account. The password must be at least eight characters, and must contain at least one numeric character or at least one of the following characters:

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

The password that is set here is also used for any JDBC data sources that are defined in the templates that you specified when you started the Quick Start Configuration Wizard.

Confirm Password

Enter the same user password. An error appears if the two entries do not match.

Advanced Configuration

Specify the following advanced configuration options for the new domain.

Domain location

This field appears only if you create a single domain.

Enter the full path for the domain (for example, C:\domains\newdomain). You can also use the Browse button to navigate to the directory in which your domains are located (for example, C:\domains). If you do so, you must enter a unique directory name for the new domain at the end of the path.

Domain parent location

This field appears only if you configure the three WebLogic Server sample domains at the end of the WebLogic Server installation.

Enter the full path for the parent domain to use for the WebLogic Server sample domains. For example, if you enter C:\domains, the following domain directories are created: C:\domains\medrec, C:\domains\medrec-spring, and C:\domains\wl_server.

You can also use the Browse button to navigate to the directory to use as the parent directory.

Application location

This field appears only if you create a single domain.

Enter the full path to the directory in which you want to store the applications that are associated with the domain (for example, C:\applications\newdomain). You can also use the Browse button to navigate to the directory in which your applications are located (for example, C:\applications). If you do so, you must enter a unique directory name for the new domain application location at the end of the path.

Application parent location

This field appears only if you configure the three WebLogic Server sample domains at the end of the WebLogic Server installation.

Enter the full path for the parent application directory to use for the domains. For example, if you enter C:\applications, the following application directories are created: C:\applications\medrec, C:\applications\medrec-spring, and C:\applications\wl_server.

Note:

This directory determines the location of the WebLogic server examples, which are installed in application_parent_directory/wl_server/examples/src/examples. The default location is user_projects/applications/wl_server/examples/src/examples.

You can also use the Browse button to navigate to the directory to use as the parent directory.

Administration Server Listen Address

From the drop-down list, select a value for the listen address.

See Specifying the Listen Address.

Administration Server Listen Port

Enter a valid value for the listen port to be used for regular, non-secure requests (through protocols such as HTTP and T3). The default value is 7001 for the Administration Server. The valid listen port range is from 1 to 65535.

See Specifying the Listen Port.

SSL Listen Port

Enter a valid value to be used for secure requests (through 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.

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.

See SSL: An Introduction in Administering Security for Oracle WebLogic Server.

Coherence Listen Port

Specify the listen port to use on the Administration Server for Coherence.

Templates

Use the Templates screen to create or extend a domain that is configured automatically to support selected products. You can also use this screen to create or extend a domain based on an existing domain or application template.

Each template in the displayed list is associated with a single product template (a JAR file), which configures the required domain resources for the product. If the selected template has dependencies on other templates, the dependency templates are automatically selected or included in the domain.

Note:

Positioning the cursor over a template displays a description of the template, its location, and the name of the template JAR file.

See Template Dependencies in Domain Template Reference.

Option Description

Create Domain Using Product Templates

This option is available only when you create a new domain.

By default, the Basic WebLogic Server Domain option is selected and cannot be cleared.

Select the check boxes that correspond to the other products that you want to include in the domain. If you select a product that depends on resources provided by another product or products in the list, those products are also selected automatically. If you select a product that is incompatible with another selected product, an error appears.

When you click Next, if any of the selected templates require resources provided by another product that is not selected, a warning dialog box appears. Return to the Templates screen to select the dependency product before you proceed.

Filter Template

You can filter the displayed list of templates based on the product home (example em), name of the product (example WebLogic), or the version of templates (example 12.2.1.3). The text that you type is case-sensitive.

If you do not specify a filter text, you can see the names of all templates in the available template list.

Include all selected templates

Select this option if you want to include all the selected templates to be part of the filtered list of templates.

Note:

This option is applicable only if you are creating a new domain.

Include all previously applied templates

Select this option if you want to include all the previously applied templates to be part of the filtered list of templates.

Note:

This option is applicable only when you extend a domain. You can view all the previously applied templates.

Update Domain Using Product Templates

This option is available only if you select Update an existing domain on the initial screen.

Select the check boxes for the products to add to your WebLogic domain. The products already included in your domain are indicated by grayed-out check boxes. You cannot deselect these checkboxes.

When you click Next, if any of the selected templates require resources provided by another product that is not selected, a warning dialog box appears. Return to the Templates screen to select the dependency product before you proceed.

Note:

When extending a domain, you are not required to select additional products before you proceed. For example, you do not have to select any products if you only want to add servers or clusters to your domain, or change service targeting.

Create Domain Using Custom Template

Select this option if you want to create a domain by using an existing custom domain template. Enter the full path to the template JAR file in the Template location field, or click Browse to navigate to the directory containing the required template. The template you select must define at least an Administration Server.

When you click Next, if the selected template requires resources provided by another template, a warning dialog box appears. You must create the domain by using the required template first. After doing so, extend the domain by using the template that you initially selected.

Update Domain Using Custom Template

This option is available only if you select Extend an Existing Domain on the initial screen.

Select this option if you want to extend your domain by using an existing custom extension template. Specify the path to the extension template JAR file in the Template location field or click Browse to navigate to the directory containing the extension template.

You can use this option only in the following situations:

  • The template JAR you select is a domain template.

  • The template JAR you select is an extension template that is being added to a domain that already includes all dependency templates required by the extension template.

When you click Next, if the selected template requires resources provided by another template that is not already included in the domain, a configuration error message appears. You must first create or extend the domain by using the required template. After doing so, extend the domain by using the template that you initially selected.

High Availability Options

You can configure service migration and persistence settings for high availability. High availability ensures the availability of a system or a device whenever required.

This screen appears only if the templates that you have selected in the Templates screen are configured for high availability.

Specify the following details to configure high availability:

Field Description

Enable Automatic Service Migration

This option is available only if the domain contains a cluster that belongs to at least one server group for which the asm-configurable parameter is set to ‘True’. This setting applies to all managed servers in the cluster.

If selected, pinned services migrate automatically to a healthy Managed Server for failover.

If you select this option, you must also select the basis for automatic migration:

  • Database Basis: This version of leasing requires a high-availability database to store leasing information. Managed Servers use a table on a valid JDBC System Resource for leasing. If you have a high availability database, such as Oracle RAC, to manage leasing information, configure the database for server migration. See High-availability Database Leasing in Administering Clusters for Oracle WebLogic Server.

  • Consensus Basis: This version of leasing stores the leasing information in-memory within a cluster member. You use Node Manager to control Managed Servers in the cluster.

JTA Transaction Log Persistence

JTA Transaction Log (TLOG) contains information about committed transactions that may not have been completed. You can store TLOGs in the default persistent store or a JDBC TLOG store.

Default Persistence Store: The default store is a file-based store that maintains its data in a group of files in a server instance (in this location: data\store\default).

JDBC TLog Store: You can configure a JDBC TLOG store to persist transaction logs to a database.

JMS Server Persistence

A persistent JMS store is a physical repository for storing persistent message data and durable subscribers. It can be either a disk-based file store or a JDBC-accessible database. A JMS file store can also be used for the paging of messages to disk when memory has been exhausted.

  • JMS File Store: Select this option to configure each eligible JMS server to use JMS File stores as its persistence store.

  • JMS JDBC Store: Select this option to configure each eligible JMS server to use JDBC stores for all its JMS servers.

Application Location

Use the Application Location screen to specify the full path to the directory in which you want to store the applications that are associated with the domain.

You can use the Browse button to navigate to a top-level directory, and then type in the remainder of the application path.

As with domain directories, Oracle recommends that you store your applications in an application directory outside of your Oracle home directory.

Administrator Account

Use the Administrator Account screen to define the default WebLogic Administrator account for the domain. This account is used to boot and connect to the Administration Server of the domain.

Specify the following details to create the account:

Field Description

Name

The login username for the WebLogic Administrator account.

The username must not contain commas, tabs, or any of the following characters:

< > # | & ? ( ) { }

User password

The password for the WebLogic Administrator account. The password must be at least eight characters, and must contain at least one numeric character or at least one of the following characters:

! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

Confirm user password

Enter the same user password. If the two entries do not match, an error message appears.

Domain Mode and JDK

Use the Domain Mode and JDK screen to select whether you want to run WebLogic in production mode or in development mode. You can then specify the JDK for the domain.

Domain Mode

In the Domain mode section of the screen, specify the following:

Option Description

Development

In this mode, the security configuration is relatively relaxed. Username and password are required to deploy applications.

Production

In this mode, the security configuration is relatively stringent, requiring a username and password to deploy applications and to start the Administration Server. Before you put a domain into production, familiarize yourself with procedures for securing a production environment.

See Ensuring the Security of Your Production Environment in Securing a Production Environment for Oracle WebLogic Server.

For more information about the difference between development and production modes, see How Domain Mode Affects the Default Security Configuration in Securing a Production Environment for Oracle WebLogic Server.

JDK

Use the JDK section to select the JDK for the domain. Select only a JDK that is supported on the platform you are using. See Oracle Fusion Middleware Supported System Configurations on Oracle Technology Network.

Option Description

JDK

Lists the JDK that was used when you installed WebLogic Server. The default JDK is Oracle Hotspot SDK version, but you may have installed and used another JDK during installation.

Other JDK

Select this option to use a JDK other than the one that you used when you installed WebLogic Server. Use the Browse button to navigate to the directory where the JDK resides.

If you select the JDK that you used when you installed WebLogic Server, the Configuration Wizard creates server startup scripts to invoke that JDK. If you select a JDK that you did not use when you installed WebLogic Server, the Configuration Wizard does not configure the startup scripts. You must change the startup scripts manually.

For more information about startup scripts, see Setting Java Parameters for Starting WebLogic Server in Tuning Performance of Oracle WebLogic Server.

Database Configuration Type

The Database Configuration Type screen and the subsequent schema configuration screens appear only for WebLogic Server installations that include the Fusion Middleware infrastructure components.

You can use this screen to specify the information to connect to the database to retrieve schema information that is used to populate the schema fields on subsequent component schema screens (JDBC Component Schema, GridLink Oracle RAC Component Schema, or Oracle RAC Multi Data Source Component Schema). You can also skip this step and manually configure each component schema on the component schema screen.

Select one of the following options.

Field Description

RCU Data

Select this option if you want to connect to the database to retrieve schema information for all schemas that are defined in the templates that you selected on the Templates screen. If you select this option, the fields on this screen are activated. Fill in each field, by using the connection information that you specified for the Service Table component in the Repository Creation Utility (RCU). When done, click Get RCU Configuration to retrieve the schema information.

For information about Service Tables, see Understanding Service Tables in Administering Oracle Fusion Middleware.

After you successfully retrieve the schema information, click Next to continue.

Note: The only JDBC connections that RCU supports are the Oracle service type JDBC connections.

Manual Configuration

If you select this option, you must manually configure the settings for each schema. Some of the fields in the schema table on the component schema screen are populated with the default Java database values, for example, Host Name is set to dbhost.example for all schemas.

After you select this option, click Next.

Complete the following fields for the RCU Data option, and then click Get RCU Configuration.

See Database Connection Details in Creating Schemas with the Repository Creation Utility.

Field Description

Vendor

Select the database vendor.

Driver

Select the JDBC driver that is configured for the database. The list includes common JDBC drivers for the selected database vendor.

DBMS/Service

Enter the database DBMS name or, if you selected a service type driver, the service name.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number to be used to connect to the server that hosts the database.

Schema Owner

Schema Password

Enter the username and password to connect to the database's service table schema. Use the schema username and password that was specified for the Service Table component on the Schema Passwords screen of the Repository Creation Utility (RCU). The default username is prefix_STB, where prefix is the prefix that you defined in RCU. The schema you specify must be unique for the domain (not being used by any other domains).

See Schema Passwords in Creating Schemas with the Repository Creation Utility.

Note:

When you click Get RCU Configuration, the schema passwords that were specified when you created the schemas via RCU are retrieved. If schema passwords were changed from the original passwords that were set via RCU, you must manually enter the new passwords in the Schema Password field or column on the following screens:
  • JDBC Component Schema

  • GridLink Oracle RAC Component Schema

  • Oracle RAC Multi Data Source Component Schema

JDBC Component Schema

For some Fusion Middleware components, the JDBC data sources may be defined as part of the component's database schema. These data sources are loaded during installation of the component by using the Repository Creation Utility (RCU).

When you create a WebLogic domain for such components by using the Configuration Wizard, you can configure the JDBC component schema settings, such as database driver, schema owner, password, and so on.

  • If you select the RCU Data option on the Database Configuration Type screen, the schema table is already populated appropriately and you can click Next to continue.

    If, however, schema passwords were changed from the original passwords that were set using RCU, you must manually enter the new passwords in the Schema Password field or column.

  • If you have selected the Configure Using Embedded Database option, any schema components that have a corresponding dev-database entry in database.xml do not appear on this screen.

  • If you selected the Manual Configuration option on the Database Configuration Type screen, you must configure the schemas listed in this table manually before you continue.

The JDBC component schemas associated with the products for which you are creating the domain are listed in the lower half of the screen.

Select the schemas for which you want to specify data source settings by selecting the check box next to each schema name.

Note:

When you select multiple component schemas, the text Varies among component schemas might appear in certain fields, indicating that the current values of those fields are different across the selected component schemas. If you change the values in such fields, the new values are applied uniformly across the selected component schemas.

The default values of component schema parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

Field Description

Vendor

Select the database vendor.

Driver

Select the JDBC driver to connect to the database. The list includes common JDBC drivers for the selected database vendor.

DBMS/Service

Enter a database DBMS name, or service name if you selected a service type driver.

Host Name

Enter the name of the server hosting the database.

Port

Enter the port number to be used to connect to the server that hosts the database.

Schema Owner

Enter the username for connecting to the database.

Schema Password

Enter the password for this username.

The values that you specify appear in the appropriate columns in the schema list, for the selected schemas.

To convert one or more schemas to GridLink RAC schemas, select the check boxes for those schemas, and select the Convert to GridLink option. Click Next when done. When you click Next, the GridLink Oracle RAC Component Schema screen appears.

See Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server

To convert one or more of the schemas to Oracle RAC multi-data source schemas, select the check boxes next to the name of those schemas, and select the Convert to RAC multi data source option. Click Next when done. When you click Next, the Oracle RAC Multi Data Source Component Schema screen appears.

See Using WebLogic Server with Oracle RAC in Administering JDBC Data Sources for Oracle WebLogic Server.

GridLink Oracle RAC Component Schema

Use the GridLink Oracle RAC Component Schema screen to configure the component schemas that are included in your WebLogic domain as GridLink RAC data sources. A GridLink data source is a single data source that represents a service that responds to Fast Application Notification (FAN) events.

For more information about GridLink RAC data sources, see Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server.

The component schemas that you opted to configure as GridLink RAC data sources in the JDBC Component Schema screen of the wizard are listed in the lower half of the screen.

  • If you selected the RCU Data option on the Database Configuration Type screen, the schema table has already been populated appropriately and you can click Next to continue.

    If, however, schema passwords were changed from the original passwords that were set using RCU, you must manually enter the new passwords in the Schema Password field or column.

  • If you selected the Manual Configuration option on the Database Configuration Type screen, you must configure the schemas listed in this table manually before you continue.

In the schema list in the lower half of the screen, select the schemas to configure as GridLink RAC data sources by selecting the check box next to each schema name.

Note:

When you select multiple data source schemas, the text Varies among component schemas might appear in certain fields, indicating that the current values of those fields are different across the selected schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected schemas.

Field Description

Driver

Select the appropriate driver. Some or all the following drivers are listed:

  • Oracle Driver (Thin) for GridLink Connections.

    This is the GridLink Type 4 non-XA driver.

  • Oracle Driver (Thin XA) for GridLink Connections.

    This is the GridLink Type 4 XA driver.

Service Name

Enter a database Oracle RAC service name.

Schema Owner

Enter the username for connecting to the database.

Schema Password

Enter the password for this username.

Enable FAN

When selected, the data source registers for and processes FAN notifications.

Enable SSL

When selected, SSL is enabled, and you must specify a wallet file, wallet password, and at least one Oracle Notification Service (ONS) host/port.

Wallet File

If SSL is enabled, specify the full path to the wallet file that contains the credentials for ONS/SSL. A wallet file is an Oracle credential file that stores keys and certificates.

Wallet Password

Specify the password for the wallet file. The password is encrypted in the module configuration file.

Service Listener

Enter the name of the GridLink database Service Listener. You must configure the Service Listener for at least one database instance.

Port

This port is the listen port for the database service listener. It defaults to 1521 and is not changed.

Protocol

Click in this field and select the protocol to use for communication between WebLogic Server and the database service listener.

ONS Host

Specify the Oracle Notification Service (ONS) host name. If SSL is enabled, you must specify at least one ONS host and port.

Port

Specify the listen port to use on the ONS host.

The values that you specify appear in the appropriate columns in the schema list, for the selected schemas.

To add another row to the Service Listener table, click anywhere in the table, and then click Add.

To add another row to the ONS Host table, click anywhere in the table, and then click Add.

To delete a row from the Service Listener table, click anywhere in the row, and then click Delete.

To delete a row from the ONS Host table, click anywhere in the row, and then click Delete.

Oracle RAC Multi Data Source Component Schema

Use the Oracle RAC Multi Data Source Component Schema screen to configure the component schemas that are included in the WebLogic domain as Oracle RAC multi-data sources.

See Using WebLogic Server with Oracle RAC in Administering JDBC Data Sources for Oracle WebLogic Server.

The component schemas that you opted to configure as Oracle RAC multi-data sources in the JDBC Component Schema screen of the wizard are listed in the lower half of the screen.

  • If you selected the RCU Data option on the Database Configuration Type screen, the schema table has already been populated appropriately and you can click Next to continue.

    If, however, schema passwords were changed from the original passwords that were set using RCU, you must manually enter the new passwords in the Schema Password field or column.

  • If you selected the Manual Configuration option on the Database Configuration Type screen, you must configure the schemas listed in this table manually before continuing.

In the schema list in the lower half of the screen, select the schemas to configure as Oracle RAC multi-data sources by selecting the check box next to each schema name.

Note:

When you select multiple data source schemas, the text Varies among component schemas might appear in certain fields, indicating that the current values of those fields are different across the selected schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected schemas.

Field Description

Driver

Select the JDBC driver to connect to the database.

Service Name

Enter a database Oracle RAC service name.

Username

Enter the username for connecting to the database.

Password

Enter the password for the specified username.

Host Name

Enter the name of the server hosting the Oracle RAC database instances.

Instance Name

Enter the name of each Oracle database instance.

Port

Enter the port number to connect to the server that hosts the database.

Note:

Specify the host name, instance name, and port number of at least one database instance.

To add another database instance for the currently selected schemas, click Add Host.

To delete a database instance, click anywhere in that row in the Host Name table, and then click Delete.

The values that you specify for the schema appear in the appropriate columns in the schema list, for the selected schemas.

JDBC Component Schema Test

Use the JDBC Component Schema Test screen to test all the JDBC component schema configurations that you specified for the data sources in the JDBC Component Schema screen.

Note the following before you begin to test the configurations for the data sources:

  • If the JDBC driver JAR file for a data source is not in the classpath, you cannot select the data source for testing.

  • If you are updating a domain, all data sources that exist in the original domain are not selected by default. Only new data sources are selected and tested by default.

Select the check boxes next to the names of the schemas to test, and then click Test Selected Connections.

The wizard tests the configuration for each schema by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the schema.

The result of the test is indicated in the Status column. Details appear in the Connection Result Log section.

JDBC Data Sources

A JDBC data source contains a pool of database connections that are created when the data source instance is created — when it is deployed or targeted, or at server startup.

Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.

Use the JDBC Data Sources screen to configure the JDBC data sources defined in your domain source.

The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen.

Select one or more data sources for which you want to specify settings by selecting the check box next to each data source name. The values that you specify appear in the appropriate columns in the data source list, for the selected data source.

Note:

When you select multiple data sources, the text Varies among component schemas might appear in certain fields, indicating that the current values of those fields are different across the selected data sources. If you change the values in such fields, the new values are applied uniformly across the selected data sources.

The default values of data source parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

Field Description

Vendor

Select the database vendor.

Driver

Select the JDBC driver to connect to the database. The list includes common JDBC drivers for the selected database vendor.

DBMS/Service

Enter a DBMS SID or service name. The value that you enter depends on the driver that you selected.

If the name of the Oracle driver that you selected contains the words for Instance connections, you must enter the SID.

If the name of the Oracle driver contains the words for Service connections, you must enter the service name.

For information about configuring a DataDirect driver, see the DataDirect documentation.

Host Name

Enter the name of the server hosting the database.

Port Name

Enter the port number to be used to connect to the server.

Username

Enter the username for connecting to the database.

Password

Enter the password for the specified username.

To convert one or more data sources to GridLink RAC data sources, select the check boxes for the data sources, and select the Convert to GridLink option. Click Next when done. When you click Next, the GridLink Oracle RAC Data Sources screen appears.

See Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server

To convert one or more of the data sources to Oracle RAC multi-data sources, select the check box next to the name of the required data source, and select the Convert to RAC multi data source option. When you click Next, the Oracle RAC Multi Data Sources screen appears.

See Using WebLogic Server with Oracle RAC in Administering JDBC Data Sources for Oracle WebLogic Server.

GridLink Oracle RAC Data Sources

A GridLink data source is a single data source that represents a service that responds to the Fast Application Notification (FAN) events. Use this screen to configure the data sources that are included in the WebLogic domain, as GridLink Oracle RAC data sources.

For more information about GridLink data sources, see Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server

The data sources that you opted to configure as GridLink RAC data sources in the JDBC Data Sources screen of the wizard are listed in the lower half of the screen.

In the data source list in the lower half of the screen, select the data sources to configure as GridLink RAC data sources by selecting the check box next to each data source name.

Note:

When you select multiple data sources, the text Varies among data sources might appear in certain fields, indicating that the current values of those fields are different across the selected data sources. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected data sources.

Field Description

Driver

Some or all the following drivers are listed:

Check this list periodically, may be new ones

  • Oracle Driver (Thin) for GridLink Connections.

    This is the GridLink Type 4 non-XA driver.

  • Oracle Driver (Thin XA) for GridLink Connections.

    This is the GridLink Type 4 XA driver.

Service Name

Enter a database Oracle RAC service name.

Username

Enter the username for connecting to the database.

Password

Enter the password for the specified username.

Enable FAN

When selected, the data source registers for and processes FAN notifications.

Enable SSL

When selected, SSL is enabled, and you must specify a wallet file, wallet password, and at least one Oracle Notification Service (ONS) host/port.

Wallet File

If SSL is enabled, specify the full path to the wallet file that contains the credentials for ONS/SSL. A wallet file is an Oracle credential file that stores keys and certificates.

Wallet Password

Specify the password for the wallet file. The password is encrypted in the module configuration file.

Service Listener

Enter the name of the GridLink database Service Listener. You must configure the Service Listener for at least one database instance.

Port

This is the listen port for the database service listener. It defaults to 1521 and is usually not changed.

Protocol

Click in this field and select the protocol to use for communication between WebLogic Server and the database service listener.

ONS Host

Specify the Oracle Notification Service (ONS) host name. If SSL is enabled, you must specify at least one ONS host and port.

Port

Specify the listen port to use on the ONS host.

The values that you specify appear in the appropriate columns in the data source list, for the selected schemas.

To add another row to the Service Listener table, click anywhere in the table, and then click Add.

To add another row to the ONS Host table, click anywhere in the table, and then click Add.

To delete a row from the Service Listener table, click anywhere in the row, and then click Delete.

To delete a row from the ONS Host table, click anywhere in the row, and then click Delete.

Oracle RAC Multi Data Sources

Use the Oracle RAC Multi Data Sources screen to configure the data sources that are included in the domain as Oracle RAC data sources.

The data sources that you opted to configure as Oracle RAC data sources on the JDBC Data Sources screen are listed in the lower half of the screen.

Select one or more data sources for which you want to specify settings by selecting the check box next to each data source name.

For information about Oracle RAC data sources, see Using WebLogic Server with Oracle RAC in Administering JDBC Data Sources for Oracle WebLogic Server.

Note:

When you select multiple data sources, the text Varies among data sources might appear in certain fields, indicating that the current values of those fields are different across the selected data sources. If you change the values in such fields, the new values are applied uniformly across the selected data sources.

Field/Column Description

Driver

Select the JDBC driver to connect to the database.

Service Name

Enter an Oracle RAC database service name.

Username

Enter the username for connecting to the database.

Password

Enter the password for the specified user account.

Host Name

Enter the name of the server hosting the Oracle RAC database instances.

Instance Name

Enter the name of each Oracle database instance.

Port

Enter the port numbers to be used to connect to the server that hosts the database.

To add a new database instance, click Add, and then specify the host name, instance name, and port number.

JDBC Data Sources Test

Use the JDBC Data Sources Test screen to test the data source connections that you configured in the JDBC Data Sources and the Oracle RAC Multi Data Sources screens.

Note:

To test the database connections, the database to which you are connecting must be running. If you do not want to test the connections, do not select any data sources. Click Next to continue.

Select the check box for each data source you want to test, and then click Test Connections.

The wizard tests the configuration for each selected data source by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the data source.

The result of the test is indicated in the Status column. Details appear in the Connection Result Log section.

Database Scripts

A domain template may contain a set of SQL files organized by database type. If the domain template contains SQL files, use the Database Scripts screen to run these files while creating a WebLogic domain.

The database content for each of the data sources defined in a WebLogic domain is set up by using preexisting SQL or database loading files.

Note:

No databases are defined in the WebLogic Server Base Domain (wls.jar) template. If you selected only the WebLogic Server Base Domain template as the basis for the WebLogic domain, the Configure JDBC Data Sources and the Run Database Scripts screens are not displayed.

  1. In the JDBC Data Sources section, select the data source for which you want to run the scripts. The scripts that can be executed appear in the SQL Files section.

  2. Select the database version from the DB Version drop-down list.

  3. Click Run Scripts.

    All the scripts that appear in the SQL Files section for the selected data source are executed, and the results appear in the Results section. To capture test output in a log file, select the Enable Logging check box and specify the full path for the log file in the Log File field.

  4. Repeat steps 1 through 3 for each data source for which you want to execute SQL scripts.

  5. Click Next once you have executed all scripts.

Credentials

You can use this screen to provide credentials for each key in the WebLogic domain. If you have included the Oracle RAS Session Service template in the domain, the default key and the RAS store, oracle.rdbms.ras, are listed.

For more information on credentials, see Understanding Identities, Policies, Credentials, Keys, Certificates, and Auditing in Application Security Guide.

Column Description

Key Name

This column displays the name of each key in the domain.

Username

Password

On each row, enter the username and password to use for each key.

Store Name

This column displays the credential store that is associated with each key.

Keystore

Use the Keystore screen to specify the path to the trusted certificate for each keystore and the path to each keystore's private key, its password, and the path to the Identity Certificate of the private key.

When you click in the Trusted Certificate, Private Key, or Identity Certificate fields, a browse icon appears to the right of the field. Click this icon to browse to the appropriate file.

Option/Field Description

Store Key Name

From this drop-down list, select the store or key that you want to configure.

Trusted Certificate table

The Trusted Certificate table contains the following fields:
  • Alias: A read-only field that displays the alias for the trusted certificate as defined in the product template.

  • Trusted Certificate: Enter the full path and file name for the trusted certificate to use for the selected store or key, or click the icon on the far right of the row to navigate to and select the trusted certificate file.

Private Key table

The Private Key table contains the following fields:
  • Alias: A read-only field that displays the alias for the private key as defined in the product template.

  • Private Key: Enter the full path and file name for the private key file to use for the selected store or key, or click the icon to the right of the field to navigate to and select the private key file.

  • Password: Enter the password to use for the private key.

  • Identity Certificate: Enter the full path and file name for the identity certificate to associate with the private key, or click the icon to the right of the field to navigate to and select the identity certificate file.

Java Keystore Info

Use the Java Keystore Info screen to import key pairs and certificates from an existing Java Keystore (.jks) file into Oracle Platform Security Services (for WebLogic). A Java Keystore contains authorization certificates and key pairs that are used for authentication and encryption purposes.

For more information about securing applications with Oracle Platform Security Services (OPSS), see Introduction to Oracle Platform Security Services in Securing Applications with Oracle Platform Security Services.

Option/Field Description

Target Keystore Name

From the drop-down list, select the name of the target keystore (available in the OPSS Keystore Service) that you want to configure.

JKS File Location

Specify the location of the .jks file from which you want to import the key pairs and certificates into the target keystore.

Keystore Password

Specify the password that is required to import the .jks file. This is the password that is defined at the time of creating the .jks file. An error appears if the password does not match.

Permission Protected

The target keystore that you select can be either password protected or permission protected. If you enable permission protected, the access to the target keystore is determined by Java code-based policy grants. In this case, the password you define for the target keystore is ignored.

Target Keystore Password

Specify the password for the target keystore. The target keystore is created with this password.

Alias Name

Each key pair and certificate that is stored in the target keystore is referred by a unique alias. If you want to include additional keys and certificates from the .jks file, specify the appropriate alias name. An error appears if the alias name is not available in the keystore.

Password

Each alias that is stored in the target keystore has a unique password. Specify the appropriate password. An error appears if the password is not valid for the alias name that you select.

Note:

A password is required only if you import key pairs; it is optional for certificates.

Advanced Configuration

Use the Advanced Configuration screen to perform advanced configurations for the categories you select from the available list. You can select all the categories, if necessary.

If you do not select any items on this screen, the Configuration Summary screen appears.

Note:

The categories that are listed on this screen depend on the resources defined in the templates that you have selected for the domain.

The Administration Server option is not available when you extend a domain.

Option Description

Administration Server

Select this option to modify Administration Server settings such as server name, listen address, listen port, and SSL settings.

See Administration Server.

Node Manager

Select this option to change the Node Manager type, Node Manager username and password, and Node Manager location.

See Node Manager.

Topology

Select this option to perform the following tasks:
  • Add Managed Servers, clusters, or machines to the domain

  • Delete an existing Managed Server, cluster, or machine

  • Add Managed Servers to an existing cluster

  • Modify the settings for an existing Managed Server, cluster, or machine

  • Configure the default Coherence cluster

  • Configure Virtual Targets and Partitions for Oracle WebLogic Server Multitenant (MT)

See Managed Servers, through Assign Servers to Machines.

Domain Frontend Host Capture

Select this option to configure the domain-wide frontend host HTTP and HTTPS URLs, and whether HTTP or HTTPS is the default.

See Domain Frontend Host.

System Components

Select this option to configure and target system components, such as Oracle HTTP Server (OHS) or Oracle Data Integration (ODI).

See System Components, through Assign System Components to Machines.

Deployments and Services

Select this option to customize how application deployments and services are targeted to servers and clusters.

See Deployments Targeting, and Services Targeting.

File Store

Select this option to change the settings for your JMS file stores. You can change the name, directory, and synchronous write policy for each file store.

See File Stores.

Note:

WebLogic Server Multitenant domain partitions, resource groups, and virtual targets are deprecated in WebLogic Server 12.2.1.4 and will be removed in the next release.

Administration Server

The Administration Server is the central point from which you manage your domain. You can use this screen to configure or change the Administration Server settings.

You can access the Administration Server by using the URL protocol://listen-address:listen-port. This is the network channel for the Administration Server. The network channel for each Administration Server must be unique. The protocol can be any of the following: t3, t3s, http, https.

You can configure or change the following Administration Server settings:

Field/Option Description

Server Name

The default name is AdminServer. Valid server names are a string of characters (alphabetic and numeric).

Each server instance in a production 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. The name of the Administration Server must be unique among all component names within the WebLogic domain.

This value is specified only for identification purposes. 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. 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.

See Specifying the Listen Address.

Listen port

Enter a valid value for the listen port to be used for regular, non-secure requests (through protocols such as HTTP and T3). The default value is 7001 for the Administration Server. The valid listen port range is from 1 to 65535.

See Specifying the Listen Port.

Enable SSL

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 you selected the SSL enabled check box.

Enter a valid value to be used for secure requests (through 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.

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.

See SSL: An Introduction in Administering Security for Oracle WebLogic Server.

Server Groups

This drop-down list appears only if at least one selected template defines a user-expandable server group.

You can assign a user-expandable server group to the Administration Server, causing all application service groups that are defined for that server group to be assigned to the Administration Server.

See config-groups.xml and startup-plan.xml in Domain Template Reference.

Specifying the Listen Address

This section provides guidelines for specifying the listen address for the Administration Server. These guidelines also apply to all Managed Servers.

If you select localhost as the listen address for a server instance, remote 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.

The following table describes the behavior of each listen address type.

Type Description

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

When using an IP address or DNS name, note the following:

  • 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 a client request then specifies a DNS name, WebLogic Server attempts to resolve the DNS name. If it cannot access DNS name mapping, the request fails.

localhost

When using localhost, note the following:

  • Processes must specify localhost to connect to the server instance.

  • Only processes that reside on the machine that hosts the server instance (local processes) can connect to the server instance.

Specifying the Listen Port

Note the following guidelines when specifying the listen port for the Administration Server. These guidelines also apply to Managed Servers.

  • Although you can specify any valid port number, if you specify port 80, you can omit the port number from the HTTP request used to access resources over HTTP. For example, if you define port 80 as the listen port, you can use the URL http://hostname/myfile.html instead of http://hostname:portnumber/myfile.html.

  • On some operating systems, port 80 can be accessed only by processes that run under a privileged user or group ID. In this case, you can assign the server instance to a UNIX machine on which a post-bind UID or GID is defined.

Node Manager

Use the Node Manager screen to select the Node Manager configurations that are applicable for the domain. You can also skip this step to create the Node Manager manually at a later point.

When you start the Node Manager for a domain, it looks for the nodemanager.properties file in the Node Manager home directory.

Option/Field Description

Node Manager Type

Select one of the following Node Manager types.

Per Domain Default Location

If you select this option, the Node Manager home is predefined within the domain as <domain_name>/nodemanager and you cannot edit the Node Manager home. The Node Manager for each domain can have a different configuration, as determined by the files in this directory.

Per Domain Custom Location

Select this option if you want the Node Manager configuration files to be created in a specific location for this domain. Specify the directory in the Node Manager Home field, or click Browse to navigate to the location. The specified directory must be empty. The nodemanager.properties and nodemanager.domains files are created in this directory.

Manual Node Manager Setup

If you select this option, creation of the Node Manager configuration for the domain is skipped, and you must manually create and update the Node Manager configuration for the domain.

You can also select this option if you do not want to use Node Manager in the domain.

Note:

When you create standalone domains for OHS and ODI, do not select this option. A per domain Node Manager configuration is required for system component standalone domains.

For more information about Node Manager configuration, see Node Manager Overview in Administering Node Manager for Oracle WebLogic Server.

Username

Password

Confirm Password

The username and password that is used to start the specified Node Manager.

Node Manager Home

If you selected the Per Domain Custom Location option, click Browse and navigate to the directory location of the Node Manager that you want to use.

Managed Servers

Use the Managed Servers screen to add, delete, or clone Managed Servers, and assign a user-expandable server group (if available) to a Managed Server. You can also change the settings for an existing Managed Server.

You can create Managed Servers on remote machines by using the pack and unpack commands.

See Creating and Starting a Managed Server on a Remote Machine in Creating Templates and Domains Using the Pack and Unpack Commands.

Column Description

Server Name

Valid server names are a string of characters (alphabetic and numeric). The name must be unique in the domain.

For more information about server naming conventions, see Server Name Restrictions in Understanding Domain Configuration for Oracle WebLogic Server.

Listen Address

From the drop-down list, select a value for the listen address. See Specifying the Listen Address.

Listen port

Enter a valid value for the listen port to be used for regular, non-secure requests (through protocols such as HTTP and T3). The default value is the next available listen port. The valid listen port range is from 1 to 65535.

See Specifying the Listen Port.

Enable SSL

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 you selected the SSL enabled check box for the server.

Enter a valid value to be used for secure requests (through protocols such as HTTPS and T3S). The valid listen port range is from 1 to 65535.

Server Groups

If any of the templates that you selected to create or update your domain contain a user-expandable server group definition, the Server Groups column is displayed. For each Managed Server, select the check box for each server group that you want to assign to the server. Only server groups that are defined as user-selectable appear in the list. Typically, you can accept the defaults for Fusion Middleware product servers.

Note:

If you clone a Managed Server, the server group assignments are identical to the original server. Cloning is recommended for creating additional Fusion Middleware product servers.

The selected server group determines the applications and services that are mapped to a given Managed Server. For example, if you select the WSMPM_MAN_SVR group for a server, all applications and services that are mapped to that server group in the config-groups.xml file for the domain are automatically targeted to the server.

See config-groups.xml and startup-plan.xml and the template sections for the templates that you included in the domain in Domain Template Reference.

To add a server, click Add and configure the settings for the new server. The default name for a new server is new_ManagedServer_n, where n starts at 1 and increments for each new server you add.

To clone a server, click in the row for the server you want to clone, and then click Clone. The default name for the new clone is original_server_name_clonen, where n starts at 1 and increments for each new server that you clone from that server. When you create a Managed Server that is a clone of an existing Managed Server, all applications and libraries that are targeted to the source server are also deployed to the clone. The cloned server is also assigned to all server groups to which the source server is assigned (if any). In addition, any of the following services that are targeted to the source server are automatically targeted to the clone:

  • connectionFactory

  • queueConnectionFactory

  • topicConnection

  • Queue

  • Topic

  • activationSpec

  • Data source

  • URLProvider

  • workManager

  • busMember

  • customService

  • resourceAdapter

To delete a server, select the server and click Delete. You can delete only one server at a time.

Clusters

A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. Use this screen to add or delete clusters, or to change the settings for an existing cluster.

By creating clusters, you can group Managed Servers such that they operate as a single unit for hosting applications and resources.

Column Description

Cluster Name

Specify a valid name. The name of the cluster must be unique among all component names within the WebLogic domain.

Cluster Address

Specify the addresses for identifying 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

Frontend Host

Frontend HTTP Port

Frontend HTTPS Port

Enter the IP address, plain port (HTTP), and secure port (HTTPS) of the frontend host for the cluster, which can be one of the following:
  • a hardware load balancer

  • an Oracle HTTP Server (OHS) instance

  • a frontend host that has already been defined in the WebLogic Server configuration

You can leave these fields empty, in which case the domain-wide frontend host values that are specified on the Domain Frontend Host screen are used for the cluster. If you enter these values for the cluster, they override the values, if any, that are specified on this screen. See Domain Frontend Host

To delete a cluster, select the server and click Delete. When you delete a cluster, you do not delete the servers assigned to it; the servers are merely removed from the cluster and can then be added to another cluster. You can delete only one cluster at a time.

To add a cluster, click Add and configure the settings for the new server. The default name for a new cluster is new_Cluster_n, where n starts at 1 and increments for each new cluster you add. To change the default, type the desired name in the Name column.

For more information about clusters, see Setting Up WebLogic Clusters in Administering Clusters for Oracle WebLogic Server.

Server Templates

Use the Server Templates screen to define one or more server templates for the domain. A server template contains common, non-default settings and attributes that you can apply to a set of server instances, which then inherit the template configuration.

See Server Templates in Understanding Domain Configuration for Oracle WebLogic Server.

Server templates can be used to create dynamic clusters. Dynamic clusters consist of server instances that can be dynamically scaled up to meet the resource needs of your application. See Dynamic Clusters in Administering Clusters for Oracle WebLogic Server.

Column Description

Name

The list of server templates will include all server templates that are defined in the config-groups.xml file and the server templates that exist in the domain. You can modify or define new server templates, if required.

Listen Port

The default TCP port that the server uses to listen for regular (non-SSL) incoming connections.

Administrators must have the right privileges before binding to a port, else this operation fails and renders the console unreachable.

If this port is disabled, the SSL port must be enabled. Additional ports can be configured by using network channels. The cluster (multicast) port is configured separately.

SSL Listen Port

The port that the server uses to listen for secure (SSL) incoming connections.

Enable SSL

This option enables you to configure SSL for servers defined by the template. If the box is not checked, SSL is not configured and the SSL Listen Port is ignored.

Dynamic Servers

The Dynamic Servers screen lists each of the clusters that you have created in the current configuration session. You can designate one or more of these clusters to be a dynamic cluster.

To designate a dynamic cluster, select a server template for the cluster, or select one or more dynamic server groups.

When you indicate that a cluster is a dynamic cluster, you can then define specific properties for each cluster that control how WebLogic Server creates the dynamic servers.

See Dynamic Clusters in Administering Clusters for Oracle WebLogic Server.

Column Description

Cluster Name

By default, the names of the clusters that you created in the Clusters screen are listed here. You can change the name, if required.

Server Name Prefix

The server name prefix to use when creating the dynamic server names. By default, the prefix of the dynamic server group that you associate with the cluster in the Clusters screen is used.

Note:

Applicable only if you designate the cluster as a dynamic cluster.

Server Template

To define a cluster as a dynamic cluster, associate the cluster with a server template. The drop-down displays all server templates in the domain. The cluster element for the selected server template will be set to match the cluster to which it is assigned.

If you select Unspecified , you cannot select a dynamic server group for the cluster. The cluster will then be defined as a static cluster.

Maximum Dynamic Server Count

The maximum number of server instances allowed to be created.

This value can be set to the number of servers expected to be in the cluster. The specified number of servers are dynamically added to the configuration at runtime.

Note:

Applicable only if you designate the cluster as a dynamic cluster.

Machine Name Match Expression

The machine name expression to use when you select machine names.

Note:

Applicable only if you designate the cluster as a dynamic cluster.

Calculated Machine Names

Specifies whether machine names are calculated.

Note:

Applicable only if you designate the cluster as a dynamic cluster.

Calculated Listen Ports

Specifies whether listen ports for the server are calculated.

Note:

Applicable only if you designate the cluster as a dynamic cluster.

Dynamic Server Groups

If you have associated the cluster with a server template, you can also select a dynamic server group for the cluster. The drop-down list includes all the dynamic server groups defined in the domain depending on the template that you have associated in the Templates screen. You can associate a cluster with one or more dynamic server groups.

For more information on dynamic clusters, see Using Dynamic Clusters in the High Availability Guide.

For more information about using calculated server names, listen ports, or machine names, see Calculating Server-Specific Attributes in Administering Clusters for Oracle WebLogic Server.

Assign Servers to Clusters

Use the Assign Servers to Clusters screen to assign Managed Servers to clusters. Only Managed Servers appear in the Server list box. The Administration Server is not listed because it cannot be assigned to a cluster.

To assign one or more servers to a cluster:

  1. In the Clusters list box, select the cluster to which you want to assign a Managed Server.
  2. Assign Managed Servers to the selected cluster in one of the following ways:
    • Double-click the name of the Managed Server in the Servers list box.

    • 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 Servers list box and added below the name of the target cluster in the Clusters list box.

  3. Repeat steps 1 and 2 for each Managed Server to assign to a cluster.
  4. Review the cluster assignments.

    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 Clusters list box.

    • Select the Managed Server and click the left arrow.

    The name of the Managed Server is removed from the Clusters list box and restored to the Servers list box.

HTTP Proxy Applications

An HTTP proxy application acts as an intermediary for HTTP requests. Use the HTTP Proxy Applications screen to create an HTTP proxy application for each cluster, and specify the Managed Server on which the proxy application must be deployed.

This screen appears only if the following statements are true:

  • At least one Managed Server is assigned to a cluster.

  • At least one Managed Server is not assigned to any cluster.

Column Description

Cluster Name

This column lists each cluster in the domain.

Create HTTP Proxy

Select this check box for each cluster on which you want to deploy the HTTP proxy application.

Proxy Server

This drop-down list contains all Managed Servers that are not assigned to a cluster. Select the Managed Server on which to deploy the proxy application.

For example, a proxy application named OracleProxy4_clustername_servername is created and deployed on the Managed Server.

Coherence Clusters

The Coherence Clusters screen appears only if you have included Coherence in the WebLogic Server installation. It lists the Coherence clusters that are automatically added to the domain.

Specify the following details for the Coherence cluster:

Column Description

Name

Accept the default cluster name or type a new name for the Coherence cluster.

When updating a domain, if you have added additional Coherence clusters to the domain by using WLST or the WebLogic Server Administration Console, they are also listed here.

Unicast Listen Port

Enter the port number to use as the Coherence cluster unicast listen port.

For more information on the Coherence cluster unicast listen port, see Configure Coherence Cluster Member Unicast Settings in Administering Clusters for Oracle WebLogic Server.

When including a Coherence cluster in a domain, note the following:

  • All Managed Servers and clusters that you configure in the domain during future Configuration Wizard sessions are automatically added to the Coherence cluster.

  • Servers and clusters that exist in the domain before you add a Coherence cluster to the domain are not automatically assigned to the Coherence cluster. If desired, you can manually assign them to the Coherence cluster by using a WLST script or the WebLogic Server Administration Console.

  • When you create a domain by using the Configuration Wizard, if the domain contains only an Administration Server and no Managed Servers, the Administration Server is automatically assigned to the Coherence cluster. If, however, at least one Managed Server is added to the domain during domain creation, the Administration Server is not assigned to the Coherence cluster.

  • If there are multiple Coherence clusters in the domain (for example, you added a second Coherence cluster by using WLST or the WebLogic Server Administration Console), any servers or clusters that you subsequently add to the domain by using the Configuration Wizard are automatically assigned to the first Coherence cluster that is listed on the Coherence Clusters screen.

Machines

In a WebLogic domain, the machine definitions identify physical units of hardware and are associated with the WebLogic Server instances or system components (such as OHS servers) that they host. Use the Machines screen to add or delete machines, or to modify the settings for an existing machine.

Each machine has the following configuration settings.

Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX).

Column Description

Name

Enter a valid machine name. The machine name is used to identify the machine within the WebLogic domain; it does not have to match the network name for the machine. The name must be unique among all component names within the domain.

Enable Post Bind GID

(UNIX machines only) 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. By default, this check box is not selected.

Post Bind GID

(UNIX machines only) Enter the UNIX group ID (GID) under which a server on this machine will run after it finishes all privileged startup actions. Otherwise, the server continues to run under the group from which it was started. For this setting to take effect, you must select the Enable Post Bind GID check box.

Enable Post Bind UID

(UNIX machines only) 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. By default, this check box is not selected.

Post Bind UID

(UNIX machines only) Enter the UNIX user ID (UID) under which a server on this machine will run after it finishes all privileged startup actions. Otherwise, the server continues to run under the account from which it was started. For this setting to take effect, you must select the Enable Post Bind UID check box.

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 have to access the WebLogic Server Node Manager, you must disable host name verification.

See Using Host Name Verification in Administering Security for Oracle 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 65535. The default value is 5556.

You might want to create machine definitions in situations such as the following:

  • The Administration Server uses the machine definition, with the Node Manager application, to start remote servers.

  • WebLogic Server or other system components such as OHS use configured machine names when determining the server in a cluster that is best able to handle certain tasks, such as HTTP session replication. Those tasks are then delegated to the identified server.

    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.

Click Add to add a new machine. The default name for a new machine is new_[Unix]Machine_n, where n starts at 1 and increments by 1 for each machine that you add.

Click Delete to delete an existing machine.

Assign Servers to Machines

Use the Assign Servers to Machines screen to assign the WebLogic Server instances to each of the machines that you defined in the Machines screen of the Configuration Wizard.

To assign a WebLogic Server instance to a machine that you have defined:

  1. In the Machine list box, select the Windows or UNIX machine to which you want to assign a WebLogic Server instance.
  2. Assign a WebLogic Server instance to the selected machine in one of the following ways:
    • Double-click the WebLogic Server instance in the Server list box.

    • Select the appropriate WebLogic Server instance in the Server list box and click the right arrow.

    • Shift+click to select multiple servers in the Server list box; then, click the right arrow.

    The name of the WebLogic Server instance is removed from the Server list box and added, below the name of the target machine, in the Machine list box.

  3. Repeat steps 1 and 2 for each WebLogic Server instance to assign to a machine.
  4. Review the machine assignments.

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

    • Select the appropriate WebLogic Server instance in the Machine list box and click the left arrow.

    The name of the WebLogic Server instance is removed from the Machine list box and restored to the Server list box.

Virtual Targets

Virtual targets define the locations where a partition or resource group runs. You can use this screen to add or delete Virtual Targets for use in a WebLogic Server Multitenant (MT) environment.

Virtual Targets also provide instructions on how to route traffic, including addresses, protocol settings, and targeting. Request routing is determined by the host name and optional URI.

For more information, see the following resources in Using Oracle WebLogic Server Multitenant:

Column Description

Name

Enter the name that you want to use for the virtual target.

Target

From the drop-down list, select a Managed Server or cluster that you are creating in this domain.

Host Names

Enter the list of host names to which this virtual target serves requests. The host names that you specify must have domain name system (DNS) entries that resolve to the correct servers, or to a load balancer:

If you are not using Oracle Traffic Director to balance the connection load for a partition, then specify the actual host name of the WebLogic Server cluster or Managed Server.

If you are using Oracle Traffic Director to load balance connections for a partition, then you access applications through Oracle Traffic Director. The host names that you specify for a virtual target must resolve to the location of the Oracle Traffic Director Administration Server.

Note:

As of 12.2.1.4.0, Oracle Traffic Director is deprecated. In the future, for equivalent functionality, use Oracle HTTP Server, Microsoft IIS Web Server, or Apache HTTP Server plug-ins, or a native Kubernetes load balancer, such as Traefik.

If you do not specify a host name, then it is the equivalent of using a wild card for the host name to match all incoming requests.

The host name used by a client to access the resource group must exactly match one of the host names specified in the virtual target.

You can specify multiple host names for the virtual target. You might find it convenient to specify both the simple and the fully qualified host name to ensure a match.

URI Prefix

Enter an optional URI prefix to which this virtual target serves requests.

For example, if you enter www.example.com as the host name and MyApp as the URI prefix, then this virtual target serves requests to www.example.com/MyApp, but not to www.example.com or www.example.com/foo.

To extend this example, assume that your application root is /app. The resulting URL for the application is www.example.com/MyApp/app.

Explicit Port

Enter the explicit port for this virtual target.

Port Offset

Enter the port offset of the port for this virtual target.

Note:

WebLogic Server Multitenant domain partitions, resource groups, and virtual targets are deprecated in WebLogic Server 12.2.1.4 and will be removed in the next release.

Partitions

A domain partition is a portion of a WebLogic Server domain that is dedicated to run application instances and related resources. You can use the Partitions screen to add partitions in a WebLogic domain.

For each partition that you want to add, click Add and enter the name you want to use for the partition. The partition name must be unique within the domain.

See Configuring Domain Partitions in Using Oracle WebLogic Server Multitenant.

Note:

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

Assign Virtual Targets to Partitions

You can assign one or more existing virtual targets to a domain partition. You can use a virtual target with only one partition.

To assign Virtual Targets to a partition:

  1. In the Partitions list box, select the partition to which you want to assign a Virtual Target.

  2. Assign virtual targets to the selected partition in one of the following ways:

    • Double-click the target in the Virtual Targets list box.

    • Select the appropriate target in the Virtual Targets list box and click the right arrow.

    • Shift+click to select multiple targets in the Virtual Targets list box; then, click the right arrow.

    The name of the virtual target is removed from the Virtual Targets list box and added, below the name of the target partition, in the Partitions list box.

  3. Repeat steps 1 and 2 for each virtual target you want to assign to a machine.

  4. Review the partition assignments.

    If necessary, you can remove a virtual target from a partition in one of the following ways:

    • Double-click the name of the appropriate virtual target instance in the Partitions list box.

    • Select the appropriate virtual target in the Partitions list box and click the left arrow.

    The name of the virtual target is removed from the Partitions list box and restored to the Virtual Targets list box.

Note:

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

Domain Frontend Host

When creating a new domain, use the Domain Frontend Host screen to enable the frontend host, specify both the plain and secure URLs for the frontend host, and select the default frontend host URL.

This screen appears only if you have selected the Domain Frontend Host Capture option on the Advanced Configuration screen.

If there are one or more OHS instances configured in the domain, the Plain and SSL fields are automatically populated with the appropriate values from the first OHS instance in the domain. Otherwise, you must configure the values. The settings are then saved to a service table.

When you update a domain, the values are populated based on the values in the service table, if any. If the service table values are null and there are no OHS instances configured, the Configure Domain Frontend Host check box is deselected (unchecked) by default. In this case, you must select the check box and configure the host to enable the domain frontend host.

Field or Option Description

Configure Domain Frontend Host

If selected, the domain-wide frontend host is enabled.

To disable and delete the frontend host configuration, deselect this check box. A notification appears to indicate that the configuration is being deleted from the service table.

Plain

If not automatically populated, enter the plain URL for the frontend host, for example, http://www.myhost.com:8180. If necessary, you can also update the existing value.

SSL

If not automatically populated, enter the SSL URL for the frontend host. If necessary, you can also update the existing value.

Note:

If you are using the plain URL for the frontend host, you must still specify a default SSL URL. If you have only set up a plain connection to the Frontend Host, you can use the same URL for both plain and SSL. Otherwise, they must be different.

Default

Select the appropriate radio button to make either the Plain or SSL URL the default URL for the frontend host.

System Components

Use the System Components screen to add or delete system components such as for Oracle HTTP Server (OHS) and Oracle Data Integrator (ODI).

Field Description

System Component

Enter a unique name to identify the system component.

Component type

Enter the appropriate component type, such as OHS or ODI.

Restart interval seconds

If an application is not responding, specify the number of seconds to wait before you attempt a restart.

Restart interval delay

Specify the number of seconds to wait between restart attempts.

Click Add to add a new system component. The default name for a new component is new_SystemComponentn, where n starts at 1 and increments by 1 for each OHS or ODI instance that you add.

To delete an existing system component, click in the table row for the component and click Delete.

OHS Server

You can use this screen to configure the Oracle HTTP Server (OHS) in the WebLogic domain. Before you configure OHS, you must add OHS as a system component by using the System Component screen.

Specify the following details to configure the OHS servers:

Field Description

System Component

From this drop-down list, select the system component to configure.

Admin Host

The listen address to use for the selected OHS server for communication with Node Manager. The address must allow only loopback communication within the host (for example, 127.0.0.1).

Admin Port

The listen port to use for the selected OHS server for communication with Node Manager on this system. The port must be unique.

Listen Address

Enter the listen address to use on this system component.

For more information about listen addresses, see Specifying the Listen Address.

Listen Port

Enter the listen port to use on this system component.

For more information about listen ports, see Specifying the Listen Port.

SSL Listen Port

This field is available only if SSL is enabled on the specified WebLogic Server Administration Server.

Enter a valid value to be used for secure requests on this server instance. The valid listen port range is from 1 to 65535.

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.

See SSL: An Introduction in Administering Security for Oracle WebLogic Server.

Server Name

The server URL and listen port for the currently selected OHS server. When you add new servers, this field defaults to the server on which you run the Configuration Wizard and the port value in the Listen Port field.

ODI Server Configuration

Use the ODI Server Configuration screen to configure the co-located ODI agents in the WebLogic domain. Before you configure ODI, add ODI as a system component by using the System Component screen.

For more information on standalone and co-located ODI agents, see Understanding Oracle Data Integrator Agents in Installing and Configuring Oracle Data Integrator.

Field Description

System Component

From this drop-down list, select the ODI agent to configure.

Server Listen Address

From this drop-down list, select the appropriate server listen address for the selected ODI agent. Do not use localhost.

Server Listen Port

Enter the listen port to use for the ODI agent.

Supervisor Username

Enter the ODI username that has Supervisor privileges.

Supervisor Password

Enter the password for the Supervisor user password.

Preferred Datasource

From this drop-down list, select the data source to use for the selected ODI agent.

Assign System Components to Machines

After you configure the system components such as OHS and ODI, use the Assign System Components to Machines screen to assign these components to the machines that you have defined in the Machines screen.

To assign system components to machines:

  1. In the Machine list box, select the Windows or UNIX machine to which you want to assign a system component.
  2. Assign system components to the selected machine in one of the following ways:
    • Double-click the instance in the System Components list box.

    • Select the appropriate instance in the System Components list box and click the right arrow.

    • Shift+click to select multiple instances in the System Components list box; then, click the right arrow.

    The name of the system component is removed from the System Components list box and added, below the name of the target machine, in the Machine list box.

  3. Repeat steps 1 and 2 for each instance to assign to a machine.
  4. Review the machine assignments.

    If necessary, you can remove an instance from a machine in one of the following ways:

    • Double-click the name of the appropriate instance in the Machine list box.

    • Select the appropriate instance in the Machine list box and click the left arrow.

    The name of the instance is removed from the Machine list box and restored to the System Components list box.

Deployments Targeting

Applications associated with the product for which you configure the domain are targeted automatically to the Managed Server that is created for that product, or to the cluster to which that Managed Server is assigned. In the Deployments Targeting screen, you can target applications to additional servers and clusters.

To target an application deployment to a cluster or server:

  1. In the Target list box, select the cluster or server on which you want to deploy applications.

    The name of the selected target is displayed as the title of the list box on the right.

  2. In the target_name list box, select the check boxes corresponding to the applications to deploy on the selected target.

    The applications displayed here vary, depending on the products that you selected in the Select Domain Source screen, earlier in the wizard.

    Note:

    When you select a Managed Server in the Target list box, some of the check boxes in the target_name list box might be disabled, indicating applications that are already targeted at the cluster that contains the selected Managed Server.

    After you select applications, the names of the targeted clusters and servers appear in the Target column in the target_name list box.

  3. Repeat steps 1 and 2 for the other clusters and servers, as required.
  4. After you make the required selections, click Next.

When you extend a domain, if you delete a Managed Server or cluster to which applications are currently targeted, the Configuration Wizard automatically retargets those applications as follows:

  • If the applications were originally targeted solely to the Managed Server or cluster that you are now deleting, after you delete the Managed Server or cluster, the applications will become untargeted in the modified domain. The Configuration Wizard automatically retargets the applications to all eligible targets.

    An eligible target is any cluster or Managed Server that is not defined in the configuration groups specification (config-groups.xml file) of an included template. Servers or clusters that are specified in config-groups.xml are owned by the template and, therefore, are not eligible for automatic targeting.

  • If the applications were originally targeted to multiple targets (including Managed Servers, clusters, and the Administration Server), and one of the targeted Managed Servers or clusters is deleted, then, in the extended domain, the Configuration Wizard leaves the remaining target associations intact and does not attempt to retarget the applications.

Services Targeting

Services that are associated with the product for which you configure the domain are targeted automatically to the Managed Server created for that product, or to the cluster to which that Managed Server is assigned. In the Services Targeting screen, you can target services to additional servers and clusters.

To target services to Managed Servers or clusters:

  1. In the Target list box, select the cluster or server on which you want to deploy services.

    The name of the selected target is displayed as the title of the list box on the right.

  2. In the target_name list box, select the check boxes corresponding to the services to deploy on the selected target.

    The services displayed here vary, depending on the products that you selected in the Select Domain Source screen earlier in the wizard.

    Note:

    When you select a Managed Server in the Target list box, some of the check boxes in the target_name list box might be disabled, indicating services that are already targeted at the cluster that contains the selected Managed Server.

    After you select services, the names of the targeted clusters and servers appear in the Target column in the target_name list box.

  3. Repeat steps 1 and 2 for the other clusters and servers, as required.
  4. After you make the required selections, click Next.

When you extend a domain, if you delete a Managed Server or cluster to which services are currently targeted, the Configuration Wizard automatically retargets those services as follows:

  • If the services were originally targeted solely to the Managed Server or cluster that you are now deleting that is, after you delete the Managed Server or cluster, the services will become untargeted in the modified domain. The Configuration Wizard automatically retargets the services to all eligible targets.

    An eligible target is any cluster or Managed Server that is not defined in the configuration groups specification (config-groups.xml file) of an included template. Servers or clusters that are specified in config-groups.xml are owned by the template and, therefore, are not eligible for automatic targeting.

  • If the services were originally targeted to multiple targets (including Managed Servers, clusters, and the Administration Server), and one of the targeted Managed Servers or clusters is deleted, then, in the extended domain, the Configuration Wizard leaves the remaining target associations intact and does not attempt to retarget the services.

File Stores

A JMS file store is a disk-based file in which persistent messages can be saved. Use the File Stores screen to modify the JMS file stores that are configured in the WebLogic domain.

Specify the following details to modify the JMS file stores:

Column Description

Name

Enter a valid name for the JMS file store. The name must be a string of characters. The name of the JMS file store must be unique among all component names within the domain.

Directory

Enter the path of the directory (in your system) in which the JMS file store resides.

Synchronous write policy

From the drop-down list, select one of the following synchronous write policies to determine how the file store writes data to the disk.

If the JMS file store is used exclusively for paging non-persistent messages to the disk, the synchronous write policy is ignored.

Cache-Flush

WebLogic Server enables the default file write behavior of the operating system and storage device, which typically includes caching and scheduling file writes, but forces a flush of the cache to disk before completing a transaction.

See Cache-Flush Policy in Administering the WebLogic Persistent Store.

Direct Write

Write operations are performed directly to the disk. This policy is supported on Solaris and Windows. If this policy is active on an unsupported platform, the file store switches automatically to the cache-flush policy.

See Direct-Write Policy in Administering the WebLogic Persistent Store.

Direct-Write-With-Cache

For most scenarios, Oracle recommends using the Direct-Write-With-Cache policy. When this policy is selected, WebLogic Server writes synchronously to a primary set of files in the location defined by the Directory attribute of the file store configuration using a native I/O wlfileio driver.

See Direct-Write-With-Cache Policy in Administering the WebLogic Persistent Store.

Disabled

Transactions are complete when the writes are cached in memory. When this policy is active, completion of transactions does not depend on waiting for writes to reach the disk. This setting affects performance, scalability, and reliability.

See Disabled Policy in Administering the WebLogic Persistent Store.

Configuration Summary

The Configuration Summary screen provides a summary of the configuration settings for the WebLogic domain. Review the details before you proceed.

In the Domain Summary pane, select an item to display details about that item in the Details pane on the right.

You can limit the items that appear in the Domain Summary pane by selecting a filter option from the Summary View drop-down list.

If you want to change the configuration, click Back to return to the appropriate screen.

When done, click Create to create the domain.

Configuration Progress

If you are creating a domain, the Configuration Progress screen shows the progress of the domain creation. If you are updating (extending) a domain, this screen shows the progress of the domain update.

If you create a domain by using templates that were selected in the Templates screen, detailed messages appear as the domain is being created.

If you configure the WebLogic Server samples domains at the end of WebLogic Server installation, the following messages appear for each domain:

Generating domain domain_name

---------------------------------------------

Successfully generated domain: domain_name

When the domain creation process completes, click Next or Finish to continue. In some situations, the Finish button is not available and you must click Next.

Configuration Success

Depending on whether you run the full Configuration Wizard or the Quick Start Configuration Wizard, the appropriate configuration success message appears on this screen.

Single Domain

The message New Domain domain_name Created appears, and the domain location is provided along with the Administration Server URL to use for the domain.

On Windows systems, if you want to start the Administration Server after you close the Configuration Wizard, select the Start Admin Server check box. This check box is not available on UNIX systems.

Multiple Domains (Quick Start Configuration Wizard Only)

The following configuration details appear:

Field Description

Domain Name

The name of the new domain.

Domain Location

The path for each domain.

Status

The status of each domain creation, whether successful or failed. If the process fails, a message appears to indicate the reason of the failure.

Admin URL

The Administration Server URL.

If you used the Quick Start Wizard to create the WebLogic Server samples domains, a Start Domain check box is available on Windows to start any of the domains. To start a domain, select this check box, and then select the domain to start from the drop-down list.