SAP Basis For simple system environments, simple batch jobs are often sufficient - SAP Stuff

Direkt zum Seiteninhalt
For simple system environments, simple batch jobs are often sufficient
Avantra recently became available in the Google Cloud Marketplace. It is worth mentioning here that we have fully containerized the deployment of Avantra here, so each component runs in a separate container. For the database, we use Cloud SQL.

In addition to proactive monitoring to prevent possible errors or even complete system failures, our SAP Basis team also implements clearly defined authorization concepts. So that unauthorized persons cannot access important data and your employees are protected from unintentional violations.
IT professionals are taking the first steps in automation with the use of tools like RedHat Ansible. At our company, for example, Ansible is used for mass rollouts of agents in large environments.

It is possible to specify a trace level for each rule in the ACL file to monitor each communication channel individually. It can be used with SNC without any further configuration. The use of the file is controlled by the gw/acl_file parameter by simply setting it to the appropriate file name. Use of external programmes If an external programme wants to communicate with your SAP system, it must first register at the gateway. The programmes which this is approved are controlled by the reginfo ACL file. This defines rules that allow or prohibit certain programmes. The syntax of the file allows you to define not only the name of the programme, but also the host on which the programme runs and hosts that can use and exit the programme. The gw/reg_info parameter must be set to use this file. In addition, there is the ACL file secinfo, which allows to configure which users can start an external programme. This defines rules that allow certain usernames from the SAP system to use certain external programmes. In addition, you can also define the hosts on which these programmes will run. For example, it is possible to allow a user to run the programme "BSP" on the host "XYZ", but not on the host "ABC". This file is controlled by the gw/sec_info parameter. Using the gateway as a proxy Since the gateway of your SAP system can also serve as a proxy server, the prxyinfo ACLDatei should also be activated via the gw/prxy_info parameter. Suppose you have 3 SAP systems in your network: SRC, TRG and PRX. If SRC cannot communicate directly with TRG, but both with PRX it would be possible to use the gateway of the PRX system as a proxy server, i.e. to communicate via it. So, in order to prevent this from happening to everyone, this property should be urgently restricted. As with the other ACL files, rules are defined which hosts can communicate with which hosts via the gateway. The syntax of the different ACL files may vary depending on the release level. It is therefore advisable to read them in the appropriate SAP documentation before activating the ACL files. You can also find more support for using ACL files in the SAP Community Wiki.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs).

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

Let us now turn to the direct approach to the changeover to system variability.
SAP Stuff
Zurück zum Seiteninhalt