Tuesday, 08 June 2021 20:29

SAP HANA XS Advanced Technical Architecture

Written by Mahesh Dusanapudi
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/06/09/sap-hana-xs-advanced-technical-architecture/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

Many SAP Customers started using XS Advanced and there were several questions on how to deploy or where to deploy and what are the consideration for choosing any of those approached . Based on my experience with various customers I tried to address some key topics in this blog to consolidate information from various sources of documentations

Key Topics 

  1. Deployment Options
  2. Sizing
  3. Backup Restore
  4. High Availability with XSA
  5. Monitoring

1. Deployment Options

There are various ways of deploying the XS Advanced runtime. Before deploying the XSA many scenarios need to considered that will have impact on your landscape maintenance activity .For example the system refresh scenarios where you will need to refresh only a certain tenants instead of complete system this deployment plays a key role . I will go through the limitations in detail in backup restore section. In general, The following additional services run where XSA is deployed:

  • xscontroller: Central management component of XSA. It has a view on all deployed and/or running applications, and persists configuration and status information in the database
  • xsexecagent: Responsible for managing processes, i.e. starting, keeping alive, and stopping tasks
  • xsuaaserver: Manages user logon and logoff requests in SAP HANA XSA
  • diserver: HDI handles the deployment of design-time artefacts into SAP HANA

The following new HANA host roles are introduced for XSA:

  • XS_WORKER: Host for SAP HANA XSA runtime
  • XS_STANDBY: Optional idle standby host for SAP HANA XSA runtime in a high-availability environment 

Option 1: Scale-Up HANA, Shared Host

Option 2: Scale-Out HANA, Shared Host


Option 3: Dedicated XSA Host




Key Points

  • Sizing is one of the key factors of finalizing the deployment approach in case of intensive Application Development on XSA a dedicated host deployment (option3) is preferred.
  • If you only run a XS_WORKER on the host, then the host does not require HANA certified hardware or meet the standards of HANA Worker nodes
  • XS worker host roles can be assigned to different hosts along with XS standby
  • In Option3 configuration HANA is still considered scale-up as neither data nor database-internal workload are distributed
  • XS Advanced can be installed on SYSTEMDB or TENANTDB. This plays a key role as well due to the restriction in backup restore come in to picture based on where XSA is installed

2 . Sizing 

  • When estimating the resource consumption for running XS Advanced there are two key sizing considerations
    • It is a prerequisite for productive sizing to define how the platform will be used, what and how many applications will be developed
    • If unknown, it’s recommended to first set-up a development environment to allow DEV teams define this
  • XSA Platform Sizing
    • Basic requirement for XSA services (xsuaaserver, xscontroller etc…), system applications and application runtimes
    • Determines the maximum number of concurrent application accesses the XSA installation will serve and determines the basic resource consumption
    • XSA Application Sizing
    • Resource requirement to handle user workload and related behavior of deployed applications
    • Influenced by the scalability of deployed custom code and related user workload generated on both XSA and HANA
    • Load testing of developed applications recommended to identify requirement, expert sizing recommended to support in cases of intensive application development
    • More details and platform sizing based on profiles can be found in this help documentationhttps://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.04/en-US/7a49aa852c0c4ed089a58a840f07cc4e.html
  • Resource utilization for XSA is distributed dependent on the chosen deployment option and layout of services:
    • Central (xsuaaserver, xscontroller.
Continue reading here
Read 67 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.