Comprehensive Sap Basis Training Day 4

8/13/2019 Comprehensive Sap Basis Training Day 4

1/139

IBM Global Business Services

Copyright IBM Corporation 2009

Module 12: Solution Manager Basics

Module 13: SAP Support Package

3 Module 14: SAP System Upgrade

4 Module 15: ALE EDI RFC

5 Module 16: SAP Memory Management

Day 4: Module map

SAP Basis FastTrak WAS 7001


2/139



Course Title

Solution Manager BasicsModule 12


3/139



Module 12: Objectives

On completion of this module, you should be

able to:

Define and explain the basics of solution

manager Explain the system landscape directory



4/139


Copyright IBM Corporation 2009SAP Basis FastTrak WAS 700

Module 12: Agenda

Topic 1: Solution manager basics

Topic 2: System landscape directory

4


5/139



Basics of solution manager

Increase the reliability of SAP system

Reduce the total cost of ownership of SAP

solution

Increase the return on investment providedby SAP solution

Included in the maintenance charges for

SAP systems



6/139



What can the SAP solution manager do

Source: SAP


7/139



Functions of the SAP solution manager

Preventive services:

EarlyWatch Alert, GoingLive Check & Functional

Upgrade check

Continuous Improvement Services:

SolMan Review Services (SMR) & SolMan Optimization Services

Best Practices for SAP application:

Documents & services that are based on SAPs experience from Production

customer installations Application & System Monitoring:

SAP Service Desk:

SAP Remote Support:

Safer remote access using Internet connectionsSAP Basis FastTrak WAS 7007


8/139



The system landscape directory (SLD)

Source: SAP


9/139



To enable SAP systems to automatically send their system data to the SLD, we mustconfigure data suppliers in these systems. For ABAP-based systems, this can bedone using transaction RZ70, which uses an RFC connection to the SLD bridge.Java-based programs can use an HTTP connection to transfer system information tothe SLD server. The Visual Administrator is used for configuration purposes

Connecting ABAP-based SAP systems to the SLD

Source: SAP


10/139



The System Landscape Directory has a user interface (UI) that can be

accessed using the URL http://:/sld


The Web UI of the SLD

Source: SAP


11/139



Questions and Answers



12/139



Module 12:Summary

Having completed this module, you should now

be able to:

Understand the solution Manager basics

Explain the system landscape directory



13/139



SAP Support PackageModule 13


14/139





able to:

Put in your own words the concepts on SAP

support packages Differentiate between SPAM and SAINT

Explain SAP support package

implementation process

Recall the SPAM and SAINT update

Summarize the overview of JAVA support

package manager

Describe the SAP enhancement packages



15/139



Module 13: Agenda

Topic 1: Concepts on SAP support packages

Topic 2: Difference between SPAM and SAINT

Topic 3: SAP support package implementation

process

Topic 4: SPAM and SAINT update

Topic 5: Overview of JAVA support package

manager

Topic 6: SAP enhancement packages

15


16/139



SAP support packages

An SAP System consists of different software layers, also called

software components.

Reason for applying Support Packages to your system is to make

correction to objects and functions. During the process of applyingSupport Packages, the systems checks the objects that are affected by

the Support Packages.

The SAP System should always be kept at the current correction

status so that errors in the standard release are preventively removed.

Its very important to understand the structure of SAP system before

SAP support packages as users will be able to understand and

appreciate different types of SAP support packages.



17/139



PLUGIN

SAP ECC (R/3)

SAP_ABA

SAP_BASISSAP_BW

PLUG IN

SAP_CRM

SAP_ABA

SAP_BASISSAP_BW

SAP_APPL SAP_HRSAP_CRM

Industrysolution

SAP ECC

Enterprise extensionEA*

Many SAP SoftwareComponents, such as SAP

ECC, CRM and SCM use the

SAP WEB AS

SAP Web AS ABAP

Import supportpackages

Structure of SAP system


18/139



What is an SAP support package?

An SAP Support Package is a quantity

of corrected or new SAP objects. SAP

Support Packages are required to

correct errors in various components.

This is done by replacing erroneous

objects with corrected versions of these

objects.

Each software component has a

separate sequence of SAP SupportPackages. Different software

components have been explained in

