Week 2 Unit 1: Introduction to Near-Zero

Downtime Maintenance (nZDM) for Java

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Business needs

Message queues to production

or transport logistics allow only
small maintenance windows B2B
Business downtime is
Most scenarios have to support
critical and costly distributed business landscape
with minor downtime windows

Stability and security Maintenance Windows:

improvements are executed at How many per year?
regular intervals How long will it take?

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
nZDM Java procedure benefits

Perform maintenance
Supports great number
activities with drastically
of maintenance activities various updates reduced downtime optimized downtime

Great flexibility in
Ability to keep business-
adapting the procedure nZDM
critical functions running
to different landscapes Java during maintenance
and needs flexibility system availability

No additional charge for Ability to perform

using the nZDM Java maintenance testing
procedure without downtime
built-in uptime testing

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Main phases of the procedure

Prepare uptime
uptime Maintain uptime
uptime Switch downtime
downtime Postprocess
Post-process uptime
uptime

Approach
Approach 1 1
System switch
Switch

PRD*
PRD
clone
PRD* PRD PRD* PRD
PRD switch
switch PRD*
PRD* PRD
PRD PRD
PRD
REC
clone role
role
REC STOP
STOP RESTART STOP
STOP

Approach
Approach 2 2
PRD Production system
Switch
Database switch
REC nZDM Java recording nZDM Java replication
Maintenance (i.e. update
Isolated clone system with Software
SAP Software
Update
Update PRD* PRD*
PRD* with same SAP SID and Manager) and testing
PRD
PRD
switch
switch
PRD*
PRD* PRD
PRD PRD*
PRD*

hostname(s) RESTART
content
content STOP
STOP STOP
STOP

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Timeline of the procedure

1 Start recording on the source

Production operation Ramp down

Old Old
6 Old
Clone creation
and isolation

version version version

4
2 Phase out

nZDM UI
7 System or DB switch
Technical validation
for Java
5 Production
Various maintenance activities operation
3 New
8
Old
version version

Time t1 t2 t3 t4
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5
Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Set-up of the procedure
nZDM Java GUI/CLI

PRD
PRD PRD*
AS AS
nZDM Java
nZDM Java nZDM Java
nZDM Java

REC

PRD
PRD PRD*

REC
nZDM Java DB
DB DB nZDM Java
recording replication
PRD Production
system
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6
Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
nZDM Java automation

 SAP Landscape Management offers

Landscape Management

integration with nZDM for Java that

can be used to automate
maintenance procedures for Java-
based applications
 The automated nZDM cloning
procedure includes fencing the
cloned system (network isolation)
 After nZDM maintenance, SAP
Landscape Management can swap
these two systems and promote the
cloned system to become the new
production system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
nZDM automation – Command line interface

 The nZDM command line interface

is provided as a method for
automation as part of scripts or
commands of a high-level
orchestration tool
 The CLI client is installed with the
nZDM GUI and connects remotely
to both nZDM source and target
systems

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 8

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
nZDM is available for…

SAP Enterprise Portal (SAP EP) SAP Process Orchestration (SAP PRO)
 SAP NetWeaver 7.0 EHP 2, SP11 or higher  SAP NetWeaver 7.3 EHP 1, SP2 or higher
 SAP NetWeaver 7.3, SP7 or higher  SAP NetWeaver 7.4
 SAP NetWeaver 7.3 EHP 1, SP2 or higher  SAP NetWeaver 7.5
 SAP NetWeaver 7.4
 SAP NetWeaver 7.5 Database Support
 SAP HANA
SAP Business Process Management (SAP BPM)  SAP ASE
 SAP NetWeaver 7.3, SP7 or higher  MS SQL Server
 SAP NetWeaver 7.3 EHP 1, SP2 or higher  Oracle
 SAP NetWeaver 7.4  IBM DB2 for LUW
 SAP NetWeaver 7.5  SAP MaxDB (SAP EP only)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Customer use cases (I)
Standard method

