1. Installing and Configuring the Oracle Fusion Middleware Infrastructure
  2. Configuring the Oracle Fusion Middleware Infrastructure Domain

3 Configuring the Oracle Fusion Middleware Infrastructure Domain

Use the steps in the following order to create and configure the WebLogic Server domain for Oracle Fusion Middleware Infrastructure.

This section contains the following topics:

Creating Database Schemas

Before you configure a Fusion Middleware Infrastructure domain, you must install the following schemas on a certified database to use them with this Oracle Fusion Middleware release.

Note:

As of Oracle Fusion Middleware 14c (14.1.2.0.0), new schemas are created with editions-based redefinition (EBR) views enabled by default. When EBR is enabled, the schema objects can be upgraded online to a future Fusion Middleware release without any downtime. For more information about using editions-based redefinition, see Using Edition-based Redefinition.

  • Metadata Services (MDS)

  • Audit Services (IAU)

  • Audit Services Append (IAU_APPEND)

  • Audit Services Viewer (IAU_VIEWER)

  • Oracle Platform Security Services (OPSS)

  • User Messaging Service (UMS)

  • WebLogic Services (WLS)

  • Service Table (STB)

Follow the instructions in this topic to create database schemas:

Installing and Configuring a Certified Database

Verify that you installed and configured a certified database and that it is up and running.

See About Database Requirements for an Oracle Fusion Middleware Installation in Planning an Installation of Oracle Fusion Middleware.

Starting the Repository Creation Utility (RCU)

You start RCU from the /oracle_common/bin directory.

To start the Repository Creation Utility:

  1. Navigate to the ORACLE_HOME/oracle_common/bin directory.
  2. Start RCU:

    On UNIX operating systems:

    ./rcu

    On Microsoft Windows operating systems:

    rcu.bat

Navigating RCU Screens to Create Schemas

Follow this series of steps to create schemas for the Oracle Fusion Middleware Infrastructure domain.

Introducing RCU

Click Next on the Welcome to Repository Creation Utility screen.

Selecting a Schema Creation Method

If you have the permission and privileges to perform DBA actions on your database, select System Load and Product Load on the Create Repository screen.

(The procedure in this document assumes that you have the necessary privileges.)

If you do not have the necessary permission or privileges to perform DBA actions, you must select Prepare Scripts for System Load. This option generates a SQL script that you can give to your database administrator. See Understanding System Load and Product Load in Creating Schemas with the Repository Creation Utility.

For more about options on this screen, see Create repository in Creating Schemas with the Repository Creation Utility.

Providing Database Credentials

On the Database Connection Details screen, enter database connection details for RCU to connect to your database.

Click Next then click OK on the dialog window to confirm a successful database connection.

Database Connection Details in Creating Schemas with the Repository Creation Utility has additional details about options on this screen.

Specifying a Custom Prefix and Selecting Schemas

On the Select Components screen, enter a custom prefix you want to use for your schemas, then select AS Common Schemas.

All schemas in this section are automatically selected. The custom prefix logically groups these schemas together for this domain.

For more on custom prefixes, see Understanding Custom Prefixes in Creating Schemas with the Repository Creation Utility.

For more on how to organize schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.

Make a note of the custom prefix that you enter; you need the prefix when you create a domain.

Click Next then click OK on the dialog window to confirm that prerequisite checking for schema creation is successful.

Specifying Schema Passwords

On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

Click Next.

Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.

See About Repository Creation Utility for more details about RCU features and concepts.

Configuring Your WebLogic Domain

This topic describes how to create a WebLogic domain using the Configuration Wizard.

There are other ways to create a domain; see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.

To configure a WebLogic domain, follow these steps:

Starting the Configuration Wizard

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

On UNIX operating systems:

./config.sh

On Microsoft Windows operating systems:

config.cmd

On Windows operating systems, you can also start the Configuration Wizard from the Start menu: Select All Programs, then Oracle, then OracleHome. Select WebLogic Server 14c (14.1.2.0.0), then Tools, then Configuration Wizard.