previous slide.


SAP support package explained

18


19/139



SAINT

SAINT

SAP Add-On Installation Tool was developed to enable users to install and

upgrade Add-On directly from their standard SAP system. Prior to installation,

numerous import conditions are checked to ensure that only add-ons that fit the

available SAP system can be installed.

Add-On is the collective term for all bundles of functions that do not belong to the

standard SAP system, and which can be subsequently installed, such as Industry

Solutions, Plug-Ins and so on.



20/139



SPAM

SPAM

Support Package Manager (transaction SPAM) provides you with an easy and

effective way of importing SAP Support Packages into your system.

Support Packages are available in SAP Support Portal, underwww.service.SAP.com/patches or on collection CDs. Support Package Manager

runs at the SAP system level. Knowledge of the operating system is therefore not

required for handling this tool.

You can use Support Package Manager only with SAP GUI for Java and SAP GUI

for Windows.

Choose SAP Menu Utilities Maintenance Support PackageManager



21/139



SPAM prerequisites

The required SAP Support Packages must be available.

There must be enough space in the file system.

The import should be performed during a time of low operation.

The newest SPAM/SAINT update is required.

TMS/CTS must be configured.

No aborted Support Packages in the system.

Client 000 for importing; in all other clients only a display function is available.

Use a user that has system authorizations for transaction SPAM.

Only the system administrator should have authorization to download and

import SAP Support Packages. The same applies for confirming successfully

imported SAP Support Packages and resetting the status of an SAP Support

Package.


G S


22/139



SAP Service Marketplace

Load Support Packageto/from front end (GUI)

CD

ApplServer

SAP System

Loading SAP support packages

22

Request

Load

Settings

Queue

Import

Logs

Confirm

IBM Gl b l B i S i


23/139



General description of import process

All activities executed by the import tool run in what are known as phases.

These phases are in turn combined into modules.

The import process is divided into the following modules:

Preparation, Import1, Import2 and Clean Up

These modules have the following properties:

They can be executed individually, so one can start them as a background process.

One can control the start time of the module.


IBM Gl b l B i S i


24/139



SPAM: Settings

24

Source: SAP

Request

Load

Settings

Queue

Import

Logs

Confirm

IBM Gl b l B i S i


25/139



The standard scenario is used to import

SAP Support Packages completely; all

steps are performed.

One can use the test scenario to

determine before the actual import of the

SAP Support Package whether a

modification adjustment is required or

whether conflicts occur that must be

removed before the import. No data andobjects are imported during the test

scenario.


Importing SAP support package queue

25

IBM Global B siness Ser ices


26/139



Import queue

26

Source: SAP

Request

Load

Settings

Queue

Import

Logs

Confirm



27/139



ABAP / screen generation

This option defines whether the programs and screens delivered with the SAP

Support Packages should be generated during the import.

There are many options

Never Execute : No automatic generation, the programs and screens aregenerated the first time they are called.

Always Execute: Screens and programs are always generated. Note that

generation can last a very long time, and that this may cause errors.

According to the SAP Instruction: Programs and screens are only generated if

the generation during the import of these SAP Support Packages is allowed bySAP.




28/139



Import queue rules

SAP support packages for a selected component are placed in the queue

according to their sequence.

If SAP support packages in the queue are related to SAP support packages for

another software component (predecessor relationship, crt required), the extra

SAP support packages are added to the queue until all predecessor

relationships are included.




29/139



SPAM

ModificationAdjustment

Why?To retain customer

modifications. It works inexactly the same was as

during an upgrade

What must be adjusted?

Fields of the SAP standardtable and the customerfields.

SPAM - modification adjustment

29



30/139



SPAM - modification adjustment (continued)


Customer

SAP standard

Customer

SAP standard

Modifying add-on

Without a modifyingadd-on

With a modifyingadd-on

Support package Manual adjustmentsnecessary

30

Request

Load

Settings

Queue

Import

Logs

Confirm



31/139



Action log Import log


SAP support package managerlogs

Logs

31



32/139



SPAM: Checking logs and confirming a queue

32

Request

Load

Settings

Queue

Import

Logs

Confirm



33/139



1 3

2 4


Uptime Downtime Uptime

Sources tobe imported

