SAP BASIS Introductory Training

Program
DAY 3 – Operations in AS ABAP Systems : Part 2

CONFIDENTIAL
Day 3 : Agenda

09:00 AM - 11:00 AM SAP Memory and Buffer Management

11:00 AM - 11:15 AM Break
11:15 AM - 01:00 PM Performance and Workload Analysis
01:00 PM - 02:00 PM Lunch Break
02:00 PM - 03:30 PM System Monitoring and Troubleshooting
03:30 PM - 03:45 PM Break
03:45 PM - 05:00 PM Web Enablement & Communication in SAP
05:00 PM - 06:00 PM Exercise & Break Out Session

August 12, 2024

 SAP Buffers &
Memory Management

August 12, 2024

Overview of AS ABAP Operations – Part 2

• SAP Memory Management

• Performance monitoring of SAP systems
• Troubleshooting errors in SAP
• Using CCMS for monitoring
• ITS and ICM Technologies
• RFC Connections
• Communication & Integration Technologies

August 12, 2024

System Monitoring – Who, What, Why, When
What - Why -
Keep the system running
Components in SAP
Improve performance
SAP
(application servers,
buffers, applications, …)

Who -
Administrators
Database:
(performance, backup, ..)

Operating system: When -

(CPU, file system, ..) Periodically 11
12
1
10 2
9 3

8 4
7 5
6

August 12, 2024

SAP Memory Management

• To optimize the performance of SAP Systems , it is necessary to understand

Memory Management in SAP
• The previous sessions provided explanation on SAP work processes and how
they are executed
• For each work process to execute a certain amount of memory is required. This
memory can be a part of the RAM or part of Paging File also called Swap)

Virtual
ABAP Work DISPATCHER Memory
Processes Segment

D B B

Virtual
Memory
Segment

August 12, 2024

Concepts of Physical and Virtual Memory

• Memory refers to a part of the SAP system which is used a temporary container
of data used by processes. This includes Operating system processes , Database
processes as well as SAP application processes.
• A system consists of physical memory , called RAM
• Physical memory may not be sufficient in most cases , so some part of the file
system disk storage can be used to supplement the physical memory.
• Using the concept of virtual memory , the Operating system can provide SAP
applications with a contiguous memory combining both RAM and Files on the
OS.Such files are known as paging files or swap.
• This virtual memory available to SAP processes is called “Virtual Addressable
Space”
• The virtual memory is further subdivided into a stack area and heap area. A stack
is where data related to recursive functions and loops in function calls are stored
for the process that needs the data. A heap is where the data elements such as
constants and variables are stored during report and function execution

August 12, 2024

Concepts of SAP Memory Management

• In 32 Bit systems , each SAP work process can only address upto 2 32-1 bits of
memory space , which is around 4 GB
• But most Operating systems will not permit a single process to address 4 GB of
space. There are limitations and differences between operating systems , but
about 2 GB of virtual memory is available to each SAP work process. This is the
maximum addressable limit
• Please see the example below

VIRTUAL MEMORY
• Theoretically , the configuration
indicates a total of 108 GB of virtual
RAM memory , which can support upto 54
8 GB
SAP processes during peak memory
utilization. However the amount of
PAGING
memory to be allocated should be
FILES
100 GB decided on actual performance of the
system

August 12, 2024

Concepts of SAP Memory Management

• The operating system will reserve a part of the virtual memory , known as a
segment when the SAP work processes starts to execute. The size of this
segment is set in the SAP profile parameters.
• The operating system will reserve local process memory as well as a shared
process memory
• The “local process memory” segment can be addressed only by one of the
processes , i.e. , any one of the DVEBMS processes.
• There are data elements that needs to be shared between say , a dialog process
and an update process , and these elements are processed in the “shared
memory” segment.
• The three types of SAP Memory are shown below :

Virtual Memory

SAP Roll Area

SAP Extended Memory
Private Memory
August 12, 2024
 Types of Memory
SAP Roll Area
• This is the memory segment made available immediately to a work process.
• It has a physical memory part and a paging file part. The paging file specific to roll memory
is called a “roll” file.
• Work processes switch contexts , meaning that one work process may process data related
to a particular user request , and then may switch to perform processing related to another
user request. Whenever such a switch happens , the data in the roll area is transferred to the
roll file , which is a common memory segment for all work processes
• A roll buffer between the role area and the roll file prevents repeated copying from occurring
SAP Extended Memory
• This is the main memory segment for an SAP application
• Each work process is assigned a segment of the extended memory for further processing of
data , once the roll area memory is exhausted
Private Memory
• Work processes such as background,update,enqueue and spool may exhaust all roll area
and extended memory. In such a case , the dialog process is unable to execute. To ensure
that some amount of memory is ALWAYS available to a dialog process , SAP provides a
Private memory for each dialog work process

