4 Configuring the 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 test the configuration:

Parent topic: Installing and Configuring Oracle WebCenter Sites

4.1 Creating the Database Schemas

Before you can configure an Oracle WebCenter Sites domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.

Follow the instructions in this section to install the schemas:

4.1.1 Installing and Configuring a Certified Database

You must verify that you installed and configured a certified database, and that the database is up and running.

For more information, see Installing a Database and Database Schemas in Planning an Installation of Oracle Fusion Middleware.

4.1.2 Starting the Repository Creation Utility (RCU)

Starting RCU requires that your JDK environment variable is set correctly.

To start the Repository Creation Utility (RCU):

  1. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.
  2. Ensure that the JAVA_HOME environment variable is set to the location of a certified JDK on your system. The location should be up to but not including the bin directory. For example, if your JDK is located in /home/Oracle/Java/:

    On UNIX operating systems (in C shell):

    setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_40

    On Windows operating systems:

    set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_40

    Be sure to replace the JDK location in these examples with the actual JDK location on your system.

  3. Start RCU from the ORACLE_HOME/oracle_common/bin directory:

    On UNIX operating systems:

    ./rcu

    On Microsoft Windows operating systems:

    rcu.bat

4.1.3 Navigating the RCU Screens to Create the Schemas

Use the RCU screens to create the database schemas.

4.1.3.1 Introducing RCU

The Welcome screen is the first screen that appears when you start RCU.

Click Next.

4.1.3.2 Selecting a Method of Schema Creation

With SYSDBA permissions, you can perform database administration activities.

If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have the necessary SYSDBA privileges.

If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. 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.

4.1.3.3 Providing Database Connection Details

Provide the database connection details for RCU to connect to your database.

Click Next to proceed, then click OK on the dialog window to confirm that connection to the database was successful.

4.1.3.4 Specifying a Custom Prefix and Selecting Schemas

The custom prefix logically groups together schemas together for use in this domain only; you must create a unique set of schemas for each domain. Schema sharing across domains is not supported.

Select Create new prefix, specify a custom prefix, then select WebCenter Sites. This action automatically selects the following schemas as dependencies:

  • Oracle Platform Security Services

  • Audit Services

  • Audit Services Append

  • Audit Services Viewer

  • WebCenter Sites

  • WebCenter Sites—Visitor Services

Tip:

You must make a note of the custom prefix you choose to enter here; you will need this later on during the domain creation process.

The Configuration Wizard also automatically creates the schema Common Infrastructure Services. This schema is grayed out; you cannot select or deselect it. This schema enables you to retrieve information from RCU during domain configuration. For more information, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

Tip:

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

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

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

4.1.3.5 Specifying Schema Passwords

Specify how you want to set the schema passwords on your database, then enter and confirm your passwords.

Tip:

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

4.1.3.6 Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

The Encrypt Tablespace check box appears on the Map Tablespaces screen only if you enabled TDE (Transparent Data Encryption) in the database (Oracle or Oracle EBR) when you start RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen if you want to encrypt all new tablespaces that RCU will create.

When you reach the Completion Summary screen, click Close to dismiss RCU.

4.2 Configuring the WebCenter Sites Domain

Use the Configuration Wizard to create and configure a domain.

For information on other methods to create domains, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.

4.2.1 Navigating the Configuration Wizard Screens to Create and Configure the Domain

Use the Configuration Wizard to create and configure the domain for the topology.

Note:

You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.

The following sections step through the Configuration Wizard:

4.2.1.1 Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

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

4.2.1.2 Selecting the Domain Type and Domain Home Location (WebCenter Sites)

You must select a Domain home directory location, optimally outside the Oracle 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, where the Domain home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or reinstall software.

To specify the Domain 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.

    If you change the default Domain Location path, you must edit the grant-opss-permission.sh so that it matches the domain path. If you do not make this change, the installation fails and generates an error. See Completing Prerequisites for Configuring WebCenter Sites.

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

