11 Extending the Domain to Include WebCenter Content

This chapter describes how to extend the domain created in Chapter 11, "Extending the Domain to Include WebCenter Content," to include Oracle WebCenter Content, which includes Oracle WebCenter Content Server, using the Oracle Fusion Middleware Configuration Wizard. You can extend the resulting domain to add other Fusion Middleware components, as described in the following chapters.

This chapter includes the following sections:

• Section 11.1, "Overview of Extending the Domain to Include WebCenter Content"

• Section 11.2, "Extending the Domain for WebCenter Content"

• Section 11.3, "Restarting the Administration Server"

• Section 11.4, "Completing Postconfiguration and Verification Tasks for WebCenter Content"

• Section 11.5, "Configuring Oracle HTTP Server with the Extended Domain"

• Section 11.6, "Configuring Node Manager for Managed Servers"

• Section 11.7, "Backing Up the Installation"

Note:

Before starting the setup process, read the Oracle Fusion Middleware Release Notes for your platform for additional installation and deployment information.

11.1 Overview of Extending the Domain to Include WebCenter Content

The Oracle WebCenter Content system is installed using the WL_HOME and ORACLE_HOME locations created in Chapter 7, "Installing the Software for an Enterprise Deployment," on a shared storage.

Extend the domain to include Oracle WebCenter Content. Table 11-1 lists the steps for configuring WebCenter Content and other tasks required for extending the domain with WebCenter Content Managed Servers.

Table 11-1 Steps for Extending the Domain with WebCenter Content

Step	Description	More Information
Extend the domain for WebCenter Content	Extend the WebLogic Server domain you created in Chapter 9, "Creating a Domain for an Enterprise Deployment," to include Oracle WebCenter Content.	Section 11.2, "Extending the Domain for WebCenter Content"
Start Node Manager on the WebCenter Content Managed Servers	Run the setNMProps.sh script and then start Node Manager on WCCHOST1 and on WCCHOST2.	Section 11.4.1, "Starting Node Manager on WCCHOST2"
Propagate the domain configuration to the WebCenter Content Managed Servers	Propagate the start scripts and classpath configuration from the Administration Server's domain directory to the Managed Server domain directories.	Section 11.4.2, "Propagating the Domain Configuration to WLS_WCC1 and WLS_WCC2"
Restart the Administration Server for the domain	Stop and then restart the Administration Server.	Section 11.3, "Restarting the Administration Server"
Start the first WebCenter Content Managed Server and configure its Content Server instance	Start the WLS_WCC1 Managed Server and complete the initial Content Server configuration.	Section 11.4.3, "Starting the WLS_WCC1 Managed Server and Configuring Content Server"
Propagate the changes in the cwallet.sso file back to the Administration Server.	Copy the updated cwallet.sso file to the Administration Server directory.	Section 11.4.4, "Updating the cwallet File in the Administration Server"
Start the second WebCenter Content Managed Server and configure its Content Server instance	Configure the WLS_WCC2 Managed Server and complete the initial Content Server configuration.	Section 11.4.5, "Starting the WLS_WCC2 Managed Server and Configuring Content Server"
Verify the configuration of GridLink data sources and Oracle Notification Service (ONS)	Follow these instructions to verify that the configuration of GridLink data sources and ONS is correct.	Section 11.4.6, "Validating GridLink Data Sources for WebCenter Content"
Configure parameters for cluster nodes	Add directory locations for WebCenter Content trace and event logs, as needed.	Section 11.4.7, "Configuring Additional Parameters"
Enable service retries after an Oracle RAC failover	Set the ServiceAllowRetry configuration parameter to true in the Content Server config.cfg file.	Section 11.4.8, "Configuring Service Retries for Oracle WebCenter Content"
Configure Oracle HTTP Server with the extended domain	Configure the Oracle HTTP Server with the Managed Servers, set the front-end HTTP host and port, and set the WebLogic Server cluster address for WCC_Cluster.	Section 11.5, "Configuring Oracle HTTP Server with the Extended Domain"
Validate access to WebCenter Content through Oracle HTTP Server	Verify the URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to WCC_Cluster.	Section 11.5.2, "Validating Access Through the Load Balancer"
Configure host name verification for communication between Node Manager and the Managed Servers in the domain	Use certificates for the different addresses communicating with the Administration Server and other servers.	Section 11.6, "Configuring Node Manager for Managed Servers"
Back Up the WebCenter Content Configuration	Back up the newly extended domain configuration.	Section 11.7, "Backing Up the Installation"

