1. Installing and Configuring Oracle WebCenter Sites
  2. Installing and Configuring Oracle WebCenter Sites
  3. Installing the Oracle WebCenter Sites Software

3 Installing the Oracle WebCenter Sites Software

Follow the steps in this section to install the Oracle WebCenter Sites software.

Before beginning the installation, ensure that you have verified the prerequisites and completed all steps covered in Preparing to Install and Configure Oracle WebCenter Sites.

Parent topic: Installing and Configuring Oracle WebCenter Sites

Verifying the Installation Checklist

The installation process requires specific information.

Table 3-1 lists important items that you must know before, or decide during, Oracle WebCenter Sites installation.

Table 3-1 Installation Checklist

Information Example Value Description

JAVA_HOME

/home/Oracle/Java/jdk1.8.0_211

Environment variable that points to the Java JDK home directory.

Database host

examplehost.exampledomain

Name and domain of the host where the database is running.

Database port

1521

Port number that the database listens on. The default Oracle database listen port is 1521.

Database service name

orcl.exampledomain

Oracle databases require a unique service name. The default service name is orcl.

DBA username

SYS

Name of user with database administration privileges. The default DBA user on Oracle databases is SYS.

DBA password

myDBApw957

Password of the user with database administration privileges.

ORACLE_HOME

/home/Oracle/product/ORACLE_HOME

Directory in which you will install your software.

This directory will include Oracle Fusion Middleware Infrastructure and Oracle WebCenter Sites, as needed.

WebLogic Server hostname

examplehost.exampledomain

Host name for Oracle WebLogic Server and Oracle WebCenter Sites consoles.

Console port

7001

Port for Oracle WebLogic Server and Oracle WebCenter Sites consoles.

DOMAIN_HOME

/home/Oracle/config/domains/wcs_domain

Location in which your domain data is stored.

APPLICATION_HOME

/home/Oracle/config/applications/wcs_domain

Location in which your application data is stored.

Administrator user name for your WebLogic domain

weblogic

Name of the user with Oracle WebLogic Server administration privileges. The default administrator user is weblogic.

Administrator user password

myADMpw902

Password of the user with Oracle WebLogic Server administration privileges.

RCU

ORACLE_HOME/oracle_common/bin

Path to the Repository Creation Utility (RCU).

RCU schema prefix

WCS

Prefix for names of database schemas used by Oracle WebCenter Sites.

RCU schema password

myRCUpw674

Password for the database schemas used by Oracle WebCenter Sites.

Configuration utility

ORACLE_HOME/oracle_common/common/bin

Path to the Configuration Wizard for domain creation and configuration.

Parent topic: Installing the Oracle WebCenter Sites Software

Starting the Installation Program

Before running the installation program, you must verify the JDK and prerequisite software is installed.

To start the installation program:

  1. Sign in to the host system.
  2. Change to the directory where you downloaded the installation program.
  3. You must have installed the Oracle Fusion Middleware Infrastructure 12c (12.2.1.4.0). For instructions, see Installing the Infrastructure Software in Installing and Configuring the Oracle Fusion Middleware Infrastructure.
  4. Start the installation program by running the java executable from the JDK directory. For example:

    • (UNIX) /home/Oracle/Java/jdk1.8.0_211/bin/java -jar fmw_12.2.1.4.0_wcsites.jar

    • (Windows) C:\home\Oracle\Java\jdk1.8.0_211\bin\java -jar fmw_12.2.1.4.0_wcsites.jar

Note:

You can also start the installer in silent mode using a saved response file instead of launching the installer screens. For more about silent or command line installation, see Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer.

When the installation program appears, you are ready to begin the installation.

Parent topic: Installing the Oracle WebCenter Sites Software

Navigating the Installation Screens

The installation program shows a series of screens; see the following table for the order in which they appear.

If you need additional help with an installation screen, click the screen name. You can also click Help on the installation screens for additional instructions.

Table 3-2 Oracle WebCenter Sites Install Screens

Screen Description

Installation Inventory Setup

On UNIX operating systems, this screen opens if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location.

For more about the central inventory, see Understanding the Oracle Central Inventory in Installing Software with the Oracle Universal Installer.

