Technical Details + Process Flow – System Rename

Part of Software Provisioning Manager 1.0 SP 19

SAP SE – Product Management

February 2017 Public
Disclaimer

This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.

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

Introduction

The system rename procedure got integrated into Software Provisioning Manager 1.0 –
the procedure is no longer available as standalone tool

Overall, Software Provisioning Manager 1.0 offers relevant procedures required to install, copy,
and transform SAP systems in your landscape

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

System rename
Overview
Customer situation
 You want to rename an existing SAP system, such as for changing a physical host name to a virtual host name or
for changing the SAP system ID

 You want to rename an SAP system created as homogeneous copy of a source system:
– Many system landscape administrators copy existing SAP NetWeaver based systems for various reasons
– There are different tools and ways to perform this – system rename enables a faster alternative to the classical system copy procedure
– Copy methods supported by system rename:
o Systems created by using backup or restore with procedures offered by Microsoft Windows
o Systems created by using SAP Landscape Management
o Systems provided as virtual appliance
o Cloned systems (virtual to virtual, virtual to physical, or physical to virtual)
o UNIX only: SAP system created as copy of file system and database of source system

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

System rename
Changes with Software Provisioning Manager 1.0 SP 19
General
 Improved documentation in the parameter file for unattended execution mode of Software Provisioning Manager
– Software Provisioning Manager provides a more stable and more easily maintainable input format for unattended provisioning procedures
– See also SAP Note 2230669 - System Provisioning Using a Parameter Input File

 New platform versions (OS/DB) enabled and platform-specific improvements

– Support for SAP NetWeaver 7.50 and SAP NetWeaver 7.51 based Products with SAP HANA for Linux on IBM Power Systems le (little endian)
o For more information, see SAP Note 2378874 - Install SAP Solutions on Linux on IBM Power Systems (little endian)
– Support for IBM DB2 for z/OS Call Level Interface (CLI) failover feature

 Consistency Check for Software Provisioning Manager Data units

– With Software Provisioning Manager 1.0 SP19, the integrity of the files in the Software Provisioning Manager package is validated
– If files from a different package are used e.g. from older Software Provisioning Manager packages, a Pop-Ups will occur

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

System rename
Changes with Software Provisioning Manager 1.0 SP 19
System Copy
 Refresh Database Content without reinstalling the database or Kernel for ABAP systems for SAP HANA, Oracle, SAP ASE, MS SQL Server
and IBM DB2 (for z/OS, for i, for Linux, UNIX, and Windows)
– Using this option in the installer you can refresh the content of an existing database without having to copy the primary application server instance and without having
to reinstall additional applications servers
– “Refresh Database Content” is recommended if you need to equalize the database content of two or more already existing and configured systems, for example in
automatized system landscapes with “template” systems which have to correspond to precisely defined standards, such as predefined host names, network settings,
users or security policies
– This is a “Lightweight” functionality compared to the old version with the installation of a DB instance
– With this functionality no separate media with the database content is necessary for a system copy
– You can now also refresh the content of an existing database using a database backup
– If your SAP system is based on SAP NetWeaver 7.3 or higher, this functionality can be used, independent of the SAP Product you are using

 ABAP System Copy export with a separate Kernel is now possible

– The kernel of the system that is copied, does not need to be replaced
– During the define parameters phase of the source system export, you can now specify dedicated SAP kernel archives that you want to use for the system copy
– Using this feature, you no longer have to do kernel updates in your systems just to be able to copy the system
– Instead, the installer provides you the option to use a different kernel for the purpose of system copy

 Option to restrict access to the Database Export file

– When running the database export, you can specify restricted access to the export directory
– E.g. it can now be specified that only the user <sapsid>adm executing the export has permission to read and modify the database export file

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

System rename
Two execution options

1 Integrated in easy, fast, and reliable end-to-end system copy and refresh procedure of
SAP Landscape Management (fka SAP Landscape Virtualization Management) – “dark-mode” execution
 For more information, see the SAP Landscape Management product page
 SAP recommends to regularly check for updates and download latest Support Package of system rename to profit
from latest corrections! Latest when you patch SAP Landscape Management, also update system rename to the
latest version!

2 Standalone directly in Software Provisioning Manager for other supported rename use cases –
execution with dialogs
 For more information, see next slides

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

System rename
1. Download: tool

You download latest version of Software Provisioning Manager 1.0 from SAP Support Portal at:
support.sap.com/sltoolset

Choose the archive for your release and operating system version (for more information,
see SAP Note 1680045) – for example:
 If your system is based on SAP NetWeaver 7.0x and your OS is not supporting SAP Kernel 740, use the archive
RMOS70SWPM10SP<SP number>_<patch level>*.SAR
 If your system is based on SAP NetWeaver 7.1x and higher and your OS is not supporting SAP Kernel 740, use the archive
RMOSSWPM10SP<SP number>_<patch level>*.SAR

