12 Extending the Domain to Include Oracle WebCenter Content

You need to perform certain tasks in order to extend the enterprise deployment domain with the Oracle WebCenter Content software. This includes installing the WebCenter Content, extending the domain for WebCenter Content and completing post-configuration and verification tasks.

This chapter provides information on installing the WebCenter Content, extending the domain for WebCenter Content and completing post-configuration and verification tasks.

Synchronizing the System Clocks

Verify that the system clocks on each host computer are synchronized.

Oracle recommends the use of the Network Time Protocol (NTP). See Configuring a Host to Use an NTP (time) Server.

To verify the time synchronization, query the NTP service by running the chronyc -n tracking command on each host.

Sample output:

$chronyc -n tracking
Reference ID : A9FEA9FE (169.254.169.254)
Stratum : 3
Ref time (UTC) : Tue Jan 14 15:28:01 2025
System time : 0.000043127 seconds fast of NTP time
Last offset : +0.000034640 seconds
 
...

Installing WebCenter Content for an Enterprise Deployment

The procedure for installing WebCenter Content in an enterprise deployment domain is explained in this section.

This section contains the following procedures.

Starting the Oracle WebCenter Content Installer on WCCHOST1

To start the installation program:

1. Log in to WCCHOST1.
2. Go to the directory where you downloaded the installation program.
3. Launch the installation program by invoking the java executable from the JDK directory on your system, as shown in the example below.

   $JAVA_HOME/bin/java -jar Installer File Name

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

   Replace Installer File Name with the name of the actual installer file for your product listed in Identifying and Obtaining Software Distributions for an Enterprise Deployment.

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

Navigating the Installation Screens

The installation program displays a series of screens, in the order listed in the following table.

If you need additional help with any of the installation screens, click the screen name.

Screen	Description
Installation Inventory Screen	If you did not create a central inventory when you installed the Oracle Fusion Middleware Infrastructure software, then this dialog box appears. Edit the Inventory Directory field so it points to the location of your local inventory, and then click OK.
Welcome	This screen introduces you to the product installer.
Auto Updates	Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization.
Installation Location	Use this screen to specify the location of your Oracle home directory. For more information about Oracle Fusion Middleware directory structure, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware.
Prerequisite Checks	This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, you can refer to one of the documents in the Roadmap for Verifying Your System Environment section in Planning Your Oracle Fusion Middleware Infrastructure Installation.
Installation Summary	Use this screen to verify the installation options you selected. Click Install to begin the installation.
Installation Progress	This screen allows you to see the progress of the installation. Click Next when the progress bar reaches 100% complete.
Installation Complete	Review the information on this screen, then click Finish to dismiss the installer.

Installing Oracle WebCenter Content on the Other Host Computers

If you have followed the EDG shared storage recommendations, there is a separate shared storage volume for product installations on WCCHOST2, and you must also install the software on WCCHOST2. See Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

Verifying the Installation

After you complete the installation, you can verify it by successfully completing the following tasks.

Reviewing the Installation Log Files

Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see Understanding Installation Log Files in Installing Software with the Oracle Universal Installer.

Checking the Directory Structure

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

The addition of Oracle WebCenter Content will add the following directory and sub-directories:

/u01/oracle/products/fmw/wccontent
axf
common
ipm
plugins
ucm
wccadf
wccadfrui

/u01/oracle/products/fmw/wccapture
capture
common
plugins

For more information about the directory structure you should see after installation, see "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware.

Viewing the Contents of Your Oracle Home

You can also view the contents of your Oracle home by using the viewInventory script. See Viewing the contents of an Oracle home in Installing Software with the Oracle Universal Installer.

Creating the Oracle WebCenter Content Database Schemas

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

Follow the instructions in this section to install the schemas.

Starting the Repository Creation Utility (RCU)

To start the Repository Creation Utility (RCU):

1. Navigate to the $ORACLE_HOME/oracle_common/bin directory on your system.
2. Make sure 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 /u01/oracle/products/jdk:

   On UNIX operating systems:

   export JAVA_HOME=/u01/oracle/products/jdk

3. Start RCU:

   On UNIX operating systems:

   ./rcu

   Note:

   If your database has Transparent Data Encryption (TDE) enabled, and you want to encrypt your tablespaces that are created by the RCU, provide the -encryptTablespace true option when you start RCU.

   This defaults the appropriate RCU GUI Encrypt Tablespace checkbox selection on the Map Tablespaces screen without further effort during the RCU execution. See Encrypting Tablespaces in Creating Schemas with the Repository Creation Utility.

Navigating the RCU Screens to Create the Schemas

After you start the RCU, you can then use the wizard screens to select and install the required schemas for your Oracle Fusion Middleware product. Schema creation involves the following tasks.

Task 1   Introducing RCU

Click Next.