August 12, 2024

Virtual Address Space for a Process

August 12, 2024

Important Profile Parameters

August 12, 2024

 Concept of SAP Buffers
• SAP buffers store frequently-used data, and make this data available to the local
application server instance. This helps to reduce the number of database accesses, the
load on the database server (it does not need to be accessed repeatedly to obtain the
same information), and network traffic. As a result, system performance is
considerably improved
• Each SAP instance (application server) has its own buffers. These buffers are also
known as client caches because they are implemented on the client, that is, the
application server. SAP buffers occupy memory areas that are local to the work
process, and in individual shared memory segments that can be accessed by all work
processes.
• The roll area discussed earlier is considered to be a type of SAP Buffer
• The data that is buffered includes ABAP programs and screens, ABAP Dictionary data,
& company-specific data. Typically these remain unchanged during system operation
• You can change, or tune, the sizes of buffers to optimize performance for a particular
hardware configuration. There are several ways to tune buffers. As there are many
constraints to consider when change the buffer size, several difficulties may arise.
• You can use table buffering to fine-tune applications, that is, some or all of the
contents of infrequently changed tables can be held in local buffers

August 12, 2024

Types of SAP Buffers
There are 8 groups of SAP Buffers found in the shared memory segment :

Buffer Purpose
Repository (Nametab) The name table (nametab) contains the table and field definitions that are activated in
Buffer the SAP System. An entry is made in the Repository buffer when a mass activator or a
user (using SE11) requests to activate a table. The corresponding name table is then
generated from the information that is managed in the Repository. There are 4 sub-
buffers : Table definition , Field definition , Short Nametab and Initial records.
Table Buffer This buffer can store a single record with its field values , or multiple table records.
There are two types , Partial Table and Generic Table buffer
Program Buffer Compiled version of ABAP programs are stored in this buffer

SAPgui Buffer There are two types : Presentation and CUA buffers. The generated screens from
SAP transactions are stored in this buffer as well as SAPgui menus , pushbutton
definitions etc.
Roll & Paging Buffers & This buffer stores the input & output data from a user request for processing. The
Extended Memory extended memory stores a large portion of the internal tables of a program.
SAP Calendar Buffer All defined factory and public holiday calendar objects are stored in this buffer

Import/Export Buffer Import / export buffers are used to store data that must be available to several work
processes. They are used, for example, for the Available-To-Promise logic (ATP logic)
in Logistics
SAP Cursor Cache The SAP cursor cache helps to improve system performance by reducing the number
of parsing of SQL statements; it is database-dependent

August 12, 2024

SAP Buffer Management – ST02

Hit Ratio is
percentage of times
an object was found in
Size of the Buffer in
the SAP buffer ,
KBs
instead of having to
fetch the object from
Number of Objects in
the database. A high The swaps value is the number of objects that had
the buffer
hit ratio signifies very been kept in the buffer for sometime , but had to
good buffer quality swapped with a new object that was fetched from
and is indicative of the database as part of new user request. Ideally
good system the number of swaps should not exceed the setting
performance for directory size in a system. As part of buffer
tuning , ensure that number of swaps are not more
than twice the number of objects set for a buffer. If
this is not the case , increase the size of the Buffer
memory to reduce swaps and reduce the database
access calls

The sum of “In Mem” will give you the

Total Physical Memory allocated to
this SAP instance by the Operating
System. In this case the total RAM
allocated is 3.5 GB 12, 2024
August
Tuning of SAP Buffers

NOTE
Using ST02 , you can
tune the buffer
parameter values.
Typically the program
and table buffers are
allocated higher values.
But buffer tuning is a
fine art. The SAP
system after installation
will have some default
values. You must
observe the system
behavior for a couple of
months and then see
the buffer quality and
swaps pattern to take a
decision to change the
memory limit for a
buffer

August 12, 2024

 Summary Graphic for SAP Memory and Buffers
Frontend: SAP GUI
LAN / WAN

Request Dispatcher
queues Work
process n
Screen
Internal memory

Work
process 1 processor
ABAP
processor
Task
handler ...
Database
interface

Buffer access Roll out Roll in

