SAP Basis Define Tasks and Systems - SAP Basis

Direkt zum Seiteninhalt
Define Tasks and Systems
Versioning
This is the heart of the SAP system. In the classic three-tier model, this would be the logic or control layer. One or more application servers host the necessary services for the various applications at this layer. These application servers provide all the services required by the SAP applications. In theory, a single server could fill this role. In practice, these services are in most cases distributed among several servers, each serving different applications.

SAP HANA base administrators can master the database in a way that wasn't possible back then. The SAP database is much more self-healing. Errors do less damage, are easier to detect and fix, and are less likely to impact system performance and availability before they are fixed. Monitoring tools can automatically scan the application logs, identify potential errors, and even suggest fixes, making it much easier to get to the root of the problem.
SOST SAPconnect - send requests
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.

THE SAP basis AS AN OPPORTUNITY ALMOST EVERY INNOVATION IN THE COMPANY HAS A TECHNICAL FOOTPRINT IN THE BACKEND, WHICH MOSTLY REPRESENTS AN SAP SYSTEM. HERE, THE SAP basis CAN HELP CREATE AN ADDED VALUE FOR THE COMPANY. EARLY INVOLVEMENT IN THE PROJECT IS ESSENTIAL.

"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP base.

If the number of jobs and the complexity increases, an automatic job control is a good choice.

It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).
SAP BASIS
Zurück zum Seiteninhalt