Inactivesources

Activesources

Inactivesources

Activesources

Obsoletesources

Activesources

Initial

status

Inactiveimport

Switch off thereport sources

Final status

Inactive import

33



34/139



SPAM/SAINT Update

SPAM / SAINT update

34

How are theydifferent?

How importantare they?

Why?



35/139



Importing a SPAM / SAINT update

35

Request

Load

Perform

Update

Logs



36/139



Java support package manager (JSPM)

Usability

Offers a simple and intuitive graphical user interface (GUI)

Automatically detects and offers you only components that upgrade deployed

components Deployed Component Overview

Displays support package level information

Support Package Level AdministrationChecks whether a new s/w

component version may correctly upgrade an existing software component

version

Deployment Component Level Administration

Checks deployment dependencies between development components




37/139

G oba us ess Se ces


Java support package manager (JSPM) (continued)

Update of kernel binaries, internet graphics server (IGS) and JSPM

Deployment

Allow to apply single support packages

Allow to deploy SAP and third party s/w components

Informs if restarting of AS java is necessary during the deployment process

Allows you to restart the deployment of support packages




38/139


Apply java support packages using JSPM




39/139


Apply java support packages using JSPM (continued)



40/139


Apply kernel patch using JSPM



41/139


Apply kernel patch using JSPM (continued)



42/139


SAP enhancement packages (EHP)

What are EHPs?

A new software delivery strategy that allows to add innovations on top of SAP

ERP 6.0 without the need for fully upgrading current release

Optionally installed and activated software innovations for SAP ERP 6.0

SAP enhancement packages for SAP ERP include functional enhancements,

industry specific enhancements, and UI simplifications

Cumulative in nature; current enhancement packages contain the entire

content of earlier packages

Enhancement packages are not support packages




43/139


Characteristics of SAP enhancement packages (EHP)

Characteristics

Selective installation of software components

Each SAP EHP contains new versions of existing software components,

which do not constitute an innovation on their own. But with SAP EHP,we only update software components that are related to the functionality

we want to use

After the installation no UI or process changes take place

Selective activation of new functionality

New functionality must be explicitly switched on to become active in the system

Changes are predictable, with changes only in the activated areasno side

effects




44/139






45/139


Module 12: Summary


be able to:


support packages

Differentiate between SPAM and SAINT

Explain SAP support package implementation

process

Recall the SPAM and SAINT update

Summarize the overview of JAVA support

package manager

Describe the SAP enhancement packages




46/139


Module 22: SAP support package

Module 23: SAP system upgrade


Day 8: Module map




47/139


SAP System UpgradeModule 13



48/139




able to:

Describe the planning and preparation of

SAP system upgrade

Categorize several tools available in

performing system upgrade

Explain modification adjustment




49/139


Module 13: Agenda

Topic 1: Planning and preparation of SAP system

upgrade

Topic 2: Tools available for system upgrade

Topic 3: Modification adjustment

49



50/139


Planning and performing an SAP system upgrade

50

Source: SAP



51/139


SAP system upgrade: Factors

51

Factors decidingupgrade



52/139


Plan Prepare PerformPost UpgradeActivities

Plan Prod start fornew R/3 release

Upgrade planning


Plan Prepare PerformPost UpgradeActivities

Plan Prod start fornew R/3 release

PREPARE ScriptOS Upgrade?Hardware

Upgrade?DB CheckModifications

PERFORMTechnical UpgradeDB UpgradeR/3 UpgradeAdjust Modifications

Post UpgradeBackupDB Clean upNew AuthorizationsR/3 Release and upgradeCustomizingUser upgradation tests

Perform Tech upgradeDB upgradeR/3 upgradeBind Adjustments

Post UpgradeBackupDB Clean upImport new AuthorizationsImport R/3 Release and upgrade Customizing

SchedulePlan system downtime



53/139


PlanGather systemrequirements

Start

Check

Perform upgradeStart post upgradeactivities

Steps during upgrade

53



54/139


Sgen

Icnv

Prepare

Upgrade assistant

Upgrade monitor

Upgrade tools

54



55/139


PREPARE has to run prior to the SAP System upgrade.

PREPARE performs checks on the source release.

PREPARE collects SAP Support Packages and Add-Ons for binding them to

