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.

Topics:

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

Topics:

12.1.1 Starting the Installation Program

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 -d64 -jar fmw_12.2.1.3.0_wccontent_generic.jar
    

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

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

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

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

12.1.4 Verifying the Installation

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

Topics:

12.1.4.1 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 Oracle Fusion Middleware Installing Software with the Oracle Universal Installer.

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

12.1.4.3 Viewing the Contents of Your Oracle Home

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

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

Topics:

12.2.1 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 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 created by the RCU, provide the -encryptTablespace true option when you start the RCU.

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

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

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

  2. Select Connection Parameters.

  3. Enter the DBMS/Service details.

  4. Enter the Schema Owner and Schema Password details.

  5. 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, select the WebCenter Content schema. This will automatically select the following schemas as dependencies:

  • Oracle WebCenter Content Imaging

  • Oracle WebCenter Content Server - Complete

  • Oracle WebCenter Enterprise Capture

  • Oracle WebCenter Content Server - Search Only

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  

SQL*Plus: Release 12.1.0.1.0 Production on Tue Mar 7 00:28:06 2017  

Copyright (c) 1982, 2013, Oracle. All rights reserved.  

Enter user-name: FMW12213 
Enter password:  

Connected to: 
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production 
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, 
Advanced Analytics and Real Application Testing options  

SQL> exit 
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production 
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, 
Advanced Analytics and Real Application Testing options

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

Topics:

12.3.1 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 will be 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.

To start the Configuration Wizard:

  1. From the WebLogic Server Console, stop any managed servers that will be modified by this domain extension. Managed Servers that are not effected can remain on-line.
  2. For any managed servers to be modified, verify 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
    

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

Follow the instructions in the following sections to extend the domain for the topology with static or dynamic clusters.

Topics:

12.3.2.1 Extending the Domain with Static Clusters

Follow the instructions in this section to extend the domain for the topology with static clusters.

Note:

You can use the procedure described in this section to extend an existing domain with static clusters. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.