4.2.1.3 Selecting the Configuration Templates for Oracle WebCenter Sites

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

  • Oracle WebCenter Sites - 12.2.1.0.0 [wcsites]

  • Oracle WebCenter Sites - Visitor Services- 12.2.1.0.0 [wcsites]

  • Oracle WebCenter Sites - Insights - 12.2.1.0.0 [wcsites]

  • Oracle Enterprise Manager - 12.2.1.0 [em]

  • Oracle WebCenter Sites - SiteCapture - 12.2.1.0.0 [wcsites]

  • Oracle WebCenter Sites - Satellite Server - 12.2.1.0.0 [wcsites]

  • Oracle JRF - 12.2.1.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12 2.1.0 [wlserver]

Description of GUID-B2E39119-D9E1-49D3-A4E1-AADACA90B348-default.png follows
Description of the illustration GUID-B2E39119-D9E1-49D3-A4E1-AADACA90B348-default.png

Tip:

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

4.2.1.4 Selecting the Application Home Location

On the Application Location screen, select the location to store applications associated with your domain, also known as the Application home directory.

Oracle recommends that you locate your Application home in accordance with the directory structure in What are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or re-install your software.

Tip:

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

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

4.2.1.5 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 enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.

4.2.1.6 Specifying the Domain Mode and JDK

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

On the Domain Mode and JDK screen:

  • Select Production in the Domain Mode field.

  • Select the Oracle HotSpot JDK in the JDK field.

Tip:

For more about the options on this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

4.2.1.7 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 JDBC Component Schema screen.

After selecting RCU Data, fill in the following fields:

Field Description

DBMS/Service

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

Example: orcl.exampledomain.com

Host Name

Enter the name of the server hosting the database.

Example: examplehost.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 RCU (see Specifying Schema Passwords).

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

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

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

Successfully Done.

Tip:

For more information about the RCU Data option, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

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

4.2.1.8 Specifying JDBC Component Schema Information

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

Verify that the values 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.

Tip:

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

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

4.2.1.9 Testing the JDBC Connections

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

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

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

Tip:

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

4.2.1.10 Selecting Advanced Configuration

Use the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

  • Administration Server

    Required to properly configure the listen address of the Administration Server.

  • Node Manager

    Required to configure Node Manager.

  • Managed Server, Clusters and Coherence

    Required to configure the WebCenter Sites Managed Server.

4.2.1.11 Configuring the Administration Server Listen Address

Use the Administration Server screen to select the IP address of the host.

On the Administration Server screen, select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Use Mozilla Firefox to access Internet Protocol Version 6 (IPv6) URLs. You must enter the Global IPv6 address for creating a domain and accessing URLs. (You cannot use the local IPv6 address.)

4.2.1.12 Configuring Node Manager

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

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

Tip:

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

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

4.2.1.13 Configuring Managed Servers for Oracle WebCenter Sites

You configure Oracle WebCenter Sites components in a standalone domain. See the following topics to configure Managed Servers for Oracle WebCenter Sites.

Note:

See Log File Location for Oracle Fusion Middleware Components in Administering Oracle Fusion Middleware for the log file location of Oracle WebCenter Sites components.
4.2.1.13.1 Configuring Managed Servers for WebCenter Sites

On the Managed Servers screen, a new Managed Server named wcs_server_1 is created:

  1. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on or use the system name or DNS name that maps to a single IP address. Do not use "All Local Addresses."
  2. Click Enable SSL to enable security.

    The Server Group field has WCSITES-MGD-SERVER selected by default. Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that map to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

  3. Click Add and repeat this process to create a second Managed Server named wcs_server_2. You must select the Server Group WCSITES-MGD-SERVER for additional Managed Servers that you add.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

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

    For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.

Description of GUID-37DD6EF9-FC6A-4E9B-8BBC-913A0983496F-default.png follows
Description of the illustration GUID-37DD6EF9-FC6A-4E9B-8BBC-913A0983496F-default.png

Tip:

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

4.2.1.13.2 Configuring Managed Servers for Oracle WebCenter Sites: Site Capture

Use the Managed Servers screen to configure multiple Managed Servers.