Applications buffer Roll area
Factory calendar
Shared memory Screens
ABAP programs Roll file
User context
Tables
Dictionary objects... August 12, 2024
BREAK

August 12, 2024

 Performance &
Workload Analysis

August 12, 2024

Workload Analysis using ST03N
• The transaction ST03N is the most important transaction in SAP for a BASIS
consultant
• This transaction provides information on system performance , response times for
SAP, Database and frontend , dialog steps information per user , per transaction
• The information is available as a snapshot , as well as aggregated over days, weeks
and months
• The transaction provides critical data for troubleshooting SAP performance issues
• There are various profiles for viewing the system performance data , that is , by
users , by transactions or by time of the day.
• It is possible to look individually at each dialog instance and compare the system
performance across instances of the SAP system.

August 12, 2024

Using ST03N

Dialog Instance Aggregated over All Instances

August 12, 2024

Expert Mode View – ST03N

August 12, 2024

Transaction Profile View for a Month

August 12, 2024

Linking Transaction Usage to Users

August 12, 2024

 Time Profile

The time profile information provides clues on the behavioral pattern of the system. You can identify load
and activity on the system by looking at the number of steps and the average response time for each
step. Comparatively higher response times indicate that the system is under load
August 12, 2024
User Profile

August 12, 2024

Performance Analysis using ST06
• Apart from ST03N where the performance is measured in terms of dialog steps and
response times , SAP provides ST06 for performance measurement of systems by
looking at the hardware configuration elements.
• These elements include the CPU’s , Memory , Filesystem , Disk and LAN Activity
• ST06 uses the SAP OS Collector , which runs as a process in Unix and as a service
in Windows OS.
• The SAP OS Collector must be active in order for the information to be collected.

August 12, 2024

SAP OS Collector from ST06
The saposcol can be managed from the ST06 transaction

Start the SAP OS

Collector

August 12, 2024

SAP OS Collector from Unix Command Line
The saposcol can be managed from the ST06 transaction

Commands
• saposcol –s can be used to check the
status
• Start Saposcol:
• saposcol [-l] [pf=complete name of
saposcol profile] [-t[level]] [-z]
• Stop saposcol
• saposcol -k [pf=complete name of
saposcol profile] [-t[level]] [-z]

August 12, 2024

Using Detailed Analysis in ST06

August 12, 2024

CPU Usage

Snapshot : Current real time

CPU usage

CPU Usage in Last 24 Hours

August 12, 2024

Memory , Filesystem , Disk Usage

August 12, 2024

Comparison between Recent days

August 12, 2024

LUNCH
BREAK

August 12, 2024

System Monitoring &
Troubleshooting

August 12, 2024

Monitoring Background Jobs – SM37

• Monitoring background jobs is an essential part of performance

monitoring
• The transaction SM37 can be used to check the status of jobs running
in the system
• Background jobs are essentially programs that are run by background
work processes (“B” of DVEBMGS)
• Since the programs may process large volumes of data , background
work processes are allocated a higher memory limit for usage of heap
and shared memory
• Background work processes take up a higher percentage of CPU
utilization , so care must be taken to run high volume background jobs
during a quiet window , that is , a duration where dialog users are not
active in the system.
• Typically in customer environments , such jobs are run during late
evening , night and in early part of the morning.

August 12, 2024

Using SM37

Find jobs by user ID

Find jobs by the ABAP report name

August 12, 2024

Features of SM37

August 12, 2024

Features of SM37
• The job log provides critical information from a troubleshooting perspective.In
the case of cancelled jobs , the abap dump name is provided.

August 12, 2024

ABAP Dumps Analysis using ST22
ABAP Dumps provide detailed information on the nature of the program
failure

August 12, 2024

ABAP Dump Details

August 12, 2024

Troubleshooting ABAP errors using OSS Notes

What is OSS ?
OSS is an abbreviation for Online Support Services
What are OSS Notes ?
SAP OSS Notes are technical solution briefs that provides information
on the cause of an error , its solution and a recommendation on what
technical steps are required to be taken to fix the problem
Where can I access OSS Notes ?
OSS Notes are accessible via SAP Service Market Place Portal with the
URL : https://service.sap.com/notes
How to I gain access to the SAP Service Market Place ?
You can request the SAP Super Administrator of the SAP environment
for a “S” user ID and password with the authorisation for viewing OSS
Notes

August 12, 2024

Sample Usage of OSS Notes

August 12, 2024

Browse through OSS Notes

