Technical Details - System Rename Procedure of Software Provisioning Manager 1.0
Get technical details about how you can easily change the hostname, instance number, or system ID (SAP system ID or database system ID) of an existing SAP system based on SAP NetWeaver with the system rename procedure of software provisioning manager 1.0. Download the Document
Get technical details about how you can easily change the hostname, instance number, or system ID (SAP system ID or database system ID) of an existing SAP system based on SAP NetWeaver with the system rename procedure of software provisioning manager 1.0. SAP SE – Product Management
February 2017
Technical Details + Process Flow – System Rename
Part of Software Provisioning Manager 1.0 SP 19
Public
February 2017
Technical Details + Process Flow – System Rename
Part of Software Provisioning Manager 1.0 SP 19
Public
© 2017 SAP SE or an SAP affiliate company. All rights reserved. 2Public
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.
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. 3Public
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
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. 4Public
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
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. 5Public
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
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
System rename
Changes with Software Provisioning Manager 1.0 SP 19
© 2017 SAP SE or an SAP affiliate company. All rights reserved. 6Public
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
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