Performance optimization
Backup/restore and disaster recovery
The security of an SAP system requires protection against unauthorised access, e.g. through the secinfo and reginfo files. A cleanly implemented authorisation concept protects against attacks within the SAP system. However, it is also possible to attack your SAP system via the network. Through the RFC Gateway Server, your system communicates with external servers and programmes. One particularly effective way to protect against this are so-called Access Control Lists (ACL). Find out what this is and how you can use it to better protect your SAP system. The SAP Standard offers different approaches for gate protection. All methods combined can provide even greater safety. For example, it is possible to use Access Control Lists (ACL) to monitor exactly which external programmes and which hosts can communicate with the gateway. Another option is to configure the gateway to support Secure Network Communication (SNC). Finally, there are various security parameters for the gateway. This article focuses on the use of ACL files such as secinfo and reginfo files. What is an ACL? Access control lists are files in which permitted or prohibited communication partners can be recorded. For the gateway to use these ACL files, parameters must be set in the default profile of the SAP system and of course the files must be maintained accordingly. With the help of logs and traces, which can be configured for this purpose, a precise investigation can be made in advance of the activation, which connections currently run via the gateway. This allows them to prevent important applications with which your system communicates from being blocked by the ACL files. The rules in the ACL files are read from top to bottom of the gateway to decide whether to allow a communication request. If none of the rules matches the requesting programme, it will be blocked. Network-based ACL The network-based ACL file contains permitted and prohibited subnets or specific clients.
SAP Basis represents the cornerstone of the SAP system, i.e. the foundation without which the system cannot function. Furthermore, it includes some administration tools and middleware programs. These programs can be used with the help of SAP Basis independently of the operating system and database used.
Introduction & Best Practices
At the same time, there is a need to return the solutions to the SAP standard. A collaborative approach between departments and IT technology is required to assess IT technical and business benefits. It is also necessary to check whether the adaptation of business processes to avoid modifications to the implementation may be more effective and therefore more cost-effective. This must be evaluated and decided jointly. As a result, we recommend defining and implementing business standards for creating and maintaining solutions.
Some useful tips about SAP basis can be found on www.sap-corner.de.
We actively support you in the migration of operating systems and databases. The optimization of time-critical processes guarantees a smooth process.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
They also need to be able to work in a structured manner and find creative solutions and decisions.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
SAP Patch Manager (SPAM) (BC-UPG-OCS) SAP AG SAP Patch Manager (SPAM) (BC-UPG-OCS).