Navigating Configuration Wizard Screens to Configure the Domain

In addition to creating and configuring a domain, you can use this procedure to extend an existing domain. If your settings don't match those in the procedure, change your selections as you need to or see supporting documentation for more details.

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

Selecting the Configuration Type and Domain Home Location

You must select a Domain home directory location, optimally outside the Oracle home directory.

To specify the Configuration type and Domain home directory:

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

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

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

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

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

Selecting Configuration Templates

A domain template defines the full set of resources within a WebLogic domain, including the Administration Server, clusters, servers, applications, services, security options, and other options.

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:

  • Oracle Enterprise Manager - 14.1.2.0.0 [em]

    Selecting this template automatically selects the following dependencies:

    • Oracle JRF - 14.1.2.0.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 14.1.2.0.0 [wlserver]

  • Oracle WSM Policy Manager - 14.1.2.0.0 [oracle_common]

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

Selecting the Application Home Location

On the Application Location screen, select a location to store applications associated with your domain. This location is the Application home directory.

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

For more about the Application home directory, see Choosing an Application Home in Planning an Installation of Oracle Fusion Middleware.

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

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

Configuring the Administrator Account

Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.

Oracle recommends that you make a note of the user name and password that you specify; you need these credentials later to boot and connect to the domain's Administration Server.

Specifying the Domain Mode and JDK

Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK) for your production environment.

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

    Note:

    As of WebLogic Server 14.1.2.0.0, when you select Production mode, WebLogic Server automatically sets some of the security configurations of Secured Production to more secure values. However, there are certain security configurations (such as SSL/TLS) that require manual configuration. See Using Secured Production Mode in Administering Security for Oracle WebLogic Server.

    If you want to disable the more secure default settings, then you may select Disable Secure Mode. This will enable the non-SSL listen ports.

    If you want to retain the more secure default settings of Secured Production mode in general, but want to change which ports (listen ports, SSL listen ports, or administration ports) will be enabled by default in your domain, then you may:
    • Leave Disable Secure Mode unselected, and
    • Change the default port selections under Enable or Disable Default Ports for Your Domain

    For more information, see Understand How Domain Mode Affects the Default Security Configuration in Securing a Production Environment for Oracle WebLogic Server.

  • Select the Oracle HotSpot JDK in the JDK field.

For more information about this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.
Specifying the Database Configuration Type

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

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

Note:

If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the next screen.

After selecting RCU Data, specify details in the following fields:

Field Description

Host Name

Enter the name of the server hosting the database.

Example: examplehost.exampledomain.com

DBMS/Service

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

Example: orcl.exampledomain.com

Port

Enter the port number on which the database listens.

Example: 1521

Schema Owner

Schema Password

Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Specifying Schema Passwords).

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

For an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format described in Connection Credentials for an Autonomous Transaction Processing Database.

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

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

Successfully Done.

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

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

Specifying JDBC Component Schema Information

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

Verify that the values populated on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

For an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format: 

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

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

Example connect string for Autonomous Transaction Processing-Dedicated (ATP-D) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

Example connect string for Autonomous Transaction Processing Shared (ATP-S) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

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

Testing JDBC Connections

Use the JDBC Component Schema Test screen to test datasource connections that you just configured.

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

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

Selecting Advanced Configuration

Use the Advanced Configuration screen to complete the domain configuration.

To complete domain configuration, select these options:

  • Administration Server — Required to properly configure the Administration Server’s listen address.

  • Node Manager — Required to configure Node Manager.

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

    To configure dynamic clusters, see:

You do not need to select:

  • Domain Frontend Host Capture

  • Deployments and Services

  • JMS File Store

Configuring the Administration Server Listen Address

Use the Administration Server screen to select the Listen Address and configure the Administration Server ports.

Note:

The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.

  1. Provide a name for the Administration Server. The name field must not be null or empty and cannot contain any special characters.
  2. Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.
  3. Verify the port settings. When the domain type is set to Production, then the Enable SSL Listen Port option is enabled by default. Do not specify any server groups for the Administration Server.

    Note:

    You can change the port values as needed, but they must be unique. If the same port numbers are used for different ports, you will not be able to navigate to the next step in the Configuration Wizard.

