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 6, "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.2Extending the Domain for WebCenter Content

You can 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 Oracle SOA Suite deployment (wccedg.mycompany.com).

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.

On SOAHOST1, 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

Start the Fusion Middleware Configuration Wizard:

./config.sh

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

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:

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.

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.

In the Configure Clusters screen (Figure 10-6, 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.

10.3Starting Node Manager on WCCHOST1 and WCCHOST2

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

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:

If the WebCenter Content server is sharing the Middleware home in a local or shared storage with Oracle SOA Suite, 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.

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

cd WL_HOME/server/bin
./startNodeManager.sh

10.4Propagating the Domain Configuration to the Managed Server Domain Directories

To propagate the domain configuration:

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

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

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 the local host and the server IPs:

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

10.7Updating 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):

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 SOAHOST1 at ORACLE_BASE/admin/domain_name/aserver/domain_name/config/fmwconfig/.

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

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.

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

10.9 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:

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

10.10 Configuring Additional Parameters

Using a text editor, add the following options to each cluster node's MSERVER_HOME/base_domain/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):

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.

10.11Configuring 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:

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

Open the Administration page, and then choose Admin Server.

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

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

ServiceAllowRetry=true

Click Save, and restart all WebCenter Content Managed Servers.

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. Do not forget to restart all WebCenter Content Managed Servers.)

10.12Configuring 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:

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:

10.13Validating 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:

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

Access http://wcc.mycompany.com/cs to verify it is functioning properly.

Start WLS_WCC1 from the WebLogic Server Administration Console.

Stop WLS_WCC2 from the WebLogic Server Administration Console.

Access http://wcc.mycompany.com/cs to verify it is functioning properly.

10.14Configuring 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. For more details, see Chapter 13, "Setting Up Node Manager." The procedures in that chapter must be performed twice using the information in the following table.

Even though the WLS_IMG Managed Servers are not yet 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 Oracle WebCenter Content: Imaging are configured here to provide a one-step configuration process that includes both types of servers. For information about configuring the WLS_IMG Managed Server, see Chapter 11, "Extending the Domain to Include Imaging."

For server migration of WLS_IMG1 and WLS_IMG2, you need to associate these 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 3.4, "Configuring IPs and Virtual IPs."

10.15Backing 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:

Back up the web tier on WEBHOST1:

Shut down the instance using opmnctl.

ORACLE_BASE/admin/instance_name/bin/opmnctl stopall

Back up the Middleware home on the web tier using the following command (as root):

tar -cvpf BACKUP_LOCATION/web.tar MW_HOME

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

tar -cvpf BACKUP_LOCATION/web_instance_name.tar ORACLE_INSTANCE

Start the instance using opmnctl:

cd ORACLE_BASE/admin/instance_name/bin
opmnctl startall

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.

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

Scripting on this page enhances content navigation, but does not change the content in any way.