FAQ on SAP Basis
SWI2_DIAG Access to work item analysis (SWI2)
Through a sound expertise in the SAP technology environment, it is recommended to bring the know-how of the SAP basis into the IT strategy and IT roadmap. For this, the responsibility lies primarily with the CIO as the carrier and responsible of the IT strategy and the IT organisation. Likewise, the SAP basis should serve as a sparring partner for individuals and boards (such as enterprise architects) that significantly influence the strategy.
Another way to secure your gateway using the SAP standard is to encrypt communication using Secure Network Communication (SNC). In the case of unprotected data communication paths between different client and server components of the SAP system that use the SAP protocol RFC or DIAG, the data exchange takes place in plain text and there is a risk that this can be read. With the help of SNC, you can create end-to-end encryption (E2EE), which can be used to secure communication between two components, such as between the application server and SAP GUI. In addition, SNC encryption provides the basis for using SAP Single Sign-On (SSO) as a security solution, which significantly reduces the internal effort of password management.
Storage Management Parameters in the SAP System
A positive aspect of standardisation and automation is the increase in the quality of tasks, since manual errors can be almost excluded. It also increases the speed at which certain tasks can be performed. This is accompanied by a reduction in the proportion of administrative activity and thus in the proportion of the operation of the system landscape.
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP ships it together with the SAP R/3 Plug-In.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
From there, it went on to the network team, the storage team, the operating system team, and the database team.
Enter the tab configuration.