Abstract
“The electricity has to be of good quality”—in the early days of electrification when customers didn’t have experience with this new technology the city council of a German village wrote this sentence in the contract with a utility company. This is quite similar to the definitions in many service level agreements for SAP solutions on public and private clouds.
This chapter discusses the definition of appropriate service levels for SAP systems in cloud environments. It focuses on the question how to predict the necessary resources to fulfill the SLA and how to measure and bill their actual consumption. Topics such as service guarantees for SAP systems and availability as well as billing tools are described in detail.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The way utilize excess compute power during times of low demand is to “store the request” instead of the power. This is nothing but batch processing.
- 2.
Developed by the British government, now under support of the IT Service Management Forum (http://www.itsmf.com).
- 3.
Missbach, Stelzel, SAP System Operations, SAP PRESS 2004. ISBN 1-59229-025-8.
- 4.
CCMS transaction DINOGUI display the execution time of the dialog step on the servers. The time displayed as DIALOG also includes the runtimes on the network up to the SAP GUI.
- 5.
See Queuing Networks and Markov Chains. Modeling and Performance Evaluation with Computer Science Applications (Wiley 1998).
- 6.
service.sap.com/quicksizing, SAP S-user credentials are necessary to access the tool.
- 7.
It is always astonishing that customers do not remember the SAPS ratings of the servers they bought a few years ago taking into account all the battles between the different vendors about this topic. Maybe it’s a good idea to write the SAPS rating to the housing of a server directly after installation. At least you should file it in the inventory.
- 8.
Actually the numbers are calculated from the numbers of dialog steps measured and are therefore a kind of hypothetical equivalent to a standard user. Depending on the number of dialog steps per week the users (identified by their user name) are sorted into categories according to:
-
low<400 dialog steps per week
-
medium<between 400 and 4800 dialog steps per week
-
high>4800 dialog steps per week
The number of “Active Users” in table “Performance Indicators” is only the sum of the high and medium users. “Low Users” are neglected. If the number of Low Users is very high compared to Medium and High Users, 10 Low Users will be counted as 1 Medium User.
-
- 9.
Christian Bornholdt (2006) automated report generating tool for hardware resources in SAP server landscapes. Andreas Nisch (2007) Web Service zur Abrechnung der Ressourcenverbräuche von SAP-Systemen. Markus Bukowski (2008) Tool zur automatischen Messung des Ressourcen-verbrauchs von SAP.
- 10.
Analyse des Ressourcenverbrauchs in virtualisierten Systemen am Beispiel der E/A-Last betriebswirtschaftlicher Standardanwendungen. Robert Wierschke, Masterarbeit Hasso am Plattner Institut Potsdam, 2009.
- 11.
Analyse des aktuellen Ressourcenverbrauchs in konsolidierten Umgebungen am Beispiel betriebswirtschaftlicher Standardsoftwaresysteme. Daniel Richter, Masterarbeit am Hasso Plattner Institut Potsdam, 2009.
- 12.
Michael Mißbach, Uwe Hoffmann, Prentice Hall 2001, ISBN 0-13-028084-4.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2016 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Missbach, M. et al. (2016). Service Levels for SAP on Cloud. In: SAP on the Cloud. Management for Professionals. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-662-47418-1_3
Download citation
DOI: https://doi.org/10.1007/978-3-662-47418-1_3
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-662-47417-4
Online ISBN: 978-3-662-47418-1
eBook Packages: Business and ManagementBusiness and Management (R0)