SHARING OF THE SAP basis INTO A SINGLE APPLICATION AND INFRASTRUCTURE-RELATED LAYER
The structure of SAP Basis
This makes the technical user the dialogue user and a login in the SAP system is unrestricted. So Johannes logs in with the known password of the RFC user in the production system. Thanks to very extensive permissions, it now has access to all sorts of critical tables, transactions, and programmes in production. With the identity of the RFC user Johannes starts with the technical compromise of the production system... RFC Security: All invented - or everyday threat? Whether a simple trim, altered biometric properties or an encapsulated technical user in the SAP system: the basis of the compromise is the same. A person uses a different identity to gain access and permissions to protected areas. Moreover, the evil in all three stories could have been prevented by pro-activity. When was the last time you thought about the security of your RFC interfaces? Can you say with certainty that all your technical RFC users only have the permissions they actually need? And do you know who exactly knows the passwords of these users? Can you 100% rule out that not now in this moment an SAP user with a false identity infiltrates your production systems? Change now: It's about pro activity! But before you start now and start looking for the "identity converter" (which I really do not recommend!), I suggest that you take root of evil and proactively strengthen your RFC security. So if you want to find out more, I have the following 3 tips for you: 1) Our e-book about SAP RFC interfaces 2) Clean up our free webinar about RFC interfaces 3) Blog post about our approach to optimising RFC interfaces As always, I look forward to your feedback and comments directly below these lines!
Administrators often need to replicate part or all of a database, for example, to create a system backup or test an upgrade before putting it into production. In the past, this was surprisingly difficult to do with most databases. With HANA, replication works instantly and offers richer features and better control than previous databases.
Change and Release Management
A first important step was the introduction of playbooks to professionalize our work. At that time, SAP installation manuals were real tomes with hundreds of pages that often went round in circles and were anything but easy to understand....
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
Standardisation of SAP operations as well as SAP systems can be seen as a preparation for automation as well as for cloud, outtasking and outsourcing service forms. Therefore, in the whole context of standardisation and automation, a sequence of tasks and systems needs to be followed. To do this, it is necessary to first make a detailed documentation of the respective object, which also describes the IST state in detail. A standardisation strategy can then be developed, defined and implemented. Only then can we consider automation, outtasking, cloud, and outsourcing.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
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.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Ten years ago, SAP HANA was little more than a promise that made SAP CEO Hasso Plattner's eyes light up.