Validating Oracle HTTP Server Through the Load Balancer Backing Up Oracle HTTP Server

Installing Oracle HTTP Server 3-3

13. In the Specify Security Updates screen, enter your e-mail address to receive

e-mail notifications of security issues if required. Enter your Oracle Support Password to receive security updates through My Oracle Support.

14. In the Installation Summary screen, ensure that the selections are correct, and

click Install. 15. In the Configuration screen, multiple configuration assistants are launched in succession, which can be a lengthy process. When it completes, the Configuration Completed screen appears.

16. In the Installation Completed screen, click Finish to exit.

3.2 Validating Oracle HTTP Server Through the Load Balancer

Define the directives of the VirtualHost section of the httpd.conf file on both OHS servers. This file is located in the ORACLE_BASEadmininstance_name configOHSohs1 or ohs2 directory. Add the following entries to the file: NameVirtualHost :7777 VirtualHost :7777 ServerName https:wc.mycompany.com:443 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost NameVirtualHost :7777 VirtualHost :7777 ServerName admin.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost NameVirtualHost :7777 VirtualHost :7777 ServerName wcinternal.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost Make sure that you restart both OHS servers after modifying the httpd.conf files: WEBHOST cd ORACLE_BASEadmininstance_namebin WEBHOST opmnctl stopall WEBHOST opmnctl startall Access the following URLs to ensure that your load balancer and Oracle HTTP Server are configured properly: ■ http:wc.mycompany.comindex.html ■ http:admin.mycompany.comindex.html ■ http:wcinternal.mycompany.comindex.html Note: For more information on setting ports, refer to Oracle Fusion Middleware Installation Guide for Oracle SOA Suite. 3-4 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter ■ https:wc.mycompany.comindex.html

3.3 Backing Up Oracle HTTP Server

After you have verified that the Oracle HTTP Server installation 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 this point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrators 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 this guide. For information on how to recover components, see 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 in the guide. To back up the installation a this point, complete these steps: 1. Shut down the instance using opmnctl. ORACLE_BASE admininstance_namebinopmnctl stopall 2. Back up the Middleware Home on the web tier using the following command: tar -cvpf BACKUP_LOCATIONweb.tar MW_HOMEweb 3. Back up the Instance Home on the web tier using the following command: tar -cvpf BACKUP_LOCATIONweb_instance_name.tar ORACLE_INSTANCE 4. Start the instance using opmnctl: ORACLE_BASE admininstance_namebinopmnctl startall 4 Creating a Domain 4-1 4 Creating a Domain This chapter describes how to create a domain using the Configuration Wizard, Oracle WebLogic Server Administration Console, Oracle Enterprise Manager, and Oracle WSM Policy Manager. You can extend the domain to add WebCenter components. This chapter contains the following sections: ■ Section 4.1, Installing Oracle Fusion Middleware Home ■ Section 4.2, Backing Up the Installation ■ Section 4.3, Enabling VIP1 in SOAHOST1 ■ Section 4.4, Running the Configuration Wizard on SOAHOST1 to Create a Domain ■ Section 4.5, Creating boot.properties for the Administration Server on SOAHOST1 ■ Section 4.6, Starting Node Manager on SOAHOST1 ■ Section 4.7, Starting the Administration Server on SOAHOST1 ■ Section 4.8, Validating the Administration Server ■ Section 4.9, Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server ■ Section 4.10, Applying the Java Required Files JRF Template to the WSM-PM_ Cluster ■ Section 4.11, Disabling Host Name Verification for the Oracle WebLogic Administration Server and the WLS_WSM1 Managed Server ■ Section 4.12, Starting and Validating the WLS_WSM1 Managed Server ■ Section 4.13, Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility ■ Section 4.14, Disabling Host Name Verification for the WLS_WSM2 Managed Server ■ Section 4.15, Starting Node Manager on SOAHOST2 ■ Section 4.16, Starting and Validating the WLS_WSM2 Managed Server Important: Oracle strongly recommends that you read the release notes for any additional installation and deployment considerations prior to starting the setup process. 4-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter ■ Section 4.17, Configuring the Java Object Cache for Oracle WSM ■ Section 4.18, Configuring Oracle HTTP Server for the Administration Server and the WLS_WSM-PMn Managed Servers ■ Section 4.19, Registering Oracle HTTP Server With WebLogic Server ■ Section 4.20, Setting the Frontend URL for the Administration Console and Setting Redirection Preferences ■ Section 4.21, Validating Access Through Oracle HTTP Server ■ Section 4.22, Manually Failing Over the Administration Server to SOAHOST2 ■ Section 4.23, Validating Access to SOAHOST2 Through Oracle HTTP Server ■ Section 4.24, Failing the Administration Server Back to SOAHOST1 ■ Section 4.25, Backing Up the Installation

4.1 Installing Oracle Fusion Middleware Home