This screen does not appear on Windows operating systems.

Welcome

This screen introduces you to the product installer.

Auto Updates

Use this screen to search for the latest software updates, including important security updates, via your My Oracle Support account.

Installation Location

Use this screen to specify your Oracle home directory location. This Oracle home should already contain Oracle Fusion Middleware Infrastructure.

You can click View to verify and ensure that you are installing Oracle WebCenter Sites in the correct Oracle home.

For more about Oracle Fusion Middleware directory structure, see Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware.

Installation Type

Choose the WebCenter Sites install option. If you want to install examples, choose WebCenter Sites — With Examples. To install Satellite Server only, choose WebCenter Sites — Satellite Server. All three options install Satellite Server.

If you want to install Visitor Services, you can optionally select the With Samples option. If the With Samples option is selected, the distribution includes the samples folder. The samples folder contains the source code and JAR for the default provider bundles available in WebCenter Sites. This sample code can be used for modifying the code in the default provider bundles, or it can be used as a starting tool for creating custom provider bundles.

Prerequisite Checks

Verifies that your system meets the minimum necessary requirements.

To view the list of tasks that gets verified, select View Successful Tasks. To view log details, select View Log.

If there are warning or error messages, see one of the documents in Roadmap for Verifying Your System Environment.

Installation Summary

Use this screen to verify installation options you selected. If you want to save these options to a response file, click Save Response File and enter the response file location and name. You can use response files later if you perform a silent installation.

All feature sets that are installed after installation is complete are listed here.

For more about silent or command line installation, see Using the Oracle Universal Installer in Silent Mode in Installing Software with the Oracle Universal Installer.

Click Install to begin the installation.

Installation Progress

Shows the installation progress.

When the progress bar reaches 100% complete, click Finish to dismiss the installer or click Next to see a summary.

Installation Complete

Review the summary information on this screen, then click Finish to dismiss the installer.

Parent topic: Installing the Oracle WebCenter Sites Software

Verifying the Installation

After you complete the installation, verify whether it was successful by completing a series of tasks.

Parent topic: Installing the Oracle WebCenter Sites Software

Reviewing the Installation Log Files

Review the contents of the installation log files to make sure that the installer did not encounter any problems.

By default, the installer writes logs files to the Oracle_Inventory_Location/logs (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory.

For a description of the log files and where to find them, see Installation Log Files in Installing Software with the Oracle Universal Installer.

Parent topic: Verifying the Installation

Checking the Directory Structure

The contents of your installation vary based on the options that you selected during the installation.

See What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware.

Parent topic: Verifying the Installation

Viewing the Contents of the Oracle Home

You can view the contents of the Oracle home directory by using the viewInventory script.

See Viewing the Contents of an Oracle Home in Installing Software with the Oracle Universal Installer.

Parent topic: Verifying the Installation

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.

Parent topic: Installing the Oracle WebCenter Sites Software

Installing and Configuring a Certified Database

Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

Note:

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must modify the wallet settings and set the environment variables, and apply patches on ORACLE HOME. For more information, see Settings to connect to Autonomous Transaction Processing Database and Applying Patches on ORACLE HOME.

See Understanding Database Requirements for an Oracle Fusion Middleware Installation.

Parent topic: Creating the Database Schemas

Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.

To start the RCU:

  1. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.4.0), the certified JDK is 1.8.0_211 and later.
  2. Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
    • (UNIX) setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_211
    • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211
  3. Change to the following directory:
    • (UNIX) ORACLE_HOME/oracle_common/bin
    • (Windows) ORACLE_HOME\oracle_common\bin
  4. Enter the following command:
    • (UNIX) ./rcu
    • (Windows) rcu.bat

Parent topic: Creating the Database Schemas

Navigating the Repository Creation Utility Screens to Create Schemas

Enter required information in the RCU screens to create the database schemas.

Parent topic: Creating the Database Schemas

Introducing the RCU

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

Click Next.

Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

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

  • If you do not have the necessary permissions 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 About System Load and Product Load in Creating Schemas with the Repository Creation Utility.

  • If the DBA has already run the SQL script for System Load, select Perform Product Load.

    Note:

    For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must create schemas as a Normal user, and though, you do not have full SYS or SYSDBA privileges on the database, you must select System Load and Product Load.