the SAP System upgrade.

PREPARE imports tools in the source SAP System that are needed for the

SAP System upgrade.


PREPARE

55



56/139


SGEN: SAP load generator

56



57/139


Upgrade Assistant: With this tool the SAP

System upgrade process runs independently

from a certain front-end.

Upgrade Monitor: the Upgrade Monitor lets you

monitor the upgrade and helps you recognize

any processes that have stopped.


Upgrade assistant and upgrade monitor

57



58/139


ICNV: incremental conversion

58



59/139


Phases of an SAP system upgrade

59

Source: SAP



60/139


Modification adjustment

60

Source: SAP



61/139






62/139


Module 13: Summary


be able to:

Describe the planning and preparation of SAP

system upgrade

Categorize several tools available in

performing system upgrade

Explain modification adjustment




63/139


Module 22: SAP support package

Module 23: SAP system upgrade


Day 8: Module map




64/139


ALE EDI RFCModule 14



65/139



On completion of this module, you should be able

to:

Put in your own words the concept of the

application link enabling (ALE)

Put in your own words the concept of the

electronic data interchange (EDI)

Explain remote function calls (RFC)

Describe RFC maintenance

Identify the types of RFC

Summarize the setting up and testing of remote

connection




66/139


Module 14: Agenda

Topic 1: Concept of the application link

enabling (ALE)

Topic 2: Concept of the electronic data

interchange (EDI)

Topic 3: Remote function calls (RFC)

Topic 4: RFC maintenance

Topic 5: Types of RFC

Topic 6: Setting and testing of remote

connection

66



67/139


Distributed application


MM-

PUR

PP

MM-

INV

PS

MM-

INV

SD-

SHP

GL

CO

SD-

ORD

67



68/139


Plant Maintenance

Inventory Management

Internal Sales, Shipping

and Billing Local Purchasing

PP

Accounting

Central Purchasing

Reference System for

master data and tax data

Central controlling

Inventory

Purchasing

Sales

Sales, Shipping and Billing

Purchasing of trading goods

Inventory management

Local controlling

Distributed businessprocess

ALE

ALE

68



69/139


1. Identifybusiness

processes andobjects involved.

2. Identify theinformation to be

transmitted. 3. Specify theformat for the

data to betransferred.

4. Decide on the

transfertechnology to beused. 5. Decide on the

transfer type.

6. Specify thedestination for

the data transfer.

ALE: Requirements

ALE

69



70/139


BAPI

IDOC

Transporttypes

Important terms

70



71/139


EDI

Source: SAP

71



72/139


EDI elements




73/139


What is RFC?

SAP systemSAP /non-

SAP system

..talks to..

73



74/139


ABAP program

RFC interface

External program

RFC interface

RFC interface

ABAP program

SAP system

External system

SAP system (can alsobe SAP R/2)

RFC connection possibilities

74



75/139


CALLING SYSTEM CALLED SYSTEM

RFC interface RFC interface

Remote function call in detail

75



76/139


RFC destinations

Source: SAP

76



77/139


Types of RFC

RFC

SynchronousRFC

TransactionalRFC

Queued RFCAsynchronous

RFC

77



78/139


Setting up a remote connection

78



79/139


Testing an RFC connection

79



80/139






81/139


Module 14: Summary


be able to:

Understand the application link enabling

(ALE) - concepts

Understand electronic data interchange (EDI)

- concepts

Explain what is remote function calls (RFC)?

Describe RFC maintenance

Identify the types of RFC

Summarize the setting up and testing of

remote connection




82/139


SAP Memory ManagementModule 15



83/139



On completion of this module, you should be able to:

Describe the architecture of SAP memory

management


memory Identify the different types of memory

Explain SAP memory allocation process

Differentiate between roll-in and roll-out concepts

Analyze PRIV mode

Describe the profile parameters of memory

management Visualize the implementation on SAP extended

memory

Interpret memory usage for SAP AS JAVA

Put in your own words the details on JVM




84/139


Module 15: Agenda

Topic 1: Architecture of SAP memory management

Topic 2: Concepts on SAP memory

Topic 3: Types of memory

Topic 4: SAP memory allocation process

Topic 5: Difference between roll-in and roll-out

