Skip to main content

SUM Tool : An Introduction

Let’s Discuss about the famous tool, that is asked in almost all the Basis and HANA interview and it is very easy to understand but a bit tricky. Tighten your seatbelts and Let’s understand in one go.


SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team and the role of functional consultants is limited and mostly confined to regression testing


What are the maintenance that are performed by help of SUM ?


  1. Release upgrade (major release change)

  2. System update (EHP installation)

  3. applying Support Packages (SPs) / Support Package Stacks

  4. applying Java patches

  5. correction of installed software information

  6. combine update and migration to SAP HANA (DMO: Database Migration Option)

  7. System Conversion from SAP ERP to SAP S/4HANA

 

First thing first , never confuse in these two things : Upgrade and Update. Updating SAP products is for applying support packs, patches or hotfixes. Upgrade term is used exclusively when product release is changed.


How would you define SUM ?


It is a multi-purpose tool that supports various processes, such as performing a release upgrade, installing enhancement packages, applying Support Package Stacks, installing add-ons, or updating single components on SAP NetWeaver.


SUM replaced the following tools , if you used them check this otherwise move directly to next point.


SAPehpi: SAP Enhancement Package Installer

SAPup: tool for upgrading ABAP-based systems

SAPJup: tool for upgrading Java-based systems

JSPM: Java Support Package Manager

CEupdateManager: tool for updating Composition Environment systems

SolManUp: tool for updating and upgrading SAP Solution Manager systems


Why do we use SUM ?


In your system landscape, you regularly face the requirement to apply fixes and software optimizations to keep everything running smoothly.


The Software Update Manager (SUM) is THE tool for system maintenance of all SAP NetWeaver based systems.



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>

  1. Change directory to SUM path 


Login as root user


cd /usr/sap/<SID>/SUM


./startup confighostagent <SID>


  1. Update SAP Host agent to latest patch.

  2. 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

  1. Mention stack.xml file that was result of maintenance planner.


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 factor,


SUM : Tool choice for Software Maintenance of SAP NetWeaver based system 


  1. SUM updates SAP NetWeaver Application Server running on SAP HANA database

  2. SUM updates SAP NetWeaver-based applications running on SAP HANA, such as

  1. SAP NetWeaver BW

  2. SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA



SUM4HANA : Tool for automated update of SAP HANA systems managed from inside your SAP HANA Studio


  1. SUM4HANA updates database server

    1. HDB database software

    2. SAP HANA client

    3. SUM4HANA (tool updates itself)

  2. SUM4HANA updates database-server-based applications


  1. Application Functional Libraries

  2. SAP HANA content


Similarities :-


  1. Both tools consume stack.xml file that was calculated by Maintenance Planner.

  2. Both tools are part of Software Logistics Toolset 



 



Data Migration Option :-


Apart from Upgrading and Updating that are performed on Application Layer, we also have option to migrate the Database along side.It is sometimes referred to as the one-step migration.


Example :- migrate an existing SAP system (running on anyDB) to a SAP HANA database,


Benefits:


  1. Migration steps are simplified

  2. System update, Unicode Conversion (*), and database migration are combined in one tool (*: only possible for a target based on 7.40)

  3. Business downtime is reduced

  4. The source database remains consistent, so a fast fallback is possible




Phase of SUM :-


You can just read the comments of Phases of SUM , reading about phases inside the phases is intermediate level of understanding 



https://whimsical.com/sum-upgrade-U4FDgQAo8TnhWNAwPnozNP



Log files :- 


Logfiles of SAPup:


TP.ECO or SAPup.ECO


*.ELG                    collected error lines from transport logs.



Logfiles of tp:


ULOG…                tp call inclusive used transport profile,

ALOG<rel>          finished steps (request, return code),

SLOG<rel>          details of tp call.


Logfiles of R3trans:


SAPI*                  (main) import logs,


Main log file of TABIM_POST_CLONE: TABUPOSTCLONE.ELG ,

Logfile of conversion step:  N<YYMMDD>.<SID>

Joblog of RDDGEN0L in SM37




Read more :-


Phases of SUM


SUM 2.0 Introduction


SUM and SUM4HANA


DMO SUM Introduction


Benchmarking tool for help in migration










Comments

Post a Comment

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue  Go to System > Status and Check the Basis SP level as well as info

SAP system migration blog series - part 1: migration overview

Summary : This blog is part 1 of the blog series on SAP system migration. In this blog, we will provide overview about SAP migration, types of migration, their differences and usage scenario. SAP migration overview :   As the Greek philosopher, Heraclitus, said: “change is the only constant.” Same goes within SAP world too, often customer have to change the SAP systems along with its underlying components to meet the changing requirements, be it change from old hardware to new one, changing operating system, database. This change in SAP system components (DB, OS or Hardware) is termed as migration. Before we go into details of migration, let’s understand architecture of a typical SAP system.   An SAP system consist of SAP application instances, running on database (DB), hosted on operating system (OS), provisioned on hardware. Change in any one or more of these underlying components (DB, OS or hardware) warrant us to perform migration. Types of migration:   Broadly, there are two types

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set