SAP Basis Objectives of the training SAP HANA - Installation and Administration: - SAP Stuff

Direkt zum Seiteninhalt
Objectives of the training SAP HANA - Installation and Administration:
REDUCTION AND AVOIDANCE OF ORGANISATIONAL INCENTIVES
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!

The technology architect is well acquainted with the company's core business, has business process and project management expertise. As part of its activities, the technology architect does not exercise project management or project management. He develops and develops strategies and solutions in coordination with higher authorities, IT departments and also business units. It defines requirements for the implementation and operation, which it aligns with the operator or with the necessary expression of the Subject Matter Expert. He also takes care of new technologies in his field of activity and is thus a driver of innovation and a catalyst from a technical point of view. He also acts as a contact for enterprise architects in the company. However, this role will be much more coordinated in the future. The range of tasks will therefore increase in width. An additional requirement in the future will be the understanding of company policy.
Optimize system performance
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.

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


Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page "www.sap-corner.de" you will find useful information on this topic.

Deleting assignments between users and roles if either the user or the role does not exist.

SAP Stuff
Zurück zum Seiteninhalt