SAP recommends that you download latest version of Software Provisioning Manager 1.0,
as it contains latest corrections and is updated regularly – even if you have installation media available!

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

System rename
1. Download: documentation

You download latest version of documentation, also from SAP Support Portal at:

http://support.sap.com/sltoolset  Documentation –
there are separate guides for every use case:
• Download the System Rename Guide

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

System rename
2. Plan

You check constraints and released use cases listed in System Rename Guide

You check the product version and platform coverage

 See product availability matrix of SL Toolset in the SAP Support Portal at: http://support.sap.com/pam
 System rename procedure released for the following product versions:
– Products based on SAP NetWeaver 7.0x and higher
– For more details, see SAP Note 1619720

You read the SAP Note that contains latest information:

 System rename: SAP Note 1619720

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

System rename
3. Prepare

You perform preparation tasks as described in guide

 Mount the file system
 Delete dialog instances (as they get not handled by the system rename procedure)
 Perform database-specific preparations

You unpack the Software Provisioning Manager 1.0 archive:

 Make sure latest version of SAPCAR archiving tool is available on each host where you want to run
Software Provisioning Manager
– Available in SAP Support Portal at: http://support.sap.com/swdc  Software Downloads  Search for SAPCAR
– For more information about SAPCAR, see SAP Note 212876

 Unpack Software Provisioning Manager 1.0 archive to a local directory using the following command:
SAPCAR –xvf <download directory>/<path>/<Archive>.SAR -R <unpack directory>

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

System rename
4. Execution

You start as described in the documentation:

 For example, double-click sapinst.exe from directory to which you unpacked the archive on Microsoft Windows
 Welcome screen offers services for several product versions and database types

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

System rename
4. Execution

You choose the service you want to execute:

 On Welcome screen, choose System Rename  <Central or Distributed System or liveCache>  <Service>

You follow the instructions on the screens

 Enter required parameters as described in the documentation

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

System rename
4. Execution

After the procedure finished, the success dialog of software provisioning manager offers a
link to statistical runtime data + direct feedback to SAP
 By clicking, evaluation form is opened in your Web browser
– Send button  anonymous statistical runtime data of executed
service sent to SAP; optionally, you can provide additional
feedback
– Full transparency what information is sent (see Process XML field)
– Data is sent via email

 This data is used by SAP to build anonymous analytical database

– Concerning used processes and runtimes on different platforms
– Will help SAP to prioritize and address the right topics
– In the future, might enable us to make predictions concerning runtimes

 For more information, see this blog in SAP Community Network

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

System rename
5. Follow-up activities

You perform follow-up activities as described in System Rename Guide – for example:
 Perform suitable follow-up activities that are also required after a system copy
 Perform database-specific follow-up activities
 Re-install any deleted dialog instances

After successful execution of your project, you remove tool from host
 For a new project, download the latest version of system rename 1.0

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

System rename
Available via the Software Logistics Toolset 1.0 (SL Toolset)

System rename procedure is offered by Software Provisioning Manager 1.0, it is no longer offered standalone

Software Provisioning Manager 1.0 is delivered in regular intervals, independent from SAP application product
shipments via Software Logistics Toolset, a central collection of software logistics tools, always up to date:
 SL Toolset is the central place in SMP download area to find & download SL tools
 Toolset and tools updated regularly, product-independent, downward-compatible
 Updates include new tools as well as recent improvements & enhancements

For more information and download, see SAP Support Portal at:
http://support.sap.com/sltoolset (incl. direct download links for comprised tools)

SAP recommends that you regularly check for updates and download the latest Support Package
of the tool to profit from latest corrections!
For the integrated use case, SAP recommends to download new version latest with update of
SAP Landscape Management
© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 16
Further information

For more information on Software Provisioning Manager 1.0:

 SAP Release Note: SAP Note 1680045
 Software Provisioning Manager 1.0 in SAP Community Network

For more information on system rename:

 System Rename Guide in SAP Support Portal at http://support.sap.com/sltoolset
 SAP Note 1619720
 System Rename in SAP Community Network

For more information on Software Logistics Toolset:

 Blog in SAP Community Network
 SAP Support Portal at http://support.sap.com/sltoolset

For more information on SAP Landscape Management:

 SAP Landscape Management product page

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

SAP Idea Place
Influence the future of software logistics
 SAP Idea Place is your public channel to participate in innovation at SAP
 Enables you to submit ideas, collaborate on and vote for ideas,
and connect with the teams that are responsible for software logistics procedures
 Complements traditional channels of interaction and feedback at SAP
 Contribute under https://ideas.sap.com/softwarelogistics

© 2017 SAP SE or an SAP affiliate company. All rights reserved. Public 18

Thank you

Contact information:

Stefan Jakobi
SAP SE – Product Management for Cloud and Lifecycle Management
stefan.jakobi@sap.com

© 2017 SAP SE or an SAP affiliate company. All rights reserved.