MONITORING
DB/2-400
There was even a case where the SAP environment required a review of the data center power and cooling. At that time, the data center infrastructure had to be upgraded before we could even proceed.
In the SAP NetWeaver BI Authorization Concept lesson, the training participant is familiarized with the authorization functions of the SAP Business Information Warehouse. The differences between the authorization concept for ERP systems and the authorization concept for NetWeaver BI are taught.
Optimizations
SAP Basis or system administrators work with SAP Basis in a company. They are responsible for the correct installation, configuration and maintenance of the SAP application servers and applications, and in some companies also for the operating system and the SAP database if no administrators are available. Using SAP's own programming language ABAP, developers and programmers design SAP applications that run on the ABAP stack of the SAP NetWeaver Application Server as the only publicly accessible ABAP runtime environment. In some cases, the boundaries between ABAP developers and SAP Basis administrators are permeable, and each of the two groups of specialists has a basic knowledge of the other. As a rule, however, the competencies remain separate.
Many companies are struggling with the introduction and use of secinfo and reginfo files to secure SAP RFC gateways. We have developed a generator that supports the creation of the files. This blog post lists two SAP best practices for creating the secinfo and reginfo files to enhance the security of your SAP gateway and how the generator helps you do this. secinfo and reginfo Request generator Option 1: Restrictive procedure In the case of the restrictive solution approach, only in-system programmes are allowed. Therefore, external programmes cannot be used. However, since this is desired, the access control lists must be gradually expanded to include each programme required. Although this procedure is very restrictive, which speaks for safety, it has the very great disadvantage that, in the creation phase, links which are actually desired are always blocked. In addition, the permanent manual activation of individual connections represents a continuous effort. For large system landscapes, this procedure is very complex. Option 2: Logging-based approach An alternative to the restrictive procedure is the logging-based approach. To do this, all connections must be allowed first by the secinfo file containing the content USER=* HOST=* TP=* and the reginfo file contains the content TP=*. During the activation of all connections, a recording of all external programme calls and system registrations is made with the gateway logging. The generated log files can then be evaluated and the access control lists created. However, there is also a great deal of work involved here. Especially with large system landscapes, many external programmes are registered and executed, which can result in very large log files. Revising them and creating access control lists can be an unmanageable task. However, this process does not block any intentional connections during the compilation phase, which ensures the system will run non-disruptively.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Several empirical studies were also carried out in the course of the work.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
Installation of SAP landscapes, transport management systems, etc.