10 Extending the Domain to Include Oracle WebCenter Content

10.1 Overview of Extending the Domain to Include Oracle WebCenter Content

The Oracle WebCenter Content system is installed using the WL_HOME and ORACLE_HOME locations created in Chapter 5, "Installing the Software for an Enterprise Deployment" on a shared storage. WCCHOST1 and WCCHOST2 mount MW_HOME and reuse the existing Oracle Weblogic Server, Oracle SOA Suite, and Oracle WebCenter Content binary installations. The pack and unpack utilities are used to bootstrap the domain configuration for the WLS_WCC1 and WLS_WCC2 servers in these two new nodes. As a result, you do not need to install any software in these two nodes.

For the Oracle WebCenter Content system to work properly, WCCHOST1 and WCCHOST2 must maintain the same system requirements and configuration that was required for installing Oracle Fusion Middleware in SOAHOST1 and SOAHOST2. Otherwise, unpredictable behavior in the execution of binaries may occur.

Extend the domain to include Oracle WebCenter Content. Table 10-1 lists the steps for configuring WebCenter Content and other tasks required for extending the domain with WebCenter Content managed servers.

10.2 Enabling WCCHOST1VHN1 on WCCHOST1 and WCCHOST2VHN1 on WCCHOST2

This step is required for server migration of WLS_WCC1 and WLS_WCC2. You will associate the WLS_WCC1 and WLS_WCC2 servers with virtual host names (WCCHOST1VHN1 and WCCHOST2VHN1). Check that these virtual host names are enabled by DNS or /etc/hosts resolution in your system and that they map to the appropriate VIPs).

For more information, see Section 9.2, "Enabling SOAHOST1VHN1 on SOAHOST1 and SOAHOST2VHN1 on SOAHOST2."

10.3 Extending the Domain to Include WebCenter Content

You must extend the domain created in Section 8, "Creating a Domain for an Enterprise Deployment" to include Oracle WebCenter Content. The instructions in this section assume that the Oracle WebCenter Content deployment uses the same database service as the SOA deployment (wccedg.mycompany.com).

To extend the domain to include Oracle WebCenter Content:

1. Ensure that the database where you installed the repository is running. For Oracle RAC databases, it is recommended that all instances are running, so that the validation check later on becomes more reliable.

2. On SOAHOST1, change the directory to the location of the Oracle Fusion Middleware Configuration Wizard. This is within the Oracle Common home directory (notice that domain extensions are run from the node where the Administration Server resides).

   cd ORACLE_COMMON_HOME/common/bin
   

3. Start the Configuration Wizard:

   ./config.sh
   

4. In the Welcome screen, select Extend an existing WebLogic domain, and click Next.

5. In the WebLogic Domain Directory screen, select the WebLogic domain directory (ORACLE_BASE/admin/domain_name/aserver/domain_name), and click Next.

6. In the Select Extension Source screen, do the following (as shown in Figure 10-1):

   • Select Extend my domain automatically to support the following added products.

   • Select the following product:

     • Oracle Universal Content Management - Content Server - 11.1.1.0 [wcc]

       This is the selection for Oracle WebCenter Content.

   The following products should already be selected and grayed out. They were selected when you created a domain in Section 8.3, "Running the Configuration Wizard on SOAHOST1 to Create a Domain" or extended a domain in Section 9.3, "Extending the Domain for SOA Components Using the Configuration Wizard":

   • Basic WebLogic Server Domain

   • Oracle SOA Suite for developers

   • Oracle SOA Suite

   • Oracle Enterprise Manager

   • Oracle WSM Policy Manager

   • Oracle JRF

   Click Next.

   Figure 10-1 Select Extension Source Screen for Oracle WebCenter Content

   
   Description of "Figure 10-1 Select Extension Source Screen for Oracle WebCenter Content"
   
   

7. In the Configure JDBC Component Schema screen, do the following (as shown in Figure 10-2):

   • Select UCM Schema (for WebCenter Content).

   • Select Convert to RAC multi date source.

   Click Next.

   Figure 10-2 Configure JDBC Component Schema Screen for Oracle WebCenter Content

   
   Description of "Figure 10-2 Configure JDBC Component Schema Screen for Oracle WebCenter Content"
   
   

