Skip Headers
Oracle® Fusion Middleware Exalogic Enterprise Deployment Guide
Release EL X2-2 and EL X3-2

Part Number E18479-10
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

1 Enterprise Deployment Overview

This chapter introduces enterprise deployment reference topologies and configuration scenario for Oracle Exalogic. It contains the following sections:

1.1 What is Enterprise Deployment?

Enterprise deployment is an Oracle best practices blueprint based on proven Oracle high-availability and security technologies and recommendations for Oracle Exalogic. The best practices described in these blueprints span all Oracle products across the entire technology stack: Oracle Database, Oracle Fusion Middleware, Oracle Exalogic machine, and Oracle Enterprise Manager Grid Control.

An Oracle Fusion Middleware enterprise deployment:

For more information about high availability practices, go to maa.htm.

1.2 Prerequisities

Setup and commissioning of Oracle Exalogic machine, including initial storage and networking configuration, as described in Oracle Fusion Middleware Exalogic Machine Owner's Guide.

1.3 Terminology

This section provides information about Oracle Fusion Middleware concepts and terminologies that are related to administering Oracle Fusion Middleware.

1.4 Benefits of Oracle Recommendations

The Oracle Fusion Middleware configurations discussed in this guide are designed to ensure security of all invocations, maximize hardware resources, and provide a reliable, standards-compliant system for enterprise computing with a variety of applications.

The security and high availability benefits of the Oracle Fusion Middleware configurations are realized through isolation in firewall zones and replication of software components.

1.4.1 Built-in Security