Providing Database Connection Details

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

Note:

If you are unsure of the database service name, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, use the database service name, <databasename>_tpurgent or <databasename>_tp, specified in tnsnames.ora. For service name details, see Database Service Names for Autonomous Transaction Processing and Autonomous JSON Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

To create schemas on an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you can specify the connection credentials using only the Connection String option. In this screen, a warning message is displayed. You can ignore the warning and continue with the schema creation. For more information, see SYS DBA Privileges Warning After Applying Patches.

To provide the database connection details:

  1. On the Database Connection Details screen, provide the database connection details.

    For example:

    • Database Type: Oracle Database
    • Connection String Format: Connection Parameters or Connection String
    • Connection String: examplehost.exampledomain.com:1521:Orcl.exampledomain.com
    • Host Name: examplehost.exampledomain.com
    • Port: 1521
    • Service Name: Orcl.exampledomain.com
    • User Name: sys
    • Password: ******
    • Role: SYSDBA

    For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), enter connect string in the following format:

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

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

    Note:

    For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, you must use only one of the database service names, <databasename>_tpurgent or <databasename>_tp, specified in tnsnames.ora. For database service name details, see Database Service Names for Autonomous Transaction Processing and Autonomous JSON Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

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

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

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

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

  2. Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.
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

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 details about schemas, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

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.

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.

Note:

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), the schema password must be minimum 12 characters, and must contain at least one uppercase, one lower case, and one number.

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.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU.

To complete schema creation:
  1. On the Map Tablespaces screen, select Encrypt Tablespace if you want to encrypt all new tablespaces that the RCU creates.
  2. In the Completion Summary screen, click Close to dismiss the RCU.

    For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, in the Map Tablespaces screen you must override the default tablespaces and the temporary tablespaces, and also override the additional tablespaces, if applicable. See Map Tablespaces.

    If you encounter any issues when you create schemas on an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), see Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database in Creating Schemas with the Repository Creation Utility and Issues Related to Product Installation and Configuration on an Autonomous Database in Release Notes for Oracle Fusion Middleware Infrastructure.

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

Parent topic: Installing the Oracle WebCenter Sites Software

Navigating the Configuration Wizard Screens to Create and Configure the Domain

Enter required information in the Configuration Wizard screens 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.

Parent topic: Installing the Oracle WebCenter Sites Software

Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

  1. Change to the following directory:

    (UNIX) ORACLE_HOME/oracle_common/common/bin

    (Windows) ORACLE_HOME\oracle_common\common\bin

    where ORACLE_HOME is your 12c (12.2.1.4.0) Oracle home.

  2. Enter the following command:

    (UNIX) ./config.sh

    (Windows) config.cmd

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Selecting the Domain Type and Domain Home Location

Use the Configuration Type screen to 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.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Configuring High Availability Options

Use this screen to configure service migration and persistence settings that affect high availability. This screen appears for the first time when you create a cluster that uses automatic service migration, persistent stores, or both, and all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

Enable Automatic Service Migration

Select Enable Automatic Service Migration to enable pinned services to migrate automatically to a healthy Managed Server for failover. It configures migratable target definitions that are required for automatic service migration and the cluster leasing. Choose one of these cluster leasing options:

  • Database Leasing - Managed Servers use a table on a valid JDBC System Resource for leasing. Requires that the Automatic Migration data source have a valid JDBC System Resource. If you select this option, the Migration Basis is configured to Database and the Data Source for Automatic Migration is also automatically configured by the Configuration Wizard. If you have a high availability database, such as Oracle RAC, to manage leasing information, configure the database for server migration according to steps in High-availability Database Leasing.

  • Consensus Leasing - Managed Servers maintain leasing information in-memory. You use Node Manager to control Managed Servers in a cluster. (All servers that are migratable, or which could host a migratable target, must have a Node Manager associated with them.) If you select this option, the Migration Basis is configured to Consensus by the Configuration Wizard.

See Leasing for more information on leasing.

See Service Migration for more information on Automatic Service Migration.

JTA Transaction Log Persistence