11.2 Extending the Domain for WebCenter Content

You can extend the domain created in Section 9, "Creating a Domain for an Enterprise Deployment" to include Oracle WebCenter Content.

Note:

Before performing these steps, back up the domain as described in the Oracle Fusion Middleware Administrator's Guide.

To extend the domain for WebCenter Content:

1. Make sure 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 WCCHOST1, change the directory to the location of the Oracle Fusion Middleware Configuration Wizard. This is within the Oracle Common home directory (domain extensions are run from the node where the Administration Server resides).

   cd ORACLE_COMMON_HOME/common/bin
   

3. Start the Fusion Middleware Configuration Wizard:

   ./config.sh
   

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

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

6. In the Select Extension Source screen (Figure 11-1), make these selections:

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

   • Select this product:

     Oracle Universal Content Management - Content Server

     This is the selection for Oracle WebCenter Content.

     Figure 11-1 Select Extension Source Screen for WebCenter Content

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

   The following products are grayed out if they were selected when you created the domain (Section 9.3).

   • Basic WebLogic Server Domain

   • Oracle Enterprise Manager

   • Oracle JRF

   Click Next.

7. In the Configure JDBC Component Schema screen (Figure 11-2), do the following steps:

   1. Select UCM Schema (for WebCenter Content).

      Figure 11-2 Configure JDBC Component Schema Screen for WebCenter Content

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

   2. For the RAC configuration, you can select Convert to GridLink or Convert to RAC multi data source (described in Appendix A, "Using Multi Data Sources with Oracle RAC"). For the instructions given here, select Convert to GridLink.

      After you select a RAC configuration, all selected schemas are grayed.

   3. Click Next.

8. In the Configure GridLink RAC Component Schema screen (Figure 11-3), do the following steps:

   1. Make sure UCM Schema is selected.

      Figure 11-3 Configure GridLink RAC Component Schema Screen for WebCenter Content

      
      Description of "Figure 11-3 Configure GridLink RAC Component Schema Screen for WebCenter Content"
      
      

   2. Enter values for the following fields, specifying the connection information for the GridLink RAC database that was seeded through RCU:

      • Driver: Select Oracle driver (Thin) for GridLinkConnections; Versions:10 and later.

      • Service Name: Enter the service name of the Oracle RAC database in lowercase letters, followed by the domain name; for example, wccedg.mycompany.com.

      • Username: Enter the complete user name for the database schema owner of the corresponding component.

        This book uses WCC as the prefix of user names for the database schemas.

      • Password: Enter the password for the database schema owner.

      • Select Enable FAN.

      • Enable SSL: Leave this option deselected.

        If you select SSL to enable Oracle Notification Service (ONS) notification encryption, provide the appropriate Wallet File and Wallet Password details.

      • Service listener: Enter the Oracle Single Client Access Name (SCAN) address and port for the Oracle RAC database being used. The protocol should be TCP.

        Oracle recommends that you use a SCAN address to specify the Service Listener (and OSN Host) so you do not need to update a GridLink data source containing a SCAN address if you add or remove Oracle RAC nodes. To determine the SCAN address, query the remote_listener parameter in the database:

        SQL>show parameter remote_listener;
         
        NAME              TYPE        VALUE
        -----             ------      -------
        remote_listener   string      db-scan.mycompany.com:1521
        

        Note:

        For Oracle Database 11g, use the virtual IP address and port of each database instance listener, as in these examples:

        custdbhost1-vip.mycompany.com (port 1521) 
        
        custdbhost2-vip.mycompany.com (1521)
        

        For Oracle Database 10g, use multi data sources to connect to an Oracle RAC database. For information about configuring multi data sources, see Appendix A, "Using Multi Data Sources with Oracle RAC."

      • ONS Host: Enter here also the SCAN address for the RAC database and the ONS remote port, as reported by the database:

        [orcl@CUSTDBHOST2~]$ srvctl config nodeapps -s
        ONS exists: Local port 6100, remote port 6200, EM port 2016
        

        Note:

        For Oracle Database 11g, use the host name and port of each database's ONS service, as in these examples:

        custdbhost1.mycompany.com (port 6200)
        
        custdbhost2.mycompany.com (6200)
        

   3. Click Next.

