Operations Guide | PUBLIC Software Provisioning Manager 1.0 SP32 Document Version: 3.3 – 2021-06-21
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows company. All rights reserved. affiliate
THE BEST RUN 2021 SAP SE or an SAP © Content
1 About this Document...... 7 1.1 Use Cases of System Rename...... 8 1.2 How to Use this Guide...... 9 1.3 About Software Provisioning Manager 1.0...... 9 1.4 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Rename Using Software Provisioning Manager 1.0 ...... 10 1.5 Naming Conventions...... 11 1.6 New Features...... 12 1.7 Constraints...... 14 1.8 SAP Notes for the System Rename...... 16 1.9 Accessing the Installation Guides and System Copy Guides...... 17 1.10 Accessing the SAP Library...... 17
2 Planning...... 18
3 Preparation...... 20 3.1 Preparation Checklist...... 20 3.2 Maintaining Users and Groups...... 21 3.3 Deleting Additional Application Server Instances...... 21 3.4 Database-Specific Preparation...... 22 Performing Preparation Steps for IBM Db2 for Linux, UNIX, and Windows...... 23 Performing IBM Db2 for z/OS – Specific Preparation Steps...... 25 Performing Oracle-Specific Preparation Steps...... 27 Performing Microsoft SQL Server-Specific Preparation Steps...... 28 Performing SAP ASE -Specific Preparation Steps...... 29 Performing SAP MaxDB-Specific Preparation Steps...... 29 Performing SAP MaxDB liveCache-Specific Preparation Steps ...... 30 Performing SAP MaxDB liveCache Client-Specific Preparation Steps ...... 31 Performing SAP HANA Database-Specific Preparation Steps...... 32 3.5 Required User Authorization for Running the Installer...... 32 3.6 Changing the Windows Domain...... 34 Requirements...... 34 Preparing SAP System Hosts for System Rename with Windows Domain Change...... 36 Procedure for System Rename with Windows Domain Change...... 36 3.7 Preparing the System Rename Media...... 37 Downloading and Extracting the Software Provisioning Manager 1.0 Archive...... 38 3.8 Preparing the File System...... 39
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 2 PUBLIC Content 4 System Rename Procedure...... 40 4.1 System Rename Procedure Checklist...... 40 4.2 Prerequisites for Running the Installer...... 41 4.3 Running the Installer...... 42 4.4 Additional Information about the Installer...... 46 Useful Information about the Installer...... 47 System Provisioning Using a Parameter Input File...... 48 Interrupted Processing of the Installer...... 52 Troubleshooting with the Installer...... 55 Using the Step State Editor (SAP Support Experts Only)...... 56
5 Follow-Up Activities...... 58 5.1 Follow-Up Activities Checklist...... 58 General Follow-Up Activities...... 59 Database-Specific Follow-Up Activities...... 59 Starting the SAP System...... 63 Configuring the Transport Management System...... 64 Changing the IGS Destination...... 64
6 Additional Information...... 65 6.1 Performing a Domain Installation Without Being a Domain Administrator...... 65 6.2 Implementing Oracle Database Vault with Software Provisioning Manager 1.0...... 66 6.3 Support of Oracle Transparent Data Encryption (Oracle TDE)...... 67 6.4 Using PowerShell...... 69
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Content PUBLIC 3 Document History
Note
Before you start reading, make sure you have the latest version of this system rename guide, which is available at https://support.sap.com/sltoolset System Provisioning Rename a System using Software Provisioning Manager Rename Option of Software Provisioning Manager 1.0 SP
The following table provides an overview on the most important document changes:
Version Date Description
3.3 2021-06-21 Updated version for Software Provisioning Manager 1.0 SP32 (SL Toolset 1.0 SP32)
3.2 2021-02-15 Updated version for Software Provisioning Manager 1.0 SP31 (SL Toolset 1.0 SP31)
3.1 2020-10-05 Updated version for Software Provisioning Manager 1.0 SP30 (SL Toolset 1.0 SP30)
3.0 2020-06-08 Updated version for Software Provisioning Manager 1.0 SP29 (SL Toolset 1.0 SP29)
2.9 2020-01-20 Updated version for Software Provisioning Manager 1.0 SP28 (SL Toolset 1.0 SP28)
2.8 2019-09-16 Updated version for Software Provisioning Manager 1.0 SP27 (SL Toolset 1.0 SP27)
● New Features: ○ Oracle 18 c or higher: Support of Transparent Data Encryption (TDE), docu mented in: New Features, SAP System Database Parameters, Support of Oracle Transparent Data Encryption ( Oracle TDE)
2.7 2019-05-27 Updated version for Software Provisioning Manager 1.0 SP26 (SL Toolset 1.0 SP26)
2.6 2019-01-21 Updated version for Software Provisioning Manager 1.0 SP25 (SL Toolset 1.0 SP25)
2.5 2018-09-17 Updated version for Software Provisioning Manager 1.0 SP24 (SL Toolset 1.0 SP24)
2.4 2018-05-07 Updated version for Software Provisioning Manager 1.0 SP23 (SL Toolset 1.0 SP23)
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 4 PUBLIC Document History Version Date Description
2.3 2018-01-15 Updated version for Software Provisioning Manager 1.0 SP22 (SL Toolset 1.0 SP22)
● New Features: ○ Installer Log Files Improvements, documented in: New Features, Useful Informa tion about the Installer, Troubleshooting with the Installer ○ Secure ABAP message server connection, documented in: New Features, SAP System Parameters ○ Enabling IPv6, documented in: New Features, Prerequisites for Running the Instal ler ● New Features section restructured: As of SP22, a dedicated subsection for each new SP has been created. New features below SP22 remain in a common table. ● The Java SDT GUI - which was in the SP21 version still available in parallel to the SL Common GUI - has been deprecated with SP22. As of SP22, SL Common GUI is the only available installer GUI: ○ The following sections which were explicitely related to Java SDT GUI were com pletely removed from this documentation: Performing a Remote Installation Re mote Processing of the Installer ( Java SDT GUI only), Starting the Java SDT GUI Separately, Running the Installer in Accessibility Mode (general accessibility infor mation was moved to Useful Information About the Installer). ○ The Java SDT GUI-specific information was removed from the common installer sections: Running the Installer, Useful Information About the Installer, Interrupted Processing of the Installer, Troubleshooting with the Installer ● New section Using the Step State Editor (SAP Support Experts Only) was added to section Additional Information About the Installer
2.2 2017-09-11 Updated version for Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21)
● New Features: ○ Media Signature Check, documented in: New Features, Running the Installer, Pre paring the System Rename Media . ○ Load tools are now available as LOADTOOLS.SAR in the Software Provisioning Manager archive, documented in: New Features, Downloading and Extracting the Software Provisioning Manager Archive ○ Simplified additional application server instance installation, documented in: New Features, Preparing the Installation Media, Downloading SAP Kernel Archives (Archive-Based Installation)
2.1 2017-05-22 Updated version for Software Provisioning Manager 1.0 SP20 (SL Toolset 1.0 SP20)
● New Features: ○ New SAPUI5-based graphical user interface (GUI) “SL Common GUI”, docu mented in: Prerequisites for Running the Installer, Running the Installer, Useful In formation About the Installer
2.0 2017-02-06 Updated version for Software Provisioning Manager 1.0 SP19 (SL Toolset 1.0 SP19)
● New Features: Verification of the integrity of data units in Software Provisioning Manager, docu mented in: New Features, Downloading the Software Provisioning Manager Archive
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Document History PUBLIC 5 Version Date Description
1.9 2016-10-07 Updated version for Software Provisioning Manager 1.0 SP18 (SL Toolset 1.0 SP18)
1.8 2016-06-06 Updated version for Software Provisioning Manager 1.0 SP17 (SL Toolset 1.0 SP17)
1.7 2016-02-15 Updated version for Software Provisioning Manager 1.0 SP10 (SL Toolset 1.0 SP16)
1.61 2015-11-13 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP15)
1.6 2015-10-12 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP15)
1.5 2015-09-14 Updated version for Software Provisioning Manager 1.0 SP09 (SL Toolset 1.0 SP14)
1.4 2015-04-27 Updated version for Software Provisioning Manager 1.0 SP08 (SL Toolset 1.0 SP13)
1.3 2014-11-24 Updated version for Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12)
1.2 2014-07-07 Updated version for Software Provisioning Manager 1.0 SP06 (SL Toolset 1.0 SP11)
1.1 2014-03-17 Updated version for Software Provisioning Manager 1.0 SP05 (SL Toolset 1.0 SP10 )
1.0 2013-10-28 Initial version
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 6 PUBLIC Document History 1 About this Document
This document describes how to rename SAP systems using the Software Provisioning Manager 1.0 SP32 (“installer” for short), which is part of SL Toolset 1.0 SP32. It is valid for SAP systems based on Application server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows .
Note
Application Server ABAP based on SAP NetWeaver 7.10, 7.11, 7.20, 7.30, 7.40 SR1 are supported in mainstream maintenance only until the end of 2020. Extended maintenance will not be provided.
For more information, see SAP Note 2980160 .
You can download the last published version of the guide set for the last Software Provisioning Manager 1.0 SP30 for out-of-maintenance products (SWPM10RMSP30_
For information about SAP system products and releases covered by this guide, see SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Rename Using Software Provisioning Manager 1.0 [page 10].
For information about Software Provisioning Manager 1.0, see About Software Provisioning Manager 1.0 [page 9].
For information about supported operating system and database platforms, see the Product Availability Matrix at https://support.sap.com/pam .
Note
As an alternative to using Software Provisioning Manager, you can rename your system with a completely automated end-to-end framework available using SAP Landscape Management. For more information, see SAP Note 1709155 and https://help.sap.com/lama .
Caution
You should only perform a system rename using the Software Provisioning Manager 1.0 if your SAP system is installed with standard SAP tools according to the documentation available at https://support.sap.com/ sltoolset System Provisioning .
Any deviations from this documentation are at your own risk. Be aware that additional consulting effort might be necessary.
Related Information
Use Cases of System Rename [page 8]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 7 About Software Provisioning Manager 1.0 [page 9] Naming Conventions [page 11] New Features [page 12] Constraints [page 14] SAP Notes for the System Rename [page 16] Accessing the SAP Library [page 17] How to Use this Guide [page 9]
1.1 Use Cases of System Rename
This section describes which system parameters you can adapt using system rename.
You can adapt one or more of the following parameters of an SAP system using the system rename procedure:
● SAP system ID (
You can rename the following SAP systems:
● Systems installed by using the standard SAP tools. ● Systems copied by using classical system copy (R3load/Jload or DB-specific procedure). ● Systems created by using backup or restore with procedures offered by Microsoft Windows ● Systems created by using SAP Landscape Management ● Cloned systems (virtual to virtual, virtual to physical, or physical to virtual)
Note
For production systems, the rename procedure should only be performed by experienced system administrators or consultants and should be tested beforehand – especially for the conversion of logic system names, the corresponding aspects outlined in SAP Note 121163 have to be considered.
More Information
For more information about offerings, methods, use cases and technical details of the system rename procedure, see http://scn.sap.com/docs/DOC-32851 .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 8 PUBLIC About this Document 1.2 How to Use this Guide
This documentation comprises the description of the system rename procedure and system rename-specific steps.
Context
For general installation or system copy-specific information, see the installation or system copy guides [page 17].
Procedure
1. You decide on the system parameters you want to change in the rename process. For more information, see Use Cases of System Rename [page 8]. 2. You follow the steps in each phase: ○ Planning [page 18] ○ Preparation [page 20] ○ Renaming [page 40] ○ Follow-Up Activities [page 59]
1.3 About Software Provisioning Manager 1.0
Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of provisioning tools, such as “SAPinst”. We strongly recommend that you always download the latest version of Software Provisioning Manager 1.0. Software Provisioning Manager 1.0 is part of the Software Logistics Toolset 1.0 (“SL Toolset” for short). This way, you automatically get the latest fixes and supported processes. For more information about Software Provisioning Manager as well as products and releases supported by it, see SAP Note 1680045 and http://scn.sap.com/docs/DOC-30236 .
“SAPinst” has been renamed to “Software Provisioning Manager” (“installer” for short) in this documentation, but the terms “SAPinst” and “sapinst” are still used in:
● The name of the technical framework of Software Provisioning Manager. For more information about the SAPinst Framework, see SAP Note 2393060 . ● Texts and screen elements in the Software Provisioning Manager GUI (SL Common GUI) ● Names of executables, for example sapinst.exe ● Names of command line parameters, for example SAPINST_HTTPS_PORT
In the following, we generally refer to Software Provisioning Manager 1.0 as the “installer”. We only use the term “Software Provisioning Manager 1.0” if this is required for technical reasons.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 9 Related Information
Preparing the System Rename Media [page 37]
1.4 SAP Products Based on SAP NetWeaver 7.3 EHP1 to 7.52 Supported for System Rename Using Software Provisioning Manager 1.0
Here you can find a list of SAP products based on SAP NetWeaver 7.3 EHP1 to 7.52 ABAP that are supported for system rename using Software Provisioning Manager 1.0, on the specific operating system and database combination described in this guide.
SAP Product Based on the following SAP NetWeaver Release
SAP S/4HANA 1709 SAP NetWeaver AS for ABAP 7.52 ● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
foundation 1709 on SAP NetWeaver Application Server for SAP NetWeaver AS for ABAP 7.52 ABAP 7.52, version for SAP HANA
SAP NetWeaver AS for ABAP 7.52 SAP NetWeaver AS for ABAP 7.52
SAP S/4HANA 1610 SAP NetWeaver AS for ABAP 7.51 innovation package
● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
SAP NetWeaver AS for ABAP 7.51 innovation package SAP NetWeaver AS for ABAP 7.51 innovation package
SAP S/4HANA on-premise edition 1511 Server Support Re SAP NetWeaver 7.5 lease 1
SAP S/4HANA on-premise edition 1511 Support Release 1 SAP NetWeaver 7.5 ● SAP S/4HANA Server ● AS ABAP for SAP S/4HANA Frontend
SAP Business Suite 7i 2016: SAP NetWeaver 7.5
● EHP4 for SAP CRM 7.0 ABAP SAP NetWeaver 7.4 Support Release 2 ● EHP8 for SAP ERP 6.0 ABAP SAP NetWeaver 7.3 EHP1 ● EHP8 for SAP ERP 6.0 ABAP including SAP S/4HANA Finance 1605 SP03 ● EHP4 for SAP SRM 7.0 ABAP ● EHP4 for SAP SCM 7.0 ABAP
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 10 PUBLIC About this Document SAP Product Based on the following SAP NetWeaver Release
SAP BW/4HANA 1.0 SAP NetWeaver 7.5
SAP NetWeaver 7.4 Support Release 2
SAP NetWeaver 7.3 EHP1
SAP Business Suite 7i 2013 Support Release 2: SAP NetWeaver 7.5
● EHP3 for SAP CRM 7.0 ABAP Support Release 2 SAP NetWeaver 7.4 Support Release 2 ● EHP7 for SAP ERP 6.0 ABAP Support Release 2 SAP NetWeaver 7.3 EHP1 ● EHP7 for SAP ERP 6.0 ABAP including SAP Simple Fi nance 1.0 / 1503 ● EHP3 for SAP SRM 7.0 ABAP Support Release 2 ● EHP3 for SAP SCM 7.0 ABAP Support Release 2
SAP NetWeaver 7.5 SAP NetWeaver 7.5
SAP Solution Manager 7.2 Support Release 2 SAP NetWeaver 7.4 Support Release 2
AS ABAP 7.4, OEM version 1.0 SAP NetWeaver 7.4 Support Release 2
SAP NetWeaver 7.4 Support Release 2 SAP NetWeaver 7.4
SAP Business Suite, powered by SAP HANA: SAP NetWeaver 7.3 EHP1
● EHP2 for SAP CRM 7.0 On SAP HANA ● EHP6 for SAP ERP 6.0 On SAP HANA ● EHP2 for SAP SCM 7.0 On SAP HANA
1.5 Naming Conventions
● In this document, we generally refer to Software Provisioning Manager 1.0 as the “installer”. We only use the term “Software Provisioning Manager 1.0” if this is required for technical reasons, for example, if we need to differentiate between Software Provisioning Manager and other installation tools, such as database-specific installers. ● “usage type”, “technical usage”, and “product instance” As of Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces the terms “ usage type” and “technical usage” . ● “SAP system” refers to “SAP NetWeaver system” or “SAP system based on SAP NetWeaver”. “SAP system” also refers to the standalone engines supported for system rename with Software Provisioning Manager 1.0, such as SAP Web Dispatcher, SAP liveCache, and standalone gateway. ● Only valid for Microsoft Failover Clustering: As of Windows Server 2008 the cluster feature is called Failover Clustering. For practical reasons we are continuing to use the previous terminology Microsoft Cluster Service and abbreviation MSCS in some sections of this guide and the corresponding installation documentation of your release.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 11 ● “SAP liveCache” refers to “SAP MaxDB liveCache”. ● “SAP liveCache client” refers to “SAP MaxDB liveCache client”.
1.6 New Features
This section provides an overview of the new features in Software Provisioning Manager 1.0 (the“ installer” for short).
Make sure that you also read the Release Notes for your SAP product at https://help.sap.com
Feature Description Availability
Switch from Kernel 7.21 has reached end of maintenance. In addition, some is Software Provisioning Manager 7.21_EXT Kernel to 1.0 SP31 (SL Toolset 1.0 SP31) sues have been fixed with the new 7.22_EXT kernel media. 7.22_EXT Kernel
Support of SAP Software Provisioning Manager 1.0 supports SAP HANA SSL Cer Software Provisioning Manager HANA SSL Certifi- 1.0 SP29 (SL Toolset 1.0 SP29) tificates for configuring secure access to the SAP HANA data cates base.
For more information, see the installation guide for SAP systems based on SAP HANA [page 17].
Support of Oracle 19 You can now perform all Software Provisioning Manager 1.0 tasks Software Provisioning Manager 1.0 SP28 (SL Toolset 1.0 SP28) (installation, system copy, system rename) for SAP systems with the Oracle 19 database.
For more information, see and https://support.sap.com/pam .
Oracle 18 c or Software Provisioning Manager 1.0 supports Oracle Transparent Software Provisioning Manager higher: Support of 1.0 SP27 (SL Toolset 1.0 SP27) Data Encryption (TDE) for SAP NetWeaver-based systems. For Transparent Data more information, see Support of Oracle Transparent Data En Encryption (TDE) cryption (Oracle TDE) [page 67].
Support of Secure Software Provisioning Manager 1.0 supports configuring the SAP Software Provisioning Manager Connection to SAP 1.0 SP26 (SL Toolset 1.0 SP26) system to be installed to access the SAP HANA database using HANA database. encryption.
For more information, see the installation guide for SAP systems based on SAP HANA [page 17].
New Look and Feel As of version 1.0 SP24 Patch Level (PL) 5, Software Provisioning Software Provisioning Manager of SL Common GUI Manager comes with a new look and feel of the SL Common GUI. 1.0 SP24, PL05 (SL Toolset 1.0 For more information, see https://blogs.sap.com/2018/11/10/ SP24) new-look-for-software-provisioning-manager/ .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 12 PUBLIC About this Document Feature Description Availability
Installer Log Files Installer log files are now available immediately after the installer Software Provisioning Manager Improvements has been started, that is before a product has been selected on 1.0 SP22 (SL Toolset 1.0 SP22) the Welcome screen. For more information, see Useful Informa tion about the Installer [page 47] and Troubleshooting with the Installer [page 55].
Media Signature The signature of media is checked automatically by the installer Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) Check during the Define Parameters phase while processing the Media Browser screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .
For more information, see Preparing the System Rename Media [page 37] and Running the Installer [page 42].
Support of Oracle Software Provisioning Manager (the “installer”) now supports sys Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) 12.2 tem rename for SAP systems with Oracle 12.2.
SL Common GUI With the new installer framework version SAPINST 7.49, you can Software Provisioning Manager with SAPINST 7.49 now use the new SAPUI5-based graphical user interface (GUI) “SL 1.0 SP20 (SL Toolset 1.0 SP20) Common GUI”. For more information, see Useful Information about the Installer [page 47], Running the Installer [page 42].
Verification of Integ The integrity of data units extracted from the Software Provision Software Provisioning Manager rity of Data Units in 1.0 SP19 (SL Toolset 1.0 SP19) ing Manager archive is verified. For more information, see Down Software Provision loading and Extracting the Software Provisioning Manager 1.0 Ar ing Manager chive [page 38] .
In addition, check SAP Note 1680045 whether additional infor mation is available.
System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager for SAP NetWeaver rename) are available for the new SAP NetWeaver 7.5 release. 1.0 SP09 (SL Toolset 1.0 SP15) 7.5 and SAP The Dual Stack option, which integrates an AS ABAP and AS Java NetWeaver 7.5- in a single system (common System ID
● After upgrading to SAP NetWeaver 7.5 PI, you first have to split the still existing dual stack-system before you can use SAP NetWeaver 7.5 PI productively. For more information, see the Upgrade Master Guide - SAP
NetWeaver 7.5 at: http://help.sap.com/nw75 Installation
and Upgrade ● SAP NetWeaver 7.5 is Unicode only ● The primary application server instance directory has been renamed from /usr/sap/
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 13 Feature Description Availability
System Provisioning All system provisioning tasks (installation, system copy, system Software Provisioning Manager for SAP Solution rename) are available for the new SAP Solution Manager 7.2 re 1.0 SP09 (SL Toolset 1.0 SP15) Manager 7.2 lease. Compared to previous SAP Solution Manager releases, SAP Solution Manager 7.2 is no longer provided as a classical dual- stack system (ABAP system with Java Add-in), but consists of a separate ABAP and Java stack.
Feedback Evaluation SAP SE’s aim is to provide fast and efficient procedures. To evalu Software Provisioning Manager Form ate the procedure you just carried out, we need information gen 1.0 SP07 (SL Toolset 1.0 SP12) erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques tionnaire and XML data generated during the procedure.
Port 4239 is used for displaying the feedback evaluation form. For more information, see Prerequisites for Running the Installer [page 41].
Option Verify Signed The digital signature ensures that the signatory of a digital docu Software Provisioning Manager Media ment can be identified unambiguously and signatory’s name is 1.0 SP06 (SL Toolset 1.0 SP11) documented together with the signed document, the date, and the time.
For more information, see SAP Note 1979965 .
1.7 Constraints
● SAP NetWeaver 7.3 on SAP HANA is only supported for BW. For more information, see SAP Note 1600929 . ● System Rename is only supported for SAP systems based on SAP NetWeaver 7.0 and higher: SAP ERP 6.0 and higher, SAP CRM 7.0 and higher, SAP SRM 7.0 and higher, SAP SCM 7.0 and higher. For a detailed list of all supported SAP system products and releases, see SAP Note 1619720 . For information about supported operating system and database platforms, see the Product Availability Matrix at https://support.sap.com/pam . ● As for renaming standalone engines and clients using Software Provisioning Manager 1.0, only SAP Web Dispatcher, SAP liveCache, and standalone gateway are supported and documented in this guide. If you want to rename other standalone engines or clients, you have to reinstall them from scratch. For more information, see https://support.sap.com/sltoolset System Provisioning Install a System using Software Provisioning Manager Installation Option of Software Provisioning Manager 1.0 SP
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 14 PUBLIC About this Document ● SAP System ID
Note
MS SQL Server only:
The
Make sure that your database ID: ○ Is unique throughout your organization ○ Consists of exactly three alphanumeric characters ○ Contains only uppercase letters ○ Has a letter for the first character ○ Does not include any of the reserved IDs listed in SAP Note 1979280 . ● System rename is not supported for high-availability systems. ● SAP systems with SAP HANA database: You can use Software Provisioning Manager (the “installer”) only for renaming the application server instances, and the ABAP central services instance . You cannot use the installer for renaming the SAP HANA database. If you want to rename the SAP HANA database, you have to do this as a separate step in advance, using SAP HANA database-specific tools. See also SAP HANA Database-Specific Preparation Steps [page 32]. ● For a comprehensive list of supported operating system and database releases, see the Product Availability Matrix (PAM) at https://support.sap.com/pam . Search for SL Toolset and then check the system rename-specific information.
Database-Specific Restrictions
Oracle Database
● System Rename is only partially supported for ASM database installations System Rename does only partly work for an Automatic Storage Management (ASM) installation of the Oracle database. You cannot use system rename to change the
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 15 IBM Db2 for Linux, UNIX, and Windows
IBM Db2 for Linux, UNIX, and Windows versions lower than 9.7 are not supported
SAP MaxDB
System Rename is not supported for SAP MaxDB versions lower than 7.8
If you try to rename an SAP system with an SAP MaxDB version lower than 7.8, several errors are reported.
There is no workaround to overcome this restriction. Instead, you first have to upgrade to SAP MaxDB version 7.8 or 7.9. For more information about the upgrade, see SAP Notes 1353266 or 1492467 , depending on your SAP MaxDB target release.
SAP HANA
Rename of the SAP HANA database schema is not supported.
You can only rename the DBSID of the SAP HANA database, but you cannot rename the schema of the SAP HANA database.
IBM Db2 for Linux, UNIX, and Windows
Rename of the IBM Db2 for Linux, UNIX, and Windows database schema is not supported.
More Information
For more constraints, see SAP Note 1619720 .
1.8 SAP Notes for the System Rename
Read the following SAP Notes before you start the system rename procedure. These SAP Notes contain the most recent information on system rename as well as corrections to the relevant documentation. Make sure that you have the most recent version of each SAP Note.
.
SAP Notes for System Rename
SAP Note Number Title Description
1680045 Release Note for Software Provisioning Software provisioning manager 1.0 with Manager 1.0 installation, system copy, system re name and dual-stack split for SAP NetWeaver-based systems
1619720 System Rename for SAP Systems Problems discovered after the publica based on SAP NetWeaver tion of the System Rename guide
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 16 PUBLIC About this Document 1.9 Accessing the Installation Guides and System Copy Guides
The references to the “installation guide” and “system copy guide” in this system rename guide always refer to the following location on the SAP Support Portal, where you can access or download the installation guide and the system copy guide for your operating system platform, database, and technical stack:
● The “ installation guide” for your operating system platform and database at: https://support.sap.com/sltoolset System Provisioning Install a System using Software Provisioning Manager Installation Option of Software Provisioning Manager 1.0 SP
1.10 Accessing the SAP Library
The references to the SAP NetWeaver Library documentation in this guide always refer to the following on SAP Help Portal. When you come across a reference to SAP Library documentation in this guide, you always have to add the path of this reference to the basic URL for the SAP NetWeaver release your SAP product is based on, as given in the list below:
● SAP systems based on SAP NetWeaver AS for ABAP 7.52: https://help.sap.com/nw752abap Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver Application Server for ABAP 7.51 innovation package: https://help.sap.com/nw751abap Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver 7.5: http://help.sap.com/nw75 Application Help SAP NetWeaver Library: Function-Oriented View ● SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74 Application Help SAP NetWeaver Library: Function-Oriented View
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows About this Document PUBLIC 17 2 Planning
This section includes the planning steps that you have to perform when you want to rename an SAP system.
● Check the product version and platform coverage using the product availability matrix of SL Toolset in SAP Service Marketplace at: https://support.sap.com/pam ● The system rename procedure is valid for the following environments: ○ ABAP ○ Java ○ Dual-stack (ABAP and Java) ○ SAP Web Dispatcher, SAP liveCache, and standalone gateway. ● You can perform the system rename on both central and distributed systems. ● Make sure that you check requirements and restrictions for the SAP system parameters that you want to rename (see section Basic Installation Parameters in the installation guide [page 17] for your operating system platform and database: ○ SAP system ID ○ Database ID ○ Instance numbers of the instances on the SAP system With the system rename procedure, you can rename the following instances: ○ Database instance ○ Primary application server instance ○ ABAP Central Services instance (ASCS instance) ○ Enqueue Replication Server instance
Note
You cannot use the installer to rename additional application server instances.
If you have installed additional application server instances, you have to do the following: 1. Delete the additional application server instances manually [page 21] from the system before the system rename. 2. Reinstall the additional application server instances on the system after the system rename.
○ Host names ● SAP systems based on AS ABAP 7.40 and higher: You can set an Individual Encryption Key for the Secure Storage. For more information, see section Basic SAP System Installation Parameters in the installation guide [page 17] for your operating system platform and database). ● Users that already exist in the SAP system are not deleted. They are available after the rename of your system. If a required user does not exist, it is created during the system rename procedure. ● Windows Domain Organizational Units You can choose the organizational units (OUs) within the Windows domain where you want to create the SAP system accounts. By default, the installer creates the domain users SAPService
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 18 PUBLIC Planning The OU feature is only available when you select Custom mode in the installer and choose Use Domain of current user. For more information, see SAP Note 2247673 . ● In an SAP SCM system with SAP liveCache, the following components can be renamed: ○ The SAP SCM system ○ The SAP liveCache server ○ The SAP liveCache client The SCM system and the SAP liveCache server can be renamed independently. The SAP liveCache client should be renamed after the SCM system has been renamed but only if the primary database is not SAP MaxDB (see also the prerequisites of section Performing SAP liveCache Client-Specific Preparation Steps [page 31] ). ● Oracle Database only: If your source system to be renamed has Oracle Database Vault, make sure that you have read section Implementing Oracle Database Vault with Software Provisioning Manager 1.0 [page 66].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Planning PUBLIC 19 3 Preparation
3.1 Preparation Checklist
This section includes the preparation steps that you have to perform when you want to rename an SAP system.
1. If you want to change the
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 20 PUBLIC Preparation 3.2 Maintaining Users and Groups
The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. If you do not want the installer to create operating system users and groups automatically, you can choose to create them before running the system rename procedure.
Context
This step is only mandatory if you want to use global accounts that are configured on separate hosts.
In all other cases, this step is optional.
Procedure
1. Log on to your SAP system as described in Running the Installer [page 42].
2. On the Welcome screen, choose System Rename Preparations Operating System Users and Groups 3. Follow the instructions in the input screens and specify the target system IDs (SAP system ID, Database ID) when creating users and groups.
3.3 Deleting Additional Application Server Instances
The system rename procedure does not implicate additional application server instances. Therefore, if additional application server instances are installed on your system, delete them before you start the rename procedure, and reinstall additional application server instances as required after the system rename.
Prerequisites
● You have installed your SAP system with standard SAP tools according to the installation documentation. ● You have made the media available that you used for installing the system on the additional application server instance host that you want to delete.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 21 Context
Note
You cannot delete an additional application server instance remotely. You have to run the tool to delete them locally on each additional application server instance host.
All file systems and subdirectories of the selected additional application server instance are deleted during the uninstall process.
The uninstall process is designed to remove as much of the additional application server instance as possible. If an item cannot be removed, a message informs you that you have to remove this item manually. As soon as you confirm the message, the uninstall process continues.
Procedure
1. Start the tool as described in Running the Installer [page 42].
2. On the Welcome screen, choose
Note
For more information about the input parameters, place the cursor on the relevant field and press F1 .
4. When you have finished, delete the local user group SAP_
a. Choose Start Programs Administrative Tools Computer Management . b. Choose Local Users and Groups Groups . c. Right-click the local group SAP_
3.4 Database-Specific Preparation
You have to do some preparation steps in the database of the system you want to rename.
Make sure you have completed the preparation steps for your database as described in the relevant section below.
Performing Preparation Steps for IBM Db2 for Linux, UNIX, and Windows [page 23] This section describes prerequisites and preparation steps that you have to perform for IBM Db2 for Linux, UNIX, and Windows before starting the system rename procedure.
Performing IBM Db2 for z/OS – Specific Preparation Steps [page 25] This section describes the prerequisites and preparation steps that you have to perform for IBM Db2 for z/OS before starting the system rename procedure.
Performing Oracle-Specific Preparation Steps [page 27]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 22 PUBLIC Preparation This section describes prerequisites and preparation steps that you have to perform for the Oracle database before starting the system rename procedure.
Performing Microsoft SQL Server-Specific Preparation Steps [page 28] This section describes the prerequisites and preparation steps that you have to perform for MS SQL Server before starting the system rename procedure.
Performing SAP ASE -Specific Preparation Steps [page 29] This section describes the prerequisites and preparation steps that you have to perform for SAP ASE before starting the system rename procedure.
Performing SAP MaxDB-Specific Preparation Steps [page 29] This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB before starting the system rename procedure.
Performing SAP MaxDB liveCache-Specific Preparation Steps [page 30] This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) , before starting the system rename procedure.
Performing SAP MaxDB liveCache Client-Specific Preparation Steps [page 31] This section describes the prerequisites and preparation steps that you have to perform for SAP Max DB liveCache client (“SAP liveCache client” for short) , before starting the system rename procedure.
Performing SAP HANA Database-Specific Preparation Steps [page 32] This section describes the prerequisites and preparation steps that you have to perform forSAP HANA database before starting the system rename procedure.
3.4.1 Performing Preparation Steps for IBM Db2 for Linux, UNIX, and Windows
This section describes prerequisites and preparation steps that you have to perform for IBM Db2 for Linux, UNIX, and Windows before starting the system rename procedure.
Prerequisites
● The database instance must be either stopped or - if it is running - there must not be any database connections. During the procedure it will be started and stopped automatically if required. After the preparation it will be stopped. ● The patch level of db6util is patch level 10 or higher. For more information, see SAP Note 1776691 . ● The patch level of the brdb6brt tool is patch level 32 or higher. If tool brdb6brt does not exist within the \sapmnt\
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 23 Make sure that your
Procedure
1. Make sure that the SAP system is stopped. 2. If the user that you use to run the tool does not have the required authorizations to create users and groups, you must create all required groups and users before you start the system rename process. 3. Create the relocate.template file as described below. This file is required in the dialog phase of the tool. All actions have to be performed on the database host of your SAP source system landscape. a. Log on as an administrator on the database host of your source system. b. Create the directory sapdbctrl-config under a temporary directory, for example
Note
If directory \temp does not exist, you have to create it before you perform the steps listed below.
Proceed as follows: 1. Execute cd
Caution
If you run a rename of an already renamed system, you must reboot the system host before starting the second or subsequent renames. Otherwise you get an error message like the following when executing the PrepareDatabaseCopy command:
Error: sapdbctrl: Internal error: HANDLE_SQLCA exception occured! SQLCODE: -1032
Error: saphostcontrol: PrepareDatabaseCopy failed (sapdbctrl exit code = 99)
The system creates the relocate.template file in directory
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 24 PUBLIC Preparation g. Check if the file relocate.template contains one or more entries for CONT_PATH or STORAGE_PATH. If not, you must not start the system rename procedure.
This is an example of the files created in the sapdbctrl-config directory:
C:\temp\sapdbctrl-config > dir
Volume in drive C has no label.
Volume Serial Number is
Directory of C:\temp\sapdbctrl-config
05/31/2012 09:07 AM
05/31/2012 09:07 AM
05/21/2012 01:52 PM 2495 db2ph5.cfg
05/21/2012 01:52 PM 913 db2ph5.net
05/21/2012 01:52 PM 8119 relocate.template
3 File(s) 11527 bytes
2 Dir(s) 119644123136 bytes free
4. Make sure that the contents of the db6_update_db.SAR archive attached to SAP Note 1365982 are available in the sapdbctrl-config directory. 5. Make sure that the SAP system and the database are stopped. You also have to make sure that all SAP and database-related services are offline. Do this by checking if the SAP* and DB2* services are stopped.
Note
Keep all directories at their current locations. The tool will find and move them to the correct directory and set the required ownerships and permissions.
3.4.2 Performing IBM Db2 for z/OS – Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for IBM Db2 for z/OS before starting the system rename procedure.
Context
No rename actions are performed on the database subsystem itself.
There are two types of renaming:
Procedure
● Rename of an SAP system without copying the IBM Db2 for z/OS subsystem: ○ The application server is renamed; no changes are made on the IBM Db2 for z/OS subsystem. ○ The renamed SAP system stays connected to the original IBM Db2 for z/OS subsystem
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 25 Rename of an SAP System without copying the IBM Db2 for z/OS Subsystem ● Rename of an SAP system after copying the IBM Db2 for z/OS subsystem.
Before running the tool , you have to copy your IBM Db2 for z/OS database using the offline system copy method.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 26 PUBLIC Preparation Rename of an SAP System after copying the IBM Db2 for z/OS Subsystem
For more information about the system copy procedure, see the SAP Note 680746 .
3.4.3 Performing Oracle-Specific Preparation Steps
This section describes prerequisites and preparation steps that you have to perform for the Oracle database before starting the system rename procedure.
Procedure
1. If you use one Oracle software installation for more than one SAP system instance installations, make sure that no other Oracle services are running with this ORACLE_HOME software before you start the system rename process. 2. For the offline backup method, we recommend that you shut down the database. Alternatively, the installer can also make an instance recovery of the database if it has not been shut down before the copy process. For the online backup method, you have to set the database to a backup mode and the backup control files and the Oracle archives will be copied to an existing shared directory. You can set the database to a backup mode using the following command:
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 27 saphostctrl -user sapadm
After the database backup has finished, you have to set the database back to a normal mode using the following command:
saphostctrl -user sapadm
It is possible to rename the Oracle database software automatically with the installer when the database software has the same
Example
The Oracle software is under c:\oracle\C11\112 and the Oracle database files are under c: \oracle\C11 and d:\oracle\C11.
The installer moves c:\oracle\C11 to c:\oracle\T11 and d:\oracle\C11 to d:\oracle\T11 with all subdirectories.
If there are database files under the directory that contains the Oracle software and you do not want to move the Oracle software, you have to move the database directory manually.
For more information about how to install the Oracle database software, see the Oracle installation guide of your release and stack at https://support.sap.com/sltoolset System Provisioning Installation Option of Software Provisioning Manager Installation Guides - Application Server Systems .
3.4.4 Performing Microsoft SQL Server-Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for MS SQL Server before starting the system rename procedure.
Procedure
Currently, there are no MS SQL Server-specific preparation steps.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 28 PUBLIC Preparation 3.4.5 Performing SAP ASE -Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for SAP ASE before starting the system rename procedure.
Procedure
Currently, there are no SAP ASE-specific preparation steps.
3.4.6 Performing SAP MaxDB-Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB before starting the system rename procedure.
Procedure
1. Create a database-specific configuration file sapdbConfig.txt, which describes the software of the source system and store it locally on the host.
The database-specific configuration file sapdbConfig.txt for SAP MaxDB 7.8 and higher looks as shown below: ○ Default:
IndepDataPath=c:/sapdb/data
GlobalProgramsPath=c:/sapdb/programs
CL_
○ Distributed installation with the database and the primary application server instance on different hosts. On the primary application server instance host:
IndepDataPath=c:/sapdb/data
GlobalProgramsPath=c:/sapdb/programs
CL_
On the database instance host:
IndepDataPath=c:/sapdb/data
GlobalProgramsPath=c:/sapdb/programs
CL_
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 29 2. Make sure that you shut down the SAP system including the database and that all SAP and SAP MaxDB related services are offline before your start the system rename procedure. To check this, verify that the services Xserver* and MaxDB* are stopped.
3.4.7 Performing SAP MaxDB liveCache-Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) , before starting the system rename procedure.
Procedure
1. Create a database-specific configuration file sapLvcConfig.txt, which describes the software of the source system and store it locally on the host.
Example
SAP MaxDB liveCache 7.9:
If the application server of the SAP system and the SAP liveCache server are on the same host, the content of the configuration file must be as follows:
IndepDataPath=c:\sapdb\data
GlobalProgramsPath=c:\sapdb\programs
CL_
If the SAP liveCache server is on a dedicated server, the content of the configuration file must be as follows:
IndepDataPath=c:\sapdb\data
GlobalProgramsPath=c:\sapdb\programs
SAP MaxDB liveCache lower than 7.9:
IndepDataPath=c:\sapdb\data
GlobalProgramsPath=c:\sapdb\programs
2. Make sure that you shut down the SAP system including the database and the liveCache and that all SAP and SAP liveCache related services are offline before your start the system rename procedure. To check this, verify that the services Xserver* and MaxDB* are stopped. 3. You must start a separate installer run [page 42] for the liveCache rename.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 30 PUBLIC Preparation 3.4.8 Performing SAP MaxDB liveCache Client-Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform for SAP Max DB liveCache client (“SAP liveCache client” for short) , before starting the system rename procedure.
Context
These steps are not required if the SAP liveCache Server is also located on the same host and SAP liveCache Server-specific preparation steps are already done or will be done.
Procedure
1. Create a database-specific configuration file sapLvcClientConfig.txt, which describes the software of the source system and store it locally on the host.
Example
Database-specific configuration file sapLvcClientConfig.txt
IndepDataPath=c:/sapdb/data
GlobalProgramsPath=c:/sapdb/programs
CL_
2. Make sure that you shut down the SAP system including the database and the liveCache and that all SAP and SAP liveCache related services are offline before your start the system rename procedure. To check this, verify that the services Xserver* and MaxDB* are stopped. 3. You must start a separate installer run [page 42] for the liveCache rename.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 31 3.4.9 Performing SAP HANA Database-Specific Preparation Steps
This section describes the prerequisites and preparation steps that you have to perform forSAP HANA database before starting the system rename procedure.
Context
You can use the installer only for renaming the application server instances, and the ABAP central services instance , but you can not rename the SAP HANA database with this tool. If you want to rename the SAP HANA database, you have to do this as a separate step in advance .
Procedure
You perform the rename for the SAP HANA database as described in section Changing the SAP HANA System in the SAP HANA Administration Guide at http://help.sap.com/hana_platform System Administration .
3.5 Required User Authorization for Running the Installer
Although the installer automatically grants the rights required for the installation to the user account used for the installation, you have to check whether this account has the required authorization to perform the installation. The authorization required depends on whether you intend to perform a domain or local installation. If necessary, you have to ask the system administrator to grant the account the necessary authorization before you start the installation. If you attempt the installation with an account that does not have the required authorization, the installation aborts.
This section informs you about the authorization required for a domain and a local installation.
Procedure
Caution
Do not use the user
Domain Installation
For a domain installation the account used for the installation needs to be a member of the local Administrators group. In many old installation guides, you find the information, that the account must be a
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 32 PUBLIC Preparation member of the Domain Admins group. The account can be either a member of the Domain Admins group, or belongs to the Domain Users group and has the necessary rights to create/modify objects in the domain.
All machines in the system must belong to the same domain. In a domain installation, the user information is stored centrally on the domain controller and is accessible to all hosts in the system.
If the SAP system is to be distributed across more than one machine, SAP strongly recommends that you perform a domain installation to avoid authorization problems.
Caution
● If you install a distributed system as a local installation, this can lead to authorization problems for the operating system users
For a domain installation, you need to:
1. Check that the account used for the installation is a member of the domain Admins group. 2. If required, obtain these rights by asking the system administrator to enter the account as a member of the domain Admins group.
Local Installation
For a local installation the account used for the installation needs to be a member of the local Administrators group of the machine involved. In a local installation, all Windows account information is stored locally on one host and is not visible to any other hosts in the system.
If the SAP system is to run on a single machine, you can perform a local installation.
Caution
Do not use the Windows built-in account Administrator or the renamed built-in account to install your SAP system. The built-in account only has restricted network access rights that are required by the installer. If you renamed the built-in account Administrator, do not create a new account named Administrator.
For a local installation, you need to:
1. Check that the account used for the installation is a member of the local Administrators group. 2. If required, obtain these rights by asking the system administrator to enter the account as a member of the local Administrators group.
Related Information
Performing a Domain Installation Without Being a Domain Administrator [page 65]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 33 3.6 Changing the Windows Domain
This section describes how to use system rename for changing a Windows domain.
If your SAP system installation is a local installation, not a domain installation, and if you only want to change the Windows Active Directory domain of the server, there is no need to perform a system rename procedure, because all SAP system users and their configurations are local and do not change with a domain change.
When performing a system rename procedure, the installer creates the SAP system users in the new domain , but this is not required in the case of a local installation, because the SAP system users of a local installation are local to the system.
You must only apply the system rename procedure if you want to change the domain and the installation type from a local installation to a domain installation.
If you have a local system installation and you want to change only the domain of the server, the SAP system installation as such is not affected, therefore no system rename is required.
Requirements [page 34] This section is about the requirements for a system rename with Windows domain change.
Preparing SAP System Hosts for System Rename with Windows Domain Change [page 36] This section is about how to prepare system hosts for a system rename with Windows domain change.
Procedure for System Rename with Windows Domain Change [page 36] Proceed as follows to perform a system rename with changing the Windows domain.
3.6.1 Requirements
This section is about the requirements for a system rename with Windows domain change.
Requirements for the SAP System Hosts for Systems with all Instances on one Host and Distributed Systems
To change the domain during system rename, we recommend that you check that all SAP system hosts are members of the target Windows domain. We recommend this for all SAP system setups. We assume that you are familiar with checking Windows domain structures.
For more information, see the Windows documentation.
Using Virtual Host Names
You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to conceal their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure.
● Make sure that the virtual host names can correctly be resolved in your Domain Name System (DNS) setup.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 34 PUBLIC Preparation ● Make sure that you configured the Windows operating system properly to use virtual host names. For more information, see SAP Note 1564275 .
Required User Authorization for System Rename with Domain Change
● Check that the account used to execute system rename is a member of the domain Admins group in the target domain. ● If required, obtain these rights by asking the system administrator to enter the account as a member of the domain Admins group in the target domain. ● To execute system rename with a user who is not member of the domain Admins group in the target domain, proceed as described in Maintaining Users and Groups [page 21].
Note
To run the installer, do not use user
● Make sure that the user that you use to run the system rename has access to the database. MS SQL Server: ○ If there is a trust relationship between the old and the new domain, you can directly grant the new user access to SQL Server. If not, you need a local user that has access to SQL Server to grant the new domain user access to SQL Server. ○ Add the login to the sysadmin server role. Properties Server Roles
You can do this in the SQL Management Studio as follows: Right click on the login and choose
Deciding Whether to Use Organizational Units (OUs) in the Windows Domain
Note
You do not need this step for a local installation.
For a domain installation, the installer needs to create certain OS users for SAP and database operations in the Windows domain, also called the “Active Directory” (AD). These users are created by default in the AD container “Users”.
Depending on a customer's AD landscape and security policy, there are certain restrictions on where to store users and groups in AD. Contact the administrator of your AD infrastructure to understand where to store all SAP and database-related domain users and domain groups.
The SAP installer offers to define an existing OU in AD to create all needed SAP and database users in this OU.
There are many different scenarios and prerequisites concerning how to use OUs. For more information, see SAP Note 2247673 , which explains these issues in detail and shows some examples of how to use them.
Caution
The installer does not create OUs. The installer does not move existing domain users or groups. The installer does not delete existing users, groups, OUs, nor any other object in a Windows domain.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 35 The only exception to this rule is the Uninstall option in the installer.
3.6.2 Preparing SAP System Hosts for System Rename with Windows Domain Change
This section is about how to prepare system hosts for a system rename with Windows domain change.
System with all Instances on one Host
Before you start the system rename, make sure that the SAP system host is a member in the planned target domain, otherwise stop all SAP instances and their Windows services, remove the auto start parameter of the services and join the host to the target domain and restart the SAP system host.
After the SAP system host is available again, start the system rename.
System with its Instances Distributed over Several Hosts
Before you start the system rename for a distributed system, make sure that all hosts of the SAP system are members of the future target domain, otherwise stop all SAP instances and their Windows services on the relevant hosts, remove the auto start parameter of the services and join all hosts of this distributed installation to the target domain.
For more information, see the Windows documentation.
After the SAP system host is available again, start system rename procedure.
3.6.3 Procedure for System Rename with Windows Domain Change
Proceed as follows to perform a system rename with changing the Windows domain.
Prerequisites
Make sure you have completed the preparation steps required for your database. For more information, see Database-Specific Preparation [page 22] .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 36 PUBLIC Preparation Procedure
1. Change the Windows domain manually on the host. 2. Restart the server. 3. Run the system rename procedure with the Windows domain administrator of the target Windows domain.
Note
If you want to use Organizational Units (OUs) in the Windows domain, make sure that you choose option option Use domain of current user on the Windows Domain screen.
Related Information
System Rename Procedure [page 40] Database-Specific Preparation [page 22]
3.7 Preparing the System Rename Media
This section describes how to prepare the media required for the system rename procedure.
Note
The signature of media is checked automatically by the installer during the Define Parameters phase while processing the Media Browser screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .
Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 38] You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 37 3.7.1 Downloading and Extracting the Software Provisioning Manager 1.0 Archive
You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.
Prerequisites
● Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software Provisioning Manager archive.
Note
An older SAPCAR version might extract archive files in a wrong way and this could prevent the installer from working consistently.
Proceed as follows to get the latest version of SAPCAR: 1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS SAPCAR . 2. Select the archive file for your operating system and download it to an empty directory. 3. To check the validity of the downloaded executable, right-click the executable and choose Properties. On the Digital Signatures tab you can find information about the SAP signature with which the executable was signed. 4. Rename the executable to sapcar.exe. For more information about SAPCAR, see SAP Note 212876 .
Procedure
1. Download the latest version of the Software Provisioning Manager 1.0 archive SWPM10SP
https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager 2. Unpack the Software Provisioning Manager archive to a local directory using the following command:
Note
Make sure that all users have at least read permissions for the directory to which you unpack the installer.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 38 PUBLIC Preparation Caution
Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.
3.8 Preparing the File System
Use this step to make the file system available on the system that you plan to rename.
Prerequisites
You have performed the database specific preparation steps.
Procedure
● If you want to perform the system rename on a central system, you can start the system rename procedure without any further preparatory steps. ● If you want to perform the system rename on a distributed system, you have to prepare the SAP global host. To do this, run the installer and choose System Rename Distributed System Global Host Preparation .
Related Information
Database-Specific Preparation [page 22] Running the Installer [page 42]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Preparation PUBLIC 39 4 System Rename Procedure
4.1 System Rename Procedure Checklist
This section includes the renaming steps that you have to perform for the following options:
● Standard system ● Distributed system
The installer adapts the SAP system on an operating system level. The system parameters are adapted offline.
The installer automatically starts the following instances during the system rename:
● Database ● Instance services of a Windows operating system ● ABAP Central services instance (ASCS instance) if an ASCS instance is available
Central System
You check the Prerequisites for Running the Installer [page 41] and run the installer to rename the system as described in Running the Installer [page 42].
Distributed System
Note
See also table System Rename Options and Sequence how to Execute Them in Running the Installer [page 42].
1. If your SAP system has an ASCS instance, you check the Prerequisites for Running the Installer [page 41] and run the installer to rename the ASCS instance as described in Running the Installer [page 42]. 2. You make sure that the global directories (exe, profile, global) are exported to the instance hosts of the SAP system to be renamed. If your SAP system has an ASCS instance and the ASCS instance host is the SAP global host of the system, you export the global directories to the database instance host, to the primary application server instance host, and – if required – to the additional application server instance hosts of the SAP system to be renamed. For more information, see Preparing the File System [page 39]. 3. You check the Prerequisites for Running the Installer [page 41] and run the installer to rename the database instance as described in Running the Installer [page 42]. 4. You check the Prerequisites for Running the Installer [page 41] and run the installer to rename the primary application server instance as described in Running the Installer [page 42].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 40 PUBLIC System Rename Procedure 5. Optional: You check the Prerequisites for Running the Installer [page 41] and run the installer to rename existing standalone Gateway instances as described in Running the Installer [page 42]. 6. Optional: You check the Prerequisites for Running the Installer [page 41] and run the installer to rename the SAP Web Dispatcher instance as described in Running the Installer [page 42].
Next Steps
You perform follow-up activities [page 58]
4.2 Prerequisites for Running the Installer
Make sure you fulfil the following prerequisites before running the installer.
● For the SL Common GUI, make sure that the following web browser requirements are met: ○ You have one of the following supported browsers on the device where you want to run the SL Common GUI: ○ Google Chrome (recommended) ○ Mozilla Firefox ○ Microsoft Edge ○ Microsoft Internet Explorer 11 or higher. Always use the latest version of these web browsers. ○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.
Caution
The installer uses a self-signed certificate, which is used temporarily only while the installer is running. This certificate is not trusted by the browser unless it is imported manually by the user running the installer. This behavior is intentionally designed in this way because - unlike ordinary public web servers - the installer has different usage patterns. You must configure your browser do trust the self-issued certificate of the installer after carefully performing the “thumbprint” verification described in Running the Installer [page 42]. For more information about adding trusted certificates, see the documentation of your browser.
For more information about the SL Common GUI, see Useful Information about the Installer [page 47].
● You need at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. The installer creates an installation directory sapinst_instdir, where it keeps its log files, and which is located directly in the %ProgramFiles% directory. For more information, see Useful Information About the Installer [page 47]. ● Make sure that the following ports are not used by other processes: ○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL Common GUI.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 41 If this port cannot be used, you can assign a free port number by executing sapinst.exe with the following command line parameter: SAPINST_HTTPS_PORT=
● If you want to change the host name of your system, change the computer name and the host name on OS level and make sure that the host name resolution and UNC paths work. For more information, see SAP Note 23538 . If you want to change the virtual host name, see SAP Note 962955 . ● SAP ASE: Make sure the system and database are not running when starting the installer. ● If you are carrying out a domain switch, ensure you have completed all additional actions in section Changing the Windows Domain [page 34] before starting the installer.
4.3 Running the Installer
This section describes how to run the installer to perform the system rename .
Prerequisites
For more information, see Prerequisites for Running the Installer [page 41].
Context
The installer has a web browser-based GUI named “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.
This procedure describes an installation where you run the installer and use the SL Common GUI, that is you can control the processing of the installer from a browser running on any device.
For more information about the SL Common GUI, see Useful Information About the Installer [page 47].
Procedure
1. Log on to the host where you want to run the installer.
Make sure that you log on as a user with the required authorization for running the installer.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 42 PUBLIC System Rename Procedure For more information, see Required User Authorization for Running the Installer [page 32].
Caution
Do not use an existing
If your security policy requires that the person running the installer is not allowed to know administrator credentials on the host where the installer is to perform the system rename , you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe from the command line. You must confirm that the user is a trusted one. For more information, see SAP Note 1745524 . 2. Make the required media available.
For more information, see Preparing the System Rename Media [page 37]. 3. Start the installer as follows:
Double-click sapinst.exe from the directory to which you unpacked the Software Provisioning Manager archive file.
Note
By default, the SL Common GUI uses the default browser defined for the host where you run the installer. However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst executable with command line option SAPINST_BROWSER=
The installer GUI starts automatically by displaying the Welcome screen. 4. The installer is starting up.
The installer now starts and waits for the connection with the SL Common GUI. If you have a supported web browser (see Prerequisites for Running the Installer [page 41]) installed on the host where you run the installer, the SL Common GUI starts automatically by displaying the Welcome screen.
If the SL Common GUI does not open automatically, you can find the URL you require to access the SL Common GUI at the bottom of the Program Starter window of the installer. You find the icon of the Program Starter window in the taskbar of your Windows host. Open a supported web browser and run the URL from there.
... ************************************************************************ Open your browser and paste the following URL address to access the GUI
https://[
Logon users: [
************************************************************************ ...
Note
If the host specified by
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 43 You can use a fully-qualified host name.
Caution
After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid security risks such as SSL stripping .
Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst process on this computer could not be verified.
Proceed as follows to avoid security risks such as a man-in-the-middle attack: 1. Click on the certificate area on the left hand side in the address bar of your browser, and view the certificate. 2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones displayed in the console output of the installer. Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: %userprofile%\.sapinst\ 2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the command line option get_my_name -p. As a result, you get the server fingerprint or thumbprint from the server certificate. 3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not be verified.
The SL Common GUI opens in the browser by displaying the Welcome screen. 5. In the Welcome screen, proceed according to your system variant :
○ If your system is a standard system , choose System Rename Standard System System Rename . ○ If your system is a distributed system, choose System Rename Distributed System
System Rename Options and Sequence how to Execute Them
Option Description When to Execute Execution Order
System Rename for ASCS Executes system rename If your system does not First step for systems with Instance for the ASCS instance have an ASCS instance, AS ABAP, if they have an skip this option. ASCS instance
System Rename for ERS Executes system rename If your system does not Execute this option after Instance for the ERS instance have an ERS instance, skip you have performed the re this option. name option for the ASCS instance (if available) above, as required
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 44 PUBLIC System Rename Procedure Option Description When to Execute Execution Order
System Rename for Data Executes system rename Execute in any case (even Execute this option after base Instance for the database instance if you change the SAP sys you have performed the re tem ID, the host name or name options for the ASCS the instance number) instance (if available) and the ERS instance above, as required
System Rename for the Executes system rename Execute this option after Execute this option after Primary Application Server for the primary application renaming the database in you have performed the re Instance server instance stance. name options for the ASCS instance (if available), the ERS instance, and the da tabase instance above, as required
System Rename for a Executes system rename If your system host does Execute this option after Gateway Instance for a standalone Gateway not have a standalone you have performed the re instance Gateway instance, skip this name options for the ASCS option. instance (if available), the ERS instance, the data base instance, and the pri mary application server in stance above, as required
System Rename for Web Executes system rename If your system does not Execute this as last option Dispatcher Instance for the SAP Web Dis have an SAP Web Dis patcher instance patcher instance, skip this option.
6. Choose Next.
Note
If there are errors during the self-extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.
7. If the installer prompts you to log off from your system, log off and on again. The installer restarts automatically. 8. Follow the instructions in the installer input screens and enter the required parameters.
Note
To find more information on each parameter during the Define Parameters phase, position the cursor on the required parameter input field , and choose either F1 or the HELP tab. Then the available help text is displayed in the HELP tab.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 45 Caution
The signature of installation media and installation archives is checked automatically during the Define Parameters phase while processing the Media Browser and - if you perform an archive-based installation - the Software Package Browser screens.
Note that this automatic check is only committed once and not repeated if you modify artifacts such as SAR archives or files on the media after the initial check has been done. This means that - if you modify artefacts later on either during the remaining Define Parameters phase or later on during the Execute Service phase - the signature is not checked again.
For more information, see SAP Note 2393060 .
9. After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default.
If required, you can revise the parameters before starting the system rename procedure. 10. To start the execution, choose Next.
The installer starts the rename procedure and displays its progress on the Task Progress screen.
When the system rename option has finished successfully, the installer displays the message Execution of
12. For security reasons, we recommend that you delete the .sapinst directory within the home directory of the user with which you ran the installer:
%userprofile%\.sapinst\ 13. The installer log files contain IP addresses and User IDs such as the ID of your S-User. For security, data protection, and privacy-related reasons we strongly recommend that you delete these log files once you do not need them any longer. You find the installer log files in the sapinst_instdir directory. For more information, see Useful Information about the Installer [page 47].
Related Information
Useful Information about the Installer [page 47] Interrupted Processing of the Installer [page 52] Troubleshooting with the Installer [page 55]
4.4 Additional Information about the Installer
The following sections provide additional information about the installer.
Useful Information about the Installer [page 47]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 46 PUBLIC System Rename Procedure This section contains some useful technical background information about the installer and the installer GUI.
System Provisioning Using a Parameter Input File [page 48] Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP systems in unattended mode with a parameter input file.
Interrupted Processing of the Installer [page 52] Here you find information about how to restart the installer if its processing has been interrupted.
Troubleshooting with the Installer [page 55] This section tells you how to proceed when errors occur while the installer is running.
Using the Step State Editor (SAP Support Experts Only) [page 56] This section describes how to use the Step State Editor available in the installer.
4.4.1 Useful Information about the Installer
This section contains some useful technical background information about the installer and the installer GUI.
● Software Provisioning Manager (the “installer” for short) has the web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short. The SL Common GUI uses the SAP UI Development Toolkit for HTML5 - also known as SAPUI5 - a client- side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are: ○ Zero foot print, since only a web browser is required on the client ○ New controls and functionality, for example, view logs in web browser. As of version 1.0 SP24 Patch Level (PL) 5, Software Provisioning Manager comes with a new look and feel of the SL Common GUI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for- software-provisioning-manager/ . The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of Software Provisioning Manager - running on the installation host using the standard protocol HTTPS. For the SL Common GUI, the installer provides a pre-generated URL in the Program Starter window. If you have a supported web browser installed on the host where you run the installer, the SL Common GUI starts automatically. By default, the SL Common GUI uses the default browser defined for the host where you run the installer. However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst executable with command line option SAPINST_BROWSER=
● As soon as you have started the sapinst.exe executable, the installer creates a .sapinst directory underneath the
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 47 create sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the TEMP environment variable. All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir directory as soon as the latter has been created. The installer records its progress in the keydb.xml file located in the sapinst_instdir directory. Therefore, if required, you can continue with the installer from any point of failure, without having to repeat the already completed steps and without having to reenter the already processed input parameters. For security reasons, a variable encryption key is generated as soon as the sapinst_instdir directory is created by the installer. This key is used to encrypt the values written to the keydb.xml file.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly installed.
● The installer extracts itself to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after the installer has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the installer has finished. You can safely delete them. The temporary directory also contains the log file dev_selfex.out from the self-extraction process of the installer, which might be useful if an error occurs.
Caution
If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.
● To see a list of all available installer properties, go to the directory %TEMP%\sapinst_exe.xxxxxx.xxxx after you have started the installer, and enter the following command: sapinst.exe -p
● If required, stop the installer by choosing the Cancel button.
Note
If you need to terminate the installer, choose File Exit in the menu of the Program Starter window.
4.4.2 System Provisioning Using a Parameter Input File
Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP systems in unattended mode with a parameter input file.
Prerequisites
Provisioning of SAP systems can also be done in unattended mode without the user interface of the installer. This means that, after inserting the required parameters into a parameter-file and running the sapinst
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 48 PUBLIC System Rename Procedure executable by providing the path to this parameter-file , the installation will run in the background and no further user interaction is required.
Context
This section describes the steps that you need to execute in addition to the procedure described in this guide, when running the installer in unattended mode using a parameter input file.
Since the new Web-based SL Common GUI (see Useful Information about the Installer [page 47]) was introduced in 2017 there are two ways to run the unattended mode: “observer mode” and “non-observer mode”.
Observer Mode
If you are running an installation in unattended mode but you are sitting in front of the screen, you might want to check the progress from time to time. In this case the “observer mode” makes sense.
Start the installation as described below in the Solution section, using the following parameters:
SAPINST_INPUT_PARAMETERS_URL=
SAPINST_EXECUTE_PRODUCT_ID=
SAPINST_SKIP_DIALOGS=true
The Software Provisioning Manager will start the installation in the background AND start a Web Dispatcher and provide an URL to access the SL Common GUI. The user who has started the installation can now connect to the URL and observe the progress of the installation, for example to look at the logfiles in the Web browser. However, all parameters will be taken from the parameter input file and can not be changed in the Web browser.
Non-Observer Mode
Choose that mode if you want to run a “scripted” or by other means automated scenario, for example overnight. In that case it is crucial that the process is started without a Web Dispatcher and therefore without a GUI. Otherwise, the automation could be stuck if the installer encounters a situation that requires user interaction.
Start the installation as described below in the Solution section, using the following parameters (use the same parameters like for Observer Mode, but provide SAPINST_START_GUISERVER=false in addition):
SAPINST_INPUT_PARAMETERS_URL=
SAPINST_EXECUTE_PRODUCT_ID=
SAPINST_START_GUISERVER=false
This will start the installation but this time NO Web Dispatcher will be started and no URL to access the SL Common GUI will be provided either. So the user can not follow the processing of the installation in a Web browser and the installation will run completely in the background.
If the process runs into an error, SAPinst will abort and you have to check for the reason in the log files.
Restrictions
In exceptional cases, parameters prompted or displayed in the Software Provisioning Manager UI are not maintainable in the parameter input file. If one of those parameters, that are only available in the GUI mode of
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 49 the Software Provisioning Manager, is needed for your unattended installations, you should create a ticket in the best fitting component below BC-INS to get the issue analyzed.
Must Know about the Input Parameter File ● The parameter input file only contains values that you entered in the Software Provisioning Manager GUI. ● With the SAPinst 749.0.69 or by other means patch we provide a better encryption of passwords in Software Provisioning Manager files: If the parameter input file has parameters which are encrypted with Des25 encryption, the instkey.pkey file available in the installation directory contains the key for the encryption. The instkey.pkey file must be always located in the same directory as the parameter input file and is used to decrypt the values of the encrypted parameters. If you need to copy a parameter input file to another directory, you must also copy the instkey.pkey file to this directory. ● Not explicitly set parameters are documented as comments in the generated parameter input file. ● Each parameter has got a documentation assigned as a comment on top.
Example
Example for a parameter that is not used and therefore commented out:
# Specify whether Software Provisioning Manager is to drop the schema if it exists. <= Documentation
# HDB_Schema_Check_Dialogs.dropSchema = false
Example
Example for a parameter that is used:
# The name of the database schema. <= Documentation
HDB_Schema_Check_Dialogs.schemaName = SAPABAP2
● The media information is provided using the following convention:
SAPINST.CD.PACKAGE.
For each media location a line. ● Restriction: Currently you can only specify complete media, not paths to single files like *.SAR archives. Make sure that you enter the full paths to all required media, relative paths are not sufficient:
Example
Example on UNIX:
SAPINST.CD.PACKAGE.KERNEL = /mnt/KERNEL
SAPINST.CD.PACKAGE.LOAD = /mnt/LOAD
SAPINST.CD.PACKAGE.RDBMS = /mnt/RDBMS
Example
Example on Windows:
SAPINST.CD.PACKAGE.KERNEL = C:\sapdvds\KERNEL
SAPINST.CD.PACKAGE.LOAD = C:\sapdvds\LOAD
SAPINST.CD.PACKAGE.RDBMS =C:\sapdvds\RDBMS
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 50 PUBLIC System Rename Procedure When performing a system copy, you need to add one additional media path:
SAPINST.CD.PACKAGE.MIGRATION1 =
● Caution: If you want to use archives for your installation, you must copy all files that are to be used to a single directory. In the parameter input file you must specify this directory as a download basket, using the archives.downloadBasket parameter. Make sure that there is only one version of the same archive in the directory, for example SAPEXE_
Procedure
1. You plan and prepare the run as described in Planning [page 18] and Preparation Checklist [page 20]. 2. Create a text file that has “.params” as a suffix as follows: 1. Start the installer as described in Running the Installer [page 42]. 2. Choose the option you want to run, and follow the instructions on the screens by entering all parameter values 3. Stop after the Parameter Summary screen has been displayed 4. Find the parameter input file named “inifile.params” in the installation directory 5. Rename the “inifile.params” file. For example, you can rename it to “my_inifile.params”. 3. Adjust the values of the parameter input file as follows: 1. Edit the parameter input file (“my_inifile.params”) file and modify the parameters according to your needs. 2. Add required media or archives information line by line. 4. Identify the Product-ID: ○ To start in unattended mode, you need to know the component ID for the option that are required for your provisioning scenario. Proceed as follows: 1. Open the sapinst_dev.log in the installation directory. 2. Check for the “product-id”
Example
product-id=NW_ABAP_ASCS:NW750.ADA.ABAP
○ Alternatively, you can check the header of the generated “my_inifile.params” file.
Example
product id 'NW_ABAP_ASCS:NW750.ADA.ABAP'
5. Run the installer [page 42] with the parameters required for unattended mode: ○ In observer mode: Start the sapinst executable from an empty directory with the following parameters:
SAPINST_INPUT_PARAMETERS_URL=
SAPINST_EXECUTE_PRODUCT_ID=
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 51
SAPINST_SKIP_DIALOGS=true
○ In non-observer mode: Start the sapinst executable from an empty directory with the following parameters:
SAPINST_INPUT_PARAMETERS_URL=
SAPINST_EXECUTE_PRODUCT_ID=
6. After the installer has completed, perform follow-up activities as described in Follow-Up Activities Checklist [page 58].
Related Information
SAP Note 2849054 SAP Note 2742212 SAP Note 2626837 SAP Note 2669183
4.4.3 Interrupted Processing of the Installer
Here you find information about how to restart the installer if its processing has been interrupted.
Context
The processing of the installer might be interrupted for one of the following reasons:
● An error occurred during the Define Parameters or Execute phase: The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.
● You interrupted the processing of the installer by choosing Cancel in the SL Common GUI.
Caution
If you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 52 PUBLIC System Rename Procedure The following table describes the options in the dialog box:
Option Definition
Retry The installer retries the installation from the point of failure without repeating any of the previous steps.
This is possible because the installer records its progress in the keydb.xml file.
We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.
If the same or a different error occurs, the installer displays the same dialog box again.
Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.
The installer records its progress in the keydb.xml file. Therefore, you can continue with the installer from the point of failure without repeating any of the previous steps. See the procedure below.
Continue The installer continues the installation from the current point.
View Log Access installation log files.
The following procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation.
Procedure
1. Log on to the installation host as a user with the required permissions as described in Running the Installer [page 42] . 2. Make sure that the media required for the system rename are still available.
For more information, see Preparing the System Rename Media [page 37] .
Recommendation
Make the installation media available locally. For example, if you use remote file shares on other Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.
3. Restart the installer by double-clicking sapinst.exe from the directory to which you unpacked the Software Provisioning Manager archive. By default, the SL Common GUI uses the default browser defined for the host where you run the installer. However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst executable with command line option SAPINST_BROWSER=
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 53 4. The installer is restarting.
The installer now starts and waits for the connection with the SL Common GUI. If you have a supported web browser (see Prerequisites for Running the Installer [page 41]) installed on the host where you run the installer, the SL Common GUI starts automatically by displaying the Welcome screen.
If the SL Common GUI does not open automatically, you can find the URL you require to access the SL Common GUI at the bottom of the Program Starter window of the installer. You find the icon of the Program Starter window in the taskbar of your Windows host. Open a supported web browser and run the URL from there.
... ************************************************************************ Open your browser and paste the following URL address to access the GUI
https://[
Logon users: [
************************************************************************ ...
Note
If the host specified by
Caution
After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid security risks such as SSL stripping .
Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst process on this computer could not be verified.
Proceed as follows to avoid security risks such as a man-in-the-middle attack: 1. Click on the certificate area on the left hand side in the address bar of your browser, and view the certificate. 2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones displayed in the console output of the installer. Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: %userprofile%\.sapinst\ 2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the command line option get_my_name -p. As a result, you get the server fingerprint or thumbprint from the server certificate. 3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not be verified.
The SL Common GUI opens in the browser by displaying the Welcome screen.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 54 PUBLIC System Rename Procedure 5. From the tree structure on the Welcome screen, select the installation option that you want to continue and choose Next.
The What do you want to do? screen appears. 6. On the What do you want to do? screen, decide between the following alternatives and continue with Next:
Alternative Behavior
Perform a new run The installer does not continue the interrupted system rename option. Instead, it moves the content of the old installer directory and all installer-specific files to a backup directory. Afterwards, you can no longer continue the old option.
The following naming convention is used for the backup directory:
log_
Example
log_01_Oct_2016_13_47_56
Note
All actions taken by the system rename before you stopped it (such as cre ating directories or users) are not revoked.
Caution
The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.
Continue with the existing one The installer continues the interrupted system rename from the point of failure.
4.4.4 Troubleshooting with the Installer
This section tells you how to proceed when errors occur while the installer is running.
Context
If an error occurs, the installer:
● Stops processing ● Displays a dialog informing you about the error
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 55 Procedure
1. Check SAP Note 2393060 for known installer issues. 2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:
○ Try to solve the problem: ○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose the LOG FILES tab.
Note
The LOG FILES tab is only available if you have selected on the Welcome screen the relevant installer option for the SAP system to be renamed .
If you need to access the log files before you have done this selection, you can find the files in the .sapinst directory underneath the
For more information, see Useful Information about the Installer [page 47].
○ To check the log and trace files of the installer GUI for errors, go to the directory %userprofile% \.sapinst\ ○ Then continue by choosing Retry. ○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more information, see Interrupted Processing of the Installer [page 52]. 3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*. For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .
4.4.5 Using the Step State Editor (SAP Support Experts Only)
This section describes how to use the Step State Editor available in the installer.
Note
Only use the Step State Editor if the SAP Support requests you to do so, for example to resolve a customer incident.
Prerequisites
● SAP Support requests you to use the Step State Editor. ● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for Running the Installer [page 41].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 56 PUBLIC System Rename Procedure Procedure
1. Start the installer from the command line as described in Running the Installer [page 42] with the additional command line parameter SAPINST_SET_STEPSTATE=true 2. Follow the instructions on the installer screens and fill in the parameters prompted during the Define Parameters phase until you reach the Parameter Summary screen. 3. Choose Next.
The Step State Editor opens as an additional dialog. Within this dialog you see a list of all steps to be executed by the installer during the Execute Service phase. By default all steps are in an initial state. Underneath each step, you see the assigned installer component. For each step you have a Skip and a Break option.
○ Mark the checkbox in front of the Break option of the steps where you want the installer to pause. ○ Mark the checkbox in front of the Skip option of the steps which you want the installer to skip. 4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step State Editor dialog.
The installer starts processing the Execute Service phase and pauses one after another when reaching each step whose Break option you have marked. You can now choose one of the following:
○ Choose OK to continue with this step. ○ Choose Step State Editor to return to the Step State Editor and make changes, for example you can repeat the step by marking the checkbox in front of the Repeat option. ○ Choose Cancel to abort the installer. 5. Continue until you have run through all the steps of the Execute Service phase of the installer.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows System Rename Procedure PUBLIC 57 5 Follow-Up Activities
5.1 Follow-Up Activities Checklist
Procedure
1. Start the primary application server instance.
For more information, see Starting the SAP System [page 63].
The installer has only started the following instances during the system rename:
○ Database ○ Instance services of a Windows operating system ○ ABAP Central services instance (ASCS instance) if an ASCS instance is available 2. Perform general follow-up activities.
For more information, see General Follow-Up Activities [page 59]. 3. Configure the transport management system.
For more information, see Configuring the Transport Management System [page 64]. 4. Perform follow-up activities for your database.
For more information, see Database-Specific Follow-Up Activities [page 59]. 5. Restart the renamed SAP system completely.
For more information, see Starting the SAP System [page 63]. 6. Change the IGS destination.
For more information, see Changing the IGS Destination [page 64].
Related Information
General Follow-Up Activities [page 59] Database-Specific Follow-Up Activities [page 59] Configuring the Transport Management System [page 64] Changing the IGS Destination [page 64] Starting the SAP System [page 63]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 58 PUBLIC Follow-Up Activities 5.1.1 General Follow-Up Activities
This section refers to the general follow-up activities that you have to perform after the rename of your SAP system.
● Potentially, all follow-up activities for a system copy are also valid for the rename of your SAP system and therefore you have to check which of them apply for your special situation and use case. For more information, see the system copy guide [page 17] for your operating system platform and database . Generally, due to the high variety of use cases, no rule which of the potential follow-up activities are valid can be given.
Example
To identify potential follow-up activities regarding logical system names, answer to the following question:
Does the renamed SAP system use logical system names?
○ If not, this aspect is not relevant for your use case. ○ If yes, answer to the following question: What naming convention was used for the logical system names? The default convention is
● Post-copy activities automated as part of SAP Landscape Management (LVM) can also be used to perform the follow-up activities after a system rename, so you can profit from an easier, faster and more reliable process. For more information, see https://archive.sap.com/documents/docs/DOC-25771 .
5.1.2 Database-Specific Follow-Up Activities
5.1.2.1 Performing Follow-Up Activities for SAP MaxDB
This section contains follow-up steps required for SAP MaxDB after the system rename has completed.
Procedure
As the rename procedure did not change the connectivity information for CCMS, delete the old connectivity using DB59 transaction and set up a new connectivity. For more information, see SAP Note 588515 .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Follow-Up Activities PUBLIC 59 5.1.2.2 Performing Follow-Up Activities for SAP MaxDB liveCache
This section contains follow-up steps required for SAP MaxDB liveCache after the system rename has completed.
Procedure
1. Add the new
Next Steps
If you get a short dump while executing the statement EXECUTE PROCEDURE "APS_PLAN_VERSION_GET", see SAP Note1015489
5.1.2.3 Performing Follow-Up Activities for SAP MaxDB liveCache Client
This section contains follow-up steps required for the SAP MaxDB liveCache client after the system rename has completed.
Procedure
Extend the PATH variable for user
/sapdb/clients/
/sapdb/clients/
/sapdb/programs/bin
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 60 PUBLIC Follow-Up Activities /sapdb/programs/pgm
If liveCache is running on the same host as the SAP system, the OS user SAPService
5.1.2.4 Performing Follow-Up Activities for IBM Db2 for Linux, UNIX, and Windows
After system rename has completed, you can change the name and location of your DB2 software copy.
Note
This follow-up step is optional.
Context
The system rename procedure does not reinstall your DB2 software copy. Thus, after performing a successful system rename procedure, the name of your DB2 software copy and its installation location will be the same as for your source system. This DB2 copy name or the installation location path might contain your old DBSID.
The DB2 copy name is referred to under DB2 services, so you might see the old DBSID in your DB2 services.
If you would like to rename your DB2 software copy or change the installation location, follow the instructions below for installing a new DB2 copy. Note, however, that these steps are purely optional and are not required for the system to run correctly.
Procedure
1. To change the DB2 software path, proceed as follows: a. Copy the file ..\ESE\win_ese.rsp from the RDBMS medium to a local directory. b. Edit the file win_ese.rsp as follows: ○ Replace @DB2SOFTWAREPATH@ as follows:
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Follow-Up Activities PUBLIC 61
For example, if your new DBSID is XXX and your new DB2 copy is located in D:\db2\newCopy \db2_software, execute the following: D:\db2\newCopy\db2_software\bin\db2iupdt.exe db2xxx /u: db2xxx,mypassword /p: D: \db2\db2xxx /a: SERVER_ENCRYPT
5.1.2.5 Performing Follow-Up Activities for SAP HANA Database
This section contains follow-up steps required for SAP HANA after the system rename has completed.
Procedure
Currently there are no follow-up steps required.
5.1.2.6 Performing Follow-Up Activities for SAP ASE
This section contains follow-up steps required for SAP ASE after the system rename has completed.
Context
After the rename, the connection to transaction DB02/DBACOCKPIT might not work. To enable it, perform the steps described below.
Procedure
1. Run transaction DBCO and switch to an edit mode. 2. Change the user to sapsa. 3. Enter the password for this user and save it.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 62 PUBLIC Follow-Up Activities Next Steps
After performing the steps listed above, you should be able to run transaction DB02/DBACOCKPIT.
5.1.2.7 Performing Follow-Up Activities for Db2 for z/OS
After the system rename, you have to perform the steps listed in this section.
Procedure
After the system rename, you must change the value of the dbs/db2/dsn_alias entry in the instance profiles from the source
5.1.2.8 Performing Follow-Up Activities for the Oracle Database
This section contains follow-up steps required for Oracle after the system rename has completed.
Procedure
If you have chosen to enable Oracle Database Vault, make sure that you perform the required configuration steps. For more information, see Implementing Oracle Database Vault with Software Provisioning Manager 1.0 [page 66]
5.1.3 Starting the SAP System
After the system rename procedure has finished you have to start the primary application server instance of the renamed system. Then, after you have performed all follow–up activities, you have to restart all instances of the renamed system.
For more information about how to start and restart an SAP system, see Additional Information Starting and Stopping the SAP System in the installation guide [page 17] for your operating system platform and database or the SAP Library [page 17] at:
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Follow-Up Activities PUBLIC 63 SAP Release and SAP Library Quick Link SAP Library Path (Continued)
● SAP NetWeaver 7.3 including Enhancement Package Application Help Function-Oriented View Solution Life 1 Cycle Management Starting and Stopping SAP Systems http://help.sap.com/nw731 Based on SAP NetWeaver ● SAP NetWeaver 7.4 http://help.sap.com/nw74 ● SAP NetWeaver 7.5 http://help.sap.com/nw75
5.1.4 Configuring the Transport Management System
You have to perform some steps to be able to use the Transport Management System.
Procedure
1. Reschedule the transport dispatcher (RDDIMPDP) in client 000: a. Log on as user DDIC. b. Call transaction SE38. c. Run program RDDNEWPP and set the priority to normal. 2. Adapt the transport parameters and transport routes in the TMS as follows: a. Call transaction STMS. b. Select Change Configuration. c. To adapt the transport parameters, choose Overview
5.1.5 Changing the IGS Destination
After renaming your ABAP system, make sure that you adapt the IGS destination.
Procedure
Call transaction SM59 and adapt the IGS destination IGS_RFC_DEST.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 64 PUBLIC Follow-Up Activities 6 Additional Information
6.1 Performing a Domain Installation Without Being a Domain Administrator
It is not required to perform the installation of the SAP system with a user who is a member of the Domain Admins group. For security reasons most customers do not provide this permission to SAP or database administrators. If the Domain Admin right has been granted, you can start any SAP installation because the user will have all necessary rights to install a standard, distributed or high-availability system.
An alternative is to ask the domain administrator to grant the required permissions to the user which installs SAP or the database. This domain user must be a member of the local Administrators group. In most cases the domain administrator will define an OU (Organizational Unit) structure, where all SAP systems and their related domain objects belong to.
To perform the installation with a domain user, the user account must meet the following requirements:
1. Create/Delete/Modify Users and Groups within OUs only. Ask the AD administrator about the company's OU concept. 2. Create/Delete/Modify Computer Objects within this OU. This is required for users which install SAP or database applications in Failover Clusters, LAMA environments or other HA environments. Optional rights might be necessary related to your company’s security policy, for example: 3. Create/Delete/Modify DNS server records within a specific DNS zone, where the Windows hosts with SAP software belong to. 4. Create/Delete/Modify Organizational Unit objects within a specific OUs only.
For standard and distributed installations (not HA installations!) the domain administrator can prepare the user and group objects in the domain for you. In this case, the domain user which will be used for the installation does not need any of the above permissions.
The required objects in the domain are:
1. Domain group SAP_
Note
The installer creates the operating system user for the SAP Host Agent by default as a local user that is not
a member of the local Administrators group. If you want to create this user manually as a domain user,
you must perform the following steps:
Creating the SAP Host Agent User and Group Manually
1. Create the new global group SAP_SAP_GlobalAdmin
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Additional Information PUBLIC 65 2. Create the SAP system user sapadm. 3. Add the user sapadm to the newly created group SAP_SAP_GlobalAdmin.
However, for security reasons we strongly recommend that you create this user as a local user.
6.2 Implementing Oracle Database Vault with Software Provisioning Manager 1.0
Software Provisioning Manager 1.0 (the “installer” for short) supports Oracle Database Vault. This section provides information about implementing Oracle Database Vault (DV) with the installer.
Prerequisites
● Your Oracle database version must be 12.1 or higher. ● Check the prerequisites, restrictions, and patch requirements as listed in SAP Note 2218115 .
Context
For system rename, the DV is already installed in the source database and must be first disabled to complete the procedure. It can be enabled before the scenario is completed.
DV requires the following addional users:
● secadmin ● secacctmgr
These users are created by the installer.
For more information about Oracle Database Vault, see the Oracle Database documentation referred to in SAP Note 2218115 .
Procedure
1. Start the installer and choose the system rename option for your system variant as described in Running the Installer [page 42]. 2. On the Oracle Database Configuration screen - if DV is installed on the source system - mark the checkbox Oracle Database Vault is installed and enabled.
Later during the system rename, the installer disables the DV. For this you have to provide the password of the secadmin user. The secadmin user grants some rights to the sysdba user. After the rename is
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 66 PUBLIC Additional Information finished, these rights are revoked again from thesysdba user and the DV is enabled again if this checkbox is set. Otherwise DV is installed but not enabled.
Next Steps
Configure Oracle Database Vault as described in SAP Note 2218115 .
6.3 Support of Oracle Transparent Data Encryption (Oracle TDE)
Oracle Transparent Data Encryption (TDE) for Oracle 18c is supported as of Software Provisioning Manager 1.0 SP27 (the “installer” for short) for SAP systems based on SAP NetWeaver.
Prerequisites
● Oracle database 18c or higher ● Software Provisioning Manager 1.0 SP 27 or higher ● SAP system is based on SAP NetWeaver 7.0 or higher ● If you perform a system copy or a database refresh with R3load, the Oracle database on the target system does not need to have the same encryption type as the Oracle database on the source system. You can always change the encryption type when the Oracle database or the Oracle tablespaces are recreated, and the data are reloaded again in the Oracle database by R3load.
Constraints
● Oracle Database 18c only supports TDE tablespace encryption, but not yet TDE full database encryption. For more information, see SAP Note 2485122 . ● With Software Provisioning Manager 1.0 you cannot configure TDE and encrypt tablespaces in the database of an already existing SAP System. You have to do this manually. ○ You can manually configure TDE in an SAP system that already exists. ○ You can manually convert a non-encrypted Oracle SAP database into an encrypted Oracle SAP database. ● With Software Provisioning Manager 1.0 you cannot deconfigure TDE and decrypt the data in the database of an existing SAP system. You have to do this manually.
For more information, see SAP Note 2485122 .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Additional Information PUBLIC 67 Supported Software Provisioning Manager 1.0 Scenarios
● SAP system installation from scratch See section Support of Oracle Transparent Data Encryption ( Oracle TDE) in the installation guide [page 17]. ● SAP system copy When you copy an SAP system with Software Provisioning Manager 1.0, there are two options for copying the database. From a security perspective, the first option is the preferred option as the SAP data remains security encrypted during the whole system copy process. See section Multitenant Database Installation of Oracle Database 12c or Higher in the system copy guide [page 17]. ● SAP system rename ● SAP system database refresh See section Support of Oracle Transparent Data Encryption ( Oracle TDE) in the system copy guide [page 17].
For more information, see SAP Note 2485122 .
Supported Oracle 18c Configuration Scenarios
● Oracle single instance installation Software keystore is located in filesystem ● Oracle Database Vault Implementing Oracle Database Vault with Software Provisioning Manager 1.0 [page 66] Oracle TDE and Oracle DV can be combined together.
For more information, see SAP Note 2485122 .
Supported TDE Encryption Algorithms
● Software Provisioning Manager 1.0 allows you to choose which encryption key to use. ● Default Encryption is TDE or AES128. ● NOTDE is the value for No Transparent Data Encryption. ● Currently only user tablespaces can be encrypted. ● Tablespaces System, Psaptemp, and Sysaux are not supported.
Log und SQ files in installation directory for TDE
During the installation, Database Refresh and Systemcopy with R3load with Software Provisioning Manager 1.0 the TDE will be set and installed when the Install Oracle TDE checkbox is marked.
For a database rename, the wallet is already available with the same master key as before. Only the Auto Login Wallet will be reset. The following log and sql files are created in the installation directory for TDE.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 68 PUBLIC Additional Information ● CreateKeystore.log & CreateKeystore.sql ○ Create keystore log and sql file ○ During the installation or system copy the keystore is created in $SAPDATA_HOME/orawallet/tde ● CreateKSKey.log & CreateKSKey.sql ○ Create keystore key log and sql file ○ The Master Key is written to the keystore file ewallet.p12 and a backup file ewallet_
6.4 Using PowerShell
SAP uses Windows PowerShell to run and describe Windows commands.
For Windows Server 2012 (R2) and higher, SAP only uses Windows PowerShell to run and describe Windows commands.
Windows PowerShell is a powerful tool integrated in the Windows operating system. It uses object-oriented methodology, which allows fast and stable script development.
For more information about the Windows PowerShell, see: http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx
There you can find links to the online help, online documentation, scripting repository, downloads, and blogs.
If you want to use the PowerShell feature, note the following:
● Windows Server 2016 Windows Server 2016 contains PowerShell 5.0 You can update to PowerShell 5.0 (search the internet for Windows Management Framework 5.0). ● Windows Server 2012 R2 Windows Server 2012 R2 contains PowerShell 4.0. ● Windows Server 2012 Windows Server 2012 contains PowerShell 3.0. You can update to PowerShell 4.0 (search the internet for Windows Management Framework 4.0). ● Windows Server 2008 R2 Windows Server 2008 R2 contains PowerShell 2.0. For more information about PowerShell 2.0, see http://support.microsoft.com/kb/968929 . You can update to PowerShell 3.0 or 4.0 (search the internet for Windows Management Framework 3.0 or Windows Management Framework 4.0). ● Windows Server 2008 You have to activate the PowerShell feature with Start Administrative Tools Server Manager Features . On Windows Server 2008, you can update to PowerShell 3.0 (search the internet for Windows Management Framework 3.0).
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Additional Information PUBLIC 69 How to Start PowerShell
Caution
Make sure that you start the PowerShell in administrator mode.
● Windows Server 2012 (R2) and higher Open the command prompt and enter the command: powershell.exe
To start PowerShell on Windows Server 2008 (R2), you have the following options:
● From the command prompt, by entering the command: powershell.exe ● From the Start Menu: ○ PowerShell 1.0: Choose Start All Programs Windows PowerShell 1.0 Windows PowerShell . ○ PowerShell 2.0: Choose Start All Programs Windows PowerShell Windows PowerShell .
How to Work with PowerShell
Most commands that are used in cmd.exe are also available in the PowerShell (defined as aliases).
You can use well-known commands, such as cd, type, copy, move, mkdir, delete, rmdir. There is also online help available, which you can access by typing the command: help (or help
This is a list of differences between PowerShell and cmd.exe:
● Before you can run PowerShells scripts (text files with the file extension .ps1 that contain PowerShell statements), you might have to change the default security setting to allow the execution of non-signed scripts as follows: set-executionpolicy ("unrestricted") ● By default, when double-clicking PowerShell scripts (.PS1 files) in the Windows explorer, this does not execute the script as is the default for .cmd files, but opens the script in an editor. If you want to activate automatic script execution after a double-click, you have to change the value HKEY_CLASSES_ROOT \Microsoft.Powershellscript.1\Shell\Open\Command from notepad.exe to the full path of the PowerShell executable. ● The output of PIPE commands is not just a stream of characters (strings) but a stream of objects. You can easily access the properties and methods for these objects (see the process list DLL example below). ● The current working directory is not part of the directory search path that the PowerShell looks at for scripts and programs. The PowerShell only searches directories listed in the environment variable path. Therefore, you might have to run a local program with ./sapcontrol.exe or specify its full path. ● You can use the UNIX-like directory delimiters, such as cd /usr/sap/C11. ● You can have your current working directory in a UNC path (cd \\sapglobalhost\sapmnt). ● The shell distinguishes between environment variables and shell variables: ○ Use of shell variables: Definition: $x="hello"
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 70 PUBLIC Additional Information Reference: write-host $x ○ Use of an environment variable: Definition: $env:x="hello" Reference: write-host $env:x ● The PowerShell has an interesting container concept called ps-drives. Within ps-drives you can navigate in other objects, such as the registry or shell internal lists in the same way as you typically navigate in a file system (cd, dir, del, and so on). dir env: to get a list of environment variables dir variable: to get the list of shell variables dir HKLM: to get a list of registry keys in HKEY_LOCAL_MACHINE get-psdrive to get a list of available ps-drives ● Windows PowerShell has full access to the .NET runtime. You can directly access missing functions in the PowerShell via .NET. ● With Windows PowerShell, you can create GUI-class user interfaces using Windows forms.
PowerShell Commands
The following table lists some PowerShell commands that are available on Windows Server 2012 (R2) and higher:
Command Explanation
stop-service sap* Stops all Windows services with service name starting with “SAP”
get-process Lists currently started processes on your system
get-process | sort starttime | select - Lists the last started process on your computer last 1
get-process | sort starttime | select - Lists all properties of the last started process last 1 | format-list -proper *
get-process | sort starttime | select - Lists all process class members (properties and methods) of last 1 | get-member the last started process
get-process | %{$_.name;"------"; Lists all processes, and the executables and DLLs the proc $_.modules} esses loaded
$processes = (get-process | sort Defines a shell variable $processes, which contains an ar starttime) ray of process objects
$processes.length The number of processes in the array (is equivalent to the number of processes on your computer)
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Additional Information PUBLIC 71 Command Explanation
$processes[$processes.length-1].kill() Invokes the kill method (terminate process) of the last started process
(dir a.txt).set_attributes("readonly") Sets the file a.txt to “read-only”
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows 72 PUBLIC Additional Information Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. ● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on Windows Important Disclaimers and Legal Information PUBLIC 73 www.sap.com/contactsap
© 2021 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. The information contained herein may be changed without prior notice.
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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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.
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. All other product and service names mentioned are the trademarks of their respective companies.
Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.
THE BEST RUN