This chapter describes an Oracle SOA Exalogic enterprise deployment on Exalogic with an external Oracle HTTP Server Web tier. It is one of the alternative topologies, discussed in Section 2.1.2, "Alternative Deployment Topologies."
This appendix contains the following topics:
In this alternative Oracle SOA topology on Exalogic topology, user requests are being routed by an Oracle HTTP Server Web tier, rather than the Oracle Traffic Director Web listeners. Compare this topology with the one shown in Chapter 2, "Introduction and Planning."
The components of the alternative Oracle SOA with Oracle HTTP Server topology are identical to those described in Chapter 2, except for the following:
The Web tier in the Oracle HTTP Server topology consists of two Oracle HTTP Server instances on separate WEHOST1 and WEBHOST2 host computers. These computers are outside of the Exalogic machine, and a firewall separates them from the application tier.
Most of the Fusion Middleware SOA components can function without the Web tier, but for most Exalogic enterprise deployments, the Web tier is desirable.
In the Web tier:
WEBHOST1 and WEBHOST2 have Oracle HTTP Server, WebGate (an Access Manager component), and the
mod_wl_ohs plug-in module installed. The
mod_wl_ohs plug-in module enables requests to be proxied from Oracle HTTP Server to a WebLogic Server running in the application tier.
WebGate (an Oracle Access Management component) in Oracle HTTP Server uses Oracle Access Protocol (OAP) to communicate with Access Manager running on SOAHOST1 and SOAHOST2, in the Fusion Middleware SOA DMZ. WebGate and Access Manager are used to perform operations such as user authentication.
On the firewall protecting the Web tier, the HTTP ports are 443 (HTTP_SSL_PORT) for HTTPS and 80 (HTTP_PORT) for HTTP. Port 443 is open.
Similar to the topology in Section 2.3, "Understanding the Topology Components." Oracle Traffic Director is used as a load balancer for internal communications within the Exalogic rack. By using Oracle Traffic Director rather than routing requests through the load balancer, you can utilize the internal IPoIB network which is both more secure and faster.
In this topology, the Oracle Traffic Director instances are in an active-passive configuration and the required virtual IP addresses used for internal communication (such as oudinternal.mycompany.com) are defined in the Oracle Traffic Director configuration.
For more information on configuring Oracle Traffic Director failover groups for active-passive mode, see "Creating Failover Groups" in the Oracle Traffic Director Administrator's Guide.