The Enterprise Deployment architectures are secure because every functional group of software components is isolated in its own Demilitarized Zone (DMZ), and all traffic is restricted by protocol and port. The following characteristics ensure security at all needed levels, as well as a high level of standards compliance:

  • Configure external load balancers to redirect all external communication received on port 80 to port 443.


    The Oracle Technology Network ( provides a list of validated load balancers and their configuration at

  • Communication from external clients does not go beyond the Load Balancing Router level.

  • No direct communication from the Load Balancing Router to the data tier is allowed.

  • Components are separated in different protection zones: the web tier, application tier, and the data tier.

  • Direct communication between two firewalls at any one time is prohibited.

  • If communication begins in one firewall zone, it must end in the next firewall zone.

  • All communication between components across protection zones is restricted by port and protocol, according to firewall rules.

1.4.2 High Availability

The enterprise deployment architectures are highly available, because each component or functional group of software components is replicated on a different computer, and configured for component-level high availability.

1.4.3 Performance

Oracle Exalogic uses InfiniBand as the I/O fabric technology. InifiniBand provides a high throughput, low latency, and scalable fabric that is suitable for fabric consolidation of inter-processor communication, network and Storage. It is optimized for cluster and storage traffic.

Regardless of the design of the application, Oracle Exalogic offers a multitude of capabilities that dramatically improve the overall performance and reliability of the application. To benefit from the features and capabilities of Oracle Exalogic, Oracle WebLogic Suite 11g users only need to deploy their applications to the Exalogic machine; no code changes or rearchitecture of applications is necessary.

1.4.4 Application Isolation

Oracle Exalogic provides a high degree of isolation among concurrently deployed applications that have diverse security, reliability, and performance requirements. It creates a default IP over InfiniBand (IPoIB) link and an Ethernet over InfiniBand (EoIB) interface during initial configuration. All compute nodes in the Exalogic Machine are members of the default InfiniBand partition.

The most common model for application isolation involves multiple IP subnetting, in which the most mission-critical applications are assigned their own IP subnets layered above the default IPoIB link. In this model, some subnets may also contain applications that have less stringent or otherwise different resource requirements. Other subnets may host WebLogic domains, which contain multiple applications, such as those dedicated to a given department or line of business, or even used for application testing and development.

1.5 Overview of Oracle Exalogic Configured Environment

Before you start implementing the Oracle Exalogic enterprise deployment topology, you should understand the current state of the Exalogic environment.

It is assumed that you have completed all tasks described in the Oracle Fusion Middleware Exalogic Machine Owner's Guide, which discusses your data center site preparation, Oracle Exalogic machine commissioning, initial networking configuration including IP address assignments, and initial setup of the Sun ZFS Storage 7320 appliance.

This section describes the state of the Exalogic configured environment before enterprise deployment.

It discusses the following topics:

1.5.1 Network

Before you start configuring the enterprise deployment topology, you must run the Exalogic Configuration Utility to complete the following tasks, as described in the chapter "Initial Configuration of Exalogic Machine Using Oracle Exalogic Configuration Utility" in the Oracle Fusion Middleware Exalogic Machine Owner's Guide:

  • Configuration of IP addresses for all Exalogic compute nodes and the Sun ZFS Storage 7320 appliance.

  • Configuration of InfiniBand gateway switches.

  • Configuration of the Cisco Ethernet management switch.

  • Setup and verification of the default IP over InfiniBand (IPoIB) link spanning all compute nodes.

  • Setup and verification of the default Ethernet over InfiniBand (EoIB) link for connectivity with components of the topology running on Ethernet.

  • Configuration of the default InfiniBand partition that covers all of the compute nodes in Exalogic Machine.

1.5.2 Sun ZFS Storage 7320 appliance

The initial configuration of the Sun ZFS Storage 7320 appliance in your Oracle Exalogic machine is completed at the time of manufacturing. For more information about default shares (Exported File Systems), see the "Default Storage Configuration" section in the Oracle Fusion Middleware Exalogic Machine Owner's Guide.

After completing this initial configuration, you must proceed to create custom shares, as described in Section 3.4.2, "Setting Up Enterprise Deployment Storage Configuration".

1.5.3 Oracle Software

Oracle Linux 5.5 or Oracle Solaris 11 is pre-installed on each of the compute nodes in your Oracle Exalogic machine.

You must download the Oracle WebLogic 10.3.4 software installer and run the installation program on one of the compute nodes. You must save the installation binaries, including Oracle Middleware Home, on a shared file system on the Sun ZFS Storage 7320 appliance. Before you can do so, you must configure shared storage by creating a Project and defining shares and LUNs to set up the directory structure, as necessary. Note down the mount point for such shares, so you can mount the required locations or directories from Exalogic compute nodes.

For more information, see Chapter 3, "Network, Storage, and Database Preconfiguration" and Chapter 4, "Installing Oracle Software".


You can download the Oracle WebLogic 10.3.4 software from Select Oracle Fusion Middleware as the Product Pack, Linux x86-64 or Oracle Solaris on x86-64 (64-bit) as the Platform, and Oracle Fusion Middleware 11g Media Pack for Exalogic as the Media Pack.

1.6 Administrator Roles and Permissions

Administration and management of Oracle Exalogic may span multiple specialized roles and separate departments in organizations. This is due to the integrated nature of Exalogic that combines multiple compute servers, shared storage and shared networking infrastructure. Oracle recommends that you align the planned use of Exalogic to the appropriate roles in your organization. For example, during initial deployment and day-to-day operations, you may consider roles, such as the following:

1.7 Task Roadmap

Table 1-1 lists high-level enterprise deployment tasks for Oracle Linux or Solaris physical environments.

Table 1-1 Enterprise Deployment Tasks for Oracle Linux or Solaris Physical Environments

Step Description For More Information


Familiarize yourself with Exalogic reference topologies.

See Enterprise Deployment Overview and Reference Topology and Slicing Diagram


Examine your Exalogic machine rack and compute nodes. Ensure that the base operating system (Oracle Linux or Solaris 11 Express) is installed on the compute nodes, and the primary IPoIB and EoIB interfaces are set up.

See Overview of Oracle Exalogic Configured Environment


Review and understand the horizontal slicing of an Exalogic machine and the example configuration scenario. Slicing of an Exalogic machine quarter rack is included as an example.

See Example: Horizontal Slicing Within Exalogic Machine Quarter Rack and Example Configuration Scenario for Exalogic x86 Physical Machines


Prepare your network, database, and storage for enterprise deployment.

See Network, Storage, and Database Preconfiguration


Install Oracle software.

See Installing Oracle Software


Configure Oracle Fusion Middleware software.

See Configuring Oracle Fusion Middleware


Configure Oracle HTTP Server.

See Mandatory: Configuring Oracle HTTP Server for Administration Server and Managed Servers


Enable Exalogic-specific optimizations in WebLogic Server.

See Enabling Exalogic-Specific Enhancements in Oracle WebLogic Server 11g Release 1 (10.3.4)


Deploy a sample application to the WebLogic cluster that is configured to run on Exalogic compute nodes.

See Deploying a Sample Web Application to an Oracle WebLogic Cluster


Manage the enterprise deployment topology.

See Managing the Topology


Monitor the software in the enterprise deployment topology by using Oracle Enterprise Manager Grid Control.

See Monitoring the Topology Using Oracle Enterprise Manager Grid Control