concepts

Topic 6: PRIV mode

Topic 7: Profile parameters of memory management

Topic 8: Implementation on SAP extended memory

Topic 9:Interpret memory usage for SAP AS JAVA

Topic 10: JVM



85/139


Memory

Memory refers to the device whose contents are dynamic but are accessible

at extremely high speed.


OS PagingFile/Swap

Space

Physical Memory

Availability of physical

memory is limited because

of the maximum space that

can be addressed by the

Operating System.

Virtual memory can

enhance the address space

to as high as twice the

main memory.

When we speak of memory at SAP level, it refers to virtual memory.



86/139


Memory areas


Local memory

Shared memory

Work

ProcessWork

ProcessWork

ProcessWorkProcess

All work processes

Of one instance

Virtual memory

Shared memory and local memory



87/139


SAP memory management system

Source: SAP



88/139


SAP memory management system (continued)

Source: SAP



89/139


Memory management: Basic concepts

Virtual memory

Address space

Memory allocation

Local process memory

Shared Memory




90/139


Local memory


Server

Virtual memory

Shared memory Local memory

Local work process memory is for:

ABAP load

Data, stack

Buffer for database transfer

Local roll area

Local paging area

Allocated at instance start

Work

Process

Work

Process

Work

Process

Local

Memory

Local

MemoryLocal

Memory

How SAP memory is used in principle

Local memory is

Associated with

Individual work processes



91/139


Shared memory


SAP buffers in shared memory

Server

Virtual memory


SAP buffers contain global objectsFor all users and work processes,

Such as programs and buffered

Table content

Work

Process

Work

Process

Work

Process

1:n

SapBuffers

Shared memory

Is associated with all

Processes of one instance



92/139


Extended memory


Server

Virtual Memory

Shared Memory Local Memory

Extended memoryContains objects/data associated

With unfinished transactions

Extended

memory

Work

Process

Work

Process

Work

Process

1:n

Extended Memory in Shared Memory in Virtual Memory



93/139


Heap memory


Server

Virtual memory


Heap memory

Contains the same type of data as the

Extended memory

Is used when extended memory is full

Is allocated and released on demand

Allocated at instance start

Work

Process

Work

Process

Work

Process

Local

Memory

Local

Memory

Local

Memory

Heap memory

(Temporary)

When memory areas are allocated

Allocated on demand



94/139


Roll memory


Roll buffers in shared memory

Server

Virtual memory


Roll memory contains initial part of user contexts

Work

Process

Work

Process

Work

Process

1:n

RollBuffers

Sap

Roll file



95/139


Paged Memory


Server

Virtual Memory


SAP paging memory contains:

ABAP objects such as extracts

Context-independent objects such as exports

WorkProcess

WorkProcess

WorkProcess

1:n

SAP pagingbuffer

SAP

pagingfile



96/139


Server

Virtual Memory


Work

Process

Work

Process

Work

Process

1:n

Roll

buffers

SAP

roll file

Heap Memory

(temporary)

Local

MemoryLocal

MemoryLocal

Memory

SAP

pagingfile

Extended

memory

SAP buffers

(programs, tables)

1:1

SAP

Paging buffer

SAP memory areas: Overview



97/139


Some important concepts

User context

Work process

Virtual address space of a

work process




98/139


SAP user SAP user SAP user SAP user

1 2 3 4

Data

For user1Data

For user 3

Dialog

Work

Process1

Dialog

Work

Process2

Work processes working on user requests

SAP memory allocation


99/139



100/139


Dialog

Work

Process1

Dialog

Work

Process2

Data

For user1

Data

For user3

Copy

Exit

Roll out


1 2 3 4



101/139


Dialog

Work

Process1

Dialog

Work

Process2

Data

For user 3

Data

For user1

Data

For user 4

Copy

Roll in


1 2 3 4



102/139


Dialog

Work

Process1

Roll

area

Paging

area

User context objects such as:

-Authorizations

-Set/Get parameters

(-Internal tables)

(-Report lists)

Memory for specific

ABAP commands

Roll and paging area of the dialog work process


1 2 3 4



103/139


Dialog

Work

Process1

Rollarea

Paging

area

Rollarea

Paging

area

Dialog

Work

Process2