This section has two options: Default Persistent Store and JDBC TLog Store.

  • Default Persistent Store - Configures the JTA Transaction Log store of the servers in the default file store.

  • JDBC TLog Store - Configures the JTA Transaction Log store of the servers in JDBC stores.

Oracle recommends that you select JDBC TLog Store. When you complete the configuration, you have a cluster where JDBC persistent stores are set up for Transaction logs.

For more details on persistent and TLOG stores, see the following topics in Developing JTA Applications for Oracle WebLogic Server:

JMS Service 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. You can use a JMS file store for paging of messages to disk when memory is exhausted.

  • JMS File Store - Configures a component to use JMS File Stores. If you select this option, you can choose the File Store option in the Advanced Configuration Screen to change the settings, if required. In the File Stores screen, you can set file store names, directories, and synchronous write policies.

  • JMS JDBC Store - Configures a component to use JDBC stores for all its JMS servers. When you complete the configuration, you have a cluster and JDBC persistent stores are configured for the JMS servers.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.4.0 [wcsites]

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

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

  • Oracle WebCenter Sites - SiteCapture - 12.2.1.4.0 [wcsites]

  • Oracle Enterprise Manager -12.2.1.4.0 [em]

  • Oracle JRF - 12.2.1.4.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12.2.1.4.0 [wlserver]

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Selecting the Application Home Location

Use the Application Location screen to 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.

For more about the Application home directory, see About the Application Home Directory.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

For an Autonomous Transaction Processing database, (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must select only the RCU Data option.

After selecting RCU Data, specify details 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 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 Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle 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:

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

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

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

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

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

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

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 .

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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 Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle 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: 

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

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

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

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

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

jdbc:oracle:thin:@dbname_medium?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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Testing the JDBC Connections

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

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

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

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

  • Topology

    Required to configure the WebCenter Sites Managed Server.

Optionally, select other available options as required for your desired installation environment. The steps in this guide describe a standard installation topology, but you may choose to follow a different path. If your installation requirements extend to additional options outside the scope of this guide, you may be presented with additional screens to configure those options. For information about all Configuration Wizard screens, see Configuration Wizard Screens in Creating WebLogic Domains Using the Configuration Wizard.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Configuring the Administration Server Listen Address

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

Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

For more information about 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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Configuring Managed Servers for WebCenter Sites

Use the Managed Servers screen to configure multiple Managed Servers.

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-SVR 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-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 Managed Server names are example names; this guide references them in other topics. If you choose different names, be sure to substitute them for the example names.

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

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 on server groups, 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 Managed Server names are example names; this guide references them in other topics. If you choose different Managed Server names, be sure to substitute them for the example names as needed.

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

Configuring Managed Servers for Oracle WebCenter Sites: Satellite Server

Use this screen to configure a Managed Server.

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 about managed servers, 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.

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

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 about server groups, 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.

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

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.

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 about clusters, see Create and Configure Clusters in Oracle WebLogic Server Administration Console Online Help.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Defining Server Templates

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

To continue configuring the domain, click Next.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Assigning WebCenter Sites Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to a new configured cluster. A configured cluster is a cluster you configure manually. You do not use this screen if you are configuring a dynamic cluster, a cluster that contains one or more generated server instances that are based on a server template.

For more on configured cluster and dynamic cluster terms, see About Dynamic Clusters in Understanding Oracle WebLogic Server.

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 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 a generic example of the Clusters pane after Managed Servers are assigned to clusters.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

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

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

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 about scale out steps, 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 a machine name, such as 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.
  5. Repeat these steps to add more machines, if required.

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.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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 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 all Managed Servers to their respective machines.

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Virtual Targets

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

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

Note:

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Partitions

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

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

Note:

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

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

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.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain

Completing WebCenter Sites Configuration

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

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

  • Domain Location

    — Needed to access scripts that start Node Manager and Administration Server.

  • Administration Server URL

    — Needed to access the Administration Server.

Links at the bottom of the screen go to this guide and the Satellite Server Guide

Click Finish to dismiss the Configuration Wizard and continue installation.

Parent topic: Navigating the Configuration Wizard Screens to Create and Configure the Domain