SAP Basis Migration to SAP HANA - SAP Corner

Direkt zum Seiteninhalt
Migration to SAP HANA
Planning and conception of the system architecture, system layout, hardware sizing, system monitoring
In the age of digitisation, the wheel need not be reinvented. Certain functions are consumed or used by platforms only, without fully retaining the necessary infrastructure. In order to participate in this compared to competitors, it is necessary to introduce these technologies, to use them and to learn about their possibilities. Examples include the use of cloud services or applications in the IoT and big data environment.

In the last few years, I have been asked time and again what SAP Basis is and what we SAP Basis administrators do in our daily work. With this blog post I would like to provide a little insight into exactly this area of work.
SMGW Gateway monitor for instance
An SAP HANA system lives on applications. When you develop these applications, you should think about securing them early. Using HTTPS instead of HTTP is one of the basics. In addition, you ensure secure authentication and implement a Secure Software Development Lifecycle to ensure backup in your own developments. In your applications, you better start to check them for risks early on and run this backup process regularly. You can analyse and restrict access to source code later. Create a risk register and address security vulnerabilities in a risk-based manner. The later you discover a risk, the more expensive the fix will be. Further information on SAP Security in addition to the article can be found here. Do you have any further questions or suggestions concerning this topic? Would you like us to go further on the subject? I look forward to your feedback!

As we explained in SAP Basis, your SAP Basis administrator (or team) is directly responsible for keeping your SAP landscape healthy, online, and up-to-date. This includes:

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

Tools that work with status dependencies and then automatically start the next job when its predecessor job has been processed without errors can help here.

Some useful tips about SAP basis can be found on www.sap-corner.de.


The goal of these conventional programs is usually to either crash the program (buffer overflow) or to artificially execute the program's own code (code injection).
SAP Corner
Zurück zum Seiteninhalt