2-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
■
biinternal.mycompany.com Ensure that the virtual server names are associated with IP addresses and are part of
your DNS. The nodes running Oracle Fusion Middleware must be able to resolve these virtual server names.
2.2.1.1 bi.mycompany.com
bi.mycompany.com is a virtual server name that acts as the access point for all HTTP traffic to the run-time Oracle BI components. Traffic to SSL is configured. Clients
access this service using the address bi.mycompany.com:443. This virtual server is defined on the load balancer.
2.2.1.2 admin.mycompany.com
admin.mycompany.com is a virtual server name that acts as the access point for all internal HTTP traffic that is directed to administration services such as Oracle
WebLogic Administration Server Console and Oracle Enterprise Manager.
The incoming traffic from clients is not SSL-enabled. Clients access this service using the address admin.mycompany.com:80 and the requests are forwarded to port 7777 on
WEBHOST1 and WEBHOST2. This virtual server is defined on the load balancer.
2.2.1.3 biinternal.mycompany.com
biinternal.mycompany.com is a virtual server name used for internal invocation of BI services. This URL is not exposed to the internet and is only accessible from the
intranet.
The incoming traffic from clients is not SSL-enabled. Clients access this service using the address biinternal.mycompany.com:80 and the requests are forwarded to port 7777
on WEBHOST1 and WEBHOST2. This virtual server is defined on the load balancer.
2.2.2 Load Balancers
This enterprise topology uses an external load balancer. For more information on load balancers, see
Chapter 4, Configuring the Web Tier.
Configuring the Load Balancer Perform these steps to configure the load balancer:
1.
Create a pool of servers. You will assign this pool to virtual servers.
2.
Add the addresses of the Oracle HTTP Server hosts to the pool. For example:
■
WEBHOST1:7777
■
WEBHOST2:7777
3.
Configure a virtual server in the load balancer for bi.mycompany.com:443.
■
For this virtual server, use your systems frontend address as the virtual server address for example, bi.mycompany.com. The frontend address is the
Note: The Oracle Technology Network
http:www.oracle.comtechnology provides a list of validated
load balancers and their configuration at: http:www.oracle.comtechnologyproductsiashi_avTested_
LBR_FW_SSLAccel.html
Database and Environment Preconfiguration 2-7
externally facing host name used by your system and that will be exposed in the Internet.
■
Configure this virtual server with port 80 and port 443. Any request that goes to port 80 should be redirected to port 443.
■
Specify HTTP as the protocol.
■
Enable address and port translation.
■
Enable reset of connections when services andor nodes are down.
■
Assign the pool created in step 1 to the virtual server.
■
Create rules to filter out access to console and em on this virtual server.
4.
Configure a virtual server in the load balancer for admin.mycompany.com:80.
■
For this virtual server, use your internal administration address as the virtual server address for example, admin.mycompany.com. This address is typically
not externalized.
■
Specify HTTP as the protocol.
■
Enable address and port translation.
■
Enable reset of connections when services andor nodes are down.
■
Optionally, create rules to allow access only to console and em on this virtual server.
■
Assign the pool created in step 1 to the virtual server.
5.
Configure a virtual server in the load balancer for biinternal.mycompany.com:80.
■
For this virtual server, use your internal administration address as the virtual server address for example, biinternal.mycompany.com. This address is
typically not externalized.
■
Specify HTTP as the protocol.
■
Enable address and port translation.
■
Enable reset of connections when services andor nodes are down.
■
Assign the pool created in step 1 to the virtual server.
■
Optionally, create rules to filter out access to console and em on this virtual server.
6.
Configure monitors for the Oracle HTTP Server nodes to detect failures in these nodes.
■
Set up a monitor to regularly ping the URL context.
■
For the ping interval, specify a value that does not overload your system. You can try 5 seconds as a starting point.
■
For the timeout period, specify a value that can account for the longest response time that you can expect from your BI system, that is, specify a value
greater than the longest period of time any of your requests to HTTP servers can take.
Tip: Use GET \n\n instead if the Oracle HTTP Servers document
root does not include index.htm and Oracle WebLogic Server returns a 404 error for .
2-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
2.2.3 IPs and Virtual IPs