For the search

criteria , a number of
OSS Notes are
provided.You will need
to spend sometime
going through each
OSS Note to see if its
relevant to solving the
ABAP dump

August 12, 2024

Sample OSS Note

August 12, 2024

System Logs Analysis using SM21

August 12, 2024

Details in SM21

The information is read from the dev_w<x> , current work process log file
This symbol signifies an error of “high priority”
This symbol signifies a “warning” , which is of low priority

August 12, 2024

Troubleshooting & Root Cause Analysis
ROOT CAUSE ANALYSIS
WHEN

• When was the performance issue first noticed ?

• Since when was this problem occuring ?
• Which are the days or hours when the users
experienced poor response times ?

SAP SYSTEM
WHERE

• Is the problem affecting some users at a work

location or is it affecting all users at the work
PERFORMANCE
location ?
•
ISSUE
Is the problem being faced by users in certain
departments but not in others ?
• Are users able to use other network devices in
their work place ?

WHAT

• What is the nature of the problem – ABAP

dumps , poor response times , unable to login ,
long running background jobs etc ?
• What is the error message provided by the SAP
system
• If this problem occurred in the past , what were
the measures taken to fix it

August 12, 2024

Troubleshooting & Root Cause Analysis
ROOT CAUSE ANALYSIS

ANALYSIS FINDINGS,OBSERVATIONS AND SOLUTION

SAP SYSTEM

HOW

PERFORMANCE • The problem occurs on all working days

ISSUE for all users in XYZ department logging
onto D11 dialog instance between 8 AM
and 11 AM

WHY

• The problem occurs due to long running

ST06 background jobs on D11 which begin at
6 AM and run until 12 Noon
ST03N
SM21
SOLUTION
Logs Files
• Bring forward the background jobs from
ST22 starting at 6 AM to 3 AM , as there is no
other impact on the system during the
early morning hours.
TRANSACTIONS FOR ANALYSIS

August 12, 2024

CCMS Monitoring Overview

• CCMS stands for Computing Center Management System

• CCMS is used for central monitoring of the entire SAP landscape
• CCMS brings under a single transaction all the necessary performance
data of SAP systems
• CCMS is started from transaction RZ20
• The system which does the central monitoring is called a “CEN” , i.e.
the central system
• CCMS can also monitor the performance of SAP interfaces , third party
systems connected to SAP as well as non-SAP applications with which
data is exchanged

August 12, 2024

CCMS Monitoring Architecture

August 12, 2024

Details of the architecture
• At the data collection level, small subareas of an SAP system are monitored by special
programs called data collectors. Data collectors can be ABAP, C, or Java programs. There are
several hundred data collectors in ABAP alone. Each data collector checks its subcomponent at
regular intervals and stores the collected monitoring data in the main memory of its host.

• At the data storage level, the area of the main memory that contains the monitoring data from
the data collector is called the monitoring segment. As the main memory data is always
overwritten, it can be permanently copied to database tables. You can then analyze the data
later. The data collection and storage elements must be present on every component that is to
be centrally monitored.

• Caution: Note that every instances of an SAP system has its own monitoring segment in shared
memory. This means that for an SAP system with eight instances, there are eight different
monitoring segments.The number of monitoring segments is determined by the number of
instances. Whether or not several instances run on the same hardware, for instance, is of no
significance here.

• The administration level allows the data from the monitoring segment to be displayed and
evaluated. SAP provides an expert tool, the CCMS Alert Monitor (transaction RZ20) as a
display transaction. The SAP Solution Manager can show the data in a business process-
oriented context. If the system identifies a problem,it can execute a prepared automatic
reaction, such as informing the responsible person. The analysis method then helps you to
investigate the problem.The CCMS Alert Monitoring Infrastructure can be extended. You can
integrate your own components using data collectors that you have written yourself.Third-party
vendors and partners can export the monitoring data from the monitoring segment using various
interfaces.

August 12, 2024

CCMS Monitor Structure
• The CCMS Alert Monitor
(transaction RZ20)
displays the monitoring
data from the monitoring
segment in a tree
structure. The tree
structure allows a clear
display when you are
displaying a large
number of measured
values.
• Any node in the tree is
called a Monitoring Tree
Element (MTE)
• The measured values
that are collected by the
data collectors are
displayed at the lowest
level in the leaves of the
tree. The leaves are
known as monitoring
attributes
• Threshold values can be
stored for a monitoring
attribute. SAP delivers
default threshold values.
However, in order to
customize the monitor as
well as possible for your
system environment, you
should check these
threshold values, and
adjust them if required
August 12, 2024
Alert Monitor – RZ20

