SCC3 Log evaluation client copy
SM37 Simple Job Selection
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.
Either temporary programme calls are blocked that are actually desired or enormously large gateway logs must be analysed. If, due to the heavy workload, one were to decide to forgo the use of the access control lists permanently, this would be a major security vulnerability. The unprotected system does not have any limitations on the external services that may register, and there are no rules for running programmes. One possible consequence would be, for example, the registration of an external system on which malicious programmes exist. At the moment when foreign programmes are running on your system without any control, you can expect that great damage will be done. For example, it ranges from an unnoticed reading of purchase and sales figures, a diversion of funds, to a paralysis or manipulation of the entire system. In addition, this scenario is also possible for poorly maintained access control lists. Our solution: secinfo and reginfo Generator for SAP RFC Gateway To solve the problem, we have developed a generator that can automatically create secinfo and reginfo files based on gateway logs. The basic idea is based on the logging-based approach. It performs the task of time-consuming analysis of log files and also ensures maximum reliability through automation. Nevertheless, the entries of the generated files should be checked by one person. Since the log files used as input are sensitive data, of course none of the inserted data leave your system. More information about the generator can be found here.
SWEQADM Administration of the event queue
He has already gathered a lot of helpful information from the day-to-day business in his department: Johannes knows the RFC interfaces and the corresponding technical RFC users from his work with the applications. He also quickly got the password for various RFC users via the radio ("As long as passwords are only communicated by phone and never exchanged in writing, we are clean!"). And that the RFC users are generously entitled even in productive systems is no longer a secret ("Better to have more permissions than too little; the RFC connections have to run, otherwise there is trouble from the specialist areas!"). Since Johannes has access to the SE37 as a developer, it is not a problem to get the necessary access using the function block BAPI_USER_CHANGE - disguised as RFC User. In short, it changes the user type of a technical RFC user in a production system from to by calling the function block.
Using profile parameters, we can configure everything in the SAP system. Some parameters are dynamically modifiable, which means that they can be changed without restarting the system. However, these changes are not permanent, i.e. after a system restart, the pre-set profile parameters are used again. Other parameters, however, are static, i.e. only with a restart and only permanently modifiable. Most profile parameters for memory allocation are actually static. However, there is the possibility to adapt it dynamically with the report RSMEMORY. Read how to find out if a parameter is static or dynamic and how to use the RSMEMORY report to dynamically adjust the memory allocation parameters. RZ11 - Maintenance of profile parameters The transaction RZ10 gives us information about profiles, which in turn contain different profile parameters. In the transaction RZ11, however, it is possible to view information about individual parameters, provided that you know their name. As you can read in our Memory Parameter Post, the following 5 parameters are particularly important for memory management: abap/heap_area_total abap/heap_area_dia abap/heap_area_nondia ztta/roll_extension_dia ztta/roll_extension_nondia If you don't know exactly what a parameter might be called, it's worth using the F4 help here. For example, for the parameter abab/heap_area_dia, the RZ11 outputs: Description of the parameter abap/heap_area_dia in the RZ11 As you can see here, it is not a dynamic parameter. Now it is rather sorry if you want to test whether there is enough memory available to restart the system again and again. For this purpose, there is the RSMEMORY report. RSMEMORY - Test your memory allocation strategy Report RSMEMORY Report View No documentation or value help available here, but SAP documentation tells you how to use the report. This first distinguishes between dialogue and non-dialogue work processes. That is, in the first area you can set Extended Memory (Storage Class 1) and Heap Memory (Storage Class 2) for Dialogue Workprocesses, and in the second area you can set it for non-dialogue workprocesses.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
DDIC_IMPORT This step imports the ABAP Dictionary.
The website www.sap-corner.de offers many useful information about SAP basis.
SAP Basis represents the cornerstone of the SAP system, i.e. the foundation without which the system cannot function.