Transcription
Week 2 Unit 1: Introduction to Near-ZeroDowntime Maintenance (nZDM) for Java
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaBusiness needsMessage queues to productionor transport logistics allow onlysmall maintenance windowsBusiness downtime iscritical and costlyStability and securityimprovements are executed atregular intervals 2016 SAP SE or an SAP affiliate company. All rights reserved.B2BMost scenarios have to supportdistributed business landscapewith minor downtime windowsMaintenance Windows:How many per year?How long will it take?Public2
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM Java procedure benefitsSupports great numberof maintenance activitiesGreat flexibility inadapting the procedureto different landscapesand needsvarious updatesreduced downtimeAbility to keep businesscritical functions runningduring maintenancenZDMJavaflexibilitysystem availabilityNo additional charge forusing the nZDM JavaprocedureAbility to performmaintenance testingwithout downtimebuilt-in 2016 SAP SE or an SAP affiliate company. All rights reserved.Perform maintenanceactivities with drasticallyoptimized downtimeuptime testingPublic3
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaMain phases of the ptimeApproachApproach 1 1System ECIsolated clone systemwith same SAP SID PRD*PRDPRDRESTARTSTOPSTOPPRDPRDApproachApproach 2 2Production systemnZDM Java recordingPRDPRDnZDM Java replicationMaintenance (i.e. updatewith SoftwareSAP SoftwareUpdateUpdateManager) and testing 2016 SAP SE or an SAP affiliate company. All rights reserved.SwitchDatabase entPRD*PRD*STOPSTOPPRDPRDPRD*PRD*STOPSTOPPublic4
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaTimeline of the procedure1Start recording on the source2Clone creationand isolationProduction operationOldversionRamp down6Oldversion4nZDM UIfor JavaOldversion75ProductionoperationVarious maintenance activitiesOldversionTimet1 2016 SAP SE or an SAP affiliate company. All rights reserved.3Newversiont2Phase outSystem or DB switchTechnical validation8t3t4Public5
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaSet-up of the procedurenZDM Java GUI/CLIPRDPRDASPRD*ASnZDM JavanZDMJavanZDM JavanZDMJavaPRDPRDPRD*DBDBDBRECRECPRDnZDM JavarecordingProductionsystem 2016 SAP SE or an SAP affiliate company. All rights reserved.nZDM JavareplicationPublic6
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM Java automation SAP Landscape Management offersintegration with nZDM for Java thatcan be used to automatemaintenance procedures for Javabased applicationsLandscape Management The automated nZDM cloningprocedure includes fencing thecloned system (network isolation) After nZDM maintenance, SAPLandscape Management can swapthese two systems and promote thecloned system to become the newproduction system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public7
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM automation – Command line interface The nZDM command line interfaceis provided as a method forautomation as part of scripts orcommands of a high-levelorchestration tool The CLI client is installed with thenZDM GUI and connects remotelyto both nZDM source and targetsystems 2016 SAP SE or an SAP affiliate company. All rights reserved.Public8
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM 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.5Database Support SAP HANASAP 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.Public9
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaRampdownDB upgradeBackup &Upgrade SAPrestore point Process OrchestrationDowntimenZDM for JavanZDMpreparationDowntimeRamp RampdownupRecordingDB upgrade 2016 SAP SE or an SAP affiliate company. All rights reserved.Upgrade SAPProcess OrchestrationOnlinereplicationPost ost MAUptimePost activitiesGo/No-GoUptimeTechnicalpost MAGo/No-GoPreparationactivitiesPhase outSys switchStandard methodCustomer use cases (I)Public10
Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaCustomer use cases (II)New SAP ProcessOrchestration 2016 SAP SE or an SAP affiliate company. All rights reserved.New DBversionNew OSversionPublic11
Thank youContact 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 affiliatecompany) in Germany and other countries. Please see ht/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 itsaffiliated 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 andservices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting 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 developor release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible futuredevelopments, 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 timefor 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 placeundue 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.Public13
Week 2 Unit 2: nZDM for Javain More Detail
nZDM for Java in More DetailApproaches comparisonSystem 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 systemDatabase Switch Useful when production system has a complex setup (e.g. HA) or has a bigDB 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.Public2
nZDM for Java in More DetailConsiderations 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.Public3
nZDM for Java in More DetailSample nZDM procedure: Prepare source (I)Uptime Make sure no other maintenanceactivities are planned on the systemsJava AS Switch the system to “Business Only”modeJava SCSDatabaseOriginal system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public4
nZDM for Java in More DetailSample nZDM procedure: Prepare source (II)Uptime Download nZDM GUI from SAPService Marketplace and install it ona separate host Run and connect the nZDM GUI/CLIto the production (source) systemJava ASnZDMGUI / CLInZDM serviceJava SCS Use nZDM GUI/CLI to start nZDMrecordingDatabaseSource system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public5
nZDM for Java in More DetailnZDM recording – DB triggers and table classificationThree types of tables in the source DB Whitelist – no triggers Greylist – recording triggersJava ASnZDMGUI / CLInZDM service Frozen – freeze triggersJava SCS Option to classify tables manuallyDatabaseSource system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public6
nZDM for Java in More DetailSample nZDM procedure: Create target (I)Uptime Clone the source system to aseparate network location The cloning should be done withoutstopping the source system 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDMGUI / CLIJava ASnZDM serviceJava SCSJava SCSDatabaseDatabaseSource systemCloned systemPublic7
nZDM for Java in More DetailSample nZDM procedure: Create target (II)Uptime Isolate the target Start the target system.It will run in “nZDM target” mode 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDMGUI / CLIJava ASnZDM serviceJava SCSJava SCSDatabaseDatabaseSource systemTarget system (isolated)Public8
nZDM for Java in More DetailCreate target – System isolation prerequisites Source/production system should not bestopped during cloning or fencing Target/clone system should be able to runin parallel with the source system At least one of the application servers ofthe source and target systems should beaccessible from the location where thenZDM GUI is located Same application server should beaccessible from the target applicationserver The database of the source system shouldbe accessible from the same applicationserver of the target system 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDM servicenZDMGUI / CLIJava ASnZDM serviceJava SCSJava SCSDatabaseDatabaseSource systemTarget system (isolated)Public9
nZDM for Java in More DetailCreate target – System isolation possible optionsAfter the online cloning of the source system is done, weneed to start it without conflicts. Here are two options: Change the hosts/IPs of all the parts – DB, SCS, appservers Isolate/fence the target system and run the target systemwithout changes to its hosts or IPs Other 2016 SAP SE or an SAP affiliate company. All rights reserved.Public10
nZDM for Java in More DetailSample nZDM procedure: Prepare target (I)Uptime Preform planned maintenanceactivities on the target system 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDMGUI / CLIJava ASnZDM serviceJava SCSJava SCSDatabaseDatabaseSource systemTarget system (isolated)Public11
nZDM for Java in More DetailSample nZDM procedure: Prepare target (II)Uptime Connect the nZDM GUI/CLI to thetarget system and start nZDMreplication Wait for the number of replicatedrecords to get close to the amount ofrecorded data Prepare/wait for system downtime 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDM servicenZDMGUI / CLIJava ASnZDM serviceJava SCSJava SCSDatabaseDatabaseSource systemTarget system (isolated)Public12
nZDM for Java in More DetailSample nZDM procedure: Switch systemsDowntime Choose to finish the nZDM procedureJava AS End of downtime 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASnZDM service Stop the target system when nZDMreplication is complete Remove isolation of the target andstart it as the new production systemnZDMGUI / CLIJava SCSJava SCSDatabaseDatabaseSource system (stopped)Target system (isolated)Public13
nZDM for Java in More DetailSample nZDM procedure: Post processingUptime Revert any changes done to makethe system run in “Business Only”modeJava ASJava SCSDatabaseUpgraded system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public14
Thank youContact 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 affiliatecompany) in Germany and other countries. Please see ht/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 itsaffiliated 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 andservices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting 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 developor release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible futuredevelopments, 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 timefor 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 placeundue 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.Public16
Week 2 Unit 3: nZDM Java in aCluster Setup
nZDM Java in a Cluster SetupCluster split: Prepare sourcenZDMGUI / CLIUptime Switch the system to “BusinessOnly” mode Download the nZDM GUI from SAPService Marketplace and install it ona separate host Run and connect the nZDM GUI/CLIto the production (source) system Use nZDM GUI/CLI to start nZDMrecordingJava ASSAP WDSAP WDJava SCSSAP SCSJava ERSSAP ERSDatabaseDatabasenZDM serviceOriginal system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Public2
nZDM Java in a Cluster SetupCluster split: Prepare sourcenZDMGUI / CLIUptime No HA/DR Remove a node from the clusterwithout stopping the source Isolate it from the network if needed Build an nZDM target system out of itJava ASSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabasenZDM serviceSource system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public3
nZDM Java in a Cluster SetupCluster split: Prepare targetnZDMGUI / CLIUptime No HA/DR Perform planned maintenanceactivities on the target system Connect the nZDM GUI/CLI to thetarget system and start nZDMreplication Prepare/wait for system downtimenZDM serviceJava ASSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabasenZDM serviceSource system 2016 SAP SE or an SAP affiliate company. All rights reserved.Java ASTarget systemPublic4
nZDM Java in a Cluster SetupCluster split: Switch systemsnZDMGUI / CLIDowntime Choose to finish the nZDMprocedure Stop the target system when nZDMreplication is complete Remove isolation of the target andstart it as the new productionsystemJava ASnZDM serviceJava ASSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabase End of downtimeSource system (stopped) 2016 SAP SE or an SAP affiliate company. All rights reserved.Target systemPublic5
nZDM Java in a Cluster SetupCluster split: Postprocessing (I)Uptime No HA/DR Revert any changes done to makethe system run in “Business Only”mode Reconnect the application serversto the updated systemJava ASSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabaseUpgraded system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public6
nZDM Java in a Cluster SetupCluster split: Postprocessing (II)Uptime Recreate the HA/DR clusterJava ASSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabaseUpgraded system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Public7
nZDM Java in a Cluster SetupCluster split: Summary Very few additional HW resources needed HA/DR setup is broken early and recreated after thedowntime 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.Public8
nZDM Java in a Cluster SetupCluster clone: Prepare systemnZDMGUI / CLIUptimeJava AS Switch the system to “Business Only”modenZDM service Download the nZDM GUI from SAPService Marketplace and install it on aseparate hostSAP WDSAP WD Run and connect the nZDM GUI/CLI tothe source (production) systemJava SCSJava SCSJava ERSJava ERSDatabaseDatabase Use the nZDM GUI/CLI to start nZDMrecordingOriginal system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Public9
nZDM Java in a Cluster SetupCluster clone: Create targetnZDMGUI / CLIUptimeJava AS Clone the source system Isolate and start the clone as thetarget systemJava ASnZDM serviceSAP WDSAP WDSAP WDSAP WDJava SCSJava SCSJava SCSJava SCSJava ERSJava ERSJava ERSJava ERSDatabaseDatabaseDatabaseDatabaseOriginal system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Target system (isolated)Public10
nZDM Java in a Cluster SetupCluster clone: Prepare targetnZDMGUI / CLIUptime Preform planned maintenanceactivities on the target system Connect the nZDM GUI/CLI to thetarget system and start nZDMreplication Prepare/wait for system downtimeJava ASJava ASnZDM servicenZDM serviceSAP WDSAP WDSAP WDSAP WDJava SCSJava SCSJava SCSJava SCSJava ERSJava ERSJava ERSJava ERSDatabaseDatabaseDatabaseDatabaseOriginal system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Target system (isolated)Public11
nZDM Java in a Cluster SetupCluster clone: Switch systemsnZDMGUI / CLIDowntimeJava ASJava AS Choose to finish the nZDMprocedure Stop the target system when nZDMreplication is complete Remove isolation of the target andstart it as the new productionsystemnZDM serviceSAP WDSAP WDSAP WDSAP WDJava SCSJava SCSJava SCSJava SCSJava ERSJava ERSJava ERSJava ERSDatabaseDatabaseDatabaseDatabase End of downtimeOriginal system (stopped) 2016 SAP SE or an SAP affiliate company. All rights reserved.Target system (isolated)Public12
nZDM Java in a Cluster SetupCluster clone: PostprocessingUptimeJava AS Revert any changes done to makethe system run in “Business Only”modeSAP WDSAP WDJava SCSJava SCSJava ERSJava ERSDatabaseDatabaseUpgraded system (HA/DR) 2016 SAP SE or an SAP affiliate company. All rights reserved.Public13
nZDM Java in a Cluster SetupCluster 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.Public14
nZDM Java in a Cluster SetupMaintenance activities: Software Update Manager (SUM Java)Maintenance activities with SUM JavaSoftware Update Manager is the SAP toolfor maintenance of SAP NetWeaver-basedsystems 2016 SAP SE or an SAP affiliate company. All rights reserved.Public15
nZDM Java in a Cluster SetupSUM Java procedure: Supported maintenance activitiesUP 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.Public16
nZDM Java in a Cluster SetupSUM 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-startprocedure of instances Reduced downtime 2016 SAP SE or an SAP affiliate company. All rights reserved.Public17
Thank youContact 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 affiliatecompany) in Germany and other countries. Please see ht/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 itsaffiliated 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 andservices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting 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 developor release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible futuredevelopments, 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 timefor 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 placeundue 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.Public19
Week 2 Unit 4: End-to-End nZDM –Java Procedure Execution
End-to-End nZDM – Java Procedure ExecutionDemo 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.Public2
End-to-End nZDM - Java Procedure ExecutionDemo set-up: Cluster clone nZDM Java GUILandscape ViewnZDM GUISource SystemTarget System Source system Target system Start recording Landscape view 2016 SAP SE or an SAP affiliate company. All rights reserved.Public3
Thank youContact 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 affiliatecompany) in Germany and other countries. Please see ht/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 itsaffiliated 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 andservices are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting 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 developor release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible futuredevelopments, 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 timefor 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 placeundue 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.Public5
Week 2 Unit 5:Troubleshooting & Wrap-Up
Troubleshooting & Wrap-UpSummary nZDM minimizes business downtime duringmaintenance of SAP NetWeaver Java-based products It enables availability of business-critical functionalityduring maintenanceJava ASnZDM servicenZDMGUI / CLIJava ASnZDM service Downtime – around one system restart Flexible, clone-based procedureJava SCSJava SCSDatabaseDatabaseSource systemTarget system (isolated) SAP Landscape Management, cloud virtualization SWPM (system copy scenario) Integration with SAP Landscape Management, CMDinterface nZDM allows preliminary testing of updated clonedsystem during uptime 2016 SAP SE or an SAP affiliate company. All rights reserved.Public2
Troubleshooting & Wrap-UpnZDM Java GUI If Java GUI loses connection, it tries toreconnect automatically If auto reconnection fails or you need to closethe GUI, restart it and manually reconnect no impact on the nZDM Java procedureexecution If the GUI loses connection during thefinalization of the procedure, you have to enterthe same connection data for the sourcesystem as for the target system 2016 SAP SE or an SAP affiliate company. All rights reserved.Public3
Troubleshooting & Wrap-UpLogs All messages from the nZDM Java procedure arestored in defaultTrace number .trc andapplications number .log files They are located at: Drive :\usr\sap\ SID \ instance name \ Jxx orJCxx \cluster\server0\log Check the latest defaultTrace number .trc andapplications number .log files for each systeminstance. This is valid for the source system andthe target system, if the latter has already beencreated 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.Public4
Troubleshooting & Wrap-UpFurther analysis – DB tablesTo perform further analysis, you can also check the followingdatabase 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.Public5
Troubleshooting & Wrap-UpRecording vs replication errorsRecording errors: Fatal to the nZDM Java procedure Recording in the source system is aborted You have to reset the nZDM Java procedure andstart over from the beginningReplication errors: Non-fatal Replication is stopped Might be able to resolve the issue and resumethe replication In the worst case, your target system might beunusable If this is the case, you have to create a newtarget system and repeat all steps from that point 2016 SAP SE or an SAP affiliate company. All rights reserved.Public6
Troubleshooting & Wrap-UpResetting the nZDM Java procedure Connect the nZDM Java
SAP NetWeaver 7.4 SAP NetWeaver 7.5 SAP Business Process Management (SAP BPM) SAP NetWeaver 7.3, SP7 or higher SAP NetWeaver 7.3 EHP 1, SP2 or higher SAP NetWeaver 7.4 SAP NetWeaver 7.5 SAP Process Orchestration (SAP PRO) SAP NetWeaver 7.3 EHP 1, SP2 or higher SAP NetWeaver 7.4 SAP
