

There are a number of performance challenges when deploying SAP Fiori for end-users over the Internet. With this capability, many SAP customers are deploying SAP Fiori to be internet facing with the flexibility to support any connectivity for the end-users globally, including connection types such as over 3G, 4G, 5G, or Wi-Fi. Due to the nature of HTML5, it runs in nearly any user devices that supports modern browsers such as mobile phones, tablets and laptops.

SAP Fiori relies on the HTTP protocol and modern web browsers as the client. It is based on SAP’s own HTML5 implementation called SAPUI5, and OData API Calls for its dynamic content. SAP Fiori is the User Interface component of SAP applications such as S/4HANA, BW/4HANA, etc. I will discuss options to address performance challenges for globally accessible SAP Fiori workloads on AWS, and highlight the potential improvements that can be achieved. In this blog, I will consider a scenario where a customer is running their SAP workloads on AWS and is interested in providing direct access to SAP applications without significant investments in dedicated network connectivity. However, access from anywhere is where the complexity lies, and customers need to consider organizational security policies, performance requirements, existing network connectivity (including its bandwidth and latency characteristics) from branch locations, users mobility, and other considerations. Access from any device is a key feature of SAP Fiori, with SAPUI5 capabilities. Access at any time is easy to achieve, by making the services to be accessed, available around the clock. SAP customers with global operations are generally interested in enabling their entire workforce access SAP applications at any time, from any device, and from anywhere.
