Indirect use of SAP
An SAP landscape is made up of numerous individual modules that are fully compatible with each other and can be used to map the business processes of all areas of a company. SAP Basis is used to ensure the functionality of the individual modules.
Together with our SAP development team, our SAP Basis experts develop programs and transaction processes using Web Dynpro technology. This includes, for example, our SAP AddOn "SAP Password Reset". We would be happy to develop your solution.
Resource management such as memory, buffers, etc
Due to the variety of tasks and the high level of complexity, I find my job extremely exciting. There are very many constellations of SAP systems and databases. Each installation, migration and update brings new aspects and challenges. It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.
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.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
Of course, SAP administration is carried out by certified and experienced employees.
For example, the JDBC or HTTP technologies are used to give two examples.