1. Installing and Configuring Oracle WebCenter Sites
  2. Installing and Configuring Oracle WebCenter Sites
  3. Configuring WebCenter Sites Domain

4 Configuring WebCenter Sites Domain

After you have installed WebCenter Sites, you can configure the domain, which you can also extend for high availability.

The configuration steps presented here assume that you have completed the installation steps covered in:

Refer to the following sections to create the database schemas, configure a WebLogic domain, and verify the configuration:

Starting the Servers

After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.

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.

For more information on additional tools you can use to manage your 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

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.

To start the Managed Servers:

  1. Sign in to Oracle Fusion Middleware Control:
    http://administration_server_host:administration_server_port/em

    The login credentials were provided on the Administrator Account screen (Configuring the Administrator Account).

  2. The Enterprise Manager landing page lists servers configured for this domain and shows their status (such as Running or Shutdown). For a newly configured domain, only the AdminServer(admin) will be running.
  3. Select the first Managed Server.
  4. Next to the WebLogic Server menu, select Start Up.
  5. Repeat Steps 3 and 4 to start all Managed Servers.
  6. On the main landing page, verify that all Managed Servers are up and running.

Verifying the Configuration

After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.

To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.