For more information, see Specifying the Listen Address in Creating WebLogic Domains Using the Configuration Wizard.

Configuring Node Manager

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

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

Tip:

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

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

Configuring Managed Servers

In this screen, you create Managed Servers.

Note:

The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.

To create two new Managed Servers:

  1. Click the Add button to create a new Managed Server.
  2. Specify infra_server_1 in the Server name column.

    Installation and configuration procedures use infra_server_# for Managed Servers names. If you use different names, substitute infra_server_# with them.

  3. In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside. Do not use "All Local Addresses."
  4. Verify your port selections. If you selected Production mode with Secure Mode enabled, Enable SSL Port is selected by default. The default port will be auto-incremented so that the ports do not conflict with any additional managed servers you add. This is true for Listen Ports and Administration Ports. You can edit any and all port values based on your configuration and machines being used. Oracle recommends that you enable SSL ports for added security. If, however, you want to change the port setting to use the less secure Listen Port, then disable the Enable SSL Port and check the Enable Listen Port option.

    Note:

    You can change the port values as needed using an integer in the range of 1 and 65535, but they must be unique. If the same port numbers are used for different ports, you will receive a port conflict error and you will not be able to start the server.

  5. Repeat this process to create a second Managed Server named infra_server_2.

    You must configure a second Managed Server to configure the standard topology for high availability. If you are not creating a highly available environment, this step is optional.

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

    For more about the next steps to prepare for high availability after your domain is configured, see High Availability Configuration Tasks.

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

Configuring a Cluster

To create a new cluster:

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

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

You can create new clusters using Fusion Middleware Control and configure cluster communication (unicast or multicast) as you go through cluster creation steps. See Create and Configure Clusters in Administration Console Online Help.

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

Defining Server Templates

If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for the domain.

To add Server Templates:

Note:

The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.

  1. Click Add to create new_ServerTemplate_1. The server template name will increment automatically when an additional server template is added (new_ServerTemplate_2).
  2. For Secure Production Mode, verify that the Enable SSL Port option is selected. The default SSL Listen Port does not increment automatically when a new server template is added. You can change the default to Enable Listen Port, but Oracle recommends that retain the default to enable SSL. Enabling Listen Port disables SSL Listen Port.

    Note:

    You can change the port values as needed using an integer in the range of 1 and 65535, but they must be unique. If the same port numbers are used for different ports, you will receive a port conflict error and you will not be able to start the server.

  3. The Administration Port does not increment when an additional server template is added.

    Note:

    If the Listen ports are disabled, then instead of seeing a number you will see Disabled.

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

Configuring Dynamic Servers

If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.

If you are not configuring a dynamic cluster, click Next to continue configuring the domain.

Note:

When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.

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

Assigning Managed Servers to the Cluster

To assign infra_server_1 and infra_server_2 to the new cluster infra_cluster_1, use the Assign Servers to Clusters screen:

  1. In the Clusters pane, select the cluster that you want to assign servers to; in this case, infra_cluster_1.
  2. In the Servers pane, take one of the following steps to assign infra_server_1 to infra_cluster_1:

    • Click once on infra_server_1 to select it, then click on the right arrow to move it beneath the selected cluster (infra_cluster_1) in the Clusters pane.

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

  3. Repeat to assign infra_server_2 to infra_cluster_1.

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

Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.

Note:

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

For Coherence licensing information, see Oracle Coherence Products in Licensing Information.

Creating a New Machine

You create a new machine in the domain using the Machines screen. You assign servers to this machine in the next screen.

Tip:

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

To create a new machine in the domain:

  1. Click the Add button to create a new machine.
  2. Specify infra_machine_1 in the Name field.
  3. In the Node Manager Listen Address field, select the IP address of the machine where you are configuring Managed Servers. You must select a specific interface, not "localhost," so that Coherence cluster addresses can calculate dynamically.
  4. Verify the port in the Node Manager Listen Port field.

    Examples in the procedures may use port number 5556. You must replace this port number with your own port number as needed.