8. In the Configure RAC Multi Data Sources Component Schema screen, do the following (as shown in Figure 10-3):

   1. Select UCM Schema (for WebCenter Content). Leave the other data sources as they are.

   2. Enter values for the following fields, specifying the connect information for the Oracle RAC database that was seeded with RCU:

      • Driver: Select Oracle driver (Thin) for RAC Service-Instance connections, Versions: 10 and later.

      • Service Name: Enter the service name of the database (wccedg.mycompany.com).

      • Username: Enter the complete user name (including the prefix) for the schemas. The user names shown in Figure 10-3 assume that DEV was used as the prefix for schema creation from RCU.

      • Password: Enter the password to use to access the schemas.

   3. Click Add and enter the details for the first Oracle RAC instance.

   4. Repeat step c for each Oracle RAC instance.

      Note:

      Leave the SOA Infrastructure, IPM Schema, User Messaging Service, OWSM MDS Schema, and SOA MDS Schema information as they are.

   5. Click Next.

   Figure 10-3 Configure RAC Multi Data Source Component Schema Screen for Oracle WebCenter Content

   
   Description of "Figure 10-3 Configure RAC Multi Data Source Component Schema Screen for Oracle WebCenter Content"
   
   

9. In the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Ensure that all connections were successful. If not, click Previous to return to the previous screen and correct your entries.

   Click Next when all the connections are successful.

10. In the Optional Configuration screen, select the following:

    • Managed Servers, Clusters and Machines

    • Deployment and Services

    Click Next.

11. In the Configure Managed Servers screen, add the required managed servers.

    A server is created automatically. Rename this server to WLS_WCC1 and add a new server called WLS_WCC2. Give these servers the attributes listed in Table 10-2. Do not modify the other servers that are shown in this screen; leave them as they are.

    Table 10-2 Managed Servers

    Name	Listen Address	Listen Port	SSL Listen Port	SSL Enabled
    WLS_WCC1	WCCHOST1	16200	n/a	No
    WLS_WCC2	WCCHOST2	16200	n/a	No

    
    

    Click Next.

12. In the Configure Clusters screen, click Add to add the clusters as shown in Table 10-3. Do not modify the other clusters that appear in this screen; leave them as they are.

    Table 10-3 Clusters

    Name	Cluster Messaging Mode	Multicast Address	Multicast Port	Cluster Address
    WCC_Cluster	unicast	n/a	n/a	Leave empty

    
    

    Click Next.

13. In the Assign Servers to Clusters screen, add the following. Do not modify the other assignments that appear in this screen; leave them as they are.

    • WCC_Cluster:

      • WLS_WCC1

      • WLS_WCC2

    Click Next.

14. In the Configure Machines screen, open the Unix Machine tab and add the following two new machines:

    Table 10-4 Machines

    Name	Node Manager Listen Address
    WCCHOST1	WCCHOST1
    WCCHOST2	WCCHOST2

    
    

    Leave all other fields to their default values. Click Next.

15. In the Assign Servers to Machines screen, assign servers to machines as follows:

    • Assign WLS_WCC1 to WCCHOST1.

    • Assign WLS_WCC2 to WCCHOST2.

    Click Next.

16. In the Target Deployments to Clusters or Servers screen, make sure that the DMS Application is targeted to the SOA_Cluster, WCC_Cluster and Admin Server. Click Next.

17. In the Target Services to Clusters or Servers screen, click Next.

18. In the Configuration Summary screen, click Extend.

19. If you see a warning dialog about port conflicts for the domain, click OK.

20. In the Creating Domain screen, click Done.

21. Restart the Administration Server to make these changes to take effect. See Section 10.7, "Restarting the Administration Server."

10.4 Propagating the Domain Configuration to WCCHOST1 and WCCHOST2 with the pack and unpack Utilities

To propagate the domain configuration:

