Comprehensive Sap Basis Training Day 4

IBM Global Business Services
Day 4: Module map

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
SAP Basis FastTrak WAS 700
Copyright IBM Corporation 2009
Course Title
Solution Manager Basics

Module 12
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
Module 12: Agenda

Topic 1: Solution manager basics Topic 2: System landscape directory
Basics of solution manager

Increase the reliability of SAP system Reduce the total cost of ownership of SAP solution Increase the return on investment provided by SAP solution Included in the maintenance charges for SAP systems
What can the SAP solution manager do
Source: SAP
6 SAP Basis FastTrak WAS 700
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 connections
The system landscape directory (SLD)
Source: SAP
Connecting ABAP-based SAP systems to the SLD
Source: SAP
To enable SAP systems to automatically send their system data to the SLD, we must configure data suppliers in these systems. For ABAP-based systems, this can be done using transaction RZ70, which uses an RFC connection to the SLD bridge. Java-based programs can use an HTTP connection to transfer system information to the SLD server. The Visual Administrator is used for configuration purposes
The Web UI of the SLD

The System Landscape Directory has a user interface (UI) that can be accessed using the URL http://<SLD-Host>:<Port>/sld
Source: SAP
10
Questions and Answers
11
Module 12:Summary
Having completed this module, you should now be able to: Understand the solution Manager basics Explain the system landscape directory
12
SAP Support Package

Module 13
On completion of this module, you should be 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
14
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
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 applying Support 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.
16
Structure of SAP system

Import support packages
SAP ECC Industry Enterprise extension solution EA* PLUGIN
Many SAP Software Components, such as SAP ECC, CRM and SCM use the SAP WEB AS
PLUG IN SAP_CRM
SAP_CRM SAP_ABA
SAP ECC (R/3)

SAP_APPL SAP_ABA SAP_HR
SAP_BW
SAP_BASIS
SAP_BASIS
SAP_BW
SAP Web AS ABAP

SAP support package explained

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 Support Packages. Different software components have been explained in previous slide.
18
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.
19
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, under www.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 Manager Utilities Maintenance Support Package
20
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.
Loading SAP support packages
Request
SAP Service Marketplace
Load
Settings
Load Support Package to/from front end (GUI)
ApplServer
Queue
Import
Logs
CD
SAP System
Confirm
22
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.
23
SPAM: Settings
Request
Load
Settings
Queue
Import
Logs
Confirm
Source: SAP
Importing SAP support package queue
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 and objects are imported during the test scenario.
25
Import queue
Request
Load
Settings
Queue
Import
Logs
Confirm
Source: SAP
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 are generated 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 by SAP.
27
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.
28
SPAM - modification adjustment
What must be adjusted? Fields of the SAP standard table and the customer fields.
Why? To retain customer modifications. It works in exactly the same was as during an upgrade
SPAM Modification Adjustment
29
SPAM - modification adjustment (continued)
Without a modifying add-on
Customer
Request
Load
SAP standard Support package
Settings
Manual adjustments necessary

Customer
Queue
Import
With a modifying add-on

SAP standard
30
Modifying add-on
Logs
Confirm
Logs
Action log
Import log
SAP support package manager logs
31
SPAM: Checking logs and confirming a queue
Request
Load
Settings
Queue
Import
Logs
Confirm
32
Inactive import
Uptime
Downtime Inactive import Switch off the report sources
Uptime
Initial status
Final status
Sources to be imported
Inactive sources
Inactive sources
Active sources
Obsolete sources
Active sources
Active sources
33
SPAM / SAINT update
How are they different?
How important are they? Why?
SPAM/SAINT Update
34
Importing a SPAM / SAINT update
Request
Load
Perform Update
Logs
35
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 Administration Checks 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
36
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
37
Apply java support packages using JSPM
38
Apply java support packages using JSPM (continued)
39
Apply kernel patch using JSPM
40
Apply kernel patch using JSPM (continued)
41
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
42
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 areas no side effects
43
44
Module 12: Summary
Having completed this module, you should now be 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
45
Day 8: Module map

Module 22: SAP support package Module 23: SAP system upgrade 3 Module 24: ALE EDI RFC
46
SAP System Upgrade