Task 2   Selecting a Method of Schema Creation

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 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 will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.

Task 3   Providing Database Connection Details

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

In the Database Type, select Oracle Database enabled for edition-based redefinition.

Note:

Oracle Database enabled for edition-based redefinition (EBR) is recommended to support Zero Down Time upgrades. For more information, see https://www.oracle.com/database/technologies/high-availability/ebr.html.

In the Host Name field, enter the SCAN address of the Oracle RAC Database.

Enter the Port number of the RAC database scan listener, for example 1521.

Enter the RAC Service Name of the database.

Enter the User Name of a user that has permissions to create schemas and schema objects, for example SYS.

Enter the Password of the user name you provided.

If you have selected the SYS user, ensure that you set the role to SYSDBA.

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

Task 4   Specifying a Custom Prefix and Selecting Schemas

Select existing prefix, and select the prefix you created while configuring the initial domain.

From the list of schemas, expand the WebCenter Content schema section and select only the Oracle WebCenter Content Server - Complete schema.

The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.

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.

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.

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

Task 5   Specifying Schema Passwords

Specify how you want to set the schema passwords on your database, then specify 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.

Task 6   Verifying the Tablespaces for the Required Schemas

On the Map Tablespaces screen, review the information, and then click Next to accept the default values.

Click OK in the confirmation dialog box.

Task 7   Completing Schema Creation

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

Task 8   Verifying the Schema Creation

To verify that the schemas were created successfully, and to verify the database connection details, use SQL*Plus or another utility to connect to the database, using the OCS schema name and the password you provided.

For example:

./sqlplus FMW1412_WLS/<wcpinfra_password>

SQL*Plus: Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems on Wed Sep 11 14:20:00 2024 Version 23.5.0.24.07
Copyright (c) 1982, 2024, Oracle. All rights reserved.


Connected to:
Oracle Database 23ai EE Extreme Perf Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems
Version 23.5.0.24.07

SQL>

Extending the Domain for WebCenter Content

You need to perform the following tasks in order to extend the existing enterprise deployment domain with the Oracle WebCenter Content software.

Extending the domain involves the following tasks.

Starting the Configuration Wizard

Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain.

Note:

If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh and configure it, for example, add custom libraries to the WebLogic Server classpath, specify Additional JAVA command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

For more information about using the setUserOverridesLate script with this Enterprise Deployment Guide, see Customizing Server Parameters with the setUserOverridesLate Script.

To start the Configuration Wizard:

1. Stop any managed servers that are modified by this domain extension. Managed Servers that are not effected can remain on-line.
2. For any managed servers to be modified, verify that the managed server shutdown has completed.
3. Stop the Administration Server once all managed servers are in a steady state.
4. Navigate to the following directory and start the WebLogic Server Configuration Wizard.

   cd ORACLE_HOME/oracle_common/common/bin
   ./config.sh

Navigating the Configuration Wizard Screens to Extend the Domain with WebCenter Content

Domain extension and configuration includes the following tasks:

• Task 1, "Selecting the Domain Type and Domain Home Location"

• Task 2, "Selecting the Configuration Template"

• Task 3, "Configuring High Availability Options"

• Task 4, "Specifying the Database Configuration Type"

• Task 5, "Specifying JDBC Component Schema Information"

• Task 6, "Providing the GridLink Oracle RAC Database Connection Details"

• Task 7, "Testing the JDBC Connections"

• Task 8, "Selecting Advanced Configuration"

• Task 9, "Configuring Managed Servers"

• Task 10, "Configuring a Cluster"

• Task 11, "Assigning Server Templates"

• Task 12, "Configuring Dynamic Servers"

• Task 13, "Assigning Managed Servers to the Cluster"

• Task 14, "Configuring Coherence Clusters"

• Task 15, "Creating Machines for WebCenter Content Servers"

• Task 16, "Assigning Servers to Machines"

• Task 17, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 18, "Writing Down Your Domain Home and Administration Server URL"

• Task 19, "Start the Administration Server"

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Update an existing domain.

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration domain home you created as part of the initial domain.

For more information about the directory location variables, see File System and Directory Variables Used in This Guide.

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.

Task 2   Selecting the Configuration Template

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

• Oracle Universal Content Management - Content Server - [wccontent]

  In addition, the following additional templates should already be selected, because they were used to create the initial Infrastructure domain:

  • Oracle Enterprise Manager - [em]

  • Oracle JRF - [oracle_common]

  • WebLogic Coherence Cluster Extension - [wlserver]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Configuring High Availability Options

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply HA options (that is, the Configuration Wizard creates the JDBC stores and configures ASM for them).

On the High Availability Options screen:

• Select Enable Automatic Service Migration with Database Basis.

• Set JTA Transaction Log Persistence to JDBC TLog Store.

