openSAP Upnw1 All Slides PDF

Week 1 Unit 1: Introduction
Introduction
The SAP NetWeaver technology platform
Provides a reliable, secure, and stable foundation to run
business applications like SAP Business Suite
Ensures that large enterprises can perform mission-critical
business processes
Is the technical foundation of SAP applications
Note: SAP NetWeaver Application Server is the runtime

environment for many SAP applications
2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
Introduction
SAP NetWeaver Application Server
Many SAP systems, such as SAP ERP, SAP Enterprise
Portal, and SAP CRM use SAP NetWeaver Application Server
SAP NetWeaver Application Server is available in the
following configurations:
AS ABAP
AS Java
AS ABAP + AS Java (dual-stack)
Public
Introduction
Upgrades affect the software components in the SAP system
An SAP system consists of different software components. All
of these components are regularly updated using support
packages
When we perform an update or upgrade, the software
components of an SAP system will be affected and will likely
change in version
Public
Introduction
Several reasons why you should upgrade
Older SAP version
End of mainstream maintenance
Migration to SAP HANA
Public
Introduction
You can update the SAP system by
Applying an SAP Note with transaction SNOTE
Applying a support package/support package stack
Installing an enhancement package
Performing a release upgrade
Public
Introduction
Before starting the upgrade, you should consider
The source and target release
If there are any dependencies between systems
If dual-stack split is required
If migration to SAP HANA is favored
Public
Introduction
Upgrading will affect the entire landscape
SAP systems will be on different release levels during the various stages of the upgrade
Sandbox
system
Development
system
Quality
system
Production
system
Public
Introduction
Upgrade services offered by SAP are
SAP GoingLive Functional Upgrade Check
SAP Upgrade Weekend Support
Note: For more information, go to

https://support.sap.com/support-programsservices/services.html
Public
Thank you
Contact information:
open@sap.com

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Public
11
Week 1 Unit 2: Planning &

Preparation
Planning & Preparation

Software Update Manager (SUM)
A multi-purpose tool that supports various
maintenance processes, such as performing a
release upgrade, installing enhancement
packages, applying support package stacks,
installing add-ons, or updating single
components
It can be downloaded from SAP Service
Marketplace at http://service.sap.com/sltoolset
It is essential to read the SUM guide and

Master Guide (for a specific product version).
These guides can be downloaded from SAP
Service Marketplace at
http://service.sap.com/instguides
Public

Product Availability Matrix (PAM) should be checked
to understand if the operating system
and/or database needs to be upgraded
before starting the upgrade.
PAM can be accessed through
http://support.sap.com/pam and the
requirement should be checked for target
release and support package stack.
Public

Upgrade Dependency Analyzer (UDA)
Can be used for checking the existence of
upgrade dependencies between two separately
installed SAP systems in your system landscape.
The result of this check is a dependency
statement that informs you of any known upgrade
dependencies between these systems.
UDA and its documents can be accessed through
http://service.sap.com/UDA
Public

A system update requires a stack.xml, provided in a maintenance transaction
The maintenance transaction calculates
the required packages based on the
source system and target release
As a result, a stack.xml is provided,
together with the software packages
The required kernel files and latest SAP
Host Agent can also be downloaded
New add-ons can be installed easily
along with the upgrade
Schedule a system
deployment of the
calculated archives at
a convenient date
Schedule
Plan
Note: The maintenance transaction is

created using either maintenance
optimizer (part of SAP Solution Manager)
or maintenance planner
Synchronization of
system data from SAP
Solution Manager to
SAP Support Portal
Plan a software
change on your
system, including
download of files
Sync
Verify
Verify system
description and
correct errors
Public

Things to consider when upgrading systems in a landscape
Start planning for an upgrade at least two
weeks before you want to begin with it
Upgrade your systems in the same
sequence in which you transport your
modifications
Think about the dual maintenance
strategy during an upgrade project
Consider the time taken for modification
adjustments and backups when deciding
on the upgrade schedule
Public

Preconfiguration modes offered by Software Update Manager
Single System:
Standard:
Advanced:
Longer downtime
Low system resource assignment
Standard downtime optimization

Moderate resource assignment
Extensive downtime optimization

High resource assignment
Near-Zero Downtime Maintenance (nZDM) possible
Public
Thank you
open@sap.com

Public
Week 1 Unit 3: Software Update

