SAP RFC Gateway Security through secinfo and reginfo ACL files
Flexible response to peak loads
A role concept according to best practice protects you from potential attacks within your SAP landscape. However, to protect your system from unauthorized access via the network, the SAP Gateway must be configured correctly. It enables the use of external programs via interfaces or the call of ABAP programs and serves as a technical component of the application server, which manages the communication of all RFC-based functions.
The database layer is used to store all company data and consists of the database management system (DBMS) and the data itself. In each NetWeaver system there is a database server on which the SAP database is located. It provides all other applications with the necessary data. The data is not only data tables, but also applications, system control tables and user data. All basic components ensure that the user has fast and reliable access to this data.
Management of databases
Reduce resources: depending on the agreement of the contract, you can ask for the service resources only when needed. This will save you some costs.
You can call the SPAM transaction in one of the following ways: Select SAP menu Tools Maintenance Patches. Enter the transaction code SPAM. Features The SAP Patch Manager provides the following features: Loading Support Packages: Requested support packages can be loaded into your system from SAPNet - Web Frontend, SAPNet - R/3 Frontend, or Collection CDs. Inserting Support Packages: Resetting When SPAM inserts a support package into your system, a fixed sequence of steps is followed. If the Support Package implementation stops, you can resume processing at a later time. The operation will resume where it was cancelled.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
ABAP code: 84% faster and more fail-safe programs.
On www.sap-corner.de you will also find useful information about SAP basis.
If Authority Checks are performed here, e.g. to query or change data on the backend server, the corresponding role must be authorised.