• Set JMS Server Persistence to JMS JDBC Store.

Note:

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an oracle database and makes resources available for all the servers in the cluster. So, the Configuration Wizard steps assume that the JDBC persistent stores are used along with Automatic Service Migration.

When you choose JDBC persistent stores, additional unused File Stores are automatically created but are not targeted to your clusters. Ignore these File Stores.

If, for any reason, you want to use Files Stores, you can retain the default values for TLOGs and JMS persistent store options in this screen and configure them in a shared location later. See Task 8, "Selecting Advanced Configuration". Shared location is required to resume JMS and HA in a failover scenario.

You can also configure TLOGs and JMS persistent stores manually in a post step. For information about the differences between JDBC and Files Stores, and for specific instructions to configure them manually, see Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Click Next.

Task 4   Specifying the Database Configuration Type

On the Database Configuration Type screen, select RCU Data.

All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.

Verify and ensure that credentials in all the fields are the same that you have provided while configuring the Oracle Fusion Middleware Infrastructure.

Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operating 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 the other options on this screen, see "Datasource Defaults" in Creating WebLogic Domains Using the Configuration Wizard.

Task 5   Specifying JDBC Component Schema Information

On the JDBC Component Schema screen, select all the UCM schemas (for WebCenter Content) in the table.

When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.

Click Convert to GridLink and click Next.

Task 6   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information that is required to connect to the RAC database and component schemas, as shown in the following table.

Element	Description and Recommended Value
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521)
ONS Host and Port	These values are not required when you are using an Oracle 12c database or later versions because the ONS list is automatically provided from the database to the driver.
Enable Fan	Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.

Task 7   Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source connections you have just configured.

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.

Tip:

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

Task 8   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

• Topology

Task 9   Configuring Managed Servers

On the Managed Servers screen, a new Managed Server for Oracle WebCenter Content appears in the list of servers.

Perform the following tasks to modify the default Oracle WebCenter Content Managed Server and create a second Managed Server:

1. Rename the default Managed Server to WLS_WCC1.

2. Click Add to create a new Managed Server and name it WLS_WCC2.

   Tip:

   The server names recommended here will be used throughout this document; if you choose different names, be sure to replace them as needed.

3. Use the information in the following table to fill in the rest of the columns for each Oracle WebCenter Content Managed Server.

Server Name	Listen Address	Listen Port	Enable SSL	SSL Listen Port	Administration Port	Server Groups
WLS_WCC1	WCCHOST1	Disabled	Checked	16251	9005	UCM-MGD-SVR
WLS_WCC2	WCCHOST2	Disabled	Checked	16251	9005	UCM-MGD-SVR

Tip:

More information about the options on the Managed Server screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

Task 10   Configuring a Cluster

In this task, you create a cluster of Managed Servers to which you can target the Oracle WebCenter Content software.

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify WCC_Cluster in the Cluster Name field.

3. Specify wcp.example.com in the Frontend Host field.

4. Leave the Frontend HTTP Port blank and use 443 (or your precise LBS listeners port for app requests) as the Frontend HTTPS port.

Note:

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

Tip:

More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 11   Assigning Server Templates

Click Next to proceed to the next screen.

Task 12   Configuring Dynamic Servers

Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.

1. Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.

2. Confirm the Server Template selection is Unspecified.

3. Click Next.

Task 13   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign WLS_WCC1 and WLS_WCC2 to the new cluster, WCC_Cluster:

1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, WCC_Cluster.

2. In the Servers pane, assign WLS_WCC1 to WCC_Cluster by doing one of the following:

   • Click once on the WLS_WCC1 Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane.

   • Double-click on WLS_WCC1 to move it beneath the selected cluster in the clusters pane.

3. Repeat to assign WLS_WCC2 to WCC_Cluster.

4. Click Next to proceed to the next screen.

Tip:

More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 14   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Update the port number value to 9991.

Note:

For Coherence licensing information, refer to Oracle Coherence in Oracle Fusion Middleware Licensing Information.

Task 15   Creating Machines for WebCenter Content Servers

If required, use the Machines screen to add two new Unix Machines:

1. On the Unix Machines tab, click the Add button.

2. Enter WCCHOST1 in the Name field.

3. Enter the host name of WCCHOST1 for the Node Manage Listener address. Leave the Node Manager port to the default value of 5556.

4. Repeat the above steps for WCCHOST2.

Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain, as shown in the following table.

Click Next to proceed.

Name	Node Manager Listen Address	Node Manager Listen Port
WCCHOST1	The value of the WCCHOST1 host name variable. For example, WCCHOST1.example.com.	5556
WCCHOST2	The value of the WCCHOST2 host name variable. For example, WCCHOST2.example.com.	5556