Manager Roadmap Steps
Software Update Manager Roadmap Steps

There are six roadmap steps in an upgrade
Extraction
Configuration
Checks
Preprocessing
Execution
Postprocessing
Public

During the Extraction roadmap step
Mandatory SAP Notes are checked
The original kernel is copied
The download directory is scanned and the
packages are extracted
Source and target systems are validated for
upgrade
Upgrade tools are imported
Kernel
Kernel
Public

During the Configuration roadmap step
Decisions are made for all add-ons
You can choose languages that are to be included
(release upgrade only)
You can choose additional support packages to be
included
The EPS/in directory is checked again for relevant
packages to be included in the upgrade
SUM reads the stack.xml, confirms that the packages in
the stack are for the correct system, and confirms the
source and target can be reached
Preconfiguration Mode is selected
Public

During the Checks roadmap step
Available disk space is checked
The consistency of the repository is checked
SUM checks the database to ensure enough
free space is available for the upgrade
The version of the operating system and the
database is checked to confirm it is
applicable for the target release
Note: Unless an error occurs, this step may not

require any interaction
Public

During the Preprocessing roadmap step
The upgrade will inform you that from
now on, the workbench will be locked.
After the workbench is locked, you can
no longer modify development objects.
Transport activity is no longer possible
The shadow system is installed
Modification adjustment of dictionary
objects is performed. This is done by
running transaction SPDD
Public

The shadow system (1)
ABAP
A shadow (SHD) system can be

used during system maintenance
(or update) parallel to the existing
system
A shadow system uses the same
system ID as the original system,
but has a separate instance
(shadow instance, own instance
number) and a separate
repository (shadow repository)
Public

Leave house
ABAP
conduct changes
move back in
Maintenance without shadow
Maintenance is transport-like
Use of house not possible for a long time (long downtime)
After start, reset is only possible based on backup (independent of SUM)
No additional resources for shadow required
Public

ABAP
move into new /

updated house
Create shadow
conduct changes
Maintenance with shadow
Usage of shadow
Short downtime (for the move)
Simple reset possible (skip the move)
Additional resources necessary: area and workers for shadow
Public

During the Execution roadmap step
The system is in downtime
The system is locked
The repository and SAP kernel are switched
Entries are imported into control tables
Reports (XPRAS) and after-import methods are run
For Java and dual-stack systems, the software
components are deployed
SAP Kernel
Repository
Note: Before entering downtime, a backup of the database,

system directory, and SUM directory must be made
Public
10

During the Postprocessing roadmap step
Log files are saved
Control tables are cleaned up
Development objects requiring modification
adjustment are displayed
Upgrade evaluation documents are generated
Public
11
Thank you
open@sap.com

Public
13
Week 1 Unit 4: Optimizing

Upgrade Performance
Optimizing Upgrade Performance

Factors that determine the performance of an upgrade
Operating system
Should be in accordance with the vendors guidelines
Landscape design
Network and location of the STMS
Database
Plays a key role during the whole process
Should be patched and tuned following SAP
recommendations
Optimizations in SUM tool
Parallelism
nZDM (near-Zero Downtime Maintenance in SUM)
Import of customer transports
Optimization of Java-based systems
Public

Understanding what parallelism is
Configurable in
PRE_CONFIGURATION/INITSUBST
phase
Increases the performance at different
stages (batch, database operations,
loading from medias, DMO)
Use KBA #1616401 as reference
Match up with databases own
parallelism for optimum performance
Public

Parallelism: configuration
ABAP processes
Used in phases that run background (batch) processes
like ACT_UPG, PARDIST, and XPRAs
SQL processes
Used in DDL-intensive phases: MVNTAB, PARCONV, and
SCEXEC*
R3trans processes
Determine the number of tp and R3trans parallel
processes during the various SHADOW_IMPORT phases
and also DDIC_UPG and TABIM_UPG
R3load processes
Set up a number of R3loads used to read data from
media / write to shadow instance during release upgrade
and in DMO scenarios, exporting and importing data
Public

How does near-Zero Downtime Maintenance (nZDM) help?
Decreases the business
downtime by ~40-60%
Available in
Advanced Configuration
preconfiguration mode
Details in SAP Note 1678564
Public

nZDM in detail (1)
Enables the main import running
on the extended shadow instance
Record and Replay technique
(CRR) for sync business
transactions between shadow and
production systems
Automated by SUM
Minimal additional hardware
requirements
Durations are based on a customer example