On the Managed Servers screen, a new Managed Server named sc_server_1 is created:

  1. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on or use the system name or DNS name that maps to a single IP address. Do not use "All Local Addresses."
  2. Click Enable SSL to enable security.
  3. Leave the Server Groups settings as they appear; the Configuration Wizard assigns the correct server group automatically. A server group ensures that the correct services target Managed Servers you are creating.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. An application service group may map to multiple server groups if needed. Any application services that map to a specific server group automatically target all servers assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

  4. Click Add and repeat this process to create a second Managed Server named sc_server_2. You must select the Server Group SITECAPTURE-MGD-SVR for additional Managed Servers that you add.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

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

    For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names are referenced throughout this document; if you choose different names be sure to replace them as needed.

Description of GUID-187A6586-F4C9-40D3-8B56-51020E7B1501-default.png follows
Description of the illustration GUID-187A6586-F4C9-40D3-8B56-51020E7B1501-default.png

Tip:

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

4.2.1.13.3 Configuring Managed Servers for Oracle WebCenter Sites: Insights

Use this screen to configure multiple Managed Servers.

On the Managed Servers screen, a new Managed Server named ins_server_1 is created:

  1. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on or use the system name or DNS name that maps to a single IP address. Do not use "All Local Addresses."
  2. Click Enable SSL to enable security.
  3. In the Server Groups drop-down list, select INSIGHTS-MGD-SVR. This server group ensures that WebCenter Sites and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers you are creating.

    There is another server group, VS-MGD-SVR, that targets only WebCenter Sites but not OWSM to the server. This is typically used if you want to have OWSM in a different server rather than with the WebCenter Sites server.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that map to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

  4. Click Add and repeat this process to create a second Managed Server named ins_server_2. You must select the Server Group INSIGHTS-MGD-SVR for additional Managed Servers that you add.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

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

    For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.

Description of GUID-DBF54815-4618-462B-AC84-568BC59B5018-default.png follows
Description of the illustration GUID-DBF54815-4618-462B-AC84-568BC59B5018-default.png

Tip:

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

4.2.1.13.4 Configuring Managed Servers for Oracle WebCenter Sites: Satellite Server

Use this screen to configure a Managed Serves.

On the Managed Servers screen, a new Managed Server namedss_server_1 is created:

  1. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on or use the system name or DNS name that maps to a single IP address. Do not use "All Local Addresses."
  2. Click Enable SSL to enable security.
  3. In the Server Groups drop-down list, select SATELLITE-MGD-SVR. This server group ensures that Oracle WebCenter Sites: Satellite Server services target the Managed Server you are creating.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that map to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.

Tip:

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

4.2.1.13.5 Configuring Managed Servers for Oracle WebCenter Sites: Visitor Services

Use this screen to configure Managed Servers.

On the Managed Servers screen, a new Managed Server named vs_server_1 is created:

  1. In the Listen Address drop-down list, select the IP address of the host that the Managed Server will reside on or use the system name or DNS name that maps to a single IP address. Do not use "All Local Addresses."
  2. Click Enable SSL to enable security.
  3. In the Server Groups drop-down list, select VS-MGD-SVR. This server group ensures that Oracle WebCenter Sites: Visitor Services and Oracle Web Services Manager (OWSM) services target the Managed Servers you are creating.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that map to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see "Application Service Groups, Server Groups, and Application Service Mappings" in Domain Template Reference.

  4. Click Add and repeat this process to create a second Managed Server named vs_server_2 You must select the Server Group VS-MGD-SVR for additional Managed Servers that you add.

    Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

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

    For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names and will be referenced throughout this document; if you choose different names be sure to replace them as needed.

Description of GUID-27CD9E59-C0E7-40F9-88B8-0A7EC17C8425-default.png follows
Description of the illustration GUID-27CD9E59-C0E7-40F9-88B8-0A7EC17C8425-default.png

Tip:

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

4.2.1.14 Configuring a Cluster for WebCenter Sites

Use the Clusters screen to create a new cluster:

  1. Click Add.
  2. Specify wcs_cluster_1 in the Cluster Name field.
  3. Leave the Cluster Address field blank.

Repeat the preceding steps to create sc_cluster_1, ins_cluster_1 and vs_cluster_1.

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.