Domain extension and configuration includes the following tasks:

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 - 12.2.1.3.0 [wccontent]

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

    • Oracle Enterprise Manager - 12.2.1.3.0 [em]

    • Oracle JRF - 12.2.1.3.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12.2.1.3.0 [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 required to connect to the RAC database and component schemas, as shown in the following table.

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

  • File Store

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 Server Groups

WLS_WCC1

WCCHOST1

16200

Unchecked

Disabled

UCM-MGD-SVR

WLS_WCC2

WCCHOST2

16200

Unchecked

Disabled

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.

For more information about the wcc.example.com virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.

Use the Clusters screen to create a new cluster:

  1. Click the Add button.

  2. Specify WCC_Cluster in the Cluster Name field.

  3. From the Dynamic Server Groups drop-down list, select Unspecified.

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

ADMINHOST

Enter the value of the ADMINVHN variable.

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 ADMINVHN to ADMINHOST.

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   Configuring Virtual Targets

Click Next to proceed to the next screen.

Task 18   Configuring Partitions

Click Next to proceed to the next screen.

Task 19   Configuring the File Store

In the File Stores screen, assign the following directory for each of the WebCenter Content Persistence stores including Content Server JMS file stores:

ORACLE_RUNTIME/domain_name/WCC_Cluster/jms

Note:

Create the jms folder before starting the managed servers.

In this example, replace ORACLE_RUNTIME with the value of the variable for you environment. Replace WCC_Cluster with the name you assigned to the WebCenter Content cluster.

Select Direct-Write from the drop-down list for Synchronous Write Policy (for both the stores).

Task 20   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 21   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 22   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.

12.3.2.2 Extending the Domain with Dynamic Clusters

Follow the instructions in this section to extend the domain for the topology with dynamic clusters.

Note:

This procedure assumes that you are extending an existing domain. If your needs do not match the instructions given in the procedure, ensure that you make your selections accordingly, or refer to the supporting documentation for additional details.

Domain extension and configuration includes the following tasks:

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 - 12.2.1.3.0 [wccontent]

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

    • Oracle Enterprise Manager - 12.2.1.3.0 [em]

    • Oracle JRF - 12.2.1.3.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12.2.1.3.0 [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 these HA options.

On the High Availability Options screen, complete the following steps:

  1. Verify that Enable Automatic Service Migration is not selected.

  2. Verify that Default Persistent Store is selected as the JTA Transaction Log Persistence option.

  3. Select JDBC Store as the JMS Service Persistence option.

You can configure only JMS Server persistence for Dynamic Clusters by using the Configuration Wizard. You cannot configure Service Migration and JTA Transaction Logs Persistence for Dynamic Clusters by using the Configuration Wizard; you have to configure them manually. Instructions are covered in later chapters of this guide.

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

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

  3. Select Connection Parameter.

  4. 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 required to connect to the RAC database and component schemas, as shown in the following table.

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

Note:

JMS JDBC stores are recommended and selected in Task 3, "Configuring High Availability Options" so there is no need to configure File Stores.

If you choose JMS File Stores in Task 3, "Configuring High Availability Options", you have to select the File Stores option to configure them in a shared location in ORACLE_RUNTIME/domain_name/SOA_Cluster/jms. Shared location is required to resume JMS and HA in a failover scenario.

Task 9   Configuring Managed Servers

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

Static Managed Server definitions are not needed for dynamic cluster configurations. To remove the default Managed Server, complete the following steps:

  1. Delete the default Managed Server.

  2. Click Next to proceed to the next screen.

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.

For more information about the wcc.example.com virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.

Use the Clusters screen to create a new cluster:

  1. Click the Add button.

  2. Specify WCC_Cluster in the Cluster Name field.

  3. Leave the Cluster Address field blank.

  4. From the Dynamic Server Groups drop-down list, select UCM-DYN-CLUSTER.

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

On the Server Templates screen, verify and update the following UCM server template configuration, add a template if necessary.

For the UCM server template, complete the following steps:

  1. Verify UCM-server-template is listed in the Name field.

  2. Specify 16200 in the Listen Port field.

  3. Leave the Enable SSL option unchecked.

  4. Click Next to proceed to the next screen.

Task 12   Configuring Dynamic Servers

Use the Dynamic Clusters screen to configure the required clusters:

  1. Locate the row with the Cluster Name value of WCC_Cluster.

  2. Verify WLS_WCC is listed in the Server Name Prefix field.

  3. From the Server Template drop-down list, select UCM-server-template.

  4. Specify 2 in the Maximum Dynamic Server Count field.

  5. Specify WCCHOST* in the Machine Name Match Expression field and select Calculated Machine Names.

    Note:

    The dynamic cluster Calculated Machine Names and Machine Name Match Expression attributes control how server instances in a dynamic cluster are assigned to a machine.
    • If the Calculated Machine Names attribute is set to False, the dynamic servers will not be assigned to a machine.

    • If the Calculated Machine Names attribute is set to True, the Machine Name Match Expression attribute is used to select the set of machines that is used for the dynamic servers.

    • If the Machine Name Match Expression attribute is not set, all of the machines in the domain get selected. Assignments are made by using a round robin algorithm.

    To make things easier regardless of your actual physical hostname, Oracle recommends that you use WCCHOSTn as your WebLogic machine names, where n is a sequential number. This is explained in Task 14, "Creating Machines for WebCenter Content Servers" of configuring the infrastructure domain. This convention makes it easy for dynamic clusters to determine where to start each cluster member. If you want to follow this convention, in the Machine Match Expression field, enter WCCHOST*.

    If you do not adopt this convention, the cluster members will be started on each machine that you define in Task 14, "Creating Machines for WebCenter Content Servers", including that of ADMINHOST. This situation is undesirable as you would end you with two cluster members that run on the same physical server but are attached to two different domain homes.

  6. Select Calculated Listen Ports and Dynamic Cluster fields.

  7. Click Next to proceed to the next screen.

Task 13   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 14   Creating Machines for WebCenter Content Servers

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.

Table 12-1 Values to Use When Creating Unix Machines

Name Node Manager Listen Address Node Manager Listen Port

ADMINHOST

Enter the value of the ADMINVHN variable.

5556

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

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.

  5. Click Next to proceed.

Task 15   Assigning Servers to Machines

Click Next to proceed to the next screen.

Task 16   Configuring Virtual Targets

Click Next to proceed to the next screen.

Task 17   Configuring Partitions

Click Next to proceed to the next screen.

Task 18   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 19   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 20   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.

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

Topics:

12.4.1 Propagating the Extended Domain to the Domain Directories and Machines

After you have extended the domain with the Oracle Content, and you have started the Administration Server on WCCHOST1, you can then propagate the domain changes to the domain directories and machines.

Topics:

12.4.1.1 Packing Up the Extended Domain on WCCHOST1

Use the following steps to create a template JAR file that contains the domain configuration information, which now includes configuration information about Oracle WebCenter Content:

  1. Log in to WCCHOST1 and run the pack command to create a template JAR file as follows:
    cd ORACLE_COMMON_HOME/common/bin
     
    ./pack.sh -managed=true 
              -domain=ASERVER_HOME 
              -template=/full_path/edgdomaintemplateExtWCC.jar 
              -template_name=edgdomaintemplateExtWCC
    

    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 directory where you want the template jar file saved.

    • 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 Oracle WebCenter Content.

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

  2. Make a note of the location of the edgdomaintemplateExtWCC.jar file you just created with the pack command.

    By default, the pack template file is created in the current directory where you ran the pack command. In this example, it would be created in the ORACLE_COMMON_HOME/common/bin directory, but you can specify a full path for the template JAR file as part of the -template argument to the pack command.

    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.

12.4.1.2 Unpacking the Domain in Managed Server Domain Home on WCCHOST1

To copy the updated domain configuration information from the Administration Server domain directory to the Managed Servers domain directory:

  1. Log in to WCCHOST1 if you haven't already.
  2. If you haven't already, create the recommended directory structure for the Managed Server domain on WCCHOST1.
  3. Run the unpack command to unpack the template in the domain directory on the local storage, as follows:
    cd ORACLE_COMMON_HOME/common/bin
    
    ./unpack.sh -domain=MSERVER_HOME  \
        -template=template=/full_path/edgdomaintemplateExtWCC.jar \
        -overwrite_domain=true \
        -app_dir=APPLICATION_HOME \
    

    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.

    • Replace full_path with the complete path to the directory where you want the template jar file saved.

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

      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 applications directory for the domain on shared 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. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on the Unpacking the Domain in on Managed Server Domain Home on WCCHOST1 shared storage device.

12.4.1.3 Unpacking the Domain on WCCHOST2

After you create a domain template jar, you can propagate the domain configuration to other hosts using the unpack command. To unpack the domain template jar file:

  1. Log in to WCCHOST2.
  2. If you haven't already, create the recommended directory structure for the Managed Server domain on WCCHOST2.
  3. Make sure the domain template jar file is accessible to WCCHOST2.
    For example, if you are using a separate shared storage volume or partition for WCCHOST2, then copy the template to the volume or partition mounted to WCCHOST2.
  4. Run the unpack command to unpack the template in the domain directory on the local storage, as follows:
    cd ORACLE_COMMON_HOME/common/bin
    
    ./unpack.sh -domain=MSERVER_HOME \
        -template=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.

      Note that if you are using a separate shared storage volume or partition for WCCHOST2 (and redundant Oracle homes), then you must first copy the template to the volume or partition mounted to WCCHOST2.

    • Replace APPLICATION_HOME with the complete path to the applications directory for the domain on shared 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.

  5. Change directory to the newly created MSERVER_HOME directory and verify that the domain configuration files were copied to the correct location on WCCHOST2.

12.4.2 Starting the Node Manager in the Managed Server Domain Directory on WCCHOST1

After you create the Managed Server domain directory, there are two domain home directories and two corresponding Node Manager instances on WCCHOST1. You use one Node Manager to control the Administration Server, running from Administration Server domain home, and you use the other Node Manager to control the Managed Servers, running from the Managed Server domain home.

You must start the two Node Managers independently.

Note:

The Node Manager for the Managed Server's MSERVER_HOME will be reset every time the domain configuration is unpacked. The ListenAddress will be changed to the ADMINVHN instead of the correct hostname. This needs to be changed to the correct value before starting the Node Manager service after an unpack is performed.

Follow these steps to update and start the Node Manager from the Managed Server home:

  1. Verify that the listen address in the nodemanager.properties file is set correctly, by completing the following steps:
    1. Change to the following directory:
      MSERVER_HOME/nodemanager/
    2. Open the nodemanager.properties file for editing.
    3. Update the ListenAddress property to the correct hostname as follows:
      WCCHOST1: ListenAddress=WCCHOST1
      
    4. Update the ListenPort property with the correct Listen Port details.
    5. Make sure that QuitEnabled is set to ‘true’. If this line is not present in the nodemanager.properties file, add the following line:
      QuitEnabled=true
      
  2. Change to the following directory:
    MSERVER_HOME/bin
  3. Use the following command to start the Node Manager:
    nohup ./startNodeManager.sh > MSERVER_HOME/nodemanager/nodemanager.out 2>&1 &
    

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

12.4.3 Starting the WLS_WCC1 Managed Server

To start the WLS_WCC1 Managed Server:
  1. Log in to the Oracle WebLogic Server Administration Console at http://admin.example.com/console.
  2. Start the WLS_WCC1 Managed Server using the WebLogic Server Administration Console, as follows:
    1. Expand the Environment node in the Domain Structure tree on the left.
    2. Click Servers.
    3. On the Summary of Servers page, open the Control tab.
    4. Select WLS_WCC1, and then click Start.
  3. Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.

12.4.4 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 http://WCCHOST1:16200/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: wcc.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 Server Administration Console.

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

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.

12.4.6 Starting the Node Manager in the Managed Server Domain Directory WCCHOST2

After you have propagated the domain configuration to WCCHOST2, you can update and start the Node Manager for the MSERVER_HOME domain directory.

You must start the two Node Managers independently.

Note:

The Node Manager for the Managed Server's MSERVER_HOME will be reset every time the domain configuration is unpacked. The ListenAddress will be changed to the ADMINVHN instead of the correct hostname. This needs to be changed to the correct value before starting the Node Manager service after an unpack is performed.

Follow these steps to update and start the Node Manager from the Managed Server home:

  1. Verify that the listen address in the nodemanager.properties file is set correctly, by completing the following steps:
    1. Change directory to the MSERVER_HOME binary directory:
      cd MSERVER_HOME/bin
      
    2. Open the nodemanager.properties file for editing.
    3. Validate the ListenAddress property to the correct hostname as follows:
      WCCHOST2: ListenAddress=WCCHOST2
      
    4. Update the ListenPort property with the correct Listen Port details.
    5. Make sure that QuitEnabled is set to ‘true’. If this line is not present in the nodemanager.properties file, add the following line:
      QuitEnabled=true
      
  2. Change directory to the MSERVER_HOME binary directory:
    cd MSERVER_HOME/bin
    
  3. Use the following command to start the Node Manager:
    nohup ./startNodeManager.sh > $MSERVER_HOME/nodemanager/nodemanager.out 2>&1 &
    

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

12.4.7 Starting the WLS_WCC2 Managed Server

To start the WLS_WCC2 Managed Server:
  1. Start the WLS_WCC2 Managed Server using the WebLogic Server Administration Console, as follows:
    1. Expand the Environment node in the Domain Structure tree on the left.
    2. Click Servers.
    3. On the Summary of Servers page, open the Control tab.
    4. Select WLS_WCC2, and then click Start.
  2. Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.

12.4.8 Configuring the Content Server on WLS_WCC2 Managed Server

To configure Content Server:
  1. Log in to WLS_WCC2 at http://WCCHOST2:16200/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 Server Administration Console.

12.4.9 Validating GridLink Data Sources

After the servers are started, verify that the GridLink data sources are correctly configured and that the ONS setup is correct. Perform these procedures for every GridLink data source created.

Topics:

12.4.9.1 Verifying the Configuration of a GridLink Data Source for WebCenter Content

To verify the configuration of a GridLink data source for WebCenter Content:
  1. Log in to the WebLogic Server Administration Console.
  2. In the Domain Structure tree, expand Services, then click Data Sources.
  3. Click the name of a GridLink data source that was created.
  4. Click the Monitoring tab.
  5. Click the Testing tab, select one of the servers, and click Test Data Source.
    The test should be successful if the configuration is correct.
  6. Repeat the test for every WebLogic Server instance that uses the GridLink data source.

12.4.9.2 Verifying the Configuration of ONS for a GridLink Data Source

To verify the configuration of ONS for a GridLink data source for WebCenter Content:
  1. In the Domain Structure tree on the Administration Console, expand Services, then click Data Sources.
  2. Click the name of a GridLink data source.
  3. Click the Monitoring tab.
  4. Click the name of the server (WLS_WCC1).
  5. Click the ONS tab.
  6. In the ONS tab, select the Testing tab.
  7. Select a server, and click Test ONS.
    The test should be successful if the configuration is correct. If the ONS test fails, verify that the ONS service is running in the Oracle RAC database nodes:
    [orcl@WCCDBHOST1 ~]$ srvctl status scan_listener
    SCAN Listener LISTENER_SCAN1 is enabled
    SCAN listener LISTENER_SCAN1 is running on node WCCDBHOST1
    SCAN Listener LISTENER_SCAN2 is enabled
    SCAN listener LISTENER_SCAN2 is running on node WCCDBHOST2
    SCAN Listener LISTENER_SCAN3 is enabled
    SCAN listener LISTENER_SCAN3 is running on node WCCDBHOST2 
     
     
    [orcl@WCCDBHOST1 ~]$ srvctl config nodeapps -s 
    ONS exists: Local port 6100, remote port 6200, EM port 2016 
     
     
    [orcl@WCCDBHOST1 ~]$ srvctl status nodeapps | grep ONS
    ONS is enabled
    ONS daemon is running on node: WCCDBHOST1
    ONS daemon is running on node: WCCDBHOST2
    
  8. Repeat the ONS test for every WebLogic Server instance that uses the GridLink data source.

12.4.10 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 Configuring Service Retries for Oracle WebCenter Content.

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.

12.4.11 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 http://WCCHOST1:16200/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.

    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.

12.4.12 Granting user administrative access to Oracle WebCenter Content

To grant users administrative access to Oracle WebCenter Content, configure the Administrators group in the LDAP directory and then add the weblogic_wcc user as a member of the group.

If adding the weblogic_wcc user to Administrators group is not allowed by your LDAP directory administrator, see Granting the WebCenter Content Administrative Roles via Credential Map.

12.4.13 Granting the WebCenter Content Administrative Roles through Credential Map

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

The WCCAdministrators 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 WCCAdministrators 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 WCCAdministrators group
         WCCAdministrators, admin
         WCCAdministrators, sysmanager
         WCCAdministrators, refineryadmin
         WCCAdministrators, rmaadmin
         WCCAdministrators, pcmadmin
         WCCAdministrators, ermadmin
    # Allow existing roles to propagate without mappings
         |#all|             , %%
    #
    # Comment the following if you are not implementing Accounts in Content Server
         WCCAdministrators, @#all(RWDA)
         WCCAdministrators, @#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_wcc 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.

12.5 Configuring Content Server for the WebCenter Content User Interface

If you are planning to use the WebCenter Content user interface (in addition to the native user interface for Content Server), you need to enable the Content Server parameters.

From the Administration tray or menu, select Admin Server > Component Manager and then enable the following parameters:

  • AutoSuggestConfig

  • DynamicConverter

  • FrameworkFolders

In addition, you need to set up the Remote Intradoc Client (RIDC) for communication between the WebCenter Content user interface and Content Server.

You can also set the following Content Server parameters for folders and searching, for the WebCenter Content user interface. To set the Content Server parameters for folders and searching for the WebCenter Content user interface:

  1. From the Administration menu, select Admin Server.

  2. Select General Configuration.

  3. On the General Configuration page, add the following parameters in the Additional Configuration Variables tab:

    • FoldersIndexParentFolderValues=true

    • FldEnforceFolderFileNameUniqueness=true

    • FldEnforceCaseInsensitiveNameUniqueness=true

    • SearchIndexerEngineName=OracleTextSearch or SearchIndexerEngineName=DATABASE.METADATA

      Select either one of the values - OracleTextSearch or DATABASE.METADATA.

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

Topics:

12.6.1 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 wcc.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).
    cd WEB_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/moduleconf/
    

    Note:

    There are separate directories for configuration and runtime instance files. The runtime files under the .../OHS/instances/ohsn/* folder should not be edited directly. Edit only the .../OHS/ohsn/* configuration files.

  2. Create the wcc_vh.conf file and add the following directive:
    <VirtualHost WEBHOST1:7777>
        ServerName https://wcc.example.com:443
        ServerAdmin you@your.address
        RewriteEngine On
        RewriteOptions inherit
    </VirtualHost>
    
  3. In the wcc_vh.conf file, add the following lines between the <VirtualHost> and </VirtualHost> tags:

    Note:

    • For static clusters: The port numbers for WCCHOST1 and WCCHOST2 are 16200.

    • For dynamic clusters: If the Calculated Listen Ports option is enabled, then the port number for WCCHOST1 is 16201 and WCCHOST2 is 16202.

    • In the following example, it is assumed that you are using dynamic clusters and the Calculated Listen Ports option is enabled.

    #UCM
    <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>
    
  4. Copy the wcc_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 wcc_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.

12.6.2 Enabling Access for Content Server Admin Applets

Because the SSL termination is configured on Oracle Web Tier for the enterprise deployment reference topology, the WebLogic Plug-In needs to be enabled for each WebCenter Content Managed Server for successful access to the Content Server Admin Applets. To enable access for Content Server Admin Applets:
  1. Log in to the WebLogic Server Administration Console at http://host.domain:port/console; for example:
    http://ADMINVHN:7001/console
    
  2. (For Dynamic clusters only) On the Environment tab, click Servers.
  3. Click WLS_WCC1.
  4. Click the General tab on the Configuration tab, and go to the Advanced section.
  5. Click Lock & Edit.
  6. Select Yes from the WebLogic Plug-In Enabled drop-down menu.
  7. Click the Save button to save the change.
  8. Click Activate Changes.
  9. Restart the WLS_WCC1 Managed Server from the Administration Console.
  10. Repeat the above instructions for the WLS_WCC2 Managed Server.

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

Topics:

12.6.3.1 Verifying the URLs

To verify the URLs:
  1. While WLS_WCC2 is running, stop WLS_WCC1 using the WebLogic Server Administration Console.
  2. Access https://wcc.example.com/cs to verify that it is functioning properly.
  3. Start WLS_WCC1 from the WebLogic Server Administration Console.
  4. Stop WLS_WCC2 from the WebLogic Server Administration Console.
  5. Access https://wcc.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.

12.6.3.2 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://wcc.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.

12.7 Enabling JDBC Persistent Stores

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.

Follow these guidelines to ensure that you use JDBC stores, when using static or dynamic clusters:

  • For static clusters

    If you have made the following selections in the High Availability Options screen, as recommended in this guide for static clusters, then JDBC persistent stores are already configured for both JMS and TLOGS:

    • Set JTA Transaction Log Persistence to JDBC TLog Store.

    • Set JMS Server Persistence to JMS JDBC Store.

  • For dynamic clusters

    You can configure only JMS Server persistence for dynamic clusters by using the Configuration Wizard. JTA Transaction Logs Persistence must be configure manually, if required. If you have made the following selections in the High Availability Options screen, as recommended in this guide for dynamic clusters, then JDBC persistent stores are already configured for JMS.

    • Set JMS Server Persistence to JMS JDBC Store.

    • Verify that JTA Transaction Log Persistence is set to Default Persistent Store.

    Additional steps are needed to configure JTA Transaction Log with JDBC store. See Roadmap for Configuring a JDBC Persistent Store for TLOGs.

In case you did not select JDBC for JMS and TLOGS persistent in the High Availability Options screen, you can still configure JDBC stores manually in a post step. For specific instructions to configure them manually, see Using JDBC Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Note:

The High Availability Options screen appears during the Configuration Wizard session for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. All subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

12.8 Enabling Automatic Service Migration

To ensure high availability for the product installed in this chapter, you must configure service migration appropriately.

Follow these guidelines to ensure that you provide the required high availability for Weblogic services when you use static or dynamic clusters:

  • For static clusters

    Automatic Service Migration is already configured if you select Enable Automatic Service Migration with Database Basis in the High Availability Options screen.

    The Database Leasing is already configured and the migratable targets are created with the appropriate policies for the cluster. If you have implemented these settings, simply validate the configuration, as described in Validating Automatic Service Migration in Static Clusters.

    In case you do not select this option during the Configuration Wizard session, you can configure automatic migration manually in a post step. For instructions to complete the steps for static clusters, see Configuring Automatic Service Migration in an Enterprise Deployment.

  • For dynamic clusters

    You cannot configure Service Migration for dynamic clusters by using the Configuration Wizard, it needs to be configured manually. The following steps are needed:

    • Configure the database leasing for the cluster.

    • Set the appropriate migration policies for JTA Service and JMS Persistent Stores.

    For instructions to complete the steps for dynamic clusters, see Configuring Automatic Service Migration in an Enterprise Deployment.

Note:

The High Availability Options screen appears during the Configuration Wizard session for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. All subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.