Task 16   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Oracle WebCenter Content Managed Servers you just created to the corresponding machines in the domain. Use a similar process as when assigning managed servers to the cluster. See Task 13, "Assigning Managed Servers to the Cluster".

Assign WLS_WCC1 to WCCHOST1, and assign WLS_WCC2 to WCCHOST2.

Tip:

More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 17   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Click Update to execute the domain extension.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Task 18   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the following items about the domain you just configured:

• Domain Location

• Administration Server URL

You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.

Click Finish to dismiss the configuration wizard.

Task 19   Start the Administration Server

Start the Administration Server, login, and then verify the clusters and servers views to ensure that the changes made to the domain have been applied.

After you have completed extending the domain with static clusters, go to Completing Postconfiguration and Verification Tasks for WebCenter Content.

Update Certificates for New Frontend Addresses

This section contains information about certificates for new frontend addresses.

Note:

About Certificates for the domain extension. Since the WCC and WSM servers use the same listen addresses (different port), there is no need to create new certificates and update stores. However, the WCC cluster uses a different front end address that will be added as a trusted endpoint in the Configuring the Web Tier for the Extended Domain.

Update the WebLogic Servers Security Settings

This section contains information about WebLogic Servers security settings.

Follow the steps described in the Updating the WebLogic Servers Security Settings and update SSL settings for the WLS_WCC1 and WLS_WCC2 servers.

Completing Postconfiguration and Verification Tasks for WebCenter Content

Several configuration and validation steps must be performed to bring the content servers online. Complete the following sections in the order listed.

Propagating the Extended Domain to the Domain Directories and Machines

Propagate the start scripts and classpath configuration from the Administration Server's domain directory to the Managed Server domain directory.

To propagate the domain configuration to the WebCenter Content Managed Servers, complete the following steps:

1. Create a copy of the Managed Server domain directory and the Managed Server applications directory.
2. Run the following pack command on WCCHOST1 to create a template pack:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./pack.sh -managed=true 
             -domain=ASERVER_HOME 
             -template=/full_path/edgdomaintemplateExtWCC.jar 
             -template_name=edgdomain_templateExtWCC

   In this example:

   • Replace ASERVER_HOME with the actual path to the domain directory you created on the shared storage device.

   • Replace full_path with the complete path to the location where you want to create the domain template jar file. You will need to reference this location when you copy or unpack the domain template jar file. It is recommended to choose a shared volume other than ORACLE_HOME, or write to /tmp/ and copy the files manually between servers.

     You must specify a full path for the template jar file as part of the -template argument to the pack command:

     SHARED_CONFIG_DIR/domains/template_filename.jar

   • edgdomaintemplateExtWCC.jar is a sample name for the JAR file you are creating, which will contain the domain configuration files, including the configuration files for the Oracle HTTP Server instances.

   • edgdomain_templateExtWCC is the name assigned to the domain template file.

3. Run the following unpack command on WCCHOST1 to propagate the template created in the preceding step to the MSERVER_HOME directory:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=MSERVER_HOME 
               -template=/full_path/edgdomaintemplateExtWCC.jar 
               -app_dir=APPLICATION_HOME 
               -overwrite_domain=true
   

   In this example:

   • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

   • edgdomaintemplateExtWCC.jar is the directory path and name of the template you created when you ran the pack command to pack up the domain on the shared storage device.

   • The -overwrite_domain=true argument is necessary when you are unpacking a managed server template into an existing domain and existing applications directories.

     For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation.

   • Replace APPLICATION_HOME with the complete path to the Application directory for the domain on local storage.

   Tip:

   For more information about the pack and unpack commands, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

4. If the full path to the packed jar file is on a shared volume available to the other servers, skip this step. Otherwise, run the following command on WCCHOST1 to copy the template pack created in step 1 to WCCHOST2. The WCPHOSTn servers do not need the domain configuration at this time.

   scp /full_path/edgdomaintemplateExtWCC.jar oracle@WCCHOST2:/full_path/
   

5. Run the following unpack command on each of the remote hosts to deploy the domain template copied in the preceding step to the MSERVER_HOME directory:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=MSERVER_HOME 
               -template=/full_path/edgdomaintemplateExtWCC.jar 
               -app_dir=APPLICATION_HOME 
               -overwrite_domain=true
   

   In this example:

   • Replace MSERVER_HOME with the complete path to the domain home to be created on the local storage disk. This is the location where the copy of the domain will be unpacked.

   • edgdomaintemplateExtWCC.jar is the directory path and name of the template you created when you ran the pack command to pack up the domain on the shared storage device.

   • The -overwrite_domain=true argument is necessary when you are unpacking a managed server template into an existing domain and existing applications directories.

     For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation.

   • Replace APPLICATION_HOME with the complete path to the Application directory for the domain on local storage.

   Tip:

   For more information about the pack and unpack commands, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