Public

nZDM in detail (2)
Durations are based on a customer example

Public

Import of customer transports (1)
Greatly reduces the business downtime
Considers all requests, including SPAU
and add-ons
Integrates with STMS, SPAU, ChaRM
Generally available: instructions on the
SUM guide
Public

Import of customer transports (2)
Public

The import in detail
Functionality available in
advanced mode
Settings are needed in the
configuration
One buffer file for all transports
Client-dependent and clientindependent
SPAU / SPDD
Repository
Customizing
Additional parameters for
transport profile
Specify clients for table logging
Choose to create a version
Public
10

The big picture: parallelism + customer transports
Uptime
Technical
downtime
(system update)
Customer
transports,
add-ons...
SGEN
System
Ramp-up
Shadow
operation
Test &
verification
Standard
mode
Installation
preparation
System
cool-down
SUM
Business Downtime
Savings of 40-60%
Savings of ~50%
Business Downtime
Uptime
Extended
shadow
operation
(system update +
custom transports)
System
Ramp-up
Shadow
operation
Technical
downtime
Test &
verification
Advanced
mode
Installation
preparation
System
cool-down
SUM
nZDM
Customer
transports
import
Public
11

Database platforms for downtime minimization capabilities of SUM
Available for
Oracle, 10g or higher
IBM DB2 LUW, 9.7 FP4 or higher
Microsoft SQL, 2005 or higher
SAP MaxDB 7.9 or higher
IBM DB2 z/OS 10.1 or higher
SAP HANA 1.00.52 or higher
SAP Adaptive Server Enterprise (ASE)

15.7.0.103 (SAP Note 1926697)
DB2 for IBM i 7.1 (SAP Note 1809339)
Public
12

nZDM Java
The near-Zero Downtime
Maintenance for SAP NetWeaver
Java (nZDM Java) solution enables
you to perform maintenance activities
in SAP NetWeaver Java-stack
systems with almost no downtime
nZDM Java can be used with SAP
Enterprise Portal (EP), SAP
Business Process Management
(BPM), SAP Process
Integration/Advanced Adapter Engine
Extended (PI/AAEX), and SAP
Process Orchestration (PO) systems
running on a Java-only system stack
Public
13
Thank you
open@sap.com

Public
15
Week 1 Unit 5:
Database Migration Option

Database migration option (DMO) is used when
You want to migrate your existing
ABAP system to the SAP HANA
database
Your SAP release needs to be
upgraded prior to migration
SAP upgrade and database
migration to SAP HANA to be
performed in one tool!
Public

Benefits of DMO are
Migration steps are simplified
System update, Unicode
conversion, and database
migration are combined in one
tool
Business downtime is reduced
Amount of testing required is
reduced
Source database remains
consistent, so fast fallback is
possible
Public

The pipe mode of migration
is used for the migration of databases
R3load is used for export from the
source DB and import into the SAP
HANA DB
It is supported for both Linux and
Windows systems
The file mode of migration is also
supported, where the data is copied to
a temporary file and processed and
imported in the target DB
Public

The process
You start the GUI tool using the link
http://<hostname>:1128/lmsl/sumabap/<SID>/doc/sluigui
Source
DB
SAP
System
Shadow system is created

Shadow repository is copied to SAP HANA DB
Downtime application tables migrated
1
2
Set up SAP HANA

specifics (client, schema )
Upgrade
Prepare
Execute Upgrade
Uptime
(until downtime phase)
Switch to downtime
Target kernel is used

Application tables are updated
DMO run is completed
Downtime
Migrate application data
Finalize Upgrade
Start SAP HANA-based system
(incl. data conversion)
Public

Important phases
EU_CLONE_MIG_UT_SIZES
EU_CLONE_MIG_DT_SIZES
EU_CLONE_MIG_UT_CREATE
EU_CLONE_MIG_DT_CREATE
EU_CLONE_MIG_UT_PRP
EU_CLONE_MIG_UT_RUN
EU_CLONE_MIG_DT_PRP
EU_CLONE_MIG_DT_RUN
- Determine table sizes for uptime migration (repository)

- Determine table sizes for downtime migration (app tables)
- Create tables on target database for uptime migration
- Create tables on target database for downtime migration
- Create directories and control files for uptime migration
- Migrate repository into target database
- Create directories and control files for downtime migration
- Migrate application tables into target database
Public