No-Go
Preparation Ramp Backup & Upgrade SAP Technical Ramp

Go/
DB upgrade Post activities
activities down restore point Process Orchestration post MA up

Uptime Downtime Uptime

Uptime Downtime Uptime

nZDM for Java

nZDM Ramp Ramp

Recording Post activities
preparation down up

Sys switch
Phase out
Target

No-Go
Upgrade SAP Online Technical

Go/
DB upgrade
system Process Orchestration replication post MA

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

Introduction to Near-Zero Downtime Maintenance (nZDM) for Java
Customer use cases (II)

New SAP Process New DB New OS

Orchestration version version

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 11

Thank you

Contact information:

[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

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 SE’s 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 forward-
looking 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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 13

Week 2 Unit 2: nZDM for Java
in More Detail
nZDM for Java in More Detail
Approaches comparison

System Switch
 Easy to use with existing virtual environment
 Most effective approach regarding downtime
 Fully integrated in LVM
 OS and DB updates are possible
 Lower resource consumption and performance impact on the source system

Database Switch
 Useful when production system has a complex setup (e.g. HA) or has a big
DB size
 Minimum modification of existing setup
 OS and DB updates are not possible
 Higher resource consumption and performance impact

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

nZDM for Java in More Detail
Considerations

 Additional hardware
 Load and space aspects
 Separate host for GUI/CLI (Windows or Linux)
 Online method for cloning should be in place
 Isolation
 Pretest is recommended

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

nZDM for Java in More Detail
Sample nZDM procedure: Prepare source (I)

Uptime

 Make sure no other maintenance

Java AS
activities are planned on the systems
 Switch the system to “Business Only”
mode
Java SCS

Database

Original system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

nZDM for Java in More Detail
Sample nZDM procedure: Prepare source (II)

Uptime
nZDM
 Download nZDM GUI from SAP GUI / CLI
Java AS
Service Marketplace and install it on
a separate host nZDM service

 Run and connect the nZDM GUI/CLI

to the production (source) system Java SCS
 Use nZDM GUI/CLI to start nZDM
recording
Database

Source system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

nZDM for Java in More Detail
nZDM recording – DB triggers and table classification

Three types of tables in the source DB

nZDM
 Whitelist – no triggers Java AS GUI / CLI

 Greylist – recording triggers nZDM service

 Frozen – freeze triggers

Java SCS

 Option to classify tables manually

Database

Source system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

nZDM for Java in More Detail
Sample nZDM procedure: Create target (I)

Uptime
nZDM
 Clone the source system to a Java AS GUI / CLI Java AS
separate network location nZDM service

 The cloning should be done without

stopping the source system Java SCS Java SCS

Database Database

Source system Cloned system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

nZDM for Java in More Detail
Sample nZDM procedure: Create target (II)

Uptime
nZDM
 Isolate the target Java AS GUI / CLI Java AS

 Start the target system. nZDM service

It will run in “nZDM target” mode

Java SCS Java SCS

Database Database

Source system Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 8

nZDM for Java in More Detail
Create target – System isolation prerequisites

 Source/production system should not be

stopped during cloning or fencing nZDM
 Target/clone system should be able to run Java AS GUI / CLI Java AS
in parallel with the source system nZDM service nZDM service
 At least one of the application servers of
the source and target systems should be
Java SCS Java SCS
accessible from the location where the
nZDM GUI is located
 Same application server should be Database Database
accessible from the target application
server
 The database of the source system should Source system Target system (isolated)
be accessible from the same application
server of the target system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

nZDM for Java in More Detail
Create target – System isolation possible options

After the online cloning of the source system is done, we

need to start it without conflicts. Here are two options:
 Change the hosts/IPs of all the parts – DB, SCS, app
servers
 Isolate/fence the target system and run the target system
without changes to its hosts or IPs
 Other…

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

nZDM for Java in More Detail
Sample nZDM procedure: Prepare target (I)

Uptime
nZDM
 Preform planned maintenance Java AS GUI / CLI Java AS
activities on the target system nZDM service

Java SCS Java SCS

Database Database

Source system Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 11

nZDM for Java in More Detail
Sample nZDM procedure: Prepare target (II)

Uptime
nZDM
 Connect the nZDM GUI/CLI to the Java AS GUI / CLI Java AS
target system and start nZDM nZDM service nZDM service
replication
 Wait for the number of replicated Java SCS Java SCS
records to get close to the amount of
recorded data
 Prepare/wait for system downtime Database Database

Source system Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 12

nZDM for Java in More Detail
Sample nZDM procedure: Switch systems

Downtime
nZDM
 Choose to finish the nZDM procedure Java AS GUI / CLI Java AS

 Stop the target system when nZDM nZDM service

replication is complete
Java SCS Java SCS
 Remove isolation of the target and
start it as the new production system
 End of downtime Database Database

Source system (stopped) Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 13

nZDM for Java in More Detail
Sample nZDM procedure: Post processing

Uptime

 Revert any changes done to make

Java AS
the system run in “Business Only”
mode

Java SCS

Database

Upgraded system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 14

Thank you

Contact information:

[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

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 SE’s 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 forward-
looking 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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 16

Week 2 Unit 3: nZDM Java in a
Cluster Setup
nZDM Java in a Cluster Setup
Cluster split: Prepare source

Uptime nZDM
GUI / CLI
 Switch the system to “Business
Only” mode
 Download the nZDM GUI from SAP
Java AS SAP WD SAP WD
Service Marketplace and install it on
a separate host nZDM service

 Run and connect the nZDM GUI/CLI Java SCS SAP SCS
to the production (source) system Java ERS SAP ERS

 Use nZDM GUI/CLI to start nZDM

recording Database Database

Original system (HA/DR)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

nZDM Java in a Cluster Setup
Cluster split: Prepare source

nZDM
Uptime No HA/DR GUI / CLI

 Remove a node from the cluster

without stopping the source
SAP WD SAP WD
 Isolate it from the network if needed Java AS
nZDM service
 Build an nZDM target system out of it
Java SCS Java SCS
Java ERS Java ERS

Database Database

Source system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

nZDM Java in a Cluster Setup
Cluster split: Prepare target

nZDM
Uptime No HA/DR GUI / CLI Java AS

 Perform planned maintenance nZDM service

activities on the target system

SAP WD SAP WD
 Connect the nZDM GUI/CLI to the Java AS
target system and start nZDM nZDM service
replication Java SCS Java SCS
 Prepare/wait for system downtime Java ERS Java ERS

Database Database

Source system Target system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

nZDM Java in a Cluster Setup
Cluster split: Switch systems

nZDM
Downtime GUI / CLI Java AS

 Choose to finish the nZDM nZDM service

procedure
 Stop the target system when nZDM Java AS SAP WD SAP WD
replication is complete
 Remove isolation of the target and Java SCS Java SCS
start it as the new production
Java ERS Java ERS
system
 End of downtime
Database Database

Source system (stopped) Target system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

nZDM Java in a Cluster Setup
Cluster split: Postprocessing (I)

Uptime No HA/DR

 Revert any changes done to make

the system run in “Business Only”
mode Java AS SAP WD SAP WD

 Reconnect the application servers

to the updated system Java SCS Java SCS
Java ERS Java ERS

Database Database

Upgraded system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

nZDM Java in a Cluster Setup
Cluster split: Postprocessing (II)

Uptime

 Recreate the HA/DR cluster

Java AS SAP WD SAP WD

Java SCS Java SCS

Java ERS Java ERS

Database Database

Upgraded system (HA/DR)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

nZDM Java in a Cluster Setup
Cluster split: Summary

 Very few additional HW resources needed

 HA/DR setup is broken early and recreated after the
downtime
 HA/DR cluster setup can’t be tested during uptime
 Higher complexity  Higher consultancy costs
 More difficult for automation

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 8

nZDM Java in a Cluster Setup
Cluster clone: Prepare system
nZDM
GUI / CLI
Uptime
Java AS
 Switch the system to “Business Only”
mode nZDM service

 Download the nZDM GUI from SAP

Service Marketplace and install it on a SAP WD SAP WD
separate host
 Run and connect the nZDM GUI/CLI to Java SCS Java SCS
the source (production) system
Java ERS Java ERS
 Use the nZDM GUI/CLI to start nZDM
recording
Database Database

Original system (HA/DR)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

nZDM Java in a Cluster Setup
Cluster clone: Create target
nZDM
GUI / CLI
Uptime
Java AS Java AS
 Clone the source system
nZDM service
 Isolate and start the clone as the
target system SAP WD SAP WD SAP WD SAP WD

Java SCS Java SCS Java SCS Java SCS

Java ERS Java ERS Java ERS Java ERS

Database Database Database Database

Original system (HA/DR) Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

nZDM Java in a Cluster Setup
Cluster clone: Prepare target
nZDM
GUI / CLI
Uptime
Java AS Java AS
 Preform planned maintenance
nZDM service nZDM service
activities on the target system
 Connect the nZDM GUI/CLI to the SAP WD SAP WD SAP WD SAP WD
target system and start nZDM
replication
Java SCS Java SCS Java SCS Java SCS
 Prepare/wait for system downtime
Java ERS Java ERS Java ERS Java ERS

Database Database Database Database

Original system (HA/DR) Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 11

nZDM Java in a Cluster Setup
Cluster clone: Switch systems
nZDM
GUI / CLI
Downtime
Java AS Java AS
 Choose to finish the nZDM
nZDM service
procedure
 Stop the target system when nZDM SAP WD SAP WD SAP WD SAP WD
replication is complete
 Remove isolation of the target and
Java SCS Java SCS Java SCS Java SCS
start it as the new production
Java ERS Java ERS Java ERS Java ERS
system
 End of downtime
Database Database Database Database

Original system (stopped) Target system (isolated)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 12

nZDM Java in a Cluster Setup
Cluster clone: Postprocessing

Uptime
Java AS
 Revert any changes done to make
the system run in “Business Only”
mode
SAP WD SAP WD

Java SCS Java SCS

Java ERS Java ERS

Database Database

Upgraded system (HA/DR)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 13

nZDM Java in a Cluster Setup
Cluster clone: Summary

 About twice as many HW resources needed

 The system keeps its HA/DR setup at all times
(except system downtime)
 HA/DR cluster setup may be tested during uptime
 Simplicity (compared to cluster split approach)
 Easier for automation

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 14

nZDM Java in a Cluster Setup
Maintenance activities: Software Update Manager (SUM Java)

Maintenance activities with SUM Java

Software Update Manager is the SAP tool

for maintenance of SAP NetWeaver-based
systems

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 15

nZDM Java in a Cluster Setup
SUM Java procedure: Supported maintenance activities

UP

 Release upgrade (major release change)

 System update (EHP installation)

 Applying support packages (SPs) / support package

 Applying Java patches

 Correction of installed software information

 Up-to-date installation

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 16

nZDM Java in a Cluster Setup
SUM Java procedure: Benefits

 Improved user experience and unified capability

 Transparency about source system state, installed products,

and content to be updated

 Overview of process details upon and after SUM procedure

 Extended prerequisite checks to optimize the stop-and-start

procedure of instances

 Reduced downtime

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 17

Thank you

Contact information:

[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

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 SE’s 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 forward-
looking 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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 19

Week 2 Unit 4: End-to-End nZDM –
Java Procedure Execution
End-to-End nZDM – Java Procedure Execution
Demo scenario: Cluster clone

 Download and run the nZDM GUI

 Connect the nZDM GUI to the source system
 Start recording
 Clone the source system and isolate the clone (target)
 Start the target system
 Perform an update using SUM Java
 Connect the nZDM GUI to the target system
 Start replication
 Finish the procedure from the nZDM GUI
 Remove target system isolation
 Start the target system as the new source

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

End-to-End nZDM - Java Procedure Execution
Demo set-up: Cluster clone

Landscape View nZDM GUI

 nZDM Java GUI
 Source system
 Target system
 Start recording
 Landscape view

Source System Target System

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Thank you

Contact information:

[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

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 SE’s 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 forward-
looking 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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

Week 2 Unit 5:
Troubleshooting & Wrap-Up
Troubleshooting & Wrap-Up
Summary

 nZDM minimizes business downtime during

maintenance of SAP NetWeaver Java-based products nZDM
 It enables availability of business-critical functionality Java AS GUI / CLI Java AS
during maintenance nZDM service nZDM service

 Downtime – around one system restart

 Flexible, clone-based procedure Java SCS Java SCS

 SAP Landscape Management, cloud virtualization

 SWPM (system copy scenario) Database Database

 Integration with SAP Landscape Management, CMD

interface Source system Target system (isolated)
 nZDM allows preliminary testing of updated cloned
system during uptime

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Troubleshooting & Wrap-Up
nZDM Java GUI

 If Java GUI loses connection, it tries to

reconnect automatically
 If auto reconnection fails or you need to close
the GUI, restart it and manually reconnect 
no impact on the nZDM Java procedure
execution
 If the GUI loses connection during the
finalization of the procedure, you have to enter
the same connection data for the source
system as for the target system

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Troubleshooting & Wrap-Up
Logs

 All messages from the nZDM Java procedure are

stored in defaultTrace_<number>.trc and
applications_<number>.log files
 They are located at:
<Drive>:\usr\sap\<SID>\<instance_name>\<Jxx or
JCxx>\cluster\server0\log
 Check the latest defaultTrace_<number>.trc and
applications_<number>.log files for each system
instance. This is valid for the source system and
the target system, if the latter has already been
created
 You can find the nZDM GUI/CLI logs under
<NZDM JAVA_dir>\java\log

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

Troubleshooting & Wrap-Up
Further analysis – DB tables

To perform further analysis, you can also check the following

database tables in your source or target system
 BC_NZDM_STATE
 BC_NZDM_CHANGE_LOG
 BC_NZDM_ERROR_LOG

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

Troubleshooting & Wrap-Up
Recording vs replication errors

Recording errors:
 Fatal to the nZDM Java procedure
 Recording in the source system is aborted
 You have to reset the nZDM Java procedure and
start over from the beginning

Replication errors:
 Non-fatal
 Replication is stopped
 Might be able to resolve the issue and resume
the replication
 In the worst case, your target system might be
unusable
 If this is the case, you have to create a new
target system and repeat all steps from that point

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

Troubleshooting & Wrap-Up
Resetting the nZDM Java procedure

 Connect the nZDM Java GUI to the source

system
 If the recording has started, choose Abort
Recording. Shortly after, the button changes to
Reset nZDM
 Reset the nZDM Java procedure by choosing
Reset nZDM. This also resets the nZDM Java
GUI
 Start the procedure from the beginning

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

Troubleshooting & Wrap-Up
Investigating on the source system

 After you have finished the nZDM Java

procedure, your target system will be your new
production system. The source system will be
stopped.
 If you need to gain access to the source system
to have some issue investigated there, it is
crucial to isolate it beforehand, the same way
you isolated the target during the procedure.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 8

Troubleshooting & Wrap-Up
Additional resources

 support.sap.com/sltoolset

Useful resources:
 nZDM Java documentation
 SAP Notes
 SAP Community Network

nZDM Java BCP component:

BC-UPG-DTM-TLJ

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

Troubleshooting & Wrap-Up
nZDM troubleshooting: Contacting SAP Support

 If you need assistance, contact SAP Support by

reporting an incident in the SAP Support Portal
 The following details will help with investigation:
 AS Java version/SP (source & target)
 Trouble ticket
 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

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

Thank you

Contact information:

[email protected]
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

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 SE’s 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 forward-
looking 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.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 12