
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2
• A virtual IP address (VIP1) that listens for requests to myPortal.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 7777 (an HTTP listening
port). You must configure the load balancing router to perform protocol conversion.
• The virtual IP address VIP1 listens for requests to myPortal.mycompany.com on port
7777 (an HTTP listening port), and balances them to the application tier Oracle Web
Caches on WEBHOST1 and WEBHOST2 port 7777 (an HTTP listening port). Port
7777 on the load balancing router receives the HTTP loop-back requests made by the
Parallel Page Engine. The 7777 port also receives requests from the Portal Metadata
Repository for web provider design time messages. This configuration may require a
Network Address Translation (NAT) rule in the load balancing router in order for the
loop-back request from the PPE to succeed.
Note: For security reasons, port 7777 on the load balancing router should not be visible
to external users.
• The virtual IP address VIP1 listens for requests to myportal.mycompany.com on port
9401 (an HTTP listening port), and balances them to the application tier Oracle Web
Caches on WEBHOST1 and WEBHOST2 port 9401 (an HTTP listening port). Port
9401 port on the load balancing router receives invalidation messages from the Oracle
Portal Repository when content that is cached in Oracle Web Cache becomes stale. This
configuration might require a Network Address Translation (NAT) rule in the load
balancing router in order for the invalidation requests from the Oracle Portal repository
to succeed.
• HTTP monitoring of OracleAS 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 OracleAS Web Cache ports must be monitored: the HTTP
request port and the invalidation port.
18
Comentarios a estos manuales