Roll

buffer

Paging

buffer

Paging file

Roll file

Copy

Roll buffer / roll file and page buffer/page file


1 2 3 4



104/139


Rollarea

Paging

area

DialogWork

Process1

Rollarea

Paging

area

Dialog

Work

Process2

swap

Mapping

Extended

Memory

(shared)

Mapping used for accessing data in extended memory


1 2 3 4



105/139


Paging

area

Dialog

Work

Process2

Extended

Memory

(shared)

1st:A defined initial part of

the roll area is used

Rolearea

Memory allocation sequence 1


1 2 3 4


106/139



107/139


Roll

Paging

area

Dialog

Work

Process2

Extended

Memory

(shared)

the extended memory

is full or

area



1 2 3 4



108/139


Roll

Paging

area

Dialog

Work

Process2

Extended

Memory

(shared)

until the user quota is

reached

area



1 2 3 4



109/139


Rollarea

Paging

area

Dialog

Work

Process2

Extended

Memory

(shared)

The rest of the WP-local

roll area is used3rd:

Paging



1 2 3 4



110/139


Roll

area

Heap

memory

Dialog

Work

Process2

Extended

Memory

(shared)

The system is forced to

use local heap memory4th:

Paging

area



1 2 3 4



111/139


Roll

Area

Heap

Memory

(Local)

Dialog

Work

Process2

Extended

Memory

(Shared)

Paging

AreaPRIV

mode

Roll

Area

Paging

Area

Dialog

Work

Process1

PRIV mode 1


1 2 3 4



112/139


Roll

area

Heap

Memory

Dialog

Work

Process2

Extended

Memory

(shared)

Paging

area

If Heap memory is in use, furthersteps of the current transaction wont

be dispatched to other Dialog work

processes

Roll

area

Paging

area

Dialog

Work

Process1

PRIV mode 2


1 2 3 4


Memory allocation sequence for dialog work processes in


113/139


Roll

Memory

Up to

Ztta/roll_first

Extended memory

Up to

Ztta/roll_extension

Or EM exhausted

Roll memory

Remainder of

Ztta/roll_area

Heap memory

Upto abap/heap area_dia

Or HM exhausted

1 2 3 4

Local

memory

Shared

memory

Memory Allocation sequence for Dialog work processes

Memory allocation sequence for dialog work processes in

detail, avoiding PRIV mode



114/139


Memory allocation sequence for all work process types


Roll

Memory

Up to

Ztta/roll_first

Extended memory

Upto

Ztta/roll_extension

Or EM exhausted

Roll memory

Remainder of

Ztta/roll_area

Heap memory

Upto abap/heap_area_dia

Or HM exhausted

1 2 3

Local

memory

Shared

memory

Allocationsequence for

non-dialog

Wpes on

Windows and

for dialog Wpes

on all platforms

Roll

Memory

Up to

Ztta/roll_first

Extended memory

Upto

Ztta/roll_extension

Or EM exhausted

Heap memory

Upto abap/heap_area_dia

Or HM exhausted

Allocationsequence fornon-dialogWpes on

All platformsexceptWindows

Time



115/139


Rollarea

Paging

Work

Process1

Roll

areaPaging

areaWork

Process2

swap

Extended

Memory

(shared)

Heap

Memoryarea

Heap memory isreleased by the work

process after use

Freeing heap memory


1 2 3 4



116/139


Freeing heap memory (continued)


Rollarea

Work

Process1

Roll

areaPaging

areaWork

Process2

swap

Extended

Memory

(shared)

Heap

Memory

But on UNIX OSsallocated swap space

in not freed by the

operating system!Paging

area


1 2 3 4



117/139


Rollarea

WorkProcess

1

Roll

areaPaging

areaWork

Process2

swap

Extended

Memory

(shared)

area

When the limit set inabap/heaplimit is

reached, the work

process is flagged for

automatic restart.Paging

Freeing heap memory


1 2 3 4



118/139


Profile parameter of memory management


Roll file

Roll

area

Roll

buffer

Heap

Memory

DIA

rdisp/roll_SHM

rdisp/roll_SMAXFS

ztta/roll_extension

Extended

Memory

(shared)

ztta/roll_first

ztta/roll_area