Modifying the Upload and Stage Directories to an Absolute Path

After you configure the domain and unpack it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters. See Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment.

Starting the WLS_WCC1 Managed Server

To start the WLS_WCC1 Managed Server:

1. Enter the following URL into a browser to display the Fusion Middleware Control login screen:

   https://admin.example.com:445/em

2. Sign in to the Fusion Middleware Control by using the administrator's account. For example: weblogic_wcp.
3. In the Target Navigation pane, expand the domain to view the Managed Servers in the domain.
4. Select only the WLS_WCC1 Managed Server and click Start Up on the Oracle WebLogic Server toolbar. When the startup operation is complete, navigate to the Domain home page and verify that the WLS_WCC1 Managed Server is up and running.

Configuring the Content Server on WLS_WCC1 Managed Server

To configure Content Server:

1. Create the runtime cluster subdirectories required for the Oracle WebCenter Content cluster configuration.

   The Oracle WebCenter Content configuration files are on a shared disk so that all members of the cluster can access them. The shared disk location of the Oracle WebCenter Content enterprise deployment is located at ORACLE_RUNTIME/WCDomain/WCC_Cluster.

   Run the following commands to create the required subdirectories:

   mkdir -p ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/vault 
   mkdir -p ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/weblayout 
   mkdir -p ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/data/users/profiles

2. Log in to WLS_WCC1 at https://wcchost1:16201/cs using the weblogic user name and password to display a configuration page.
   The Oracle WebCenter Content configuration files are on a shared disk so that all members of the cluster can access them. The shared disk location of the Oracle WebCenter Content enterprise deployment is at ORACLE_RUNTIME/wcpedg_domain/WCC_Cluster.
3. Change the following values on the server configuration page:
   Make sure that the Is new Content Server Instance? check box is selected.
   • Content Server Instance Folder: Set this to ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/

     For example:/u01/oracle/runtime/wcpedg_domain/WCC_Cluster/cs/

   • Native File Repository Location: Set this to ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/vault/

     For example:/u01/oracle/runtime/wcpedg_domain/WCC_Cluster/cs/vault/

   • WebLayout Folder: Set this to ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/weblayout/

     For example:/u01/oracle/runtime/wcpedg_domain/WCC_Cluster/cs/weblayout/

   • User Profile Folder: Set this to ORACLE_RUNTIME/domain_name/WCC_Cluster/cs/data/users/profiles/

     For example:/u01/oracle/runtime/wcpedg_domain/WCC_Cluster/cs/data/users/profiles/

   • Server Socket Port: 4444
   • Incoming Socket Connection Address Security Filter: A pipe-delimited list of the local host and the server IP addresses:

     127.0.0.1|0:0:0:0:0:0:0:1|WCCHOST1-IP|WCCHOST2-IP|WCPHOST1-IP|WCPHOST2-IP|WEBHOST1-IP|WEBHOST2-IP|wcp.example.com-IP|wcpinternal.example.com-IP|load-balancer-host-IP

     Note:

     Must use IP addresses for all entries, including the load-balancer IP addresses for the internal virtual server and the primary interface depending on network address translation configuration settings at the load-balancer.
   • WebServer HTTP/HTTPS Address: wcp.example.com:443
   • Web Address is HTTPS: Select this checkbox.
   • Server Instance Name: WCC_Cluster
   • Server Instance Label: WCC_Cluster
   • Server Instance Description: WebCenter Content cluster
   • Auto_Number Prefix: WCC_Cluster-
4. Click Submit when finished.
5. Restart the Managed Server by using the WebLogic Remote Console.

Updating the cwallet File in the Administration Server

Content Server updates the cwallet.sso file located in the MSERVER_HOME/config/fmwconfig directory when it starts. This change needs to be propagated back to the Administration Server.

When adding WebCenter Content to a WebCenter Portal enterprise deployment, you will have to copy the cwallet file from the WC Content host (WCCHOST1) to ASERVER_HOME configuration directory on the server where the Administration Server is running. In the case of the EDG topology, both locations are on WCCHOST1 in this release.

To do this, on WCCHOST1, copy the cwallet.sso file to ASERVER_HOME/config/fmwconfig/ using the following command (note the back-slash for multi-line format):

cp MSERVER_HOME/config/fmwconfig/cwallet.sso \       
ASERVER_HOME/config/fmwconfig/cwallet.sso

Note:

If any operation is performed in a WLS_WCCn server that modifies the cwallet.sso file in the MSERVER_HOME/config/fmwconfig/ directory, the file will have to be immediately copied to the Administration Server domain configuration directory on WCCHOST1 at ASERVER_HOME/config/fmwconfig.

Starting the WLS_WCC2 Managed Server

To start and validate the WLS_WCC2 Managed Server, use the procedure in Starting and Validating the WLS_SOA1 Managed Server for WLS_SOA2 Managed Server.

