SAP Certified Offerings on Azure

By Ashwin Venugopal -

 



General Prerequisites (SAP support in public cloud environments)

As we all know, SAP provides scalable, compliant, and enterprise-proven platform for a range of SAP workloads which is based on the criteria stipulated by SAP. The general prerequisites for SAP supports in public cloud environments includes the following:
  • Licensing for SAP software to be deployed.

  • SAP system sizing and knowledge of resource requirements of SAP workloads to be deployed.

  • Certified VM instance sizes and total capacity required by SAP software on the cloud provider platform.

  • Sufficient network connectivity (in regard to bandwidth, latency, and package loss) to the cloud environment that will host SAP workloads.

  • Certified operating systems on which the SAP workloads will be deployed.

  • Support agreement available from the cloud provider.

  • Experience with technical operation of SAP systems and the infrastructure of the cloud provider pertinent to the shared responsibilities model.  

Deployment options of SAP solutions on Azure

Generally, customers have three options when deploying SAP products in Azure:
  • Azure VMs- There is a growing number of Azure VM SKUs certified for hosting SAP HANA including GS5 and a number of M family VM sizes. There is also much larger selection of Azure VM SKUs that supports non-HANA  workloads (NetWeaver and non-NetWeaver products).

  • SAP HANA on Azure (Large Instances)- There are several SKUs ranging from 2 TiB per node to 20 TiB per node. 

  • SAP Cloud Appliance Library (CAL)- SAP CAL offers you to deploy pre-configured software appliances on the different public clouds, including Azure. The primary benefit of SAP CAL is that, it offers an easy way to deploy and test pre-configured SAP solutions provided by SAP without having to provision underlying infrastructure. SAP CAL on Azure includes support for SAP S4/HANA or BW/4HANA.

Note- SAP performance can be measured by relying on the SAP Application Performance Standard metric or, in short, SAPS which is a hardware-independent unit of measurement that describes the performance of  a system configuration in the SAP environment. IT is derived from the Sales and Distribution benchmark, where 100 SAPS is defined as 2000 fully business processed order line items per hour. Alternately, performance rating can also determined by considering that one SAPS is equal to 24 Sales and Distribution transactions per hour. Generally, SAPs are used to size CPU and memory of a SAP system. 









Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more