Preparation of full access to SAP systems and solutions in case of disasters (High Availability/Disaster Recovery)
SAP Enhancement Packages
SAP provides support packages: in SAPNet - R/3 Frontend in SAPNet - Web Frontend on Collection CDs Requirements The Change and Transport System is set up correctly. There is enough space in the transport directory (UNIX: /usr/sap/trans). You must have the permissions [page 7] for the SAP Patch Manager. You must be registered with the company 000. You must have called the transaction SPAM. You are using the latest SPAM version. Procedure Support Packages from SAPNet - R/3 Load Frontend Before loading a Support Package from SAPNet - R/3 Frontend, maintain the network parameters for logging in to the SAPNet - R/3 Frontend. Use Transaction OSSordering the desired support packages in the SAPNet - R/3 frontend. Download the requested support packages from SAPNet - R/3 Frontend into your SAPS system with Support Package. A list of support packages appears. You can select the desired support packages before loading. The uncompressed support packages are displayed in bytes. The size of the Support Package allows you to estimate the time it takes to load. Check the progress bar to see if the load was successful. To return to the SPAM entry screen, select Jump Back. Define the queue (page 17).
Protect: CodeProfiler for ABAP protects the SAP system from internal and external attacks from the first day of deployment. The ABAP firewall can be set up within a very short time and immediately checks every new transport request when it is released. Optimize: The audit function of CodeProfiler for ABAP specifically determines which programs are most threatened and should therefore be cleaned up first. In the long term, CodeProfiler for ABAP supports the automated correction of all findings and thus enables the timely closure of security gaps in all programs.
Planning and conception of the system architecture, system layout, hardware sizing, system monitoring
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.
If you want to skip the backgrounds and prefer a direct step-by-step guide, you can jump directly into the last section. Preparation For this workaround, you need access to both the source system and the BW system. In addition, they shall have the possibility to access the SE37 and execute functional modules there. Especially in production systems this is a very critical justification. So assume that you may need a Firefighter user for this action. Working in the BW system Now that the preparations have been completed, you have to call a FuBa on the BW system and on the source system, which solves the connection on the respective page. Beginning on the BW system, go into the transaction SE37 and call the function block "RSAR_LOGICAL_SYSTEM_DELETE": RSAR_LOGICAL_SYSTEM_DELETE Enter the required values here. The following table helps you fill in: Field Description I_LOGSYS The logical name of the source system. The name of the source system, as found in RSA1, will be entered here. In addition, this name can also be found in the DB table TBDLT. I_FORCE_DELETE Boolean, X = Delete despite error messages I_NO_TRANSPORT Boolean, X = This change should not be transported to subsequent systems I_NO_AUTHORITY Boolean, X = Ignore Permission Checks Work in the source system In the source system, go to transaction SE37 and call the function block "RSAP_BIW_DISCONNECT" : The descriptions of the fields are as follows. These can be found in the RSBASIDOC source system connection table Field Description I_BIW_LOGSYS The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". I_OLTP_LOGSYS The logical name of the source system. The column ‘SLOGSYS’ in the table RSBASIDOC. I_FORCE_DELETE The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". Completion In the end, you have to call the respective function block in the BW and source system, fill in the parameters and execute the function block.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
In addition, most business processes are mapped in such a system and offer an attack surface for sabotage.
Several companies were invited to participate and their willingness to participate actively was questioned in a DSAG survey.