Module 13
On completion of this module, you should be able to: Describe the planning and preparation of SAP system upgrade Categorize several tools available in performing system upgrade Explain modification adjustment
48
Module 13: Agenda

Topic 1: Planning and preparation of SAP system upgrade Topic 2: Tools available for system upgrade Topic 3: Modification adjustment
49
Planning and performing an SAP system upgrade
Source: SAP
SAP system upgrade: Factors
Factors deciding upgrade
51
Upgrade planning
Plan Prepare Perform Post Upgrade Activities Plan Prod start for new R/3 release
PREPARE Script PERFORM Technical Upgrade OS Upgrade? DB Upgrade Hardware R/3 Upgrade Upgrade? Adjust Modifications DB Check Modifications Schedule Plan system downtime Perform Tech upgrade DB upgrade R/3 upgrade Bind Adjustments
Post Upgrade Backup DB Clean up New Authorizations R/3 Release and upgrade Customizing User upgradation tests
Post Upgrade Backup DB Clean up Import new Authorizations Import R/3 Release and upgrade Customizing Perform Post Upgrade Activities Plan Prod start for new R/3 release
Plan
Prepare
52
Steps during upgrade
Plan
Gather system requirements
Start
Check
Start post upgrade activities
Perform upgrade
53
Upgrade tools
Sgen
Upgrade assistant
Icnv
Upgrade monitor Prepare
54
PREPARE
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.
55
SGEN: SAP load generator
56
Upgrade assistant and upgrade monitor

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.
57
ICNV: incremental conversion
58
Phases of an SAP system upgrade
Source: SAP
Modification adjustment
Source: SAP
61
Module 13: Summary
Having completed this module, you should now be able to: Describe the planning and preparation of SAP system upgrade Categorize several tools available in performing system upgrade Explain modification adjustment
62
Day 8: Module map

Module 22: SAP support package Module 23: SAP system upgrade 3 Module 24: ALE EDI RFC
63
ALE EDI RFC

Module 14
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
65
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
Distributed application
MMPUR PS GL
PP SDSHP SDORD
CO MMINV
MMINV
ALE
Distributed business process
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
ALE
68
ALE: Requirements
1. Identify business processes and objects involved.
2. Identify the information to be transmitted.
3. Specify the format for the data to be transferred.
ALE
4. Decide on the transfer technology to be used.
5. Decide on the transfer type.
6. Specify the destination for the data transfer.
69
Important terms
IDOC
BAPI
Transport types
70
EDI
Source: SAP
EDI elements
72
What is RFC?
SAP system
SAP /nonSAP system
..talks to..
73
RFC connection possibilities

SAP system (can also be SAP R/2) ABAP program RFC interface
External system External program
RFC interface
RFC interface ABAP program SAP system

74
Remote function call in detail
CALLING SYSTEM
CALLED SYSTEM
RFC interface
RFC interface
75
RFC destinations
Source: SAP
Types of RFC
RFC
Synchronous RFC
Transactional RFC
Queued RFC
Asynchronous RFC
77
Setting up a remote connection
78
Testing an RFC connection
79
80
Module 14: Summary
Having completed this module, you should now 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
81
SAP Memory Management

Module 15
On completion of this module, you should 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 Interpret memory usage for SAP AS JAVA Put in your own words the details on JVM
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
Memory
Memory refers to the device whose contents are dynamic but are accessible at extremely high speed.
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. Physical Memory
OS Paging File/Swap Space
When we speak of memory at SAP level, it refers to virtual memory.
85
Memory areas
Virtual memory
Work Work Process Work Process Work Process Process
Local memory
All work processes Of one instance
Shared memory
Shared memory and local memory

SAP memory management system
Source: SAP
SAP memory management system (continued)
Source: SAP
Memory management: Basic concepts

Virtual memory Address space Memory allocation Local process memory
Shared Memory
89
Local memory
Server Virtual memory Shared memory Allocated at instance start Local Memory Local Memory Local Memory Local memory Local memory is Associated with Individual work processes
Local work process memory is for: ABAP load Data, stack Buffer for database transfer Local roll area Local paging area
Work Process
Work Process
Work Process
How SAP memory is used in principle

Shared memory
Shared memory Is associated with all Processes of one instance Local memory Sap Buffers
Server Virtual memory Shared memory
1:n SAP buffers contain global objects For all users and work processes, Such as programs and buffered Table content Work Process Work Process Work Process
SAP buffers in shared memory