August 12, 2024

Using the Alert Monitor – RZ20

August 12, 2024

Sample View of RZ20 MTE Attributes

Attributes

August 12, 2024

Sample View of RZ20 MTE Properties

Properties

August 12, 2024

BREAK

August 12, 2024

Web Enablement &
Communication

August 12, 2024

SAP Web Server Concepts
• The SAP Internet Transaction Server (ITS) is used with Web applications
(IACs) and with SAP GUI for HTML. Depending on the system release and
scenario in question, the functions of the SAP ITS can be implemented by
means of a standalone ITS or using the ITS integrated in the AS ABAP.

• The Internet Communication Manager (ICM) is the process that turns the
conventional ABAP application server into a Web server or Web Client.

• The Internet Communication Framework (ICF) provides an environment for

handling HTTP(S) requests in the ABAP work process using Web applications
such as BSPs.

• The SAP Web dispatcher distributes HTTP(S) requests to a suitable

application server (instance).

August 12, 2024

SAP Internet Transaction Server (ITS)

• Web applications that were developed specifically for SAP ITS are called Internet Application Components
(IACs). These include Employee Self Services (ESS) that are based on SAP R/3 and SAP R/3 Enterprise or the
SAP Online Store. The SAP GUI for HTML also uses the SAP ITS.
• SAP ITS is therefore required for existingWeb applications (in IAC technology) and the SAP GUI for HTML,
regardless of the basis release of the corresponding SAP system.

August 12, 2024

SAP ICM

• SAP Kernel has been extended with the Internet Communication Manager (ICM) process to process HTTP
requests directly from the internet or to send HTTP client requests to the internet
• The ICM process forwards requests to the Internet Communication Framework (ICF), which supports numerous
programming models. This is how the SAP CRM, SAP BW, and SAP XI software components use this
infrastructure. A programming model for such applications are the Business Server Pages (BSPs)

August 12, 2024

Architecture of the ICM Process

August 12, 2024

Internal Structure of the ICM Process

August 12, 2024

ICM Monitoring using SMICM Transaction
• Transaction SMICM can be used to start and stop the ICM process
• The http trace and logs can be viewed using SMICM

August 12, 2024

Internet Communication Framework
• The Internet Communication Framework (ICF) provides a way for different
systems to communicate with each other over the Internet using standard
protocols (such as HTTP and SMTP). No additional programming libraries
(for AS ABAP) are required from SAP. However, for the HTTPS protocol,
the SAP Cryptographic Library (SAPCRYPTOLIB) must be installed and
configured (see SAP Note 510007). Your system platform only must be
configured to be Internet capable.This scenario allows for the most
flexible setup of the overall communication requirements.

• The ICF allows a response to a request to be generated using an

application. An HTTP request is sent from a client (such as a Web
browser) to the server. It is then forwarded to an application by the ICF.
Here, data is collected and sent back to the client as a response by the
ICF. The response data is then displayed in the browser.

August 12, 2024

HTTPS Request Processing
An HTTP(S) request is processed in the following steps:

1. The request is sent from the user's Web browser to the ICM using the HTTP
2. protocol. The ICM uses the requested URL to determine whether the application called is
implemented in the ABAP or Java stack of the SAP NetWeaver Application server.This example
uses an ABAP application that must be processed by a dialog work process.
3. The ICM stores the data received in a memory pipe (in the shared memory) and informs the ABAP
dispatcher.
4. The ABAP dispatcher adds the ICM request to the dispatcher queue, creates a new context (if there
is no context that is processed statefully), and selects a work process for processing.
5. The task handler in the work process reads the data from the memory pipe and transfers it to the ICF
controller, which is implemented using function module HTTP_DISPATCH_REQUEST.
6. The ICF controller transfers the request to the ICF manager, which is implemented by the ABAP
class CL_HTTP_SERVER. The ICF controller creates a server control block and fills it with the HTTP
request data that it requested from the ICM.
7. The client is then authenticated, whereby several logon options are available.
8. The HTTP request handler determined previously is called (this can process the request data, call
further applications, access the response object, and so on). When the HTTP request handler is
ready, it returns control to the ICF controller.
9. The task handler writes the response back to the memory pipe (response serialization) and signals to
the ICM that it has finished processing the request.
10. The ICM returns the response to the Web browser.

August 12, 2024

