Dependencies Network Requirements Prerequisites

14-28 Oracle Fusion Middleware High Availability Guide

14.5.2.8 Oracle Discoverer Node Failures

For information about Oracle Discoverer Node failure, see Section 14.1.3.2, Common Component Node Failures.

14.5.2.9 Oracle Discoverer WebLogic Managed Server Failures

For information about Oracle Discoverer WebLogic Managed Server failure, see Section 14.1.3.3, Common Component WebLogic Managed Server Failures.

14.5.2.10 Oracle Discoverer Database Failures

For information about Oracle Discoverer database failure, see Section 14.1.3.4, Common Component Database Failures.

14.6 Configuring Oracle Portal, Forms, Reports, and Discoverer for High Availability

This section describes procedures for configuring Oracle Portal, Forms, Reports, and Discoverer for a high availability deployment. This section contains information on the following topics ■ Section 14.6.1, Prerequisites ■ Section 14.6.2, Assumptions ■ Section 14.6.3, Creating the Metadata Repository ■ Section 14.6.4, Install and Configure Application Tier on APPHOST1 ■ Section 14.6.5, Install and Configure Application Tier on APPHOST2 ■ Section 14.6.6, Scaling Out the Deployment

14.6.1 Prerequisites

Before installing Oracle Portal, Forms, Reports and Discoverer, review the prerequisites described in this section.

14.6.1.1 Dependencies

If you are using Oracle Single Sign-On, it is assumed that a high availability Identity Management Framework is available. Oracle Portal, Forms, Reports, and Discoverer uses Single Sign-On, which is available in Oracle Identity Management 10g.

14.6.1.2 Network Requirements

This section describes network requirements. Note: Oracle strongly recommends reading the release notes for any additional installation and deployment considerations prior to starting the setup process. Note: The hostnames and ports listed in these sections are, for illustrating this example deployment. When configuring your actual deployment, you can specify your own hostnames and ports. Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-29

14.6.1.2.1 Load Balancer In order to distribute requests across the Oracle Web servers, a

load balancer is required. This external load balancer should have the following features: ■ Virtual server name and port configuration ■ Process failure detection ■ Monitoring of ports HTTP, HTTPS for Oracle HTTP and HTTPS ■ SSL Translation if required

14.6.1.2.2 Load Balancer Configuration - Virtual Server Names and Ports If you are using a

load balancing router, it must be configured to enable the following: If using SSL traffic terminated at the load balancer A virtual IP address VIP1 that listens for requests to mysite.mycompany.com on port 443 an HTTPS listening port, and balances them to the application tier Oracle Web Cache, running on WEBHOST1 and WEBHOST2, port 7777 an HTTP listening port. You must configure the Load Balancing Router to perform protocol conversion. If using site SSL A virtual IP address VIP1 that listens for requests to mysite.mycompany.com on port 443 an HTTPS listening port, and balances them to the application tier, Oracle Web Caches running on WEBHOST1 and WEBHOST2 port 443 an HTTPS listening port. If using HTTP traffic terminated at the load balancer A virtual IP address VIP1 that listens for requests to mysite.mycompany.com on port 80 an HTTP listening port, and balances them to the application tier, Oracle Web Caches running on WEBHOST1 and WEBHOST2 port 7777 an HTTP listening port. Web Cache ■ The virtual IP address VIP1 listens for requests to mysite.mycompany.com on port 9401 an HTTP listening port, and balances them to the application tier Oracle Web Cache on WEBHOST1 and WEBHOST2 port 9401 an HTTP listening port. ■ HTTPHTTPS monitoring of Oracle Web Cache: The Load Balancing Router must be configured to detect an inoperative computer and stop routing requests to it until it is functioning again. Two Oracle Web Cache ports must be monitored: the HTTP request port and the invalidation port. To monitor port 7777, use the following URL in the Load Balancing Router configuration: hostname :port_oracle_http_server_webcache_static_.html For example: http:webhost1.mycompany.com:7777_oracle_http_server_webcache_static_.html If the Load Balancing Router receives a response from this URL, then the Oracle Web Cache instance is running. If it does not receive a response, the process or the Note: For security reasons, ports 9401, 9402 and 9403 on the load balancing router should not be visible to external users. 14-30 Oracle Fusion Middleware High Availability Guide server is down, and the load balancing router forwards all requests to the active computer. To monitor port 9401, use the following URL in the Load Balancing Router configuration: http:hostname.domain.com:9401x-oracle-cache-invalidate-ping For example: http:apphost1.mycompany.com:9401x-oracle-cache-invalidate-ping The load balancing router sends an HTTP request to this URL; the response header resembles the following: HTTP1.0 The load balancing router must be configured to detect the string HTTP in the first line of the response header. Therefore, when the load balancing router detects HTTP in the first line of the response header, the invalidation port is available. If it does not, all invalidation requests are routed to the active computer. To summarize, the load balancer requires the following configuration:

14.6.1.3 Databases