Note:

If you extend an existing domain, you can assign servers to any existing machine. You don't need to create a new machine unless your situation requires it.

See Machines in Creating WebLogic Domains Using the Configuration Wizard for details about these options.

Assigning Servers to Machines

In this screen, assign the domain servers to the machine you just created.

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

  1. In the Machines pane, select the machine you want to assign the servers to; in this case, infra_machine_1.
  2. In the Servers pane, take one of the following steps to assign AdminServer to infra_machine_1:

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

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

  3. Repeat to assign both infra_server_1 and infra_server_2 to infra_machine_1. Click Next.

For more details about options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.

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

Writing Down Your Domain Name and Administration Server URL

The Configuration Success screen shows information about the domain you just configured.

  • Domain Location

  • Administration Server URL

You must make a note of both items because you need them later; you need the Domain Location to access scripts that start Node Manager and Administration Server. You need Admin Server URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

About Server Groups

Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group.

Any application services that map to a server group automatically target all servers assigned to that group. For more details, see Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.

Note:

The WSM-CACHE-SVR server group configures Nonce caching for Oracle Web Services automatically, and is suitable for most applications. Nonce is a unique number that can be used only once in a SOAP request and prevents replay attacks. Nonce caching scales with the number of added Managed Servers running Web service applications.

For advanced caching configurations, see Caching the Nonce with Oracle Coherence in Securing Web Services and Managing Policies with Oracle Web Services Manager.

Starting the Servers

When you finish configuration, take the following steps to access tools to manage your domain.

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can start and manage a domain with secured production mode enabled. Specifically, you will need to add additional parameters when starting the Administration and Managed Servers. For more information, see Using Secured Production Mode Administering Security for Oracle WebLogic Server.

Note:

For more on tools you can use to manage a domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

Starting Node Manager

To start the per-domain Node Manager:

    • (UNIX) Go to the DOMAIN_HOME/bin directory.

    • (Windows) Go to the DOMAIN_HOME\bin directory.

  2. Enter the following command:

    • (UNIX) Using nohup and nm.out as an example output file: 

      nohup ./startNodeManager.sh > LOG_DIR/nm.out&

      where LOG_DIR is the location of directory in which you want to store the log files.

    • (Windows) startNodeManager.cmd

      Note:

      On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

      See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

Starting the Administration Server

The procedures in this section describe how to start the Administration Server using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To start the Administration Server:

Note:

When using secured production mode, you must provide additional parameters to start the Administration Server. See Connecting to the Administration Server using WLST in Administering Security for Oracle WebLogic Server.

  1. (Optional) When using Production Mode, you can create a boot.properties file before starting the Administration Server and provide necessary permissions. This file can be created to bypass the need to provide a username and password when starting the Administration Server. For more information, see Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.

  2. Go to the DOMAIN_HOME/bin directory.

  3. Enter the following command:

    • (UNIX)

      ./startWebLogic.sh

    • (Windows)

      startWebLogic.cmd

    If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, and you did not create the optional boot.propeties file, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.

  4. Open a browser and verify that the Administration Server is up and running. The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.
    https://<Host_Name>:<port>
  5. Verify that all servers in the domain have unique port values. From the WebLogic Remote Console, you can review the Local Administration Port Override fields for each managed server and verify that each has a unique value. If one or more ports is using the same value, then you must change them before starting the managed servers. For more information about changing port values, see Connect to an Administration Server in the Oracle WebLogic Remote Console.

Note:

The WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

Starting the Managed Servers

To start a WebLogic Managed Server that is not set to secure product mode, you can use the startManagedWebLogic script:

  • (UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name

  • (Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name

Note:

When using secured production mode, you must provide additional parameters to start the Managed Servers. See Starting Managed Servers using a Start Script in Administering Security for Oracle WebLogic Server.

Verifying Your Configuration

Oracle recommends that you verify that your domain is configured properly.

See Basic Administrative Tasks for a New Domain to verify your configuration. Familiarize yourself with tasks that this topic describes and run them.