Special features for DMO
Table comparison (row count, row content)
Migration repetition option for fast testing
Landscape reorganization for SAP HANA
scale out
Supporting SAP HANA multi database
containers (MDC)
Public

Resetting the DMO
Can be done easily without any loss of data
The original database is preserved, which
makes the reset process very easy
During the DMO, the original database is still
active but is not in use
If a reset has to be done, it is easy to go
back to the original database
Public
Thank you
open@sap.com

Public
10
Week 1 Unit 6: Troubleshooting

and Wrap-Up
Troubleshooting and Wrap-Up

Update logs
The Software Update Manager logs all activity
in log files. These can be viewed on the UI by
clicking LOGS
The actual files can be found in the following
subdirectories:
For ABAP stack upgrades
SUM/abap/log
SUM/abap/tmp
For Java stack upgrades
SUM/sdt/log
SUM/sdt/trc
Public

If the error is with ABAP, you should
Check the main log files:
SAPupConsole.log and
SAPup_troubleticket.log
Analyze the phase-specific logs
Determine the nature of the problem
ABAP program
Batch job
Tool used by SUM (tp, R3trans,
sap_evt)
Public

If the error is with Java, you should
Raise the default trace level
Check the .TRC files in SUM/sdt/trc
Check the TroubleTicket_<xx>.txt and
<step name><nn>.log in SUM/sdt/trc
Check the deploy_api.0.log and
deploy_0.api.trc files if the error occurred in a
DEPLOY_* step
Public

When investigating errors, you should check
Upgrade and Update documentation
Upgrade and Update Troubleshooting Wiki
Software Update Manager guide
SAP Notes
SAP Knowledge Base Articles (KBAs)
SAP Community Network
Public

Resetting the update
The Software Update Manager has the
option to reset the update
Prerequisites for reset are:
Downtime has not yet started
SUM directory has not been cleaned up
If you are using DMO, the source DB
must still be available
Note: DMO can be reset to the beginning

of the update in all roadmap steps
including downtime
Public

Contacting SAP Support
If you are unable to solve your issue,
contact SAP Support by reporting an
incident in the SAP Support Portal
The following details will help with
investigation:
Product or software component
version
Trouble ticket and related logs
Phase in which the error occurred
Depending on the issue, providing an
R/3 or OS level connection can also
speed up resolution
Public

Further learning
Follow-up openSAP course on upgrades
coming in 2016!
SAP Education offerings
HA250 Migration to SAP HANA using
DMO
ADM328 SAP ECC Update/Upgrade
Public
Thank you
open@sap.com

Public
10

openSAP Upnw1 All Slides PDF

Uploaded by

Document Information

Original Title

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

openSAP Upnw1 All Slides PDF

Uploaded by

Copyright:

Available Formats

Week 1 Unit 1: Introduction

Note: SAP NetWeaver Application Server is the runtime

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Note: For more information, go to

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Week 1 Unit 2: Planning &

Planning & Preparation

It is essential to read the SUM guide and

2015 SAP SE or an SAP affiliate company. All rights reserved.

Planning & Preparation

2015 SAP SE or an SAP affiliate company. All rights reserved.

Planning & Preparation

2015 SAP SE or an SAP affiliate company. All rights reserved.

Planning & Preparation

Note: The maintenance transaction is

Planning & Preparation

2015 SAP SE or an SAP affiliate company. All rights reserved.

Planning & Preparation

2015 SAP SE or an SAP affiliate company. All rights reserved.

Standard downtime optimization

Extensive downtime optimization

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Week 1 Unit 3: Software Update

Software Update Manager Roadmap Steps

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

Note: Unless an error occurs, this step may not

Software Update Manager Roadmap Steps

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

A shadow (SHD) system can be

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

Maintenance without shadow

Use of house not possible for a long time (long downtime)

After start, reset is only possible based on backup (independent of SUM)

No additional resources for shadow required

2015 SAP SE or an SAP affiliate company. All rights reserved.

Software Update Manager Roadmap Steps

move into new /

Software Update Manager Roadmap Steps

Note: Before entering downtime, a backup of the database,

Software Update Manager Roadmap Steps

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Week 1 Unit 4: Optimizing

Optimizing Upgrade Performance

Optimizing Upgrade Performance

2015 SAP SE or an SAP affiliate company. All rights reserved.

Optimizing Upgrade Performance