The SAP Software Update Manager (SUM)
Combines many SAP update and upgrade mechanisms that were implemented
separately in previous SAP releases into one single tool .
What is the maintenance that is performed with the help of SUM?
Maintenance Task Description
Software Upgrades Upgrading to new SAP versions or releases.
Support Package Installation Applying support packages and patches.
System Migration Assisting in migrations to SAP S/4HANA or other platforms.
Database Migrations Facilitating database upgrades or changes.
Add-on Installation/Update Managing the installation or updating of SAP add-ons.
Supporting changes in the system landscape, like system
System Landscape Changes copies or reorganization.
Which SUM for which scenario?
We have two types of SUM for different Scenario: SUM 2.0 and SUM 1.0
Apart from SUM 1.0 and SUM 2.0, we have two more distinguishing factors,
Tool Description Key Updates
Tool for software maintenance of SAP Updates SAP NetWeaver Application Server
SUM NetWeaver-based systems on HANA
SAP NetWeaver BW
SAP ERP Enhancement Package 6 for SAP
HANA
Tool for automated updates of SAP HANA Updates database server and HDB
SUM4HANA systems database software
SAP HANA client
Database-server-based applications
Application Functional Libraries
SAP HANA content
Similarities:-
1. Both tools consume a stack.xml file that was calculated by Maintenance Planner.
2. Both tools are part of the Software Logistics Toolset
Data Migration Option:-
Apart from Upgrading and Updating that are performed on the Application Layer, we also have
the option to migrate the Database alongside. It is sometimes referred to as the one-step
migration.
Example:- migrate an existing SAP system (running on any DB) to a SAP HANA database,
Benefits:
Migration steps are simplified
1. System update, Unicode Conversion (*), and database migration are combined in
one tool (*: only possible for a target based on 7.40)
2. Business downtime is reduced
3. The source database remains consistent, so a fast fallback is possible
SAP SUM (Software Update Manager) Upgrade Phases
Now we can go through the detailed phases included in the SUM upgrade process
SUM Having mainly 6 steps,
● Extraction
● Configuration
● Checks
● Preprocessing
● Execution
● Postprocessing
Step 1.Extraction
● DDIC username and password
● Identify database & SAP version
● Checks the stack xml file
● Scanning of download directory where all the patches are placed
● Extract files to move to EPS/in
● Check SPAM version. Skip this if SPAM is already in latest version
● <SID>ADM credentials
● Pre-upgrade S-note list implementation
● Checks if the source and target system is valid for update
● Checks SAP system release
● Checks the system profiles
2. Configuration
● Input parameters for the type of upgrade (downtime optimizes, higher complexity,
high resource assignment)
● Keep database archiving on
● Execution strategy for transaction SGEN
● Maximum number of processes to be used for load generation. SGEN Processes
● Batch Process(Uptime) & Batch Process(Downtime)
● Maximum number of DDL processes (Uptime and Downtime)
● Number of parallel import processes (R3trans -Uptime and Downtime)
● Parallel Phases (Uptime and downtime)
● Update Instances
● Enhancement package inclusion
● Add-On selection
● Modification Adjustment (SPDD transport request and SPAU transport request)
3. Checks
● Space check in database, if space is Insufficient then extend tablespaces with
script
● BW checks and phases
● Activation and conversion checks
● Modification support
● Preliminary upgrade processing
● List Locked SAP objects
4. Preprocessing
● Check for locked objects
● ABAP Workbench locking
● Run shadow system for preparation of new release (ACT_UPG, PARDIST,
SGEN)
● SPDD Adjustments
● Downtime Starts
5. Execution
● Merging of Shadow and Real Instance
● system upgrade
● Table Conversion
● Downtime Complete
6. Post-processing
● SPAU change
● Backup
● Create a folder in the trans directory (EHPi)
SUM Path: /USR/SAP/SUM
Software Update Manager Latest Version 2.0 SP 19
SPDD (System Performance Diagnostic Data) in SAP is a tool that collects and analyzes system
performance data to identify bottlenecks and optimization potential. It provides detailed reports
and recommendations to improve system performance and troubleshooting
What is the use of shadow instance?
The shadow instance in the SUM upgrade is a temporary instance created during the upgrade
process
To test and validate the update without affecting the live system.
How to run SUM?
1. Plan your Maintenance planner
2. Log on to the primary application server instance is running as user sidadm user
(OS admin user)
3. Unpack the <archive.SAR> file (download this file from support.sap.com , Read
this before installing : http://support.sap.com/sltoolset )
SAPCAR -xf <downloadpath : path were SUM downloaded files are present> -R
<path to SUM directory >
SAPCAR –xf <download directory>/<path>/<Archive>.SAR -R /usr/sap/<sid>
4. Change directory to SUM path
Login as root user
cd /usr/sap/<SID>/SUM
./startup confighostagent <SID>
5. Update SAP Host agent to latest patch.
6. Open a web browser and open this link
https://<hostname>:1129/lmsl/sumjava/<SID>/index.html
You will prompted to enter the <sid_adm> and password
7. Mention the stack.xml file that was the result of the maintenance planner.