9. In the Test JDBC Component Schema screen (Figure 11-4), select the UCM Schema row, then click Test Connections.

   The Connection Results Log displays the results. Ensure that the connection to the database that contains the schema was successful. If not, click Previous to return to the previous screen, correct your entry, and then retry the test.

   Figure 11-4 Test JDBC Component Schema Screen for WebCenter Content

   
   Description of "Figure 11-4 Test JDBC Component Schema Screen for WebCenter Content"
   
   

   Click Next when the connection is successful.

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

    • Managed Servers, Clusters and Machines

    • Deployment and Services

    Click Next.

11. In the Configure Managed Servers screen (Figure 11-5), add the required Managed Servers.

    Figure 11-5 Configure Managed Servers for WebCenter Content

    
    Description of "Figure 11-5 Configure Managed Servers for WebCenter Content"
    
    

    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 11-2. Do not modify the other servers that are shown in this screen.

    Table 11-2 Managed Servers for WebCenter Content

    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 (Figure 11-6, click Add and enter WCC_Cluster, which Table 11-3 describes.

    Table 11-3 Cluster Configuration for WebCenter Content

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

    
    

    Figure 11-6 Configure Clusters Screen for WebCenter Content

    
    Description of "Figure 11-6 Configure Clusters Screen for WebCenter Content"
    
    

    Click Next.

13. In the Assign Servers to Clusters screen, assign the following servers to WCC_Cluster:

    • • WLS_WCC1

      • WLS_WCC2

    Click Next.

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

    Table 11-4 Machines for WebCenter Content

    Name	Node Manager Listen Address
    WCCHOST1	WCCHOST1
    WCCHOST2	WCCHOST2
    ADMINVHN	localhost

    
    

    Leave all other fields set to their default values. The machine names do not need to be valid host names or listen addresses; they are just unique identifiers of Node Manager locations.

    Click Next.

15. In the Assign Servers to Machines screen (Figure 11-7), assign servers to machines as follows:

    • Assign WLS_WCC1 to WCCHOST1.

    • Assign WLS_WCC2 to WCCHOST2.

    Figure 11-7 Assign Server to Machines Screen for WebCenter Content

    
    Description of "Figure 11-7 Assign Server to Machines Screen for WebCenter Content"
    
    

    Click Next.

16. In the Target Deployments to Clusters or Servers screen, make sure that targeting is done as follows:

    • DMS Application is targeted to WCC_Cluster and AdminServer.

    • NonJ2EEManagement Application is targeted only to AdminServer.

    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.

11.3 Restarting the Administration Server

You need to restart the Administration Server to make the domain extension changes take effect, using the Node Manager nmKill and nmStart commands through the Oracle WebLogic Scripting Tool (WLST). You can use the Administration Console instead of nmKill to stop the Administration Server. After the restart, log in to the Administration Console using the credentials for the weblogic_ecm user.

To restart the Administration Server:

1. Start the Oracle WebLogic Scripting Tool (WLST):

   cd ORACLE_COMMON_HOME/common/bin
   
   ./wlst.sh
   

2. In the WLST shell, connect to Node Manager with the nmConnect command and the Node Manager credentials (make sure Node Manager is up and running), and start the Node Manager using nmStart:

   wls:/offline>nmConnect("node_admin_user","node_admin_password", "WCCHOST1","5556","domain_name","ORACLE_BASE/admin/domain_name/aserver/domain_name")
   
   wls:/nm/domain_name> nmStart("AdminServer")
   

   The values of node_admin_user and node_admin_password are the Node Manager credentials. For more information about the credentials, see Section 9.4.3, "Starting the Administration Server on WCCHOST1."

3. Stop the Administration Server, using either the Administration Console or, as follows, the Node Manager nmKill command:

   wls:/nm/domain_name>nmKill("AdminServer")
   

4. Start the Administration Server using nmStart:

   wls:/offline>nmConnect("node_admin_user","node_admin_password", "WCCHOST1","5556","domain_name","ORACLE_BASE/admin/domain_name/aserver/domain_name")
   
   wls:/nm/domain_name> nmStart("AdminServer")
   

11.4 Completing Postconfiguration and Verification Tasks for WebCenter Content

The following sections describe how to do postconfiguration and verifications tasks for WebCenter Content:

• Section 11.4.1, "Starting Node Manager on WCCHOST2"

• Section 11.4.2, "Propagating the Domain Configuration to WLS_WCC1 and WLS_WCC2"

• Section 11.4.3, "Starting the WLS_WCC1 Managed Server and Configuring Content Server"

• Section 11.4.4, "Updating the cwallet File in the Administration Server"

• Section 11.4.5, "Starting the WLS_WCC2 Managed Server and Configuring Content Server"

• Section 11.4.6, "Validating GridLink Data Sources for WebCenter Content"

• Section 11.4.7, "Configuring Additional Parameters"

• Section 11.4.8, "Configuring Service Retries for Oracle WebCenter Content"

11.4.1 Starting Node Manager on WCCHOST2

If Node Manager has not started already on WCCHOST2, you need to start it.

To start Node Manager on WCCHOST2:

1. On 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 19.13.3, "Incomplete Policy Migration After Failed Restart of SOA Server."

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

   cd WL_HOME/server/bin
   
   ./startNodeManager.sh
   

11.4.2 Propagating the Domain Configuration to WLS_WCC1 and WLS_WCC2

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

To propagate the domain configuration to the WebCenter Content Managed Servers:

1. Create a copy of the Managed Server domain directory and the Managed Server applications directory.

2. Run the following pack command on WCCHOST1 to create a template pack:

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

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

   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
   

   Notes:

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

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

4. Run the following command on WCCHOST1 to copy the template pack created in step 1 to WCCHOST2:

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

5. Run the following unpack command on WCCHOST2 to unpack the propagated template to the WLS_WCC2 Managed Server domain directory:

   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
   

   Notes:

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

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

6. Restart the Administration Server to make these changes take effect, stopping it with the nmKill command, or with the Administration Console, and then starting it with the nmStart command, as described in Section 11.3, "Restarting the Administration Server." After the restart, log in to the Administration Server using the credentials for the weblogic_ecm user.

11.4.3 Starting the WLS_WCC1 Managed Server and Configuring Content Server

After you start the WLS_WCC1 Managed Server, you can configure Content Server through the web interface.

To start the WLS_WCC1 Managed Server:

1. Log in to the Oracle WebLogic Server Administration Console at http://admin.mycompany.com:7001/console.

2. Start the WLS_WCC1 Managed Server through the 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, click the Control tab.

   4. Select WLS_WCC1 from the Servers column of the table.

   5. 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. For possible causes, see Section 19.13, "Troubleshooting the Oracle WebCenter Content Enterprise Deployment Topology."

To configure Content Server:

1. Log in to WLS_WCC1 at http://WCCHOST1:16200/cs using your WebLogic Server 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/wcc_cluster_name/.

2. Set 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: ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/

   • Native File Repository Location: ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/vault/

   • WebLayout Folder: ORACLE_BASE/admin/domain_name/wcc_cluster_name/cs/weblayout/

   • User Profile Folder: ORACLE_BASE/admin/domain_name/wcc_cluster_name/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|WCCHOST1-IP|WCCHOST2-IP|WEBHOST1-IP|WEBHOST2-IP
     

     Note:

     This will be changed later to a host name-based list (see Section 14.5.12, "Adding the Imaging Server Listen Addresses to the List of Allowed Hosts in Oracle WebCenter Content"). At this point, you 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: wcc.mycompany.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-

3. Click Submit when finished, and restart the Managed Server, using the WebLogic Server Administration Console.

11.4.4 Updating the cwallet File in the Administration Server

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 WCCHOST1 using the following command on WCCHOST1 (all on a single line):

cp -p ORACLE_BASE/admin/domain_name/mserver/domain_name/config/fmwconfig/cwallet.sso ORACLE_BASE/admin/domain_name/aserver/domain_name/config/fmwconfig/

Note:

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

11.4.5 Starting the WLS_WCC2 Managed Server and Configuring Content Server

After you start the WLS_WCC2 Managed Server, you can configure Content Server through the web interface.

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. For possible causes, see Section 19.13, "Troubleshooting the Oracle WebCenter Content Enterprise Deployment Topology."

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

   • Content Server URL Prefix: /cs/ (default value)

   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 WebLogic Server Administration Console.

11.4.6 Validating GridLink Data Sources for WebCenter Content

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.

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 (Figure 11-8), select one of the servers, and click Test Data Source.

   Figure 11-8 Testing a GridLink Data Source for WebCenter Content

   
   Description of "Figure 11-8 Testing a GridLink Data Source for WebCenter Content"
   
   

   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.

To verify the configuration of ONS for 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.

4. Click the Monitoring tab.

5. Click the ONS tab and then the Testing tab (Figure 11-9).

6. Select a server, and click Test ONS.

   Figure 11-9 Testing the ONS Configuration for WebCenter Content

   
   Description of "Figure 11-9 Testing the ONS Configuration for WebCenter Content"
   
   

   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@CUSTDBHOST1 ~]$ srvctl status scan_listener
   SCAN Listener LISTENER_SCAN1 is enabled
   SCAN listener LISTENER_SCAN1 is running on node CUSTDBHOST1
   SCAN Listener LISTENER_SCAN2 is enabled
   SCAN listener LISTENER_SCAN2 is running on node CUSTDBHOST2
   SCAN Listener LISTENER_SCAN3 is enabled
   SCAN listener LISTENER_SCAN3 is running on node CUSTDBHOST2 
    
    
   [orcl@CUSTDBHOST1 ~]$ srvctl config nodeapps -s 
   ONS exists: Local port 6100, remote port 6200, EM port 2016 
    
    
   [orcl@CUSTDBHOST1 ~]$ srvctl status nodeapps | grep ONS
   ONS is enabled
   ONS daemon is running on node: CUSTDBHOST1
   ONS daemon is running on node: CUSTDBHOST2
   