Activating Web Services using SICF
Specific web services that will be executed by the ICF can be activated and managed in SICF

August 12, 2024

Calling Web Service using SICF

• Please NOTE the structure of the URL. The port number for calling the
ICM is always 80xx for an AS ABAP WAS , where xx is the instance
number
• The fully qualified host name must be maintained in Instance profile
parameters , i.e, icm/host_name_full

August 12, 2024

SAP Communication & Integration Technologies
RFC Fundamentals

• Remote Function Calls have been used for many years as the technical interface with which SAP and
non-SAP systems are usually connected. It is irrelevant whether data exchange is synchronous or
asynchronous, periodic or aperiodic, or transactional. Many conceivable variants are supported.

• A Remote Function Call(RFC) is the call of a function module that is

running in a different system to the calling program. You can call a function
module in the same system as an RFC too. However, RFCs are normally
used when the calling and called function modules are running in different
systems.
• In the SAP system, the RFC interface system provides this function. The
RFC interface system allows function calls between two SAP systems or
between an SAP system and an external (non-SAP) system.
• RFC is an SAP interface protocol that is based on the Common
Programming Interface for Communication (CPI-C) and allows cross-host
communication between programs. This enables external applications to
call ABAP functions and SAP systems to contact (RFC-enabled) external
applications.RFC means that ABAP programmers do not have to write their
own communication routines. For an RFC call, the RFC interface converts
all parameter data to the format required in the remote system calls the
communication routines that are required to communicate with the remote
system handles errors that occur during the communication.
• The RFC interface is easy for the ABAP programmer to use. The
processing steps for calling external programs are integrated into the CALL
FUNCTION statement.

August 12, 2024

Managing RFC Connections using SM59

August 12, 2024

 RFC Usage Variants
Synchronous RFC (sRFC)
• For communication between different systems and between SAP Web AS and SAP GUI
Asynchronous RFC (aRFC)
• For communication between different systems and for parallel processing of selected tasks.
Transactional RFC (tRFC)
• A special form of asynchronous RFC. Transactional RFC ensures transaction-like processing of
processing steps that were originally autonomous.
Queue(d) RFC (qRFC)
• Queued RFC is an extension of tRFC. It also ensures that individual steps are processed in sequence.

• RFC is a superordinate term for various implementation variants. sRFC is the synchronous call of
function modules. This means that the client waits until the server has completed its processing.
• Within an SAP system, an RFC can also be executed asynchronously in another work process. This
variant is called aRFC.
• There is also tRFC, the transactional Remote Function Call. Transactional RFC is asynchronous and
ensures that data that is sent more than once due to network problems can be recognized at the server
side, by assigning a Transaction Identifier (TID). This allows you to prevent data being processed more
than once, leading to erroneous information in the application. Due to the asynchronous
processing,however, parameters can only be transferred from the client to the server in this case
returning information or status information directly is not possible.
• qRFC with Send Queue is an extension of tRFC. It creates a layer between applications and the tRFC
and only allows the tRFC to transfer a Logical Unit of Work (LUW) to the target server when its
predecessors are no longer in the associated wait queues. After a qRFC LUW is executed, the qRFC
manager automatically processes the next waiting qRFC LUW in accordance with theAugust sequence
12, 2024 in the
wait queue.
BREAKOUT
SESSION

August 12, 2024

Exercise 1

EXERCISE

• Login into the system with the userid/password provided by your

instructor
• Study the Performance of the SAP system for a) Last week b) Last
Month using ST03N
• Using the data collected from ST03N , compare the number of dialog
steps , users and programs that generated the highest response times
• For the set of data chosen from ST03N , compare the system
performance using ST06
• Identify peak load on the system and analyze for potential causes
• Use SM21 , ST22 and SM37 to determine root cause
• Check the memory parameters in ST02 and check the profile
parameters for each of the buffers
• Adjust abap/heap_limit value by 10 MB using RZ10

August 12, 2024

Exercise 2

EXERCISE

• Go to transaction SICF
• Check the options available for activating/deactivating the nodes
• Launch the web service mentioned in the course
• Check the structure of the URL and identify the port
• Go to SMICM transaction
• Navigate to Goto -> Display Connections , Check the details of the
HTTP connections established
• From Administration , Navigate to ICM -> Exit(Soft) -> Global
• Return to SICF , and try and launch the webservice. Check the error
message received
• Return to SMICM , and Start the ICM again

August 12, 2024

Q&A Session

August 12, 2024