Data powers essentially every operation in a modern enterprise, from keeping the supply chain operating efficiently to managing relationships with customers. Modern data centers face increasing demand for agile, high-performance service delivery. With digital transformation, organizations are deploying an increasing number of new applications, with more sources of data. Organizations of all kinds rely on their relational databases for both online transaction processing (OLTP) and online analytics processing (OLAP), but many still are challenged to meet their goals for high availability, security, and performance. Applications must be able to move quickly from development to a reliable, scalable platform. An optimal solution integrates best-in-class components that can scale computing and storage resources independently to meet the needs of dynamic business requirements.
Like all FlexPod systems, FlexPod Datacenter with NetApp All Flash FAS (AFF) consists of computing resources (database, application, and management servers from Cisco), network resources (three-layer network from Cisco), and storage resources (NetApp AFF storage systems).
In the FlexPod solution described in this document, Oracle Database servers and SAP application servers can co-exist and provide exceptional performance for the organization.
The intended audience for this document includes sales engineers, field consultants, database administrators, IT managers, Oracle Database architects, and customers who want to deploy SAP application servers with the Oracle Real Application Clusters (RAC) 12cR2 or 19c database solution on FlexPod converged infrastructure with NetApp Clustered Data ONTAP and the Cisco Unified Computing System™ (Cisco UCS®) platform. A working knowledge of SAP application servers, Oracle RAC databases, Linux, storage technology, and networking is assumed but is not a prerequisite for understanding this document.
The goal of this document is to show how SAP application servers can be installed with Oracle Database on the FlexPod Datacenter solution.
This document assumes that the FlexPod solution is already set up and that Oracle Database instances are configured and running. You can connect SAP NetWeaver Application Server to the existing database that is already available, or you can create a new database while installing the SAP application server.
This document uses SAP NetWeaver Application Server 7.5 for Advanced Business Application Programming (ABAP) as an example of an SAP application server.
This document does not describe the installation or configuration of the FlexPod Datacenter solution for Oracle RAC. For this information, refer to the Cisco® Validated Design for Oracle RAC deployment on the FlexPod solution at https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/UCS_CVDs/flexpod_orc12cr2_affaseries.html
Built on innovative technology from NetApp and Cisco, the FlexPod converged infrastructure platform meets the challenge of simplifying deployments for best-in-class data center infrastructure. FlexPod is a defined set of hardware and software that serves as an integrated foundation for both virtualized and nonvirtualized solutions. Composed of pre-validated storage, networking, and server technologies, FlexPod is designed to increase IT responsiveness to organization needs and reduce the cost of computing with more uptime and less risk. With simplified delivery of data center platforms, enterprises gain the advantage of faster delivery of new services and applications.
FlexPod provides the following differentiators:
● Flexible design with a broad range of reference architectures and validated designs
● Elimination of costly, disruptive downtime through Cisco UCS and NetApp ONTAP
● Use of a pre-validated platform to decrease business disruption, improve IT agility, and reduce deployment time from months to weeks
● Use of Cisco Validated Designs and NetApp Validated Architectures that cover a variety of use cases
Cisco and NetApp have carefully validated and verified the FlexPod solution architecture and its many use cases and have created a portfolio of detailed documentation, information, and references to assist customers in transforming their data centers to this shared infrastructure model.
Figure 1 provides an overview of a FlexPod system.
FlexPod system overview
FlexPod Datacenter architecture includes three components:
● Cisco UCS servers
● Cisco Nexus® switches
● NetApp AFF storage systems
One benefit of the FlexPod architecture is the capability to customize, or flex, the environment to meet a customer's requirements. A FlexPod solution can easily be scaled as requirements and demands change. The unit can be scaled both up (adding resources to a FlexPod unit) and out (adding more FlexPod units). This document focuses on the resiliency, cost benefits, and ease of deployment SAP application landscapes using FlexPod (Figure 2).
FlexPod solution design example
Today, to support the SAP on Oracle Database strategy, whenever Oracle releases a major new database feature, a development effort is employed to integrate it into the SAP architecture and to adapt the installation, administration, and monitoring tools provided by SAP. Whenever SAP releases a new application optimization, a similar development effort is employed to integrate it with the Oracle Database technology.
Oracle RAC databases often manage the mission-critical components of a customer’s IT department. Helping ensure availability while also lowering the total cost of ownership (TCO) for IT is always a top priority. This FlexPod solution for Oracle databases delivers industry-leading storage, exceptional scalability, continuous data access, and automated data management for immediate response to business opportunities.
An SAP application landscape has three tiers:
● Presentation layer
● Application layer or business logic layer
● Database layer
Scalability is critical for a successful implementation of an SAP solution. SAP provides scaling using two- and three-tier deployment architectures, depending on the scope of business growth:
● A two-tier architecture uses a single server for all SAP applications except those on the presentation layer. In this design, the presentation layer is installed as one tier, and the application and database layer is mapped to the second tier.
● In three-tier architecture, each of the three logical tiers maps to an individual set of one or more physical servers.
A two-tier architecture offers these advantages:
● Because the application and database layers are on the same host, this architecture provides excellent performance, because no additional overhead is needed for database connections and network traffic, and no shadow processes consume resources.
● The two-tier approach simplifies administration for small installations.
A three-tier architecture offers these advantages:
● The application tier can be scaled separately from the database tier to provide both load sharing and high availability in each tier. Temporary workloads can be easily managed by temporarily adding more application servers. Enterprise SAP application implementations typically use a three-tier or multiple-tier architecture to allow smoother deployment of high availability for an individual component or tier.
● Larger installations can benefit from the additional performance that can be achieved from this type of deployment.
The flexibility of the SAP software allows organizations to choose the best approach: whether to use a two-, three-, or multiple-tiered architecture.
An SAP application landscape is a group of two or more SAP systems. An SAP system has one or more SAP instances across one or more servers. A traditional SAP landscape consists of one or more of the following types of SAP instances:
● Production system (PRD)
● Development system (DEV)
● Test and quality assurance (QA) systems
The SAP NetWeaver platform is the base for many SAP solutions, including the popular SAP Business Suite. It enables the composition, provisioning, and management of SAP applications across a different software environment.
NetWeaver applications work on three layers. The application server (AS), the application server central services (ASCS) instance, and the database (DB) layer. The application server layer handles most of the processing workload, along with the application server central services system. The database layer stores the results. All three parts are required, and organizations should plan for high availability. Multiple instances of the application servers can be used to provide high availability and handle additional load. Similarly, organizations can protect the application server central services and database instances as needed. These instances can all share the same server or operating system instance, or they can be separated with each on its own server. They can run physically on the server, or they can run on virtual servers through the use of a hypervisor.
Cisco UCS servers can be placed in all the three layers of the SAP landscape to provide a complete Cisco UCS server infrastructure for the landscape. According to the workload calculated using the SAP Quick Sizer, the following Cisco UCS servers can be used:
● The enterprise-class Cisco UCS B480 M5 Blade Server delivers market-leading performance, versatility, and density without compromise for memory-intensive mission-critical enterprise applications and virtualized workloads, among others. The Cisco UCS B480 M5 is a full-width blade server supported by the Cisco UCS 5108 Blade Server Chassis.
● The Cisco UCS C480 M5 Rack Server brings the power and automation of unified computing to enterprise applications, including Cisco Single Connect technology, drastically reducing switching and cabling requirements. Cisco UCS Manager uses service profiles, templates, and policy-based management to enable rapid deployment and help ensure deployment consistency. It also enables end-to-end server visibility, management, and control in both virtualized and bare-metal environments. The Cisco UCS C480 M5 is a storage- and I/O-optimized enterprise-class rack server that delivers industry-leading performance for information management databases (IMDBs), big data analytics, virtualization workloads, and bare-metal applications.
● The Cisco UCS C240M5 and C220M5 Rack Servers are high-density 2-socket rack servers that deliver industry-leading performance and efficiency for a wide range of workloads, including virtualization, collaboration, and bare-metal applications. The Cisco UCS C-Series Rack Servers can be deployed as standalone servers or as part of Cisco UCS to take advantage of Cisco’s standards-based unified computing innovations that help reduce customer TCO and increase business agility. These servers incorporate Intel® Xeon® Scalable processors, supporting up to 20 percent more cores per socket, twice the memory capacity, and five times more Non-Volatile Memory Express (NVMe PCIe solid-state disks (SSDs) than the previous generation of servers. These enhancements deliver significant performance and efficiency gains that will improve your application performance.
Each of these servers allows a variety of configurations for memory, CPU, storage and I/O. Although you can use many of these variations to support SAP applications, a specific optimized subset is recommended for simplicity.
With the new NetApp AFF A-Series controller lineup, NetApp provides industry-leading performance together with a full suite of enterprise-class data-management and data-protection features.
This architecture uses the NetApp AFF A400 all-flash array as the foundation for infrastructure storage. The AFF A400 controller provides the high-performance benefits of 100 Gigabit Ethernet and NVMe all-flash SSDs by using the external NetApp NS224 storage shelf (Figure 3). The shelf is connected through the NVMe and RDMA over Converged Ethernet (RoCE) protocols and offers 24 bays for NVMe SSDs.
High-speed network connectivity is achieved with 100 Gigabit Ethernet and 32-Gbps Fibre Channel fabric connectivity. Multiple expansion slots per controller can support 10, 25, 40, and 100 Gigabit Ethernet connectivity as well as 8-, 16-, and 32-Gbps Fibre Channel networking.
The capability to scale out to 24 storage nodes makes the AFF A400 an excellent storage controller for shared workload needs in a converged infrastructure.
For more information about the NetApp AFF A400 and all the AFF A-Series controllers, see the NetApp AFF product page.
You can view or download more technical specifications for the AFF A-Series controllers from the NetApp data sheet at NetApp data sheet ds-3582.
NetApp AFF A400 and NS224 storage shelf
NetApp ONTAP data management
NetApp ONTAP data management software is used with the NetApp AFF all-flash storage system in this solution design. ONTAP software offers unified storage for applications that read and write data over block- or file-access protocol storage configurations.
ONTAP implementations can run on NetApp engineered FAS or AFF series arrays. They can also run on commodity hardware (NetApp ONTAP Select) and in private, public, or hybrid clouds (NetApp Cloud Volumes ONTAP and NetApp Cloud Volumes Service). Specialized implementations offer best-in-class converged infrastructure, used here as part of the FlexPod Datacenter solution, or with access to third-party storage arrays (NetApp FlexArray virtualization).
Together these implementations form the basic framework of a data fabric supported by NetApp with a common software-defined approach to data management and fast and efficient replication across systems. FlexPod and ONTAP can serve as the foundation for both hybrid-cloud and private-cloud designs.
The ONTAP industry-leading data management software is designed on the principles of software-defined storage.
Read more about all the capabilities of ONTAP data management software at the NetApp website.
Figure 4 shows an example of SAP application server connectivity in the FlexPod Datacenter solution.
SAP application server connectivity in the FlexPod Datacenter solution
This document uses SAP NetWeaver Application Server 7.5 for ABAP to illustrate the process for installing an SAP application server on the FlexPod Datacenter platform with Oracle Database using Cisco UCS servers and NetApp AFF storage.
The following SAP software components are required to installing NetWeaver Application Server 7.5 for ABAP:
● SAP Kernel: SAPEXEXX.SAR
● SAP Kernel for Oracle Database: SAPEXEDBXX.SAR
● SAP Host Agent: SAPHOSTAGENTXX.SAR
● Database Administration Tools for NetWeaver: DBATLXX.SAR
● SAP NetWeaver Application Server for ABAP installation export
● Internet Graphics Service (IGS): IGSEXEXX.SAR
● IGS Helper IGSHELPERXX.SAR
This document assumes that the FlexPod solution is already set up and that Oracle Database instances configured and running. You can connect the NetWeaver application server to the exiting database that is already available, or you can create a new database while installing the SAP application server.
The servers used to run SAP NetWeaver Application Server depend on your choice of Cisco UCS servers.
The SAP Product Availability Matrix (PAM) points to the relevant SAP NetWeaver installation guides. Be sure that you are familiar with the relevant SAP NetWeaver master and installation guides and the SAP Notes referenced in them. To find planning, installation, patching, and operation documentation for your task, see the SAP NetWeaver Guide Finder.
For a new installation of an SAP system, including an enhancement package, you use the standard installation tool: Software Provisioning Manager 1.0. Software Provisioning Manager performs software provisioning processes such as installation, uninstallation, system copy, and system transformation. Software Provisioning Manager is the successor to product- and release-specific provisioning tools, such as SAPinst.
The SAP application server installation can be a standard system, which runs all three components of the application server on the same server and hardware; a distributed system, in which the three components reside on different servers and hardware; or a high-availability system, which is used for failover.
Figure 5 shows an example of an SAP NetWeaver Application Server 7.5 for ABAP distributed system running on Flexpod
SAP NetWeaver Application Server 7.5 for ABAP distributed system
As a best practice, you should start the SAP installation manually using the SAP GUI. To start the installer, following these steps:
1. Log on to the server on which SAP NetWeaver Application Server for ABAP is to be installed.
2. Open a terminal as the root user.
3. Copy the installable files to a local directory on the server.
4. Run the SAP GUI installer: for example, /software/<SWPM Directory>/sapinst.
Post-installation configuration of the system
After installing SAP NetWeaver Application Server, you have many choices to make about how to configure your system. These choices depend on your use case. Use SAP Best Practices to make these decisions, or make your own configuration decisions based on your needs. SAP Best Practices and SAP Rapid Deployment Solutions describe best business practices and best implementation practices for a wide range of SAP software. They are published as packages with assets covering solution design and configuration, and if applicable, they include configuration templates that you can use in your system.
You need to use the SAP client GUI to connect to the newly installed SAP system. Use the SAP system ID (SID), instance number, and master password to check that the SAP S/4HANA system was installed according to the parameters you supplied.
To verify the SAP installation, log on to the SAP GUI on the user interface and enter the required parameters (Figure 6).
Log on to the SAP GUI
The screen in Figure 7 shows the successful installation of the NetWeaver Application Server 7.5 for ABAP on a FlexPod Datacenter solution with Oracle Database.
Successful installation of SAP NetWeaver Application Server
SAP application monitoring with Cisco AppDynamics platform
The Cisco AppDynamics® application performance monitoring (APM) platform helps you understand and optimize the performance of your business applications, from your software to your infrastructure to your business processes.
The AppDynamics APM platform enables you to monitor and manage your entire application-delivery ecosystem, from a mobile app or browser client request through your network, back-end databases, application servers, and more. The AppDynamics APM gives you a single view across your application landscape, letting you quickly navigate from a global perspective of your distributed application down to the call graphs and exception reports generated on individual hosts.
The AppDynamics platform has an agent-based architecture. After the agents are installed, you see a dynamic flow map or topography of your application. The platform uses the concept of traffic lights to indicate the health of your application (green is good, yellow is slow, and red indicates potential problems), with dynamic baselining. The AppDynamics platform measures application performance based on business transactions, which essentially are the main processes of the application. When the application deviates from the baseline, the AppDynamics platform captures and provides deeper diagnostic information to help you be more proactive in troubleshooting and reduce your mean time to repair MTTR).
This SAP application server infrastructure can be monitored with the AppDynamics platform.
The core SAP monitoring components are:
● SAP ABAP Agent: Responsible for business transaction monitoring (communication between SAP and external systems, like the AppDynamics Controller).
● Datavard Insights: Responsible for collecting SAP-specific metrics, logs, and events.
SAP ABAP Agent Architecture
The ABAP Agent uses the AppDynamics C++ SDK wrapped by the AppDynamics HTTP SDK to report business transaction performance metrics and snapshots. The following diagram describes the communication between ABAP Agent and AppDynamics Controller:
Figure 8 presents an AppDynamics map showing the performance of SAP NetWeaver Application Server 7.5 for ABAP that is currently running in the organization.
AppDynamics map showing the performance of SAP NetWeaver Application Server 7.5 for ABAP
Cisco Intersight systems management
The Cisco Intersight™ solution is Cisco’s new systems management platform that delivers intuitive computing through cloud-powered intelligence. This platform offers more intelligent management and enables IT organizations to analyze, simplify, and automate their IT environments in ways that were not possible with prior generations of tools. This capability empowers organizations to achieve significant TCO savings and deliver applications faster to support new business initiatives.
The Cisco UCS platform uses model-based management to provision servers and fabrics automatically, regardless of form factor. The Cisco Intersight platform works in conjunction with Cisco UCS Manager and the Cisco Integrated Management Controller (IMC). By simply associating a model-based configuration with a resource through service profiles, your IT staff can consistently align policy, server personality, and workloads. These policies can be created once and then used by IT staff with little effort to deploy servers. The result is improved productivity and compliance and lower risk of failures due to inconsistent configuration.
The Cisco Intersight platform can be integrated with data center and hybrid cloud platforms and services to securely deploy and manage infrastructure resources across data center and edge environments. In addition, Cisco will provide future integrations with third-party operations tools to allow customers to use their existing solutions more effectively.
The Cisco Intersight platform monitors all Cisco UCS servers and switches in the solution and offers cloud-based, centralized management of Cisco UCS servers across all enterprise locations. The unique capabilities is delivers include the following:
● Integration with Cisco Technical Assistance Center (TAC) for support and case management
● Proactive, actionable intelligence for issues and support based on telemetry data
● Compliance checks through integration with Cisco Hardware Compatibility List (HCL)
● Centralized service profiles for policy-based configuration
For more information about the Cisco Intersight p0latform and the various editions, see Cisco Intersight: SaaS Systems Management Platform.
NetApp SnapCenter is a centrally managed, web-based application that runs on Microsoft Windows and manages and protects multiple servers remotely.
Figure 9 shows the high-level architecture of a NetApp SnapCenter Server deployment.
NetApp SnapCenter architecture
The SnapCenter Server has an HTML5-based GUI and Microsoft Windows PowerShell cmdlets and APIs. The SnapCenter Server is capable of high availability without additional configuration. If one SnapCenter host becomes unavailable for any reason, the second SnapCenter Server can take over seamlessly, and no operations are affected.
The SnapCenter Server can push out plug-ins to remote hosts. These plug-ins are used to interact with applications, databases, and file systems. Usually, the plug-ins must be present on the remote host so that application-level or database-level commands can be issued from the same host on which the application or database is running.
SnapCenter uses SM Service to manage plug-ins and interactions between the SnapCenter Server and the plug-in host. SM Service is a NetApp SnapManager web service running on top of Microsoft Windows Server Internet Information Services (IIS) on SnapCenter Server. SM Service handles all client requests, including backup, restore, and clone requests.
The SnapCenter Server communicates those requests to SMCore, a service that runs within the SnapCenter Server and remote servers. SMCore plays a significant role in coordinating with the SnapCenter plug-ins package for Microsoft Windows.
SnapCenter Virtualization (SCV) is a plug-in that manages virtual servers running on VMware and helps discover the host file system, databases on virtual machine disks (VMDKs), and raw device mapping (RDM).
SnapCenter enables you to create application-consistent snapshot copies and to complete data-protection operations, including snapshot copy-based backup, clone, restore, and backup-verification operations. SnapCenter provides a centralized management environment, and it uses role-based access control (RBAC) to delegate data-protection and management functions to individual application users across the SnapCenter Server and Microsoft Windows hosts.
SnapCenter offers the following main features:
● A unified and scalable platform across applications and database environments, with virtual and nonvirtual storage powered by the SnapCenter Server
● Consistency of features and procedures across plug-ins and environments supported by the SnapCenter user interface
● RBAC for security and centralized role delegation
● Application-consistent snapshot copy management, restore, clone, and backup verification support from both primary and secondary destinations (using NetApp SnapMirror and NetApp SnapVault technology)
● Remote package installation from the SnapCenter GUI
● Nondisruptive, remote upgrades
● A dedicated SnapCenter repository for faster data retrieval
● Load balancing that is implemented by using Microsoft Windows network load balancing (NLB) and application request routing (ARR), with support for horizontal scaling
● Centralized scheduling and policy management to support backup and clone operations
● Centralized reporting, monitoring, and dashboard views
● SnapCenter 4.3 support for data protection for VMware virtual machines, Microsoft SQL Server databases, Oracle databases, MySQL, SAP HANA, MongoDB, and Microsoft Exchange
SAP data protection with NetApp SnapCenter
The FlexPod solution can be extended with additional software and hardware components to handle data-protection, backup and recovery, and disaster-recovery operations. You can enhance SAP backup and disaster recovery using the NetApp SnapCenter plug-in for SAP on Oracle.
Storage-based snapshot backups provide a fully supported and integrated backup method available for Oracle databases.
Storage-based snapshot backups are implemented with the NetApp SnapCenter plug-in for Oracle, which creates consistent snapshot backups by using the interfaces provided by the Oracle database.
Snapshot copies created within primary storage can be replicated to the secondary backup storage by using NetApp SnapMirror technology controlled by SnapCenter. Different backup retention policies can be defined for backups held on the primary storage and for backups held on the secondary storage. The SnapCenter plug-in for Oracle manages the retention of snapshot-based data backups and log backups. The SnapCenter plug-in for SAP HANA also allows a block integrity check of the SAP HANA database by running a file-based backup.
Storage-based snapshot backups provide significant advantages over file-based backups. Advantages include the following:
· Rapid backup (less than a minute)
· Faster restoration on the storage layer (less than a minute)
· No performance impact on the Oracle database host, network, or storage during backup
· Space-efficient and bandwidth-efficient replication to secondary storage based on block changes
SAP disaster recovery with asynchronous storage replication
Oracle disaster recovery can be performed either on the database layer or on the storage layer by using storage replication technologies. This section provides an overview of disaster-recovery solutions based on asynchronous storage replication.
The same SnapCenter plug-in that is described in the section above is also used for the asynchronous mirroring solution. A consistent snapshot image of the database at the primary site is asynchronously replicated to the disaster-recovery site with SnapMirror.
For an offsite backup and disaster-recovery solution, the following additional hardware and software components are required:
● A Microsoft Windows host to run SnapCenter Server software
● Offsite backup storage to replicate backups from primary storage to a secondary storage system
● Disaster-recovery storage to replicate backups from primary storage to a disaster-recovery site
The SnapCenter Server must be able to communicate with the storage virtual machines (SVMs) that are used at the primary location (within the FlexPod instance), the offsite backup location, and the disaster-recovery storage.
The primary storage must have a network connection to the offsite storage and to the disaster-recovery storage. Storage-cluster peering must be established between the primary storage, the offsite storage, and the disaster-recovery storage.
The SnapCenter Server must have a network connection to the SAP Oracle Database hosts to deploy the Oracle plug-in and to communicate with the plug-in after deployment.
SAP Landscape Management (LaMa) enables SAP system administrators to automate SAP system operations, including end-to-end SAP system copy and refresh operations. SAP LaMa is one of the few SAP software products with which infrastructure providers such as NetApp and Cisco can integrate their products. With such integration, customers can employ NetApp functions directly from the SAP LaMa GUI.
NetApp offers NetApp Storage Services Connector (SSC), which allows SAP LaMa to directly access technologies and features such as NetApp FlexClone instant cloning and NetApp SnapMirror data replication. These technologies help reduce storage use and shorten the time required to create SAP system clones and copies.
With the help of the built-in functions and a robust set of extensibility features within SAP LaMa, FlexPod customers can directly integrate storage-based backups or instantaneously create space-efficient FlexClone system copies in the primary data center. They can even use storage at either the offsite backup site or the disaster-recovery site.
Figure 10 shows how SAP LaMa and NetApp SSC can be integrated into the overall FlexPod architecture.
● From an administrator's perspective, SAP LaMa is the central tool for operating and monitoring SAP systems, computing instances, and required storage resources. Figure 10 illustrates the required network communications between the various components:
● SAP LaMa must be able to communicate with the SAP Host Agent instance running on the physical or virtual host. Although SAP Host Agent is automatically installed during an SAP system installation, it can be manually configured to include hosts in SAP LaMa management that do not run SAP software, such as web servers.
● To communicate with NetApp storage systems, SAP LaMa must be able to communicate with NetApp SSC. For more information about NetApp SSC, see the NetApp SSC for SAP LaMa website.
For a detailed description of SAP LaMa and NetApp SSC, see the technical report Integrating NetApp ONTAP Systems with SAP Landscape Management.
Note that SAP LaMa does not include regular backup and recovery or disaster-recovery functions. These functions are provided by NetApp SnapCenter.
Cisco and NetApp have partnered to deliver the FlexPod solution, which uses best-in-class storage, server, and network components to serve as the foundation for a variety of workloads, enabling efficient architectural designs that can be quickly and confidently deployed. FlexPod Datacenter is predesigned to provide agility to the large enterprise data centers with high availability and storage scalability. With a FlexPod-based solution, customers can leverage a secure, integrated, and optimized stack that includes compute, network, and storage resources that are sized, configured, and deployed as a fully tested unit running industry standard applications such as Oracle Database 12c RAC, 19c RAC or standalone deployments.
The following factors make the combination of Cisco UCS with NetApp storage so powerful for SAP application environments with Oracle as database backend:
● Cisco UCS stateless computing architecture provided by the Service Profile capability of Cisco UCS allows for fast, non-disruptive workload changes to be executed simply and seamlessly across the integrated UCS infrastructure and Cisco x86 servers.
● Cisco UCS, combined with NetApp’s highly-scalable FAS storage system with NetApp’s Clustered Data ONTAP®, provides the ideal combination for Oracle's unique, scalable, and highly available FAS technology.
● Hardware level redundancy for all major components using Cisco UCS and NetApp availability features.
FlexPod is a flexible infrastructure platform composed of pre-sized storage, networking, and server components. It's designed to ease your IT transformation and operational challenges with maximum efficiency and minimal risk.
FlexPod differs from other solutions by providing:
● Integrated, validated technologies from industry leaders and top-tier software partners.
● A single platform built from unified compute, fabric, and storage technologies, allowing you to scale to large-scale data centers without architectural changes.
● Centralized, simplified management of infrastructure resources, including end-to-end automation.
● A flexible Cooperative Support Model that resolves issues rapidly and spans across new and legacy products.
SAP related Documentation
Important SAP Notes
● 1680045 Release Note for Software Provisioning Manager 1.0
● 2172935 Installation - SAP Systems based on SAP NetWeaver on Oracle
● 2660020 Central Technical Note for Oracle Database 18c
● 2470660 Central Technical Note for Oracle Database 12c Release 2 (12.2)
● 789220 Support Package levels for SAP NetWeaver installations/upgrades
● 2369910 SAP Software on Linux: General information
Cisco Product information