abap/heap_area_dia

abap/heap_area_total

em/initial_size_MB



119/139


Configuring parameters

ztta/roll_area

rdisp/ROLL_SHM

rdisp/ROLL_MAXFS

abap/heap_area_dia

abap/heap_area_nondia

abap/heaplimit

abap/heap_area_total




120/139


ztta/roll_area: Roll area

Source: SAP



121/139


Configuring parameters (continued)

rdisp/ROLL_SHM

Determines Roll Buffer Size.

rdisp/ROLL_MAXFS

Determines Maximum Roll File Size




122/139


abap/heap_area_dia

Source: SAP



123/139


abap/heap_area_nondia

Source: SAP



124/139


abap/heaplimit: Work process restart

Source: SAP



125/139


abap/heap_area_total: Total quota for heap memory


Source: SAP



126/139


Controlling memory management

abap/heaplimit: Work Process Restart

ztta/roll_extension: Limit for Extended Memory

ztta/roll_extension_dia: EM Quota for Dialog Work Processes

ztta/roll_extension_nondia: EM Quota for Non-Dialog Work Processes

abap/heap_area_dia: Heap Memory Limit for Dialog Work Processes

abap/heap_area_nondia: Heap Memory Limit for Non-Dialog Work Processes

abap/heap_area_total: Total Quota for Heap Memory

ztta/roll_area: Size of Roll Area Roll Area

ztta/roll_first: Size of the Initial Allocation from the Roll Area




127/139


ztta/roll_extension: Extended memory limit

Source: SAP



128/139


ztta/roll_first: Initial allocation size from the roll area

Source: SAP



129/139


Memory management limitations

abap/heap_area_total: Heap Memory Limit

em/initial_size_MB: Extended Memory Pool Size

rdisp/ROLL_SHM: Roll Buffer Size

rdisp/ROLL_MAXFS: Maximum Roll File Size

rdisp/PG_SHM: Size of the Paging Buffer

rdisp/PG_MAXFS: Maximum Size of SAP Paging File

em/blocksize_KB: Segment Size for the Extended Memory

em/stat_log_size_MB: Statistics - User Context Size

em/stat_log_timeout: Statistics - User Context Size




130/139


Roll

MemoryExtended memory Heap Memory

User context

Local

WP

SAP

buffers

Userindependent

data

SAP

Work

process

Address space (1.7 to 3.8 GB)

em/initial_size_MB abap/heap_area_(non)dia

Localmemory

Shared

memory

Address space restriction due to Unix 32 bit architecture

32- bit Restriction on UNIX OS

Implementation of SAP extended memory


E d d 32 bi i d OS


131/139


em/initial_size_MB

Roll

Memory Extended memory Heap MemoryLocalWP

SAP

buffers

SAP

Work

process

Address space (approx 1.8 GB)

em/address_space_MB abap/heap_area_(non)dia

Localmemory

Shared

memory

Extended memory (initial total)

Parameter em/address_space_MB determines the amount of

extended memory per work process

Parameter em/initial_size_MB can be very large

Extended memory on 32-bit windows OS


S t / t b ff


132/139


Setups / tune buffers summery



S t / t b ff ( ti d)


133/139


Setups / tune buffers summery (continued)



M f SAP W b AS J


134/139


Memory usage for SAP Web AS Java


How the Java Virtual Machine handles memory resources


Details of the Java VM memory management (Java hotspot

VM b SUN)


135/139


VM by SUN)


-Xmx (Max Heap Size)


Si i th t f th J i t l hi


136/139


Sizing the memory management of the Java virtual machine


Memory Area Initial Size Max Size

Young generation -XX:NewSize -XX:MaxNewSize

Tenured generation See below See below

Permanent generation -XX:PermSize -XX:MaxPermSize


Setting the memor management


137/139


Setting the memory management

Source: SAP


138/139


Module 15: Summary


139/139

Module 15: Summary

Having completed this module, you should now be able

to:

Describe the architecture of SAP memory

management

Put in your own words the concepts on SAP memory

Identify the different types of memory

Explain SAP memory allocation process

Differentiate between roll-in and roll-out concepts

Analyze PRIV mode

Describe the profile parameters of memory

management Visualize the implementation on SAP extended

memory