SAP Basis SAP Workload Analysis

Direkt zum Seiteninhalt
SAP Workload Analysis
CREATE OPEN SPACES
Overall, the application layer is the link between the database layer on the one hand and the presentation layer on the other. Thus, the applications on the application layer request required data from the database in order to process it afterwards.

Better technologies have expanded the role of SAP Basis Administrators, paralleling the IT industry as a whole. It's no longer enough to keep the system running and performing well. An SAP HANA Basis Administrator also plays a role in cost control, IT strategy and even business policy.
SCC1 Client copy
New risks in SAP HANA: In addition to the known risks, there are also new risks from the use of SAP HANA. A very good example are frequently used web applications that represent something new in the SAP area. In contrast to an SAP ERP system, HANA systems consist mainly of web applications, which were considered optional in the previous versions. These web applications can be found by various search engines on the Internet. This also applies to SAP Portal or Netweaver. There are URL schemes that help locate the system. This also applies to other SAP systems that use Web applications. This makes the new technology vulnerable to typical web attacks. SQL Injection, ABAP Code Injection, or XSS are all included. All risks known for a normal SAP system also apply to a SAP-HANA system. The data is stored unencrypted in RAM. Only then does the system gain this speed advantage. This results in risks such as a read-out by memory scraping malware. These pick up data in memory. Encryption costs performance, so it is not used by default. Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape. Also note: HANA has its own tools and settings that need to be known and configured. The bottom line is that the system simply needs more attention when operating. Many settings often result in more errors. Three - points - HANA Security Plan 1) Roles and permissions In a previous SAP system, roles and permissions are certainly one of the main pillars of a secure system. Roles and permissions work differently in a HANA system. There are two types of users: 1) Default (limited): With this type of user, there are different access methods to the database. For example, the JDBC or HTTP technologies are used to give two examples.

SAP Basis or system administrators work with SAP Basis in a company. They are responsible for the correct installation, configuration and maintenance of the SAP application servers and applications, and in some companies also for the operating system and the SAP database if no administrators are available. Using SAP's own programming language ABAP, developers and programmers design SAP applications that run on the ABAP stack of the SAP NetWeaver Application Server as the only publicly accessible ABAP runtime environment. In some cases, the boundaries between ABAP developers and SAP Basis administrators are permeable, and each of the two groups of specialists has a basic knowledge of the other. As a rule, however, the competencies remain separate.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

As a result, the know-how is often lacking and it is quickly taken to the next search engine, where long and partially incomplete forum entries make finding the right approach even more difficult.

In the past, when we deployed SAP environments, we first had to work out detailed sizing and architecture and pass this on to the procurement team, who then ordered the systems and installed them in the data center.
SAP Corner
Zurück zum Seiteninhalt