7. Repeat the ONS test for every WebLogic Server instance that uses the GridLink data source.

11.4.7 Configuring Additional Parameters

Using a text editor, add the following options to each cluster node's ORACLE_BASE/admin/domain_name/mserver/domain_name/ucm/cs/bin/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=ORACLE_BASE/admin/domain_name/mserver/domain_name/servers/WLS_WCCN/logs
EventDirectory=ORACLE_BASE/admin/domain_name/mserver/domain_name/servers/WLS_WCCN/logs/event/
ArchiverDoLocks=true 
DisableSharedCacheChecking=true 

The trailing N should match your nodes' server names, like WLS_WCC1 is WCCHOST1 and WLS_WCC2 is 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 Section 11.4.8, "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.

11.4.8 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 your WebLogic Server administration user name 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, and restart all WebCenter Content Managed Servers, using the WebLogic Server Administration Console.

Note:

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

ORACLE_BASE/admin/domain_name/wcc_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.)

11.5 Configuring Oracle HTTP Server with the Extended Domain

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. Then you can validate access to the Managed Servers through the load balancer.

This section includes the following topics:

• Section 11.5.1, "Configuring Oracle HTTP Server for the WLS_WCC Managed Servers"

• Section 11.5.2, "Validating Access Through the Load Balancer"