Configuring the Content Server on WLS_WCC2 Managed Server

To configure Content Server:

1. Log in to WLS_WCC2 at https://wcchost2:16201/cs using the weblogic administration user name and password to display a configuration page.
   The Oracle WebCenter Content configuration files are on a shared disk so that all members of the cluster can access them. The shared disk location of the Oracle WebCenter Content enterprise deployment is at ORACLE_RUNTIME/WCDomain/WCC_Cluster.
2. Change the following values on the server configuration page:
   • Content Server Instance Folder: Set this to ORACLE_RUNTIME/WCDomain/WCC_Cluster/cs.
   • Native File Repository Location: Set this to ORACLE_RUNTIME/WCDomain/WCC_Cluster/cs/vault.
   • WebLayout Folder: Set this to ORACLE_RUNTIME/WCDomain/WCC_Cluster/cs/weblayout.
   • User Profile Folder: Set this to ORACLE_RUNTIME/WCDomain/WCC_Cluster/cs/data/users/profiles.
   • Content Server URL Prefix: /cs/ (default value)
   Make sure that the Is new Content Server Instance? check box is not selected.
3. Click Submit when finished.
4. Restart the Managed Server by using the WebLogic Remote Console.

Configuring Additional Parameters

Using a text editor, add the following options to each cluster node's MSERVER_HOME/ucm/cs/bin/WLS_WCCn_intradoc.cfg file, where the directories specified are on a direct-bus-attached-controlled local disk and not a remote file system, such as a UNIX/Linux mounted NFS or clustered file system (like OCFS2, GFS2, or GPFS):

TraceDirectory=MSERVER_HOME/servers/WLS_WCCN/logs
EventDirectory=MSERVER_HOME/servers/WLS_WCCN/logs/event/
ArchiverDoLocks=true 
DisableSharedCacheChecking=true 

The trailing N should match your nodes server names, like WLS_WCC1 is for WCCHOST1 and WLS_WCC2 is for WCCHOST2, and so on.

These changes will take effect after a restart of all WebCenter Content Managed Servers, at the end of the procedure described in Granting the WebCenter Content Administrative Roles via Credential Map section.

Note:

The directories can reside in any local disk path that you have determined to have enough space to hold the WebCenter Content logs and any trace that you may configure. The preceding paths are a suggestion.

Configuring Service Retries for Oracle WebCenter Content

The following parameter should be set in the Content Server config.cfg file to enable login retries during an Oracle RAC failover:

ServiceAllowRetry=true

If this value is not set, users will need to manually retry any operation that was in progress when the failover began.

To configure service retries for Oracle WebCenter Content:

1. Go to Content Server at https://WCCHOST1:16201/cs, and log in using the non-LDAP WebLogic Server administration user name (for example, weblogic) and password.
2. From the Administration tray or menu, choose Admin Server, then General Configuration.
3. On the General Configuration page, add the following parameter in the Additional Configuration Variables box:

   ServiceAllowRetry=true

