Make sure, that the SAP system SMA is started and running without problems.
In SAP GUI, use System → Status to check the current patch of the software components of your SAP system SMA, especially for SAP_BASIS and ST.
Via Remote Desktop Connection, log on to smxhost with user smaadm.
Note
It is important to log on with user smaadm – not with user install. Maybe you have to open a new Remote Desktop Connection. For license reasons, not more than two Remote Desktop Connections are possible in parallel. So it could be, that you have to log off of one Remote Desktop Connection in order to open a new one.Open a Windows explorer and check the free space on directory D:. There should be some free disk space available.
The files to be imported by SUM were calculated by MP, already. They were downloaded to D:\Media\Update_SMA\02_MP_Download. This folder can be used as download directory. But some files are missing there: copy the stack XML, provided by MP, to the download directory. Also, you can optionally copy the statistics file from a previous, similar SUM run to the download directory.
Use the Windows Explorer to copy the file MP_Stack_1002049064_20240720_.xml from D:\Media\Update_SMA\03_MP_Stack_XML to D:\Media\Update_SMA\02_MP_Download.
Note
This step is essential: The stack XML file needs to exist in the same directory in which the update media reside. When obtaining the update files and the stack XML file from the Maintenance Planner, they will be usually located (after download) in two different places.Use the Windows Explorer to copy the file UPGANA.XML from D:\Media\Update_SMA\04_Statistics to D:\Media\Update_SMA\02_MP_Download.
Open a command prompt at D:\usr\sap\SMA.
Extract the SUM archive, delivered by the Maintenance Planner, to this directory:
sapcar -xf D:\Media\Update_SMA\02_MP_Download\SUM11SP03_1-80006853.SAR
A folder D:\usr\sap\SMA\SUM is created and about 25.000 files are extracted from the archive.
Configure SAP Host Agent for SUM:
Open a command prompt at D:\usr\sap\SMA\SUM\abap.
Execute SUMSTART.BAT confighostagent SMA.
The URL for starting SUM in a browser is displayed: https://wdflbmt0910:1129/lmsl/sumabap/SMA/sluigui
On the WTS, open a browser, for example Google Chrome
Copy the URL presented by SUM into the browser: https://wdflbmt0910:1129/lmsl/sumabap/SMA/sluigui.
Note
Please note that the first access to the SUM UI will take several minutes before the UI shows in the browser. Even when the browser asks for leaving the seemingly unresponsive page, don't do so.Log on to the SUM UI with user smaadm.
The files to be imported by SUM were calculated by MP, already. They were downloaded to D:\Media\Update_SMA\02_Download. This folder can be used as download directory. The stack XML file was already copied into this directory in an earlier step, as well as a statistics file from a previous, similar SUM run.
Now start the SUM:
If not stated differently, always choose Next to continue. There will be screens that require just choosing Next.
Parameters and Data for Updating SAP Solution Manager AS ABAP using SUM with scenario strategy Single System (Part 1/4)
| Screen Name | Field Name | Value |
|---|
| Welcome to Software Update Manager | STACKFILE | D:\Media\Update_SMA\02_MP_Download\MP_Stack_1002049064_20240720_.xml |
| Required System Passwords | DDIC PASSWORD | enter the master password set during installation – should be MasterSMA80 |
| Required System Passwords | OS PASSWORD | enter the master password set during installation – should be MasterSMA80 |
| Operating System and Stack Kernel Checks | | operating system and SAP kernel are OK |
| Operating System and Download Kernel Checks | | operating system and SAP kernel are OK |
| Database Migration Option | DATABASE TYPE | confirm the selection No migration |
| Operating System and Download Kernel Checks | | operating system and SAP kernel are OK |
| Information | | check the several information items displayed at the end of roadmap step Extraction |
| Continue with roadmap step "Configuration" | | read the information messages displayed |
| Tool Configuration | Single System | select |
| Tool Configuration | Switch expert mode on | select |
| Tool Configuration | Keep archiving on during the whole procedure | select |
| Parameters for procedure | ABAP PROCESSES (UPTIME) | set to 8 |
| Parameters for procedure | ABAP PROCESSES (DOWNTIME) | set to 12 |
| Parameters for procedure | SQL PROCESSES (UPTIME) | set to 8 |
| Parameters for procedure | SQL PROCESSES (DOWNTIME) | set to 12 |
| Parameters for procedure | R3TRANS PROCESSES (UPTIME) | set to 8 |
| Parameters for procedure | R3TRANS PROCESSES (DOWNTIME) | set to 12 |
| Parameters for procedure | R3LOAD PROCESSES (UPTIME) | set to 12 |
| Parameters for procedure | R3LOAD PROCESSES (DOWNTIME) | set to 64 |
| Parameters for procedure | Automated batch job distribution | select this option |
| Parameters for procedure | Choose an execution strategy for transaction SGEN | IMPORTANT!: select Do not start ABAP load generation during the update |
Continue the update using SUM, entering the data as shown in the table.
Parameters and Data for Updating SAP Solution Manager AS ABAP using SUM with scenario strategy Single System (Part 2/4)
| Screen Name | Field Name | Value |
|---|
| Add-On Selection | | do not change the default selection |
| Select Support Packages You Want To Include | | do not change the default selection |
| Include Change Request | | do not change the default selection (no transport requests) |
| Operating System and Download Kernel Checks | | operating system and SAP kernel are OK |
| Modification Adjustment | | do not change the default selection (no transport requests) |
| Information | | check the several information items displayed at the end of roadmap step Configuration |
| Continue with roadmap step "Checks" | | read the information messages displayed |
Continue the update using SUM, entering the data as shown in the table.
Parameters and Data for Updating SAP Solution Manager AS ABAP using SUM with scenario strategy Single System (Part 3/4)
| Screen Name | Field Name | Value |
|---|
| Information | | check the information items displayed at the end of roadmap step Checks |
| Continue with roadmap step "Preprocessing" | | read the information messages displayed |
| Lock Development Environment | | select Lock now |
| Open Repairs found (if there are any) | This screen will only be shown in case there are unreleased transport requests. | in case there are any open repairs, release the corresponding tasks and transport requests in transaction SE09 |
| Preparations for Downtime | | in the context of this course do not perform the required actions and select Actions completed |
| Backup Request | | select Backup completed |
| Continue with roadmap step "Execution" | | read the information displayed |
| End of Downtime | | read the confusing information displayed |
| Continue with roadmap step "Postprocessing" | | read the information displayed |
| Procedure Complete | No SPAU transport imported | do not select Continue and proceed right now, but perform SPAU first! |
| STOP here | perform SPAU modification adjustment | leave SUM waiting, don’t select anything in SUM |
Log on to SAP system SMA, client 001, with user ADMIN_001.
Note
Please note: SPAU won't work as designed, because the connection to the SAP Support Backbone Infrastructure is not configured as it would be in customer systems. The configuration for the newly installed system to access and download Digitally-signed SAP Notes is described in SAP Note 2836302 and related SAP Notes. Therefore, the activities in transaction SPAU in this training should be seen as additional information of what would be required to do during a real update.Call transaction SPAU.
Choose Execute.
Select Reset Obsolete Notes and create a transport request with the title SPS 19: SPAU.
In a second SAP GUI window, call transaction SM37 and wait until the batch job SCWB_BGR_OBS_NOTE_RESET has finished.
Without successful connection to the SAP Support Backbone Infrastructure, the previous step can not be executed successfully, as you can see in the job log.
In transaction SPAU: Reset the SAP notes with the gray traffic light - and ignore the error indicating, that there is no valid HTTPS connection to SAP Support Portal. Re-implement the SAP Note(s) with the yellow traffic light. Proceed SAP Note by SAP Note and follow the instructions. Use the transport request created for SPAU.
In a second SAP GUI window, call transaction SE09 and release the task of the transport request containing the objects from modification adjustment. Do not release the transport request itself!
In the other SAP GUI window, still in SPAU, choose Assign Transport and select the transport request for SPAU.
Confirm the pop up Confirm transport request with Yes.
Continue the update using SUM, entering the data as shown in the table.
Parameters and Data for Updating SAP Solution Manager AS ABAP using SUM with scenario strategy Single System (Part 4/4)
| Screen Name | Field Name | Value |
|---|
| Procedure complete | Continue | read the information |
| Start of Cleanup Processing | | read the information |
| Feedback to SAP | | Close |
| Procedure Finished | | check the information by SUM about some of the many required post update activities. In the context of this course do not perform any actions. |
| Procedure Finished | | select More → Exit |
| Tool start required | | again, select More → Exit |
In the SMA system, check at System → Status for the new, updated software component level. :-)