11.5.1 Configuring Oracle HTTP Server for the WLS_WCC Managed Servers

To configure Oracle HTTP Server for the WLS_WCC Managed Servers:

1. For each of the web servers on WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_INSTANCE/config/OHS/ohs1/moduleconf/wcc_vh.conf and ORACLE_INSTANCE/config/OHS/ohs2/moduleconf/wcc_vh.conf files:

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

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

To verify the URLs:

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

2. Access http://wcc.mycompany.com/cs to verify 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 http://wcc.mycompany.com/cs to verify 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.

To verify the cluster node:

1. Log in to the following WebCenter Content page, using your admin_user and admin_password credentials:

   https://wcc.mycompany.com/cs/idcplg?IdcService=CONFIG_INFO
   

2. Browse to the Administration/Configuration for instance page.

3. When the page is displayed, in the Options and Others section, 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.

11.6 Configuring Node Manager for Managed Servers

Oracle recommends using host name verification for 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. For more details, see Chapter 16, "Setting Up Node Manager for an Enterprise Deployment." The procedures in that chapter must be performed for the Oracle WebCenter Content deployment. The procedures in Section 16.3, "Enabling Host Name Verification Certificates for Node Manager," must be performed once for each host name and virtual IP address, using the information in the following table.

Run	Host Name (HOST)	Virtual IP Address (VIP)	Server Name (WLS_SERVER)
Run 1	WCCHOST1	n/a	WLS_WCC1 and WLS_IBR1
Run 2	WCCHOST2	n/a	WLS_WCC2 and WLS_IBR2
Run 3	WCCHOST1	WCCHOST1VHN1	WLS_SOA1
Run 4	WCCHOST2	WCCHOST2VHN1	WLS_SOA2
Run 5	WCCHOST1	WCCHOST1VHN2	WLS_IMG1
Run 6	WCCHOST2	WCCHOST2VHN2	WLS_IMG2
Run 7	WCCHOST1	WCCHOST1VHN3	WLS_CPT1
Run 8	WCCHOST2	WCCHOST2VHN3	WLS_CPT2

