Skip to main content

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome to the latest installment of our ongoing blog series, where we embark on a journey to demystify the intricate relationship between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). The intention behind this series is to provide a comprehensive resource for individuals exploring SAP BTP, whether you're pivoting from a different platform or delving into it for the first time. We aim to equip you with  notes, ensuring you're well-prepared to navigate the powerful collaboration between SAP BTP and AWS.

OpenSAP Course Link : https://open.sap.com/courses/aws1

To start with it is ideal that you have the basic idea of SAP BTP for that I found this blog really interesting . As we go down this blog will be more of the introduction to :-

"Rise with SAP" Initiative on AWS

Graviton 3 Processor Advancements

AWS Infrastructure and Redundancy

Testimonials: Successful Digital Transformations

GDPR Compliance and Data Protection



Since 2008, Amazon Web Services (AWS) has been a supporter of SAP, fostering a collaborative partnership that has borne fruit in projects like Concur and SAP Analytics Cloud. However, as technology evolves, so do the demands of businesses. Enter "Rise with SAP," an ambitious go-to-market initiative designed to facilitate the seamless migration of workloads to the public cloud. This initiative offers a guided transformation journey, yet it acknowledges the complexities that arise from legacy systems and extensive customizations, which can present formidable challenges for organizations.

The crux of the matter lies in recognizing that there isn't a one-size-fits-all solution for every customer. This is where "Rise with SAP" on AWS steps in, offering a multifaceted approach. It involves a thorough reimagining of business processes and a strategic shift towards the AWS public cloud. The real potency of this transition is unveiled when we tap into the potential of the SAP Business Technology Platform (BTP). This platform stands as a linchpin, facilitating the adaptation of a clean core model, which is essential for modernizing and optimizing operations.

The Graviton 3 processor offers several significant advantages over its predecessor, the Graviton 2. It boasts up to three times better machine learning performance, demonstrating a substantial leap in computational capabilities. Additionally, the Graviton 3 processor provides up to two times higher floating-point performance, indicating its enhanced processing power for complex numerical computations. Moreover, it demonstrates up to two times faster cryptographic workload performance, showcasing its proficiency in handling secure data processing tasks.

In addition to this technical innovation, AWS has fortified its offering with a robust architecture. Availability Regions and Availability Zones provide redundancy and fault tolerance, ensuring a robust infrastructure for critical business operations. This dual-layered approach enhances the resilience of applications and services, guarding against disruptions and minimizing downtime.

With these foundational elements in place, the AWS-SAP partnership stands poised to address the diverse and intricate needs of businesses seeking to leverage the full potential of modern cloud computing. The tapestry of technological innovation, strategic vision, and real-world application is woven into the fabric of every project, promising a transformative journey for businesses venturing into the cloud-driven future.

AWS Availability Zones (AZs) exhibit robust characteristics that ensure high availability and reliability. These zones are interlinked with high-bandwidth, low-latency networking, facilitating seamless communication between resources hosted in different AZs. Each AZ encompasses one or more discrete data centers equipped with redundant power, networking, and connectivity infrastructure. This redundancy ensures uninterrupted operations even in the event of hardware or network failures

Series of compelling testimonials from companies that have successfully embarked on their digital transformation journey with "Rise with SAP" in collaboration with AWS. One notable example is the Manchester Airports Group (MAG), a conglomerate overseeing multiple airports in the UK. MAG, which served over 60 million passengers in 2019, has recently gone live with "Rise with SAP." This marks the initial step in a five-year transformation plan with SAP, a testament to the long-term commitment and vision inherent in this partnership and and other testimonials were mentioned 

RISE with SAP offers a suite of capabilities designed to facilitate a comprehensive transformation journey. It encompasses technical migration services, streamlining the process of transitioning existing systems and applications to the cloud. Additionally, it provides expertise in business process redesign, enabling organizations to optimize their workflows for enhanced efficiency. Furthermore, RISE with SAP lays a solid foundation for businesses, setting the stage for a successful and sustainable digital transformation.

When it comes to data protection, one cannot overlook the paramount importance of GDPR compliance. GDPR mandates that personal data must be processed securely, employing appropriate technical and organizational measures. AWS has devised a shared responsibility model to delineate accountability. In this model, AWS assumes responsibility for cloud security, while SAP inherits security responsibilities within the context of "Rise with SAP." As tenants of AWS and "Rise with SAP," customers bear the onus of ensuring security in the cloud.

This collaborative effort between AWS and SAP extends to engineering endeavors, resulting in the creation of the SAP BTP EU Access region. This region boasts 100% GDPR compliance, providing a secure haven for applications and services. Any application built and deployed within this region is guaranteed to remain within the boundaries of the European Economic Area or Switzerland, affording an added layer of data sovereignty and security.

Yet, the complexity of multi-cloud environments introduces an additional dimension to consider: application performance. Picture a scenario in a bustling retail store where a customer attempts to make a purchase. However, delays in transaction validation at the point of sale (POS) system lead to frustration and eventual abandonment of the purchase. This illustrates the critical role that network latency plays in application performance. The challenge lies in ensuring that applications remain performant even when traversing multiple clouds.

Enter AWS with a solution: running "Rise with SAP" workloads such as S/4HANA, ECC, CRM, and more on their platform, in conjunction with utilizing BTP services. AWS's network infrastructure operates at a fundamental hardware level, with network routers discerning the source and target of requests. If both endpoints are hosted on AWS's public IPs, traffic is efficiently routed through the AWS backbone network. This principle holds true whether the IPs belong to the customer or a SaaS service. The implications of this streamlined routing are far-reaching, impacting any customer leveraging SaaS services alongside enterprise workloads on AWS.

This architectural advantage not only enhances application performance but also carries ancillary benefits. It translates into cost savings and a reduced security footprint, reinforcing the value proposition of adopting AWS as the cloud infrastructure of choice. These technical intricacies exemplify how the AWS-SAP collaboration isn't just about integration, but about fine-tuning the underlying architecture to optimize performance and security, ultimately driving tangible business value for customers on their digital transformation journey.

It unveils a symphony of successful endeavors, where businesses from diverse industries have harnessed the combined might of AWS and SAP to navigate their digital transformation journeys.

These stories paint a vivid picture of the transformative power of "Rise with SAP" on AWS. Manchester Airports Group (MAG), with its vast passenger volumes and workforce, Revlon with its exponential e-commerce growth, American Air Filter in its critical role during the pandemic, and Ballance's strategic move to leverage SAP platforms - all underscore the adaptability and scalability of this collaborative venture.

Furthermore, the testimonials from Zalando and Frucor Suntory on the SAP Business Technology Platform (BTP) side exemplify the depth of innovation and value that can be unlocked through this partnership. Beyond cost reduction, the integration and extension of services and data analytics capabilities catalyze meaningful business transformation.

GDPR compliance. AWS's shared responsibility model, coupled with the engineering effort invested in creating the GDPR-compliant SAP BTP EU Access region, showcases the commitment to safeguarding sensitive data.

The discussion on application performance, particularly in multi-cloud environments, illuminates the strategic advantage offered by AWS's network infrastructure. The seamless routing of traffic through the AWS backbone network not only optimizes performance but also brings about cost efficiencies and heightened security.

Disclaimer: The notes provided here are intended solely for educational purposes. For comprehensive and accurate information, please consult the official SAP Guide documentation and contact SAP directly for further clarification or in case of any discrepancies. This content is not a substitute for professional advice or official documentation.

Comments

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c