Extended memory
Server Virtual Memory
Shared Memory
Local Memory
Extended memory 1:n Work Process Extended memory Contains objects/data associated With unfinished transactions Work Process Work Process
Extended Memory in Shared Memory in Virtual Memory

Heap memory
Server Virtual memory Shared memory
Allocated at instance start Local Memory
Local memory
Allocated on demand
Heap memory (Temporary) Local Memory Local 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
Work Process
Work Process
Work Process
When memory areas are allocated

Roll memory
Server
Virtual memory Shared memory Roll Buffers Local memory
Sap Roll file
1:n Work Process Work Process Work Process
Roll memory contains initial part of user contexts
Roll buffers in shared memory
94
Paged Memory
Server
Virtual Memory Shared Memory Local Memory
SAP paging buffer
SAP paging file
1:n Work Process Work Process Work Process
SAP paging memory contains: ABAP objects such as extracts Context-independent objects such as exports
SAP memory areas: Overview

Server Virtual Memory Shared Memory Roll buffers SAP buffers (programs, tables) Local Memory Heap Memory (temporary)
SAP Paging buffer
Extended memory 1:n SAP paging file
Local Memory
Local Memory
Local Memory
1:1
Work Process Work Process Work Process
SAP roll file
96
Some important concepts

User context Work process Virtual address space of a work process
97
SAP memory allocation

1 SAP user 2 SAP user 3 SAP user 4 SAP user
Dialog Work Process 1
Data For user1
Data For user 3
Work processes working on user requests

Work processes processing one step at a time
1
SAP user
2
SAP user
3
SAP user
4
SAP user
Data For user1
Data For user3
99
Roll out
1 SAP user Exit Dialog Work Process 1 Data For user3 Data For user1 Copy Dialog Work Process 2 2 SAP user 3 SAP user 4 SAP user
100
Roll in
Dialog Data Work For user 4 Process 1
Data For user1 Copy
Data For user 3
101
Roll and paging area of the dialog work process

Roll area
User context objects such as: -Authorizations -Set/Get parameters (-Internal tables) (-Report lists) Memory for specific ABAP commands
Paging area
102
Roll buffer / roll file and page buffer/page file

1 SAP user 2 SAP user
Roll buffer
3 SAP user
4 SAP user
Roll area Paging area Copy
Roll area Paging area
Roll file Paging buffer
Paging file
103
Mapping used for accessing data in extended memory

1 SAP user 2 SAP user 3 SAP user Roll area 4 SAP user
Mapping
Paging area
Dialog Work Process 2 Extended Memory (shared)
swap
Memory allocation sequence 1

1st
A defined initial part of the roll area is used
Role area Paging area
Extended Memory (shared)
105

2nd
Extended memory is : used until
Roll area
mapping
Paging area
106

the extended memory is full or
107

until the user quota is reached
108

3rd
The rest of the WP-local roll area is used
Roll area Paging Paging area
109

1 SAP user 2 SAP user 3 SAP user 4 SAP user Roll area Paging Dialog area Work Heap Process memory 2 Extended Memory (shared)
4th :
The system is forced to use local heap memory
110
PRIV mode 1
1 SAP user 2 SAP user 3 SAP user 4 SAP user Roll Area Paging Area Heap Memory (Local)
Dialog Work Paging Area Process 1
Roll Area
PRIV mode
Extended Memory (Shared)

PRIV mode 2
1 SAP user 2 SAP user 3 SAP user 4 SAP user Roll area Paging Dialog area Work Heap Process Memory 2 Extended Memory (shared)
Dialog Work Paging Process area 1
Roll area
If Heap memory is in use, further steps of the current transaction wont be dispatched to other Dialog work processes
112
Memory allocation sequence for dialog work processes in detail, avoiding PRIV mode
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
Local memory
Memory Allocation sequence for Dialog work processes

Shared memory
113
Memory allocation sequence for all work process types

Allocation sequence for non-dialog Wpes on Windows and for dialog Wpes on all platforms
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
Allocation sequence for non-dialog Wpes on

All platforms except Windows Local memory
Heap memory Upto abap/heap_area_dia Or HM exhausted
Extended memory Upto Ztta/roll_extension Or EM exhausted
3
Time
Shared memory
Freeing heap memory