4. Click Save.

   These changes will take effect after a restart of all WebCenter Content Managed Servers, at the end of the procedure described in Granting the WebCenter Content Administrative Roles via Credential Map section.

   Note:

   The new parameter is included in the config.cfg file, which is at the following location:

   ORACLE_RUNTIME/domain_name/cluster_name/cs/config/config.cfg

   (You can also edit this file directly in a text editor. Remember to restart all WebCenter Content Managed Servers.

Granting the WebCenter Content Administrative Roles through Credential Map

You must configure the Credential map to grant the Content Server administrative roles to the WCPAdministrators LDAP group.

The WCPAdministrators LDAP group is created in the Provisioning an Enterprise Deployment Administration User and Group section completed earlier. This configuration of credential map ensures consistent use of the LDAP administrative user for all configuration, administration, and maintenance tasks.

To configure a credential map and provide the necessary role grants to the LDAP-based WCPAdministrators group:

1. Log in to content server using the weblogic account.
2. Expand the Administration menu, select Credential Maps.
3. In the Map Identifier Field, enter a name for the new credential map: LDAPAdmins.
4. Add the following lines to map the LDAP group to the multiple administrative roles:

   # Assign full set of administration roles to the LDAP WCPAdministrators group
        WCPAdministrators, admin
        WCPAdministrators, sysmanager
        WCPAdministrators, refineryadmin
        WCPAdministrators, rmaadmin
        WCPAdministrators, pcmadmin
        WCPAdministrators, ermadmin
   # Allow existing roles to propagate without mappings
        |#all|             , %%
   #
   # Comment the following if you are not implementing Accounts in Content Server
        WCPAdministrators, @#all(RWDA)
        WCPAdministrators, @#none(RWDA)

   Note:

   If you are not implementing Accounts, comment out the last two lines of the previous example.
5. Click Update.
6. Navigate to Administration > Providers.
7. Click the info link for the existing JPS provider.
8. Make sure that the Credential Map parameter does not already have a map identifier listed.
9. Click the Edit button.
10. Enter the name of the Map Identifier from step 3 above as the Credential Map value.

    Note:

    Double-check the value entered for any typos, extra characters, and so on. If this is set incorrectly, you will not be able to log-in to your content server instances.
11. Click Update.
12. Repeat a modified process for the content server on WCCHOST2.

    1. Confirm that the LDAPAdmins credential map is already available for selection on the Credential Maps view.

    2. Repeat the edit of the JpsUserProvider noting that even though the correct LDAPAdmins credential Map value appears in the form automatically, it must still be submitted on each server to take effect.

13. Restart the managed servers in the WCC_Cluster.
14. Log in to each content server using the weblogic_wcp LDAP user and verify that the administrative menu options appear in the user interface.

    Note:

     If the provider configuration was entered incorrectly and you can no longer log-in, the jpsuserprovider data file needs to be corrected manually.  In this case, shutdown all content server instances and edit the value of the ProviderCredentialsMap parameter in ORACLE_RUNTIME/DOMAIN_NAME/WCC_Cluster/cs/data/providers/jpsuserprovider/provider.hda, and restart/test one server instance at a time.

Configuring Oracle HTTP Server for the WebCenter Content Cluster

The instructions for configuring Oracle HTTP Server for the WebCenter Content Cluster are available in this section.

Generate the Required Certificates for OHS SSL Listeners

Follow the steps described in the Generate Required Certificates for OHS SSL Listeners section in Starting the Oracle HTTP Server Instances to add the new fronted address to the certificate stores and update the SAN for the OHS listeners certs.

When asked to replace the existing OHS Virtual Host certificates, answer yes so that they are updated with the new frontend address for the WCC cluster as SAN.

Configuring Oracle HTTP Server for the WLS_WCC Managed Servers

To configure the Oracle HTTP Server instances in the web tier so they route requests correctly to the Oracle WebCenter Content cluster, use the following procedure to create an additional Oracle HTTP Server configuration file that creates and defines the parameters of the wcp.example.com virtual server. To configure Oracle HTTP Server for the WLS_WCC Managed Servers:

1. Log in to WEBHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (ohs1).
2. Copy the existing admin_vh.conf file to the wcp_vh.conf file. This will transfer most of the required SSL configuration:

   cp admin_vh.conf wcp_vh.conf

3. Edit the file and and customize with the required values for Listen, ServerName, VirtualHost, SSLWallet and Location directives.

   
   #[Listen] OHS_SSL_PORT
   
   Listen WEBHOST1:4443
   ##
   ## SSL Virtual Host Context
   ##
   #[VirtualHost] OHS_SSL_VH
   <VirtualHost WEBHOST1:4443>
   ServerName wcp.example.com:443
     <IfModule ossl_module>
   
      # SSL Engine Switch:
      # Enable/Disable SSL for this virtual host.
      SSLEngine on
   
      # Client Authentication (Type):
      # Client certificate verification type and depth. Types are
      # none, optional and require.
      SSLVerifyClient None
   
      # SSL Protocol Support:
      # Configure usable SSL/TLS protocol versions.
      SSLProtocol TLSv1.2 TLSv1.3
      
      # Option to prefer the server's cipher preference order
      SSLHonorCipherOrder on
      
      # SSL Cipher Suite:
      # List the ciphers that the client is permitted to negotiate.
      SSLCipherSuite TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
      
      #Path to the wallet
      #SSLWallet "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/keystores/default"
      SSLWallet "/u02/oracle/config/keystores/orapki/orapki-vh-WEBHOST1"
            
      <FilesMatch "\.(cgi|shtml|phtml|php)$">
         SSLOptions +StdEnvVars
      </FilesMatch>
   
      <Directory "${ORACLE_INSTANCE}/config/fmwconfig/components/${COMPONENT_TYPE}/instances/${COMPONENT_NAME}/cgi-bin">
         SSLOptions +StdEnvVars
      </Directory>
            BrowserMatch "MSIE [2-5]" \
            nokeepalive ssl-unclean-shutdown \
            downgrade-1.0 force-response-1.0
   
      # Add the following directive to add HSTS
      <IfModule mod_headers.c>
      Header always set Strict-Transport-Security "max-age=63072000; preload; includeSubDomains"
      </IfModule>
   
        <Location /cs>
           WebLogicCluster WCCHOST1:16201,WCCHOST2:16202
           WLSRequest ON
           WLCookieName JSESSIONID
           WLProxySSL ON
           WLProxySSLPassThrough ON
        </Location>
   	 
        <Location /adfAuthentication>
           WebLogicCluster WCCHOST1:16201,WCCHOST2:16202
           WLSRequest ON
           WLCookieName JSESSIONID
           WLProxySSL ON
           WLProxySSLPassThrough ON
        </Location>
   	 
        <Location /_ocsh>
           WebLogicCluster WCCHOST1:16201,WCCHOST2:16202
           WLSRequest ON
           WLCookieName JSESSIONID
           WLProxySSL ON
           WLProxySSLPassThrough ON
        </Location>
   </IfModule>
   </VirtualHost>

4. Copy the wcp_vh.conf file to the configuration directory for the second Oracle HTTP Server instance (ohs2):

   WEB_DOMAIN_HOME/config/fmwconfig/components/ohs2/moduleconf/

5. Edit the wcp_vh.conf and change any references of WEBHOST1 to WEBHOST2 in the <VirtualHost> directives.
6. Restart the Oracle HTTP server instances on WEBHOST1 and WEBHOST2.

Validating Access Through the Load Balancer

You should verify URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to WCC_Cluster.

Verifying the URLs

To verify the URLs:

1. While WLS_WCC2 is running, stop WLS_WCC1 using the WebLogic Remote Console.
2. Access https://wcp.example.com/cs to verify that it is functioning properly.
3. Start WLS_WCC1 from the WebLogic Remote Console.
4. Stop WLS_WCC2 from the WebLogic Remote Console.
5. Access https://wcp.example.com/cs to verify that it is functioning properly.

You can verify the cluster node to which you were directed after the traffic balancing provided through your load balancer and then again through the web tier.

Verifying the Cluster Nodes

To verify the cluster node:

1. Log in to the following WebCenter Content page, using your administrator user and password credentials:

   https://wcp.example.com/cs/idcplg?IdcService=CONFIG_INFO

2. Browse to the Administration/Configuration for WCC_Cluster page.
3. In the Options and Others section of the page, click Java Properties on the right.
4. Obtain the value for weblogic.Name.

   This value denotes the cluster node you are accessing at the moment.

Configuring Oracle WebCenter Content for WebCenter Portal

This section describes tasks required for configuring Oracle WebCenter Content Server for use with WebCenter Portal.

This section includes the following topics.

Enabling Mandatory Content Server Components

For WebCenter Portal, you must enable the following Content Server components:

• WebCenterConfigure - Enable it to configure an instance of Content Server for WebCenter Portal.

• Folders_g or FrameworkFolders - Enable either of these components to specify the folder service configured on Content Server.

  • Folders_g - Provides a hierarchical folder interface to content in Content Server. For an Oracle WebCenter Portal instance patched from an earlier release that used the Folders_g component, you can continue to use Folders_g or choose to migrate to the FrameworkFolders interface. Oracle recommends that you migrate to the FrameworkFolders interface for better performance and so that you can use any new Content Server features.

  • FrameworkFolders - Provides a hierarchical folder interface similar to a conventional file system, for organizing and locating some or all of the content in the repository. FrameworkFolders is a scalable, enterprise solution and is intended to replace Folders_g as the folder service for Content Server. For new installations of Oracle WebCenter Portal, it is recommended that you enable the FrameworkFolders component on Content Server.

    Note:

    Make sure you enable AutoSuggestConfig component before you enable FrameworkFolders component.

For detailed steps, see Enabling Mandatory Components in Administering Oracle WebCenter Portal.

Note:

If Oracle WebCenter Portal is configured to use the Folders_g component, and Folders_g is not enabled, the following exception displays:

SEVERE: UCM feature folders is not installed on server. at
oracle.webcenter.content.integration.spi.ucm.UCMBridge.getBridge(UCMBridge.java:349) ....

If Oracle WebCenter Portal is configured to use the FrameworkFolders component, and FrameworkFolders is not enabled, the following message is displayed:

Foldering service from content server Folders_g and Portal Server Configuration FrameworkFolders do not match

Enabling and Configuring the Dynamic Converter Component

This task is optional, but strongly recommended.

This configuration is required for the Slide Previewer capability in WebCenter Portal, which makes use of the HTML renditions generated on the fly by the Dynamic Converter.

The configuration for the Dynamic Converter consists of two steps: enabling the Dynamic Converter, and defining the file types for which the Dynamic Converter is available. For detailed steps, see the Configuring the Dynamic Converter Component section in Administering Oracle WebCenter Portal.

Configuring Additional Content Server Features

There are several other Content Server features that, while not mandatory, can provide additional functionality in your WebCenter Portal enterprise deployment. For example, you can enable features such as Site Studio, OracleTextSearch, and so on. 

To find out more, and for detailed steps, see the Configuration Roadmap for Content Server section in Administering Oracle WebCenter Portal.

Backing Up the Configuration

It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.

The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.

For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.