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 IBM i 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...... 11 1.7 Constraints...... 14 1.8 SAP Notes for the System Rename...... 16 1.9 Accessing the Installation Guides and System Copy Guides...... 16 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 Performing IBM i - Specific Preparation Steps...... 22 3.5 Performing SAP MaxDB liveCache-Specific Preparation Steps on IBM i...... 24 Performing SAP MaxDB liveCache-Specific Preparation Steps on UNIX...... 24 Performing SAP MaxDB liveCache-Specific Preparation Steps on Windows...... 25 3.6 Performing SAP MaxDB liveCache Client-Specific Preparation Steps on IBM i...... 26 3.7 Configuring TCP/IP...... 27 3.8 Adjusting the Relational Database Name...... 34 3.9 Preparing the System Rename Media...... 35 Downloading and Extracting the Software Provisioning Manager 1.0 Archive...... 35 3.10 Copying the Installation Media Manually to Your IBM i...... 36 3.11 Preparing the SAP Installation User on IBM i...... 39 3.12 Enable the User QSECOFR...... 40
4 System Rename Procedure...... 42 4.1 System Rename Procedure Checklist...... 42 4.2 Prerequisites for Running the Installer...... 43 4.3 Running the Installer...... 45 4.4 Additional Information about the Installer...... 51 Useful Information about the Installer...... 51
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 2 PUBLIC Content System Provisioning Using a Parameter Input File...... 53 Interrupted Processing of the Installer...... 57 Troubleshooting with the Installer...... 60 Removing the Installer Installation Files...... 61 Using the Step State Editor (SAP Support Experts Only)...... 62
5 Follow-Up Activities...... 64 5.1 Follow-Up Activities Checklist...... 64 General Follow-Up Activities...... 65 Database-Specific Follow-Up Activities...... 65 Starting the SAP System...... 69 Configuring the Transport Management System...... 69 Changing the IGS Destination...... 70
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 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)
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 IBM i 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 ○ Cleanup of operating system users, documented in: SAP System Parameters, Creating Operating System Users and Groups
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Document History PUBLIC 5 Version Date Description
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
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 IBM i 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 IBM i.
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 IBM i About this Document PUBLIC 7 About Software Provisioning Manager 1.0 [page 9] Naming Conventions [page 11] New Features [page 11] 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 perform system rename in the following cases:
● You want to rename an existing system.
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 IBM i 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 16].
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 42] ○ Follow-Up Activities [page 65]
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 ● Names of command line parameters, for example SAPINST_HTTPS_PORT ● Names of operating system user groups, such as the additional group sapinst
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i About this Document PUBLIC 9 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.
Related Information
Preparing the System Rename Media [page 35]
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 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
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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 10 PUBLIC About this Document 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.
● “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
SAP Rename for The SAP Rename for IBM i now supports SAP systems installed Software Provisioning Manager SAP systems instal on the IASP. For more information, see the SAP Rename guide for 1.0 SP29 (SL Toolset 1.0 SP29 led on the independ IBM i. In the past, the SAP System Copy had to be used to rename ent auxiliary storage a system located on the IASP. pool (IASP).
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 16].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i About this Document PUBLIC 11 Feature Description Availability
Software Provision The new OS release IBM i 7.4 is certified for SAP Solutions since Software Provisioning Manager ing Manager on IBM July 19, 2019. For more information, see the SAP on IBM i blog en 1.0 SP27 (SL Toolset 1.0 SP27) i now supports the try "SAP on IBM i: IBM i 7.4 Certified for SAP Solutions ". In ad new OS release IBM dition, see SAP Note 1680045 , section Planning and Prepara i 7.4 tion : SAP System Installation on OS release IBM i V7R4.
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 16].
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/ .
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 51] and Troubleshooting with the Installer [page 60].
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 35] and Running the Installer [page 45].
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 51], Running the Installer [page 45].
Cleanup of Operat You can now specify during the Define Parameters phase that the Software Provisioning Manager ing System Users 1.0 SP20 (SL Toolset 1.0 SP20) group SAPINST is to be removed from the operating system users after the execution of the installer has completed.
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 35] .
In addition, check SAP Note 1680045 whether additional infor mation is available.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 12 PUBLIC About this Document Feature Description Availability
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 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.
System Rename System rename is supported for SAP systems based on SAP Software Provisioning Manager Supported for SAP NetWeaver 7.1 (SAP NetWeaver Mobile 7.1, SAP NetWeaver 7.1 for 1.0 SP08 (SL Toolset 1.0 SP13) systems based on Banking Services from SAP 5.0 and 6.0, SAP NetWeaver SAP NetWeaver 7.1 , Composition Environment 7.1) , 7.1 EHP1 (SAP NetWeaver Mobile 7.1 EHP1 , and 7.2. 7.1 EHP1 , SAP NetWeaver 7.1 EHP1 for Banking Services from SAP 5.0 and 6.0, SAP NetWeaver Composition Environment 7.1 EHP1 ), and 7.2 (SAP NetWeaver Composition Environment 7.2).
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 43].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i About this Document PUBLIC 13 Feature Description Availability
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 .
Automatic user The installer checks if the user QSECOFR and the IBM i installa Software Provisioning Manager check of the tion user are prepared correctly. Only if the installer detects an in 1.0 SP20 (SL Toolset 1.0 SP20) QSECOFR and the consistency, then a dialog screen appears. IBM i installation For more information about how to prepare these users, see Pre user paring the SAP Installation User on IBM i [page 39] and Enable the User QSECOFR [page 40] .
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
● SAP System ID
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 14 PUBLIC About this Document 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 . ● The installer only runs on IBM i 6.1 or higher. ● You can only rename SAP systems that are using the SAP NetWeaver kernel 7.20 or higher. ● As of Software Provisioning Manager 1.0 SP29 the independent auxiliary storage pool (IASP) is supported for the system rename option. You can now rename SAP systems which are installed on an IASP. Before Software Provisioning Manager 1.0 SP29 you had to use SAP system copy on IBM i for renaming an SAP system located on the IASP.
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
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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i About this Document PUBLIC 15 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
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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 16 PUBLIC About this Document Copy Guides - Software Provisioning Manager 1.0 System Copy - Target Databases Other than SAP HANA SAP Application Server Systems Based on SAP NetWeaver In the table, filter for the following: Product Release = SAP NetWeaver 7.X, Operating System Platform =
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 IBM i 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 16] for your operating system platform and database: ○ SAP system 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 16] 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. During the Define Parameters phase of the installer, you can specify that the operating system users are to be removed automatically from the group SAPINST after the execution of the installer has completed. For more information, see section Basic SAP System Installation Parameters in the installation guide [page 16] for your operating system platform and database.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 18 PUBLIC Planning Note
The removal of the operating system users from the sapinst group is only accomplished in the renamed target system, whereas the operating system users in the source system keep their assignment to the sapinst group. .
● For an SAP SCM system with SAP liveCache, the following rename options are supported by the installer: ○ Renaming the SAP SCM system ○ Renaming the SAP liveCache server ○ Renaming the SAP liveCache client The SAP SCM system and the SAP MaxDB liveCache client are always installed on the same host. The SAP MaxDB liveCache server can be installed on the same host as the SAP SCM system but it can also be installed on a different host. The SAP MaxDB liveCache server can only be installed on a host running an operating system which supports MaxDB. When you rename your SAP SCM system, you also must rename your SAP MaxDB liveCache. There are two scenarios for renaming an SAP SCM system with SAP MaxDB liveCache: 1. The SAP SCM system, the SAP MaxDB liveCache server und the SAP MaxDB liveCache client are on the same host: Perform the following two rename options of the installer: System Rename and Rename SAP liveCache The installer option Rename SAP liveCache automatically renames the SAP MaxDB liveCache client if the latter is located on the same host. There is no need to run option Rename SAP liveCache Client. 2. The SAP SCM system and the SAP MaxDB liveCache client are installed on a different host than the SAP MaxDB liveCache server: Perform the following three rename options of the installer on the relevant host: System Rename, Rename SAP liveCache, and Rename SAP liveCache Client. See also the prerequisites in section Performing SAP MaxDB liveCache-Specific Preparation Steps on IBM i [page 24].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 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 IBM i 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 45].
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 are logged on with a user account that has the required authorization to run the tool. For more information, see Preparing an IBM i User Profile [page 39].
Caution
Do not use the user
● 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 IBM i 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 45].
2. On the Welcome screen, choose
Note
For more information about the input parameters, place the cursor on the relevant field and press F1 .
3.4 Performing IBM i - Specific Preparation Steps
In general, the installer changes objects which are already existing. Since, locked objects are not changeable this can break the renaming process. Make sure that no user or process not related to the SAP system is locking an object such as the database library or the kernel library.
Procedure
1. The best way to unlock the objects of a running SAP system is to shut the system down completely. This means you must stop also the sapstart services, the XDN server and the subsystems.
To do this, log on as user
STOPSAP SID(
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 22 PUBLIC Preparation a. To check the kernel library, log on as QSECOFR or your installation user and enter the following command:
WRKOBJLCK OBJ(SAP
If the command WRKOBJLCK gives you a list of jobs, you must stop all jobs which have locked the kernel library using option 4 (End job).
Note
The kernel library of an SAP system is normally locked when someone is logged on as
b. To check the database library, log on as QSECOFR or your installation user and enter the following command:
WRKOBJLCK OBJ(R3
and/or
WRKOBJLCK OBJ(SAP
If the command WRKOBJLCK gives you a list of jobs, you must stop all jobs which have locked the database library using option 4 (End job).
Results
Now most likely no objects are locking any object of the SAP system anymore and the installer will run without any locking problem.
Next Steps
Distributed systems only:
After the file system has been renamed on the global host, you must adjust the link of the remote host to the global directories of the SAPGLOBALHOST. The following steps are not required for the rename of a standard system.
The name of the current remote
You must enter the following commands on the remote host only, not on the global host:
1. Change the link /sapmnt/
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 23 Note
Only valid for distributed SAP systems with distributed database instance and without ASCS instance:
After the rename of the database instance on the remote host, the link to the SAPGLOBALHOST has to be newly set even if the file system on the SAPGLOBALHOST is not already renamed and the new link cannot be resolved.
2. Change the link /usr/sap/
3.5 Performing SAP MaxDB liveCache-Specific Preparation Steps on IBM i
This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on IBM i, before starting the system rename procedure.
Note
The SAP liveCache server is not supported on IBM i. The preparation steps for the SAP liveCache server must be done on the respective host. You must use the rename documentation for UNIX or Windows, corresponding to the operating system of the host where your SAP liveCache server is installed.
Performing SAP MaxDB liveCache-Specific Preparation Steps on UNIX [page 24] This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on UNIX, before starting the system rename procedure.
Performing SAP MaxDB liveCache-Specific Preparation Steps on Windows [page 25] This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on Windows, before starting the system rename procedure.
3.5.1 Performing SAP MaxDB liveCache-Specific Preparation Steps on UNIX
This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on UNIX, before starting the system rename procedure.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 24 PUBLIC Preparation Procedure
1. On the target host, create the SAP liveCache OS group sdba and the SAP liveCache OS user sdb. The group and the user must have the same IDs as on the source SAP liveCache host. 2. Make available the entire SAP liveCache file system content from the source host on the target host with the following directories (if available), while keeping the ownership and access permissions:
/sapdb/
/sapdb/clients/
/sapdb/programs
/sapdb/data
/etc/opt/sdb
/usr/spool/sql
/var/lib/sdb 3. If the directories are implemented on the mount points, pay attention to the following: ○ The directory /sapdb/
3.5.2 Performing SAP MaxDB liveCache-Specific Preparation Steps on Windows
This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on Windows, before starting the system rename procedure.
Note
The SAP MaxDB liveCache server is not supported on IBM i. The preparation steps for the SAP MaxDB liveCache server must be done on the respective host. You must use the rename documentation for
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 25 Windows, corresponding to the operating system of the host where your SAP MaxDB liveCache server is installed.
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:
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 45] for the liveCache rename.
3.6 Performing SAP MaxDB liveCache Client-Specific Preparation Steps on IBM i
This section describes the prerequisites and preparation steps that you have to perform for SAP Max DB liveCache client (“SAP liveCache client” for short) on IBM i, before starting the system rename procedure.
Note
At the moment, in this section there are no preparation steps on IBM i that you have to perform. And there are no steps you have to perform on Unix or Windows.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 26 PUBLIC Preparation 3.7 Configuring TCP/IP
Use
This section describes how to integrate IBM i into your TCP/IP network.
Prerequisites
Before configuring TCP/IP, you must do the following:
● Make sure that you have the following information: ○ The interface of your IBM i to which the Local Area Network is attached ○ The IP addresses of your IBM i, subnet mask, and router or Gateway ○ The local domain name ○ The IBM i host name ● Decide on your IBM i host name. The host name cannot be longer than eight characters although SAP allows 13 characters as of Release 4.6. For more information, see SAP Note 611361 .
Note
The TCP/IP configuration on IBM i is case sensitive. Do not enter your host name once in uppercase and then in lowercase characters. It is important that you enclose your host name entry in single quotation marks. Otherwise, the IBM i interprets the characters as uppercase characters.
Procedure
Note
An IP address is a unique address in a TCP/IP network for a particular IBM i. A subnet mask is a mask used to divide a single network address into multiple logical networks.
1. To change the name of the computer, enter the command chgneta and prompt F4 . You must then enter the following information and choose ENTER : ○ System name ○ Local network ID ○ Default local location name
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 27 The following screen appears:
2. To set up the description line, enter the command WRKHDWRSC TYPE(*CMN) and proceed as follows: 1. On the Work with Communication Resources screen, enter option 5 (Work with configuration descriptions) for the port and choose ENTER . 2. On the Work with Configurations Description screen, enter option 1 (Create) to enter the description gigaline or ethline and choose ENTER . On the following screen, enter the line speed and duplex and then press F10 and page down two screens.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 28 PUBLIC Preparation On the Create Line Desc (Ethernet) (CRTLINETH) screen, make sure the autocreate controller is set to *yes.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 29 3. To call the TCP/IP configuration menu, enter the command CFGTCP and proceed as follows: 1. To work with interfaces, enter option 1 (Work with TCP/IP interfaces).
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 30 PUBLIC Preparation The following screen appears:
You need at least two entries: one for the loopback entry and one for the IP address of your IBM i. The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 and line description *LOOPBACK. To add an entry, enter option 1 (ADD) and choose ENTER . Add entries for the first three fields and accept the default values for the other fields. 2. To work with routes, enter option 2 (Work with TCP/IP routes).
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 31 The following screen appears:
If the route to the remote host, in this case the PC workstation, is through a Gateway or if the remote host resides in a different network or subnetwork to the local host, you need to configure a route. 3. To change the domain information, enter option 12 (Change TCP/IP domain information).
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 32 PUBLIC Preparation The following screen appears:
Note
It is important that you enclose your host name entry in single quotation marks. If you do not, the IBM i interprets the characters as uppercase characters.
If you have one or more remote name servers, you need to define the IP address here. Note that the Host name server priority must be set to *LOCAL.
Testing the TCP/IP Connection
Before proceeding with the SAP installation (that is, the installation of the executable programs), check that this TCP/IP connection has been set up correctly. To do so, enter the command ping (Network Connection) specifying your own system as Remote system. Do this twice, once specifying only
Example
In this example we assume that the host name is as0008 and the domain name is wdf.sap.corp. In this case, your entries are the following:
● ping 'as0008'
● ping 'as0008.wdf.sap.corp'
After installing the SAP system kernel, check the TCP/IP connection again with the command:
WRKLNK '/QFileSvr.400/
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 33 Your host name should be displayed under Object link, for example, as0008 for the host in the example given above.
For more information about TCP/IP configuration, see the IBM documentation in the IBM Knowledge Center.
Result
The IBM i is integrated into your TCP/IP network.
3.8 Adjusting the Relational Database Name
Use
You use the following procedure to adjust the local relational database name (RDB name) so it is the same as the TCP/IP host name.
Note
The *Local database name must match the TCP/IP host name for the SAP system to work properly.
Procedure
1. Log on to your database host as user QSECOFR. 2. To display your TCP/IP host name, enter the following command and press F4 : CHGTCPDMN 3. Search for the contents of HOSTNAME. This is your TCP/IP host name. 4. Before you can adjust the local RDB name, you have to check if the entry remote location equals *Local exists. To do this, enter the following command: WRKRDBDIRE 5. Depending on the outcome, proceed as follows: ○ If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 34 PUBLIC Preparation To do this, enter the following command: ADDRDBDIRE RDB(
3.9 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 35] 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.
3.9.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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 35 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. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589 . Afterwards, do not forget to perform an IPL to make the change effective. Otherwise, the file copying is very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i. 3. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the following command:
Note
Make sure that all users have at least read permissions for the directory to which you unpack the installer.
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.
4. We recommend that you copy the Software Provisioning Manager 1.0 to the IFS of the IBM i host. For more information about how to do this, see the section Copying the Installation Media Manually to Your IBM i [page 36].
3.10 Copying the Installation Media Manually to Your IBM i
This section describes a secure way to copy the required installation media from your Windows PC to your IBM i using OS version V7R2 and higher. To copy the media, you have to use a binary share TMPSAP. This guarantees that the content of the media is copied correctly from the Windows PC to your IBM i. No copied content is corrupted, and no copied files with longer file names are shortened by a converting share.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 36 PUBLIC Preparation Note
This procedure should not be used on a V7R1 IBM i host. On V7R1, you must use an alternative method such as FTP.
Note
In the past, we suggested to create a binary share pointing to the root directory / on your IBM i host. We do not recommend this because it is not considered secure anymore.
Procedure
Creating a Binary Share on IBM i
If you do not already have a binary share TMPSAP on your IBM i, and you want to copy manually media from your Windows PC into the IFS of your IBM i, you have to create this share manually using the IBM Systems Director Navigator for i. To do so, proceed as follows:
1. Start the IBM Systems Director Navigator for i on your Windows PC. 2. Connect to your IBM i using My Connections. 3. To create or change the share TMPSAP, choose File Systems File Shares . 4. Right-click File Shares Open i5/OS Netserver . A new screen i5/OS Netserver appears. 5. Click the folder Shared Objects to see the shares. 6. To check the already existing share TMPSAP or create a new share TMPSAP, right-click New File .
Note
The share TMPSAP must have the access permission Read/Write and the path name should be /tmp/ SAP. If the directory /tmp/SAP does not exist directly create it manually as QSECOFR or installation user using the following command:
mkdir /tmp/SAP .
7. On the Text Conversion tab, do not select Allow file text conversion. 8. To save the share TMPSAP, press OK.
Now you have created the share TMPSAP on your IBM i.
Copying the Installation Media Manually Using the Binary Share TMPSAP
1. To open the command prompt on Windows, choose Start Run . 2. Enter cmd.exe. 3. Press OK. The command prompt appears. 4. In the command prompt, enter net use.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 37 All network connections to shared resources are displayed. 5. Only valid for 'Software Component': SAP CRM, SAP ERP, SAP NetWeaver, SAP SRM Check if you have a connection to your IBM i. If you find \\
Note
We use the user name SAPIUSR and the password SAP as examples. For more information about how to create the installation user SAPIUSR, see Preparing the SAP Installation User on IBM i [page 39].
End of 'Software Component': SAP CRM, SAP ERP, SAP NetWeaver, SAP SRM 6. Only valid for 'Software Component': SAP SCM Check if you have a connection to your IBM i. If you find \\
Note
For more information about how to prepare the user QSECOFR, see Preparing the SAP Installation User onIBM i [page 39].
End of 'Software Component': SAP SCM 7. To change to the new network drive, enter X: in the command prompt. 8. Create the subdirectories in your IFS where you want to copy the required media. For each media, enter: mkdir /tmp/SAP/
Note
You must avoid blanks or commas in the media path name.
9. Copy the installation media from your Windows drive (for example D:\) or your download directory to the IFS of your IBM i host by entering the following command: xcopy D:\ X:\
Note
You must copy the root directory of the media respectively of the
10. For each required media, create a subdirectory and copy the required media.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 38 PUBLIC Preparation Note
For advanced users only: Instead of copying the complete media you also can copy only dedicated subdirectories. For IBM i the following directories have to be copied:
● K_
3.11 Preparing the SAP Installation User on IBM i
For running the installer, you must create the SAP installtion user profile on the IBM i host.
The following requirement applies:
● The SAP installation user profile on IBM i must have user class *SECOFR and all special authorities that belong to the user QSECOFR. ● SCM Only: The IBM i installation user profile must be the user QSECOFR.
Note
This is different to other installations on IBM i. For other installations, we recommended that you create user SAPIUSR. However for SCM, you need to use the user QSECOFR because the liveCache client software has to be installed by this special user.
Procedure
Note
The user name SAPIUSR and the password SAP are used as examples. You can use a different user name for the SAP installation user. Make sure you do not user SAP as the password as this is not secure.
To create the SAP installation user profile, enter the following command:
CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
SCM Only: To change the user QSECOFR, enter the following command:
CHGUSRPRF USRPRF(QSECOFR) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
After the installation, you can revert the user profile QSECOFR back to the old values.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 39 Caution
You should not set the system variable QIBM_PASE_CCSID. Do not leave this variable empty. Make sure that QIBM_PASE_CCSID is deleted at least for the time while you are installing your SAP system using the following command:
RMVENVVAR ENVVAR(QIBM_PASE_CCSID) LEVEL(*SYS)
Note
In previous releases, we recommended that you create the user SAPINST on IBM i to install the SAP system. In the current release, a group SAPINST is created generically on all platforms and is used for the installation of the SAP system. If the user SAPINST already exists on your system, you must delete this user. If you do not want to delete this user for any reason, you must add to the user profile SAPINST the feature of a group by adding SAPINST to the group of a SAP installation user profile such as SAPIUSR. To do this, use the following command:
CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST)
Now the user SAPINST can also be used as a group by the installer.
Note
If you have already an old SAP installation user and you want to make sure this user is configured correctly for your next SAP system installation, enter the following command:
CHGUSRPRF USRPRF(SAPIUSR) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE)
Note
In a distributed environment, the SAP installation user must have the same name and password on all hosts so that the required remote access permissions are available. For example, the profile directory on the global host should be accessible to the SAP installation user of a remote additional application server instance.
3.12 Enable the User QSECOFR
The user QSECOFR is the standard administrator user on IBM i. This user has the most authority. For running the installer on IBM i, the user QSECOFR must be enabled. Although for running the installer you only require the installation user, the SAP kernel tools on IBM i need some adopted permissions from the user QSECOFR. If the user QSECOFR is disabled this will lead to errors when SAP kernel tools such as CRTR3INST are called.
Note
If the SAP Host Agent release 7.21, patch level 43 and higher is used, the QSECOFR can be disabled. Whether the QSECOFR needs to be disabled depends on the customer's security concept. As of SAP Host Agent release 7.21, patch level 43, the installation no longer requires an enabled QSECOFR.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 40 PUBLIC Preparation For more information, see SAP Note 1031096 - Installing Package SAPHOSTAGENT.
Procedure
1. To check the status of the user profile QSECOFR use the following command using your installation user: DSPUSRPRF USRPRF(QSECOFR) 2. To enable the user QSECOFR use the following command using your installation user: CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)
Note
In a distributed environment, the installation user must have the same name and password on all hosts so that the required remote access permissions are available. For example, the profile directory on the global host should be accessible to the installation user of a remote additional application server instance.
Recommendation
Check also if the password of the user QSECOFR is expired. To do this, login as QSECOFR. When the password is already expired you will be asked for a new password. Set a new password and the password of QSECOFR is then no longer expired.
Only when the password of the QSECOFR is not expired the installation procedure will finish successfully.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Preparation PUBLIC 41 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
Note
For IBM i, the database is always up and running.
● Instance services of an IBM i operating system ● ABAP Central services instance (ASCS instance) if an ASCS instance is available
Note
If you do not change the SAPSID, the installer does not have to rename or change the database library and the journal receiver library. This will speed up the rename process as renaming a database library and stopping or starting the journaling is time consuming.
Note
Only SAP systems are renamed, which are using the SAP NetWeaver 7.20 kernel or higher.
Note
The installer is not able to change objects that are locked. Make sure that no object of the to be renamed SAP system is locked. For more information, see Perfoming IBM i-Specific Preparation Steps [page 22].
Central System
You check the Prerequisites for Running the Installer [page 43] and run the installer to rename the system as described in Running the Installer [page 45].
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 42 PUBLIC System Rename Procedure Distributed and High-Availability System
Note
See also table System Rename Options and Sequence how to Execute Them in Running the Installer [page 45].
1. If your SAP system has an ASCS instance, you check the Prerequisites for Running the Installer [page 43] and run the installer to rename the ASCS instance as described in Running the Installer [page 45]. 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. 3. You check the Prerequisites for Running the Installer [page 43] and run the installer to rename the database instance as described in Running the Installer [page 45]. 4. You check the Prerequisites for Running the Installer [page 43] and run the installer to rename the primary application server instance as described in Running the Installer [page 45]. 5. Optional: You check the Prerequisites for Running the Installer [page 43] and run the installer to rename existing standalone Gateway instances as described in Running the Installer [page 45]. 6. Optional: You check the Prerequisites for Running the Installer [page 43] and run the installer to rename the SAP Web Dispatcher instance as described in Running the Installer [page 45].
Next Steps
You perform follow-up activities [page 64]
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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 43 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 45]. 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 51].
● Make sure that you have logged on to your host as an installation user with similar authorization rights to QSECOFR. For more information about how to create an installation user, see Preparing the SAP Installation User on IBM i [page 39]. ● Check the value of the temporary directory set in the environment if available:
Shell Command
Command prompt WRKENVVAR
Qp2Term echo $TEMP, echo $TMP or echo $TMPDIR
● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry. ● Each SAP instance requires a separate installation directory.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly installed.
● Make sure that you have 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. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables. You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 51]. ● 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. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTPS_PORT=
Example
CD DIR('
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 44 PUBLIC System Rename Procedure CALL PGM(QP2TERM) PARM('./sapinst' 'SAPINST_HTTPS_PORT=
○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing. The filled-out evaluation form is then sent to SAP using HTTPS. If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=
● If you have changed the host name of your system, you also have to perform the steps described in sections Configuring TCP/IP [page 27] and Adjusting the Relational Database Name [page 34].
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 43].
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 51].
Procedure
1. Log on to the host where you want to run the installer.
Make sure that you log on as a user with similar authorization rights to QSECOFR. For more information, see Preparing an IBM i User Profile [page 39].
Caution
Make sure that the installation user has not set any environment variables for a different SAP system or database by using the command WRKENVVAR.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 45 If your security policy requires that the person running the installer is not allowed to know QSECOFR like 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 the sapinst executable 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 35]. Recommendation
Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.
3. Start the installer as follows:
Open a command prompt and enter the following command:
CD DIR('
CALL PGM(QP2TERM) PARM(’./sapinst’) Note
If you want to use a virtual host name, start the installer with the installer property SAPINST_USE_HOSTNAME as follows:
CALL PGM(QP2TERM) PARM(’./ sapinst’ ’SAPINST_USE_HOSTNAME=
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when starting the Java Virtual Machine.
4. The installer is starting up.
The installer now starts and waits for the connection with the SL Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.
... ************************************************************************ 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 IBM i 46 PUBLIC System Rename Procedure You can use a fully-qualified host name.
Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page 43]).
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: /home/
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 SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 47 Option Description When to Execute Execution Order
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 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. 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 IBM i 48 PUBLIC System Rename Procedure Caution
When performing a rename of a distributed SAP system, the UID of the user
The installer asks you in the Define Parameters phase of the ASCS instance for the password of the user
In this screen, you must also set an appropriate UID for the
If the chosen UID is already used on one of the hosts, the rename procedure will fail.
For an easy way to check if a chosen UID is already in use on an IBM i host you can use the IBM i system table QSYS2.USER_INFO.
Use the following SQL statement:
SELECT COUNT(USER_ID_NUMBER) FROM QSYS2.USER_INFO WHERE USER_ID_NUMBER=
If the SQL result set is 0 for the chosen UID, then the UID is not in use by any user profile of that specific host. Do this check on all related IBM i hosts, to make sure your chosen UID is available everywhere you need it for the rename of the distributed SAP system.
Caution
Whenever you are asked by the installer for the password of the user
DSPUSRPRF USRPRF(
CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' '
The SCS or ASCS installation is the installation which initially determinates the UID of the user
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 .
8. 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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 49 9. 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
Recommendation
Keep all installer directories until you are sure that the system, including all instances, is completely and correctly installed. Once the system is completely and correctly installed, make a copy of the installer directories with all their contents. Save the copy to a physically separate medium, such as a medium or a USB drive that is separate from your installation hosts.
This might be useful for analyzing any issues that might occur later when using the system. For security reasons, do not keep the installer directories on hosts where you processed it, but make sure that you delete them after saving them separately.
11. If you copied installation media to your hard disk, you can delete these files when the installer has successfully completed.
Note
For more information about how to remove the installer files on IBM i, see Removing the Installer Installation Files [page 61].
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:
/home/
Note
This step is only required, if you did not specify during the Define Parameters phase that the group SAPINST is to be removed from the operating system users after the execution of the installer has completed.
14. 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 51].
Related Information
Useful Information about the Installer [page 51] Interrupted Processing of the Installer [page 57]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 50 PUBLIC System Rename Procedure Troubleshooting with the Installer [page 60]
4.4 Additional Information about the Installer
The following sections provide additional information about the installer.
Useful Information about the Installer [page 51] This section contains some useful technical background information about the installer and the installer GUI.
System Provisioning Using a Parameter Input File [page 53] 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 57] Here you find information about how to restart the installer if its processing has been interrupted.
Troubleshooting with the Installer [page 60] This section tells you how to proceed when errors occur while the installer is running.
Removing the Installer Installation Files [page 61]
Using the Step State Editor (SAP Support Experts Only) [page 62] 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 at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there. For more information about supported web browsers see Prerequisites for Running the Installer [page 43]. If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of your web browser.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 51 ● As soon as you have started the sapinst executable, the installer creates a .sapinst directory underneath the /home/
Shell Used Command
Command prompt ADDENVVAR ENVVAR(TEMP) VALUE('
Qp2Term export TEMP=
Note
When you leave your Qp2Term session, all changes of the environment variables done by the command export are reverted.
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started.
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 the temporary directory. These executables are deleted again 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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 52 PUBLIC System Rename Procedure 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, enter the following commands: CD DIR('
● If required, stop the installer by choosing the Cancel button.
Note
If you need to terminate the installer, press Shift + Esc then 2 on your IBM i host.
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 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 51]) 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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 53 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 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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 54 PUBLIC System Rename Procedure 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
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 45]. 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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 55 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 45] 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=
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 64].
Related Information
SAP Note 2849054 SAP Note 2742212 SAP Note 2626837 SAP Note 2669183
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 56 PUBLIC System Rename Procedure 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.
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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 57 Procedure
1. Log on to the installation host as a user with the required permissions as described in Running the Installer [page 45] . 2. Make sure that the media required for the system rename are still available.
For more information, see Preparing the System Rename Media [page 35] .
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 from the installation media directory to which you unpacked the Software Provisioning Manager archive.
Enter the following commands:
CD DIR('
CALL PGM(QP2TERM) PARM('./sapinst') 4. The installer is restarting.
The installer now starts and waits for the connection with the SL Common GUI.
You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.
... ************************************************************************ Open your browser and paste the following URL address to access the GUI
https://[
Logon users: [
************************************************************************ ...
Note
If the host specified by
Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page 43]).
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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 58 PUBLIC System Rename Procedure 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: /home/
The SL Common GUI opens in the browser by displaying the Welcome screen. 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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 59 Alternative Behavior
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
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 them in the .sapinst directory underneath the /home/
For more information, see Useful Information about the Installer [page 51].
○ To check the log and trace files of the installer GUI for errors, go to the directory /home/
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 60 PUBLIC System Rename Procedure 4.4.5 Removing the Installer Installation Files
You use this procedure to gain disk space after the installation by deleting the installer.
On the IBM i host, you should remove the installation directory, the temporary installer files, and the copied installation media.
Caution
You might want to disconnect from the share TMPSAP and remove it from the IBM i. However, if you want to start tools like the SAP NetWeaver AS for Java EE ConfigTool from the share TMPSAP on your Windows PC, then you should keep the share.
Caution
Do not use this procedure until all instances of the SAP system on the IBM i host have been installed.
Prerequisites
● You have completed the SAP system installation. ● The SAP system is up and running.
Procedure
Caution
Only delete the log files if you are sure that you do not need them again. Do not delete log files other than those in the paths given here.
On IBM i:
1. If you want to remove the installer installation directory, enter the following command: RMVDIR DIR('
Note
If you have chosen one of the three variables: TEMP, TMP, or TMPDIR for your temporary directory in section Useful Information about the Installer [page 51], you must use this temporary directory instead of '/tmp'.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i System Rename Procedure PUBLIC 61 4. To remove the downloaded and/or copied installation media, enter the following command: RMVDIR DIR('/tmp/sap/
To disconnect your mapped drive from the IBM i, enter the following command on your Windows PC: net use
4.4.6 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 43].
Procedure
1. Start the installer from the command line as described in Running the Installer [page 45] 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:
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 62 PUBLIC System Rename Procedure ○ 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 IBM i System Rename Procedure PUBLIC 63 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 69].
The installer has only started the following instances during the system rename: ○ Database
Note
For IBM i, the database is always up and running.
○ Instance services of an IBM i 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 65]. 3. Configure the transport management system.
For more information, see Configuring the Transport Management System [page 69]. 4. Perform follow-up activities for your database.
For more information, see Performing Follow-Up Activities for IBM Db2 for i [page 66].
If your SAP SCM system has SAP MaxDB liveCache, see also the follow-up activies in section Performing SAP MaxDB liveCache-Specific Follow-Up Activities on IBM i [page 66]. 5. Restart the renamed SAP system completely.
For more information, see Starting the SAP System [page 69]. 6. Change the IGS destination.
For more information, see Changing the IGS Destination [page 70].
Related Information
General Follow-Up Activities [page 65] Database-Specific Follow-Up Activities [page 65]
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 64 PUBLIC Follow-Up Activities Configuring the Transport Management System [page 69] Changing the IGS Destination [page 70] Starting the SAP System [page 69] Removing the Installer Installation Files [page 61]
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 16] 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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Follow-Up Activities PUBLIC 65 5.1.2.1 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.2 Performing Follow-Up Activities for IBM Db2 for i
In addition to the follow-up activities described in the system copy documentation, you must perform the following follow-up activities for system rename.
Procedure
1. Identify and delete the backup of the journal receiver library of the source system.
The backup was created by the installer, using the command SAVLIB on the journal receiver library into a SAVE FILE of a backup library. The naming convention of the backup library is the following:
R3
Correct the CDS Views of your ABAP stack after the rename of your SAP system based on SAP NetWeaver 7.4 and higher.
For more information, see SAP Note 2368628 .
5.1.2.3 Performing SAP MaxDB liveCache-Specific Follow- Up Activities on IBM i
This section describes the follow-up activities that you have to perform for SAP MaxDB liveCache (“SAP liveCache” for short) on IBM i, before starting the system rename procedure.
Note
The SAP liveCache server is not supported on IBM i. The follow-up activities for the SAP liveCache server must be done on the respective host. You must use the rename documentation for UNIX or Windows, corresponding to the operating system of the host where your SAP liveCache server is installed.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 66 PUBLIC Follow-Up Activities Performing Follow-Up Activities for SAP MaxDB liveCache on UNIX [page 67] After the rename of the SAP MaxDB liveCache on UNIX some manual follow-up activities are required.
Performing Follow-Up Activities for SAP MaxDB liveCache on Windows [page 68] This section contains follow-up steps required for SAP MaxDB liveCache on Windows after the system rename has completed.
Performing SAP MaxDB liveCache Client-Specific Follow-Up Activities on IBM i [page 69] This section describes the follow-up activities that you have to perform for SAP Max DB liveCache client (“SAP liveCache client” for short) on IBM i, after having completed the system rename procedure.
5.1.2.3.1 Performing Follow-Up Activities for SAP MaxDB liveCache on UNIX
After the rename of the SAP MaxDB liveCache on UNIX some manual follow-up activities are required.
Note
The SAP MaxDB liveCache server is not supported on IBM i. The follow-up activities for the SAP MaxDB liveCache server must be done on the respective host. You must use the rename documentation for UNIX, corresponding to the operating system of the host where your SAP MaxDB liveCache server is installed.
Context
Manually change the SAP liveCache connection information for the database connections LCA, LDA, and LEA by performing the following steps for each connection.
Procedure
1. Connect to the SAP system using the SAP liveCache and start transaction LC10. 2. In the field Name of Database Connection enter the required name, for example LCA. 3. Click on Integration . 4. Click on the icon Display <—> Change or press Shift and F1 . 5. Update the configuration with the new SAP liveCache data as required. 6. Save the data .
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Follow-Up Activities PUBLIC 67 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.2 Performing Follow-Up Activities for SAP MaxDB liveCache on Windows
This section contains follow-up steps required for SAP MaxDB liveCache on Windows after the system rename has completed.
Note
The SAP MaxDB liveCache server is not supported on IBM i. The follow-up activities for the SAP MaxDB liveCache server must be done on the respective host. You must use the rename documentation for UNIX, corresponding to the operating system of the host where your SAP MaxDB liveCache server is installed.
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
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i 68 PUBLIC Follow-Up Activities 5.1.2.3.3 Performing SAP MaxDB liveCache Client-Specific Follow-Up Activities on IBM i
This section describes the follow-up activities that you have to perform for SAP Max DB liveCache client (“SAP liveCache client” for short) on IBM i, after having completed the system rename procedure.
Note
At the moment, in this section there are no follow-up activities on IBM i that you have to perform. And there are no steps you have to perform on Unix or Windows.
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 SAP System Instances in the installation guide [page 16] for your operating system platform and database or the SAP Library [page 17] at:
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.
System Rename for SAP Systems Based on Application Server ABAP of SAP NetWeaver 7.3 EHP1 to 7.52 on IBM i Follow-Up Activities PUBLIC 69 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 IBM i 70 PUBLIC Follow-Up Activities 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 IBM i Important Disclaimers and Legal Information PUBLIC 71 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