1 SAP user 2 SAP user 3 SAP user 4 SAP user Roll area Paging Work area Process 2 Heap Memory
Work Process 1
Heap memory is released by the work process after use
swap

Freeing heap memory (continued)

Work Process 1
But on UNIX OSs allocated swap space in not freed by the operating system!
Roll area Paging area Heap Memory
Work Process 2
swap

Freeing heap memory

1 SAP user 2 SAP user 3 SAP user 4 SAP user Roll area Paging area
Work Process 1
When the limit set in abap/heaplimit is reached, the work process is flagged for automatic restart.
Work Process 2
swap
Profile parameter of memory management

DIA
ztta/roll_first
ztta/roll_area
Roll area
Roll buffer
rdisp/roll_SHM
Heap Memory
Roll file
rdisp/roll_SMAXFS
abap/heap_area_dia abap/heap_area_total
ztta/roll_extension
Extended
Memory
(shared)
em/initial_size_MB
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
119
ztta/roll_area: Roll area
Source: SAP
Configuring parameters (continued)

rdisp/ROLL_SHM
Determines Roll Buffer Size.
rdisp/ROLL_MAXFS
Determines Maximum Roll File Size
121
abap/heap_area_dia
Source: SAP
abap/heap_area_nondia
Source: SAP
abap/heaplimit: Work process restart
Source: SAP
abap/heap_area_total: Total quota for heap memory
Source: SAP
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
126
ztta/roll_extension: Extended memory limit
Source: SAP
127
ztta/roll_first: Initial allocation size from the roll area
Source: SAP
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
129
Implementation of SAP extended memory

em/initial_size_MB User independent data abap/heap_area_(non)dia
User context Roll Memory Extended memory Heap Memory
Local WP
SAP buffers
Address space (1.7 to 3.8 GB)

SAP Work process Address space restriction due to Unix 32 bit architecture 32- bit Restriction on UNIX OS Local memory Shared memory
130
Extended memory on 32-bit windows OS

em/initial_size_MB Extended memory (initial total) em/address_space_MB abap/heap_area_(non)dia
Local WP
SAP buffers
Roll Memory
Extended memory
Heap Memory
Address space (approx 1.8 GB) SAP Work process
Local memory
Parameter em/address_space_MB determines the amount of extended memory per work process Parameter em/initial_size_MB can be very large
Shared memory
Setups / tune buffers summery
132
Setups / tune buffers summery (continued)
133
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 by SUN)

-Xmx (Max Heap Size)
135
Sizing the memory management of the Java virtual machine
Memory Area Young generation Tenured generation
Initial Size -XX:NewSize See below
Max Size -XX:MaxNewSize See below
Permanent generation
-XX:PermSize
-XX:MaxPermSize
136
Setting the memory management
Source: SAP
138
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 Interpret memory usage for SAP AS JAVA Put in your own words the details on JVM

Comprehensive Sap Basis Training Day 4

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Comprehensive Sap Basis Training Day 4

Uploaded by

Copyright:

Available Formats

IBM Global Business Services

Day 4: Module map

4 Module 15: ALE EDI RFC

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

Solution Manager Basics

Copyright IBM Corporation 2009

IBM Global Business Services

Module 12: Objectives

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

Module 12: Agenda

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

Basics of solution manager

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

What can the SAP solution manager do

IBM Global Business Services

Functions of the SAP solution manager

Continuous Improvement Services:

Best Practices for SAP application:

IBM Global Business Services

The system landscape directory (SLD)

IBM Global Business Services

Connecting ABAP-based SAP systems to the SLD

IBM Global Business Services

The Web UI of the SLD

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

Questions and Answers

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

SAP Support Package

Copyright IBM Corporation 2009

IBM Global Business Services

Module 13: Objectives

Explain SAP support package implementation process

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

Module 13: Agenda

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

SAP support packages

SAP Basis FastTrak WAS 700

Copyright IBM Corporation 2009

IBM Global Business Services

Structure of SAP system

SAP ECC Industry Enterprise extension solution EA* PLUGIN

SAP ECC (R/3)

SAP Web AS ABAP

IBM Global Business Services

SAP support package explained

SAP Basis FastTrak WAS 700