1. Run the pack command on SOAHOST1 to create a template pack using the following commands:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./pack.sh -managed=true -domain=ORACLE_BASE/admin/domain_name/aserver/domain_name -template=edgdomaintemplateWCC.jar -template_name=edgdomain_templateWCC
   

2. Run the following command on SOAHOST1 to copy the template pack created in the previous step to WCCHOST2:

   Note:

   Assuming that WCCHOST1 shares the ORACLE_HOME with SOAHOST1, the template will be present in the same directory in WCCHOST1; otherwise, copy it also to WCCHOST1.

   scp edgdomaintemplateWCC.jar oracle@WCCHOST2:ORACLE_BASE/product/fmw/oracle_common/common/bin
   

3. Run the unpack command on WCCHOST1 to unpack the propagated template.

   Note:

   Make sure to run unpack from the ORACLE_COMMON_HOME/common/bin directory, not from WL_HOME/common/bin.

   cd ORACLE_COMMON_HOME/common/bin
   
   ./unpack.sh -domain=ORACLE_BASE/admin/domain_name/mserver/domain_name -template=edgdomaintemplateWCC.jar -app_dir=ORACLE_BASE/admin/domain_name/mserver/applications
   

   Note:

   The ORACLE_BASE/admin/domain_name/mserver directory must exist before running unpack. In addition, the ORACLE_BASE/admin/domain_name/mserver/applications must be empty.

4. Repeat step 3 for WCCHOST2.

10.5 Configuring the Load Balancer to Route WebCenter Content Traffic

In this WebCenter Content enterprise deployment, the Load Balancer load-balances traffic across both Content Servers. The Load Balancer forwards the socket connection from applications to one of the Content Servers (on WCCHOST1 or WCCHOST2). Since the connection is persistent, one Content Server receives most of the traffic, if not all. The other Content Server functions as a failover server in case the primary server is not available.

You must configure your Load Balancer with a rule that specifies how to route WebCenter Content traffic, for example:

• (LBR)10.110.10.135:4444 -> 10.110.10.23:4444 (WCCHOST1) -> 10.110.10.24:4444 (WCCHOST2)

10.6 Starting Node Manager on WCCHOST1 and WCCHOST2

To start Node Manager on WCCHOST1 and WCCHOST2 if Node Manager has not started already:

1. On both WCCHOST1 and WCCHOST2, run the setNMProps.sh script, which is located in the ORACLE_COMMON_HOME/common/bin directory, to set the StartScriptEnabled property to true before starting Node Manager:

   cd ORACLE_COMMON_HOME/common/bin
   
   ./setNMProps.sh
   

   Note:

   You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 16.11.3, "Incomplete Policy Migration After Failed Restart of SOA Server."

   Note:

   If the WebCenter Content server is sharing the Middleware home in a local or shared storage with SOA, as suggested in the configuration described in Chapter 3, "Preparing the Network for an Enterprise Deployment" it is not required to run setNMProps.sh again. In this case, Node Manager has already been configured to use a start script.

2. Run the following commands on both WCCHOST1 and WCCHOST2 to start Node Manager:

   cd WL_HOME/server/bin
   
   ./startNodeManager.sh
   

10.7 Restarting the Administration Server

Restart the Administration Server to make these changes take effect. To restart the Administration Server, stop it first using the Administration Console and then start it again as described in Section 8.4.3, "Starting the Administration Server on SOAHOST1."

10.8 Starting WLS_WCC1 Managed Server and Configuring Content Server

After you start the WLS_WCC1 managed server, you can configure Oracle WebCenter Content Server through the web interface.

Starting the WLS_WCC1 Managed Server

To start the WLS_WCC1 managed server:

1. Start the WLS_WCC1 managed server using the Oracle WebLogic Server Administration Console as follows:

   1. Expand the Environment node in the Domain Structure window.

   2. Choose Servers.

   3. On the Summary or Servers page, open the Control tab.

   4. Select WLS_WCC1 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. See Section 16.11, "Troubleshooting the Oracle WebCenter Content Enterprise Deployment Topology" for possible causes.

Configuring Content Server

To configure Content Server:

1. Log in to WLS_WCC1 at http://WCCHOST1:16200/cs using your Oracle WebLogic administration user name and password to display a configuration page.

   Note:

   The 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_BASE/admin/domain_name/aserver/wcc_cluster_name.

2. Change the following values on the server configuration page (make sure to select the Is New Content Server Instance checkbox to see all options):

   • Content Server Instance Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs.

   • Native File Repository Location: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/vault.

   • WebLayout Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/weblayout.

   • User Profile Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/data/users/profiles.

   • Server Socket Port: Set this to 4444.

   • Incoming Socket Connection Address Security Filter: Set this to a pipe-delimited list of localhost and the server IPs:

     127.0.0.1|WCCHOST1|WCCHOST2|WEBHOST1|WEBHOST2
     

     Note:

     This will be changed later to a host name-based list (see Section 11.13, "Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content"). At this point, we need the connections to be allowed for operations that will be done before the security filter is changed to host names.

   • WebServer HTTP/HTTPS Address: Set this to wcc.mycompany.com:443.

   • Web Address is HTTPS: Select this checkbox.

   • Server Instance Label: Set this to WCC_Cluster1.

   • Server Instance Description: Set this to Cluster wcc_cluster1.

   • Auto_Number Prefix: Set this to wcc_cluster1-.

3. Click Submit when finished and restart the managed server using the Oracle WebLogic Server Administration Console.

10.9 Updating the cwallet File in the Administration Server

Oracle WebCenter Content Server updates the cwallet.sso file located in ORACLE_BASE/admin/domain_name/mserver/domain_name/config/fmwconfig when it starts. This change needs to be propagated back to the Administration Server. To do this, copy the file to ORACLE_BASE/admin/domain_name/aserver/domain_name/config/fmwconfig on SOAHOST1 using the following command on WCCHOST1 (all on a single line):

scp ORACLE_BASE/admin/domain_name/mserver/domain_name/config/fmwconfig/cwallet.sso oracle@SOAHOST1:ORACLE_BASE/admin/domain_name/aserver/domain_name/config/fmwconfig/

10.10 Starting the WLS_WCC2 Managed Server and Configuring Content Server

After you start the WLS_WCC2 managed server, you can configure Oracle WebCenter Content Server through the web interface.

Starting the WLS_WCC2 Managed Server

To start the WLS_WCC2 managed server:

1. Start the WLS_WCC2 managed server using the Oracle WebLogic Server Administration Console as follows:

   1. Expand the Environment node in the Domain Structure window.

   2. Choose 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. See Section 16.11, "Troubleshooting the Oracle WebCenter Content Enterprise Deployment Topology" for possible causes.

Configuring Content Server

To configure Content Server:

1. Log in to WLS_WCC2 at http://WCCHOST2:16200/cs using your Oracle WebLogic administration user name and password to display a configuration page.

   Note:

   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_BASE/admin/domain_name/aserver/wcc_cluster_name.

2. Change the following values on the server configuration page:

   • Content Server Instance Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs.

   • Native File Repository Location: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/vault.

   • WebLayout Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/weblayout.

   • User Profile Folder: Set this to ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/data/users/profiles.

   Make sure that the Is new Content Server Instance? checkbox is not selected.

3. Click Submit when finished and restart the managed server using the Oracle WebLogic Server Administration Console.

10.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 add the configuration parameter for Oracle WebCenter Content:

1. Go to Oracle WebCenter Content Server at http://WCCHOST1:16200/cs, and log in using your Oracle WebLogic Server administration user name and password.

2. Open the Administration page, and then choose Admin Server.

3. On the Content Admin Server page, click General Configuration on the left.

4. On the General Configuration page, add the following parameter in the Additional Configuration Variables box:

   ServiceAllowRetry=true
   

5. Click Save and restart all WebCenter Content managed servers.

ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/config/config.cfg

10.12 Configuring Oracle HTTP Server for the WLS_WCC Managed Servers

To enable Oracle HTTP Server to route to WCC_Cluster, which contain the WLS_WCC1 and WLS_WCC2 managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:

