SAP ON AZURE OR AWS
Installing, maintaining and servicing other software that is not an SAP system but also provides important functions such as SAP Router, SAP Cloud Connector, TREX, SAP ETD and many more
Tasks such as the update of components, the insertion of security updates or monitoring should be further automated. It is recommended to use only one automation tool (SAP Solution Manager or SAP LVM). Custom solutions and scripts should not be used or replaced with standard tools if possible, because otherwise different script languages and script versions will have to be managed, resulting in a lot of maintenance. Standardised SAP scripts are welcome here. A useful definition of thresholds, for example on the basis of historical system behaviour, must also be defined for monitoring.
Instead of letting the power consumer determine each parameter individually, the SAP basis can now create meaningful bundles, such as the power server with a lot of processor power, memory and disk space, and the light server in a simpler setup. Each bundle has its own price, which requires preparation and consideration. The principle of consistently aligning IT services with repeatable standards is thus directly linked to the standardisation of processes and technical specifications. Standardised products can only be offered if process processes are standardised. Likewise, these can only be offered as simple and comprehensible product bundles if technical standards are established.
Regular maintenance tasks or the standard procedures must be described and defined to build checklists based on them and to control compliance with this standard. The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures. In this context, it is also necessary to document the functionality of an underlying application and thereby determine what testing and monitoring activities are necessary. This is a reconciliation process between the SAP basis, other IT departments and, if necessary, the business areas concerned. The defined standard and the system's IST situation must be fully documented and regularly checked for compliance. This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists. Only the regular review of the standards guarantees their compliance. It can also support the regular use of SAP services such as Go-live Checks or Early Watch. Examples of how to standardise procedures are listed here: ・ Naming of system instances and logical hosts, or at least one central registry in a directory service, or LVM or SAP customer portal ・ Centrally starting and stopping systems, such as via the LVM ・ Categorising SAP instances by T-shirt size to define profile standards and cost them.
SAP Basis Operation is responsible for ensuring the technical functionality of an SAP system. It includes all the technical components mentioned above. These are used to perform the following tasks.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Above all, the lack of access to his social system makes him.
SKILLS & ROLLS In the future, SMEs will support thematic outtasking, especially for rarely performed tasks such as upgrades, and will ensure documentation (e.g. interfaces and customer developments) so that intervention can take place in an emergency.