Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview. Disclaimer. The following is intended
An Oracle White Paper April 2014
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud An Architectural Overview
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Introduction ....................................................................................... 1 Simplicity, Reliability and Performance for SAP Deployments ........... 3 Oracle Exalogic Deployment Scenarios ............................................. 5 Physical Deployment Scenario ...................................................... 5 Virtual Deployment Scenario ......................................................... 6 Oracle Exalogic System Tuning. .................................................... 7 Oracle Exalogic and Oracle Exadata for SAP NetWeaver ................. 7 Prerequisites for Running SAP NetWeaver 7.x .................................. 9 Oracle ZFS Storage Appliance Usage in SAP Environments........... 11 Software Development Lifecycle Considerations ............................. 13 High Availability for SAP NetWeaver on Oracle Exalogic and Oracle Exadata................................................................................ 13 Expanding Capacity, Multiple Oracle Exalogic and Oracle Exadata Machines ........................................................................... 14 Conclusion ...................................................................................... 15 References ...................................................................................... 16
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Introduction SAP customers, like other ERP and CRM customers, face the challenge of building and maintaining infrastructure made up of disparate components (including compute, storage and networking) to support a growing and ever-changing application topology. The use of these individual components in combination can add an additional amount of complexity and risk to an already difficult and usually time-sensitive process of implementing and operating such systems. Time and resources are then spent tuning and re-tuning suboptimal performance of this infrastructure as new environments are built, and new phases of the project are entered. Oracle Engineered Systems offer a cost effective and standardized set of hardware, network, storage and software components—all prewired, optimized and tested—ready to run critical business processes such as SAP workloads. They use best-in-class standardized components to provide maximum performance leveraging synergies between components that are based on open standards, resulting in reliability and scalability. This allows organizations to start small and grow with business needs. Oracle Engineered Systems enable a shift that makes sense for the majority of companies— to focus IT investment on enabling their core competencies and business rather than on managing low-level infrastructure details. Oracle Exalogic Elastic Cloud is such an Engineered Solution. As of August 2011, SAP officially supported Oracle Exalogic Elastic Cloud as a deployment platform, as documented in SAP Note 1617188. In 2014, support for virtual deployments of Oracle Exalogic Elastic Cloud has been added. Virtualization enables a system’s resources (CPUs, memory, network, and storage) to be subdivided, so that multiple systems or applications can be consolidated onto a single physical system. This consolidation results in greatly increased utilization of system resources and a lower total cost of ownership (TCO). In addition, virtualization provides flexibility in provisioning and can help deploy new services faster and more easily.
1
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
This document outlines the value of using SAP on Oracle Exalogic Elastic Cloud, and discusses architectural and practical considerations when deploying SAP on Oracle Exalogic and Oracle Exadata Database Machine. We begin with a short overview of Oracle Exalogic as a system and the close interaction with Oracle Exadata as its back-end database. We then discuss the prerequisites for running SAP on Oracle Exalogic including architectural, version and other requirements. We explore the role of the integrated Oracle ZFS Storage Appliance system for providing shared storage to the application servers, and offer other potential uses for it. Finally, we outline the installation process for SAP on Oracle Exalogic, including high availability (HA) and software lifecycle considerations, and explore ways to easily build and scale SAP environments. It is recommended to also read the Oracle white paper Using SAP NetWeaver with the Oracle Exadata Database Machine for details on setting up the Oracle Database environment for SAP on Oracle Exadata.
2
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Simplicity, Reliability and Performance for SAP Deployments Most SAP customers strive to achieve three goals when deploying SAP:
Simplicity, so they can quickly and effortlessly install, customize and operate their SAP application landscape, at minimum TCO.
Reliability, so that running the infrastructure for SAP doesn't interfere with offering services to users and running business operations.
Performance, to minimize transaction times for users, while enabling new business opportunities based on superior, previously unavailable performance levels.
Along with these requirements for deploying SAP landscapes, all Oracle Engineered Systems offer customers the ability to:
Save time, as system components (hardware and software) are developed, built and tested before being shipped to customers; installation onsite therefore take less time than running this process on customer premises for every installation.
Consolidate, as systems are optimized for optimal performance and usage, more throughput can be achieved, saved space and resources can therefore be used to consolidate older and numerous systems.
Reduce risk, by using an integrated product stack provided by one vendor, you have only one “throat to choke” to deploy and run your complete underlying infrastructure.
Previously there were two fundamental types of infrastructure for deploying SAP, with varying potential to deliver against these goals:
Traditional, high-end, vertically scalable Unix servers: These systems provide great reliability and performance, but come at a relatively high cost to purchase and maintain.
Commodity, horizontally scalable x86 systems: While offering high performance at low cost, these systems are complex to integrate, test, deploy, operate and service due to their highly distributed nature and the differences in quality, make and configuration across component vendors. Reliability has to be achieved through fail-over mechanisms, extensive testing and certification programs, assuming that every component can fail at any time.
Now, there is a third choice for SAP infrastructures that combines the best of both worlds: Engineered Systems. Oracle Exalogic is the Engineered System for running middleware and packaged applications, capable of virtually unlimited scale, unbeatable performance, and previously unimagined management simplicity. As mentioned previously, Oracle Engineered Systems offer a standardized set of hardware, network, storage and software components, prewired and tested, ready to run (see Figure 1).
3
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Figure 1. Oracle Exalogic Elastic Cloud Full Rack
In the case of Oracle Exalogic Elastic Cloud, this includes using high-performance x86-based compute nodes, Oracle ZFS Storage Appliance, Sun Network QDR InfiniBand Gateway and Sun Datacenter InfiniBand switches, running Oracle Exalogic Elastic Cloud software. The Oracle Exalogic hardware is pre-assembled and delivered in standard 19” 42 Unit rack configurations. There are 4 sizes available, starting at an Eighth rack, providing 4 compute nodes through to Quarter, Half and Full, with 8, 16 and 30 compute nodes respectively. Each Oracle Exalogic configuration contains the integrated Oracle ZFS Storage Appliance, a clustered, high-performance disk storage subsystem, and the Exabus communication fabric—a high-bandwidth, low-latency InfiniBand interconnect fabric to connect individual components within the configuration, as well as to additional Oracle Exalogic and other Oracle Engineered Systems. In addition, each Oracle Exalogic configuration includes 10 Gigabit Ethernet connectivity to the data center service network and Gigabit Ethernet for integration with the data center management network. Oracle Exalogic runs either Oracle Solaris or Oracle Linux, and Oracle VM virtualization software. Additional Oracle Exalogic Elastic Cloud software includes: Exabus, communication fabric software; Traffic Director, for load balancing and monitoring; Storage Management Software; and Exalogic Control, for management and monitoring. Oracle Exalogic Elastic Cloud, as part of Oracle's Engineered Systems family, is designed to provide simplicity for application deployment: By offering modular building blocks that are designed, integrated, tested, shipped, installed, configured and operated as a whole, Oracle Exalogic radically reduces complexity for SAP environments. For SAP customers, this means a quick, efficient and easy-todeploy way of providing infrastructure for SAP landscapes. All Oracle Exalogic configurations are fully redundant at every level and are designed with no single point of failure. Furthermore, all components are highly standardized, factory-integrated, vertically
4
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
optimized, certified and tested, with a single point of contact for all storage, server, OS and system management support and service needs. But not only does this mean that there is less work to do to set it up, it also means that all customers run the same Oracle Exalogic configuration that was tuned and tested at the Oracle factory, substantially reducing risk of errors, simplifying diagnosis, and standardizing operations. Oracle Exalogic Control’s built-in anti-affinity functions, together with SAP’s own high availability techniques, can be utilized to provide reliability for SAP infrastructure deployments. This is discussed in subsequent chapters.
Oracle Exalogic Deployment Scenarios As of version 2.0.6 of Oracle Exalogic Elastic Cloud, there are two deployment scenarios available for SAP customers, physical and virtual:
Physical
Oracle Linux 5.x x86_64
Oracle Solaris 11 x86_64
Virtual
Oracle VM 3.2.1 (running Oracle Linux 5.x x86_64 guests)
Oracle Solaris Zones in Oracle Solaris 10 or 11
Physical Deployment Scenario In a physical deployment scenario, each Oracle Exalogic compute node is a fully self-contained unit of compute capacity running either Oracle Linux 5.x x86_64, or Oracle Solaris 11 x86_64. This configuration includes the complete number of multi-core x86 Xeon processors, redundant power supplies, fast ECC memory, and redundant InfiniBand Host Channel Adapters of a compute node. Each compute node also contains two solid-state disks (SSDs), which host the operating system images used to boot the node and act as high-performance local swap space and storage for diagnostic data. To implement SAP NetWeaver 7.x on a physical (non-virtualized) deployment of Oracle Exalogic Elastic Cloud, use the following steps. These steps assume that an Oracle Exadata Database Machine has been already set up as the Oracle Database for SAP in accordance with the Oracle white paper Using SAP NetWeaver with the Oracle Exadata Database Machine. Oracle Exadata needs to be connected to Oracle Exalogic using the built-in InfiniBand fabric. 1. Perform a standard install of Oracle Exalogic with the latest supported release of Oracle Linux or
Oracle Solaris on all compute nodes as documented in the standard Oracle Exalogic Installation and Configuration Guide. 2. Set up Oracle Linux for installation of SAP in accordance with standard SAP Linuxlab procedures.
5
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
3. Set up the built-in Oracle ZFS Storage Appliance in Oracle Exalogic for providing the /sapmnt, /usr/sap, /usr/sap/trans, /oracle, /oracle/client and any other necessary NFS shares.
Set up all Oracle Linux nodes for mounting these shares from the Oracle ZFS Storage Appliance. 4. Perform a standard installation of SAP on one node in Oracle Exalogic, using the NFS shares
created above. See SAP Note 1567511 – Oracle Linux 5.x SAP installation and upgrade for details. 5. Use Oracle Recovery Manager (Oracle RMAN) to move the SAP database onto Oracle Exadata and
enable Oracle Real Application Clusters (Oracle RAC) on the Oracle Exadata machine. Make sure
that the necessary SAPInst RAC/ASM Exadata Database Instance Preparation steps have been executed on all database nodes on the Oracle Exadata system before using Oracle RMAN. 6. Install additional SAP instances on Oracle Exalogic and connect them with the corresponding
Oracle RAC nodes on Oracle Exadata according to your needs.
Virtual Deployment Scenario The virtual deployment scenario includes an enhanced Oracle VM installation, a tightly integrated server virtualization layer with unique capabilities allowing the consolidation of multiple, separate virtual machines containing applications or middleware on each server node while introducing essentially no I/O virtualization overhead to the Exabus InfiniBand network and storage fabric. The purpose of server virtualization is to fundamentally isolate the operating system and applications stack from the constraints and boundaries of the underlying physical servers. By doing this, multiple virtual machines can be presented with the impression that they are each running on their own physical hardware when, in fact, they are sharing a physical server with other virtual machines. This allows server consolidation in order to maximize the utilization of server hardware, while minimizing costs associated with the proliferation of physical servers—namely hardware, cooling, and real estate expenses. While virtualization on Oracle Exalogic could be achieved via an Oracle Solaris Zone configuration, in this white paper, we will concentrate on the Oracle VM with Linux guest configuration. The white paper Installing New SAP Application Server Instances with SAP LVM 2.0 on Oracle Solaris can be used as a basis for running SAP components on Oracle Solaris Zones on Oracle Exalogic. To implement SAP NetWeaver 7.x on a virtual deployment of Oracle Exalogic Elastic Cloud, follow the steps below: 1. Perform a standard install of Oracle Exalogic Virtual Configuration with the latest supported release
of Oracle VM and Oracle Exalogic Control as documented in the standard Oracle Exalogic Installation and Configuration Guide. 2. Create a Virtual Datacenter (vDC) Account for the SAP Landscape. 3. Deploy a virtual machine using the standard Oracle Exalogic Guest Based Template for installation
of SAP in accordance with standard SAP Linuxlab procedures.
6
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
4. Set up the built-in Oracle ZFS Storage Appliance in Oracle Exalogic for providing the /sapmnt, /usr/sap, /usr/sap/trans, /oracle, /oracle/client and any other necessary NFS shares. 5. Perform a standard installation of SAP on the virtual machine (VM) in Oracle Exalogic, using the
NFS shares created above. See SAP Note 1567511 – Oracle Linux 5.x SAP installation and upgrade for details. 6. Implement SAP monitoring requirement using Oracle VM Utilities in an Oracle Exalogic VM. 7. Use Oracle RMAN to move the SAP database onto Oracle Exadata and enable Oracle RAC on the
Oracle Exadata machine. Make sure that the necessary SAPInst RAC/ASM Exadata Database
Instance Preparation steps have been executed on all database nodes on the Oracle Exadata system before using Oracle RMAN. 8. Deploy additional Oracle Exalogic VMs, mounting the shares from the Oracle ZFS Storage
Appliance. Connect them with the corresponding Oracle RAC nodes on Oracle Exadata according to your needs.
Oracle Exalogic System Tuning. Oracle Exalogic is tuned for a wide range of workload types, including data-intensive and I/O-intensive workloads. There is therefore no need to configure parameters for a particular capability. The built-in InfiniBand interconnect—in both the physical and virtual deployment scenarios—offers 4 times more bandwidth and a tenth the latency per link than traditional 10 GbE networks. When connecting to data, it offers 96 times greater throughput, as there is 960 gigabits/sec throughput between Oracle Exalogic and Oracle Exadata. This super-fast low-latency network, in combination with fast, multi-core processors and fast ECC memory, delivers unprecedented levels of performance and short transaction times for even the most demanding SAP environments. Oracle Exalogic provides simplicity, lowers the time to and the risk of deployment, and offers high levels of performance and scalability, making it an ideal, stable and reliable infrastructure solution for running the application server tier of a typical three-tier SAP installation.
Oracle Exalogic and Oracle Exadata for SAP NetWeaver SAP NetWeaver on Oracle Exalogic requires the use of an Oracle Database running on Oracle Exadata. Oracle Exadata Database Machine is an easy-to-deploy solution for hosting Oracle Database that delivers the highest levels of database performance available. Oracle Exadata Database Machine comprises database servers, Oracle Exadata Storage Servers, an InfiniBand fabric for storage networking and all the other components required to host an Oracle Database. It delivers outstanding I/O and SQL processing performance for online transaction processing (OLTP), data warehousing (DW) and consolidation of mixed workloads. Extreme performance is delivered for all types of database applications by leveraging a massively parallel grid architecture using Oracle Real Application
7
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Clusters and Oracle Exadata storage. Oracle Exadata Database Machine storage delivers breakthrough performance with linear I/O scalability, is simple to use and manage, and delivers mission-critical availability and reliability. The same benefits of an Engineered System that apply to Oracle Exalogic also apply to Oracle Exadata: All components have been engineered together, are vertically optimized, take less time to set up, and offer simplified operation, thus reducing risk of errors, simplifying diagnosis, and enabling more efficient, lower-cost operation. Oracle Exalogic connects to Oracle Exadata through the same high-speed, low-latency InfiniBand fabric that is used inside the systems, providing a scalable and powerful networking foundation for communication between nodes in a system, as well as for scaling across multiple Oracle Exadata and Oracle Exalogic racks (see Figure 2). The InfiniBand fabric that spans Oracle Exalogic and Oracle Exadata components provides the following key ways of simplifying and accelerating SAP NetWeaver installations running on Oracle Exalogic:
NFS mounts from the Oracle ZFS Storage Appliance to SAP application nodes in Oracle Exalogic use the InfiniBand infrastructure for faster data transport than traditional TCP/IP over 10 GbE. This benefits both SAP application servers running in Oracle Exalogic and Enqueue Servers running on Oracle Exadata.
SAP application servers running the ABAP stack use Oracle Net Services through Oracle Instant Client to connect to the Oracle database. This enables them to easily use the SDP protocol over InfiniBand at high bandwidth and low latency, bypassing the traditional TCP/IP stack.
All remaining standard TCP/IP connections running on the InfiniBand fabric will benefit from the 4x higher bandwidth per network connection compared to 10 GbE.
Both networking and storage connections to and from SAP NetWeaver application server nodes are handled through a single fabric, reducing complexity and improving reliability through using reduced component counts.
In addition, IP over InfiniBand can be used for the communication between the SAP work processes and the Enqueue Server on Oracle Exadata.
8
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Figure 2: Oracle Exalogic and Oracle Exadata combined offers superior performance
Oracle Exalogic is the best solution for realizing the full performance benefits of Exadata for SAP, because it integrates directly into the heart of the Exadata backplane: The InfiniBand fabric. Simplicity is another key advantage for SAP on Oracle Exalogic: Because all components of Oracle Exalogic have been engineered, assembled and tuned together at the factory, set-up time is significantly reduced. And by reducing risk of errors, simplifying diagnosis, and enabling more efficient, lower-cost operation, total infrastructure costs can also be drastically reduced.
Prerequisites for Running SAP NetWeaver 7.x When using Oracle Exalogic Elastic Cloud in SAP environments, the following prerequisites need to be in place:
Only SAP NetWeaver 7.x or higher is supported, including SAP products which are based on SAP NetWeaver 7.x. Please check the SAP Product Availability Matrix for details regarding supported SAP product releases. Examples include:
9
SAP ERP (ECC) 6.0 SAP BW 7.x SAP CRM 2005 / 2007 / 7.x SAP PLM 6.0 / 7.0x SAP SRM 2005 / 2007 / 7.x SAP SCM 2005 / 2007 / 7.x SAP Oil&Gas 2005 / 6.x SAP Banking Services 5.0 / 6.0 / 7.0 / 8.0
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Running SAP on Oracle Exalogic is only supported as a three-tier SAP installation. SAP instances run on the Oracle Exalogic Elastic Cloud VMs or physical nodes.
Only Unicode SAP NetWeaver 7.x or higher certified for Oracle Linux 5 or Oracle Solaris 11 x64 is supported, including SAP products which are based on SAP NetWeaver 7.x.
SAP monitoring for virtualization will be accomplished by leveraging features in Oracle VM Utilities. The installation and implementation steps are described in SAP Note 1817065 and in the Oracle VM Utilities Guide. Oracle VM Utilities is a small collection of command line utility scripts that can be installed on any Oracle Linux Server and virtual machines. The test was done with Oracle VM Utilities running in the EC Control instance but for production uses, it's highly recommended to run Oracle VM Utilities on an Oracle Exalogic VM outside of the control instance to minimize the potential impact to the Oracle Exalogic control stack.
The SAP Central Services must be hosted via Oracle RAC on Oracle Exadata, with their own separate cluster service. Note: While the Central Services can reside on Oracle Exalogic, it is only with the conditions that HA capabilities are disabled. And this is not recommended.
The Oracle Database for SAP must run on Oracle Exadata. Oracle Exalogic can only be used in combination with Oracle Exadata and may not be used in combination with other database server hardware or other non-Oracle databases.
Figure 3 illustrates the relationship between the SAP components, Oracle Exalogic and Oracle Exadata in a three-tier configuration:
Figure 3: Oracle Exalogic and Oracle Exadata SAP three-tier configuration
10
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
See the Oracle white paper Using SAP NetWeaver with the Oracle Exadata Database Machine for details on how to set up Oracle Exadata for use with SAP. The minimum supported Oracle Database release is Oracle Database 11g Release 2 Patchset 1 (11.2.0.2) on Oracle Exadata with SAP Software on Oracle Exalogic.
Oracle ZFS Storage Appliance Usage in SAP Environments The Oracle Exalogic storage subsystem stores all application binaries, log files and content necessary for the applications to execute. Compute nodes (and VMs, in the case of virtual configurations) mount configured storage system partitions over the InfiniBand network. This eliminates the need to back up individual servers. And in the event of failure of a compute node or VM, the partition can simply be mounted from another machine while the failed compute node is serviced or replaced. The Oracle Exalogic storage subsystem consists of two physically separate storage heads in an active/standby configuration and a large shared disk array. Each of the storage heads is directly attached to the I/O fabric with redundant QDR InfiniBand connections. The storage subsystem is accelerated with two types of solid state disks that are used as read and write caches, in order to increase system performance. The storage heads transparently integrate the many Serial Attached SCSI (SAS) disks in the disk array into a single ZFS cluster, which is then made available to Oracle Exalogic servers via standard Network File System (NFSv3/4) protocol. The Oracle Exalogic storage subsystem provides its own dedicated management interface and offers a number of user-selectable options for security, reliability and quota management. It also offers built-in support for storage replication, allowing each Oracle Exalogic configuration to be paired with another geographically remote system as part of a larger disaster recovery strategy. It is also possible to attach selected Oracle ZFS Storage Appliances directly to the Oracle Exalogic I/O backplane using InfiniBand in order to expand the system’s storage capacity or implement a highperformance backup solution.
11
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Figure 4. Oracle ZFS Storage Appliance—SAP Central Storage Repository
The Oracle ZFS Storage Appliance included in the Oracle Exalogic Elastic Cloud is ideally suited to act as a Central Storage Repository for SAP by providing shared file systems in a highly available and highperformance manner for the complete SAP landscape, consisting of application servers running on Oracle Exalogic and the SAP Central Services running on Oracle Exadata (see Figure 4). This configuration offers one of the highest potential service levels and throughput compared to more traditional implementations. In an SAP landscape, it is common that all SAP Application Servers have access to several shared filesystems (/sapmnt and /usr/sap/trans, for example) which are used to store the SAP kernels, profiles, trace files and to provide the global SAP transport directory where all patches for the SAP system itself and for customer-written applications (programs) are stored. The Oracle ZFS Storage Appliance supports the concepts of projects and shares for allocating and organizing storage to users, applications and other consumers. In the case of SAP storage for Oracle Exalogic, the following strategy is recommended:
One project trans with one share saptrans for the /usr/sap/trans directory.
One project oracle with one share for providing the /oracle directory and one share per Oracle client software release, mounted as /oracle/client/.
One project per SAPSID, with three shares per project: usrsap
12
for the /usr/sap/ directory,
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
sapmnt
for the /sapmnt/ directory,
oracle
for the /oracle// directory.
Furthermore, additional Oracle ZFS Storage Appliances connected to Oracle Exadata and Oracle Exalogic using the same backplane InfiniBand network can be used as a target for very fast backups from the Oracle Exadata Database Machine and replication target for Oracle Exalogic, providing a simple, reliable and powerful off-rack backup and replication option. Because of the broad variety of supported protocols available on the external Oracle ZFS Storage Appliance, (including HTTP, which allows access to the ZFS appliance through WebDAV), Oracle ZFS Storage Appliances can be used in combination with Oracle Exalogic to implement SAP's ILM concept using either the standard ArchiveLink ADK or the XML Direct Archiving Service.
Software Development Lifecycle Considerations Oracle Exalogic Control, the management interface for virtual deployments of Oracle Exalogic Elastic Cloud, includes a set of APIs for Infrastructure as a Server (IaaS) deployment scenarios. Utilizing this interface, along with Oracle Exalogic’s built-in Oracle ZFS Storage Appliance modules of snapshot and cloning, whole deployments can be cloned and recreated quickly and simply: 1. Create a new vDC Account for the environment. 2. Clone and replicate the required ZFS project and shares to a new project. 3. Utilize the Oracle Exalogic Control IaaS APIs to build a new set of VMs. 4. Attach the cloned shares to the new VMs. 5. Reconfigure the new environment as required.
High Availability for SAP NetWeaver on Oracle Exalogic and Oracle Exadata Inside Oracle Exalogic, all servers, networking components and connections as well as other infrastructure components such as power distribution units are fully redundant. Similarly, the Oracle Exadata Database Machine, where the Oracle Database for SAP and the SAP Central Services are running, is composed out of fully redundant components. A level of high availability for guest VMs (in virtual deployments of Oracle Exalogic) is enabled by default when the VM is created. If the VM or underlying compute node fails, the guest is automatically restarted on the same compute node if available, or migrated to a different compute node if the original node is down. Oracle Exalogic and Oracle Exadata are ideally suited for setting up a highly available infrastructure for SAP. Since both systems leverage industry standard x86 servers for running applications, standard practices like Oracle RAC, Oracle Clusterware or Data Guard can be used unchanged for making the Oracle Database, SAP services and application servers highly available. In addition, Oracle Maximum Availability Architecture (MAA), a comprehensive set of best practices blueprints for using proven
13
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Oracle HA technologies, provides guidance on avoiding downtime and enabling rapid recovery from planned and unplanned failures. These best practices are based on thorough validation from the Oracle engineering team and accumulated production experience from thousands of world-wide customers to help achieve optimal high availability at the lowest cost and complexity. The following SAP support notes are helpful in setting up HA for SAP on Oracle Exalogic and Oracle Exadata:
SAP Note 1552925 – Linux: High Availability Cluster Solutions
SAP Note 1496927 – Protection of SAP instances through Oracle Clusterware
Expanding Capacity, Multiple Oracle Exalogic and Oracle Exadata Machines In addition to extreme performance, lower risk, and simplified deployment and operations, Oracle Exalogic and Oracle Exadata offer a simple and comprehensive way of scaling the SAP NetWeaver infrastructure. Within a rack, both Oracle Exalogic and Oracle Exadata offer deployment units of a eighth, quarter, half or full rack (see Figure 5). By using the InfiniBand fabric, multiple racks can be joined together to quickly and easily grow the underlying infrastructure.
Figure 5: Seamless scalability from Eighth Rack through to 8+ racks on a single InfiniBand Fabric
For growing SAP NetWeaver 7.x environments, this capability offers a simple, quick, low-risk, and modular growth path. This avoids the typically long, complex, time- and resource-intensive, and errorprone process of selecting, qualifying, acquiring, testing, and quality assuring of multiple individual components. Instead, with the Oracle Exalogic Elastic Cloud and Oracle Exadata Database Machine, infrastructure for SAP environments of any size can now be installed and expanded in a matter of days, while substantially reducing TCA and TCO costs.
14
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
Conclusion The Oracle Exalogic Elastic Cloud offers a simple, reliable and high performance solution for providing infrastructure to SAP application servers, in combination with Oracle’s Exadata Database Machine. Installation of SAP on Oracle Exalogic is straightforward and leverages existing Oracle Linux best practices for running SAP on x86 systems, on both physical and virtual deployment scenarios. The additional benefits of using superior networking infrastructure of InfiniBand, and highly available and high-performance storage of the integrated Oracle ZFS Storage Appliance built into Oracle Exalogic, ensure the SAP landscape is both scalable and simple. High availability for SAP can be achieved through leveraging standard mechanisms such as Oracle RAC, Oracle Clusterware, Data Guard and built-in HA resilience of Oracle Exalogic guest VMs. Through growing Oracle Exalogic and Oracle Exadata from Eighth to Quarter to Half and Full Rack configurations and by adding more racks of Oracle Exalogic and Oracle Exadata, Oracle Engineered Systems provide a very flexible and scalable infrastructure solution for SAP, while maintaining simplicity and high levels of stability. With Oracle Exalogic and Oracle Exadata, deploying simple, reliable and high performance infrastructure for SAP can now be achieved quickly, cost-effectively and at low risk.
15
Running SAP NetWeaver on Oracle Exalogic Elastic Cloud: An Architectural Overview
References For more information about Oracle Exalogic, Oracle Exadata, and SAP products, see the following documents and web sites: White papers:
SAP NetWeaver and Oracle Exadata Database Machine: Technical Guide for installation, migration and configuration. http://www.oracle.com/us/products/database/sap-exadata-wp-409603.pdf
Oracle Exalogic Elastic Cloud: System Overview. http://www.oracle.com/us/products/middleware/exalogic/exalogic-system-overview-1724075.pdf
A Technical Overview of the Oracle Exadata Database Machine and Exadata Storage Server. http://www.oracle.com/technetwork/database/exadata/exadata-dbmachine-x4-twp-2076451.pdf
Web sites:
Oracle Engineered Systems for SAP: Oracle Exadata. http://www.oracle.com/us/solutions/sap/engineered-systems/exadata/index.html
Oracle Engineered Systems for SAP: Oracle Exalogic. http://www.oracle.com/us/solutions/sap/engineered-systems/exalogic/index.html
Oracle Exalogic Elastic Cloud. http://www.oracle.com/us/products/middleware/exalogic/overview/index.html
Oracle Exadata Database Machine. http://www.oracle.com/us/products/database/exadata/overview/index.html
16
Running SAP NetWeaver on Oracle Exalogic
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
Elastic Cloud April 2014
This document is provided for information purposes only, and the contents hereof are subject to change without notice. This
Authors: Gavin Parish, Thomas Schuele, Jan
document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in
Klokkers, Mark Mundy
law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
Contributing Authors: Kelly Goetsch, Nishit Rao, Michael Ahrens, Jan Brosowski, Ulrich Conrad, Michael Palmeter, Martin Sautter, Joachim Schuster, Constantin Gonzalez, Sachin Pikle
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Oracle Corporation World Headquarters
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
500 Oracle Parkway
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
Redwood Shores, CA 94065
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0114
U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com/solutions/SAP