1. On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf file:

   # UCM
   <Location /cs>
      WebLogicCluster WCCHOST1:16200,WCCHOST2:16200
      SetHandler weblogic-handler
      WLCookieName JSESSIONID
      WLProxySSL ON
      WLProxySSLPassThrough ON
   </Location>
   
   <Location /adfAuthentication>
      WebLogicCluster WCCHOST1:16200,WCCHOST2:16200
      SetHandler weblogic-handler
      WLCookieName JSESSIONID
      WLProxySSL ON
      WLProxySSLPassThrough ON
   </Location>
   
   <Location /_ocsh>
      WebLogicCluster WCCHOST1:16200,WCCHOST2:16200
      SetHandler weblogic-handler
      WLCookieName JSESSIONID
      WLProxySSL ON
      WLProxySSLPassThrough ON
   </Location>
   

2. Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2:

   ORACLE_BASE/admin/instance_name/bin/opmnctl restartproc ias-component=ohsX
   

   For WEBHOST1, use ohs1 for ias-component and for WEBHOST2 use ohs2.

10.13 Validating Access Through Oracle HTTP Server

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

1. While WLS_WCC2 is running, stop WLS_WCC1 using the Oracle WebLogic Server Administration Console.

2. Access http://WEBHOST1:7777/cs to verify it is functioning properly.

3. Start WLS_WCC1 from the Oracle WebLogic Server Administration Console.

4. Stop WLS_WCC2 from the Oracle WebLogic Server Administration Console.

5. Access http://WEBHOST1:7777/cs to verify it is functioning properly.

10.14 Configuring Node Manager for the WLS_WCC and WLS_IMG Managed Servers

Oracle recommends using host name verification for the communication between Node Manager and the servers in the domain. This requires the use of certificates for the different addresses communicating with the Administration Server and other servers. See Chapter 13, "Setting Up Node Manager" for further details. The procedures in that chapter must be performed twice using the following information:

^{* Optional; required only for Oracle WebCenter Content: Imaging managed servers (WLS_IMG).}

Please note the following:

• Even though the WLS_IMG managed servers are not yet configured at this point (see Chapter 11, "Extending the Domain to Include Imaging") and are not mandatory for an Oracle WebCenter Content configuration that includes only WebCenter Content, the virtual host names used by Oracle WebCenter Content: Imaging are configured here \to provide a one-step configuration process that includes both types of servers.

• Perform all steps in Chapter 13, "Setting Up Node Manager" except for Section 13.3.5, "Configuring Managed Servers to Use the Custom Keystores" for the WLS_IMG servers. This step can be done after the WLS_IMG servers are added to the domain.

10.15 Backing Up the Installation

After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At that point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrator's Guide provides further details. For information on describing the Oracle HTTP Server data that must be backed up and restored, refer to the "Backup and Recovery Recommendations for Oracle HTTP Server" section in that guide. For information on how to recover components, see the "Recovery of Components" and "Recovery After Loss of Component" sections in the guide. For recommendations specific to recovering from the loss of a host, see the "Recovering Oracle HTTP Server to a Different Host" section in the guide. Also refer to the Oracle Database Backup and Recovery Guide for information on database backup.

To back up the installation at this point:

1. Back up the web tier on WEBHOST1:

   1. Shut down the instance using opmnctl.

      ORACLE_BASE/admin/instance_name/bin/opmnctl stopall
      

   2. Back up the Middleware Home on the web tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web.tar MW_HOME
      

   3. Back up the Oracle instance on the web tier using the following command:

      tar -cvpf BACKUP_LOCATION/web_instance_name.tar ORACLE_INSTANCE
      

   4. Start the instance using opmnctl:

      cd ORACLE_BASE/admin/instance_name/bin
      opmnctl startall
      

2. Back up the database. This is a full database backup (either hot or cold) using Oracle Recovery Manager (recommended) or operating system tools such as tar for cold backups if possible.

3. Back up the Administration Server and managed server domain directory to save your domain configuration. The configuration files all exist in the ORACLE_BASE/admin/domain_name directory. Run the following command on SOAHOST1 to create the backup:

   tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name