You can also create clusters using Fusion Middleware Control. In this case, you can configure cluster communication (unicast or multicast) when you create the new cluster. For more information, see "Create and configure clusters" in Oracle WebLogic Server Administration Console Online Help.

Tip:

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

4.2.1.15 Assigning WebCenter Sites Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to the new cluster.

On the Assign Servers to Clusters screen:

  1. In the Clusters pane, select the cluster to which you want to assign the Managed Servers; in this case, wcs_cluster_1.
  2. In the Servers pane, assign wcs_server_1 to wcs_cluster_1 by doing one of the following:

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

    • Double-click on wcs_server_1 to move it beneath the selected cluster (wcs_cluster_1) in the Clusters pane.

  3. Repeat to assign wcs_server_2 to wcs_cluster_1.
The following image shows an example of the Clusters pane after Managed Servers are assigned to clusters.

Figure 4-1 Managed Servers Assigned to Clusters

Description of Figure 4-1 follows
Description of "Figure 4-1 Managed Servers Assigned to Clusters"

Tip:

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

4.2.1.16 Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number 0 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.

See Table 5-2 for more information and next steps for configuring Coherence.

Note:

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

4.2.1.17 Creating a New WebCenter Sites Machine

Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.

Tip:

If you plan to create a high availability environment and know the list of machines your target topology requires, you can follow the instructions in this section to create all the machines at this time. For more information, see Optional Scale Out Procedure in High Availability Guide.

To create a new WebCenter Sites machine so that Node Manager can start and stop servers:
  1. Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
  2. In the Name field, specify wcs_machine_1.
  3. In the Node Manager Listen Address field, select the IP address of the machine in which the Managed Servers are being configured.

    You must select a specific interface and not localhost. This allows Coherence cluster addresses to be dynamically calculated.

  4. Verify the port in the Node Manager Listen Port field.

Note:

If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.

Tip:

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

4.2.1.18 Assigning Servers to WebCenter Sites Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created.

On the Assign Servers to Machines screen:

  1. In the Machines pane, select the machine to which you want to assign the servers; in this case, wcs_machine_1.
  2. In the Servers pane, assign AdminServer to wcs_machine_1 by doing one of the following:

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

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

  3. Repeat these steps to assign the remaining Managed Servers to their respective machines.
The following figure shows an example of the Machines pane after Managed Servers are assigned to machines.

Figure 4-2 Assign Managed Servers to Machines

Description of Figure 4-2 follows
Description of "Figure 4-2 Assign Managed Servers to Machines"

Tip:

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

4.2.1.19 Reviewing Your Configuration Specifications and Configuring the Domain

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

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

Tip:

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

4.2.1.20 Writing Down Your Domain Home and Administration Server URL

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

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

  • Domain Location

  • Administration Server URL

You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

4.3 Starting the Servers

After configuration is complete, you can use tools to manage your domain.

Note:

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.

Follow the instructions in the following sections:

4.3.1 Starting the Node Manager

To start your per-domain Node Manager, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, start the Node Manager as shown below, using nohup and nm.out as an example output file:

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

In this command, LOG_DIR is the location of directory in which you want to store the log files.

On Windows operating systems, run:

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.

For more information, see Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

For more information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.

4.3.2 Starting the Administration Server

To start the Administration Server, go to the DOMAIN_HOME/bin directory.

On UNIX operating systems, run:

./startWebLogic.sh

On Windows operating systems, run:

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.

Tip:

For more information about starting the Administration Server, see Starting and Stopping Administration Servers in Administering Oracle Fusion Middleware.

In production mode, a boot identity file can be created to bypass the need to provide a user name 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.

You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the Configuration Success screen in Writing Down Your Domain Home and Administration Server URL (http://administration_server_host:administration_server_port/console). The default Administration Server port number is 7001.

Note:

Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.

For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.

4.3.3 Starting the Managed Servers

To start the Managed Servers:

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

    The Administration Server host and port number were in the URL on the Configuration Success screen (Writing Down Your Domain Home and Administration Server URL). The default Administration Server port number is 7001.

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

  2. The Enterprise Manager landing page lists the servers configured for this domain and displays 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 the Managed Servers are up and running.

4.4 Verifying the Configuration

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

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