SAP Basis SolMan - the Solution Manager takes over the monitoring of the system status and enables central application management - SAP Basis

Direkt zum Seiteninhalt
SolMan - the Solution Manager takes over the monitoring of the system status and enables central application management
Web Dynpro
If you look at everything I've described up front in its entirety, it quickly becomes clear which direction things are headed: the SAP basis will increasingly move toward an SRE-centric environment over the next decade. This is what the future of SAP looks like, and I look forward to an exciting journey.

Basis includes a client/server architecture and configuration, a relational database management system (DBMS), and a graphical user interface (GUI). In addition to the interfaces between system elements, Basis includes a development environment for R/3 applications, a data directory, and user and system administration and monitoring tools.
After installing the GUI, the GUI patches should be applied as far as available. This includes the hotfixes after the patches, which are necessarily installed after the patches. BI Addon Patch A new service package and patch may need to be installed. It may also be that can be patched directly if another SP exists. The process takes about 30 minutes. The progress of the installation pauses at a certain percentage, as already mentioned above, so you do not have to cancel the installation prematurely. If the installation is not possible, the latest version will be included in another setup. Installation of the Precalculation Server The Precalculation Server is installed. You can also install any patches here. Service The installations create a service. This can be called under Services. Set the Startup Type of the service to "Automatic" (Standard Manual) Enter Login Credentials Recovery for First and Second Failure to "Restart the Service" Start Service Logon SAP Login to the SAP system with the appropriate client from the Precalculation Server. You can use the SAP system's own login. Warning: There must be permissions for the transaction RSPRECALCADMIN and SM51. The transaction SM51 will then be called. Before creating the instances, it must be ensured that the correct application server is selected, otherwise problems with the instances in the user's application may occur later. The transaction RSPRECALCADMIN is then called. A certain number of instances are displayed. They should all be marked and deleted until the view is empty again. They are then re-created with a continuous numbering in order to distinguish them later. Only the ID and description must be entered. The rest will be awarded automatically. The service will now restart and all instances should be green. This may take 2-3 minutes. Important: In the end, all instances must be green. This completes the creation and configuration.

You can view them using the RSPUTPRT report or the AL11 transaction. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_? This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Checks whether the queue is fully processed. In this case, transport buffer entries should no longer exist for the Queue. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

Note that the SAP Patch Manager takes into account the configuration of your SAP system and only adds support packages to the queue that can be inserted into your system.

We use the XAMS Security Architect tool, with which we have had good experiences.
Zurück zum Seiteninhalt