Notes:

• Even though not all the Managed Servers are configured at this point and are not mandatory for an Oracle WebCenter Content configuration that includes only WebCenter Content, the virtual host names used by the other Managed Servers are configured here to provide a one-step configuration process that includes both types of servers. For information about configuring the other managed servers, see the following chapters.

• For server migration of Capture, Oracle SOA Suite, and Imaging Managed Servers, you need to associate these servers with the specified virtual host names. Check that these virtual host names are enabled by DNS or /etc/hosts resolution in your system and that they map to the appropriate virtual IP addresses. For more information, see Section 3.4, "IP Addresses and Virtual IP Addresses."

• For the Capture, Oracle SOA Suite, and Imaging Managed Servers, perform all steps in Chapter 16, "Enabling Host Name Verification Certificates for Node Manager," except for Section 16.3.5, "Configuring Managed Servers to Use the Custom Keystores." You can do this step after you add the Managed Servers for each product to the domain.

11.7 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. For information about database backup, see the Oracle Database Backup and Recovery User's Guide.

To back up the installation at this point:

1. Back up Oracle 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 Oracle Web Tier using the following command (as root):

      tar -cvpf BACKUP_LOCATION/web.tar MW_HOME
      

   3. Back up the Oracle instance on Oracle 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 WCCHOST1 to create the backup:

   tar -cvpf edgdomainback.tar ORACLE_BASE/admin/domain_name