Operations Guide | PUBLIC Software Provisioning Manager 2.0 SP09 Document Version: 1.9.0 – 2021-06-21

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 This Guide is Valid for SAP Systems based on the Following SAP Product Versions: - SAP BW/4HANA 1.0 Support Release 1 company. All rights reserved. affiliate

THE BEST RUN 2021 SAP SE or an SAP © Content

1 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0...... 5 1.1 About Software Provisioning Manager 2.0...... 6 SAP Products Supported by Software Provisioning Manager 2.0...... 7 1.2 Use Cases of System Rename...... 8 1.3 How to Use this Guide...... 8 1.4 Naming Conventions...... 9 1.5 New Features...... 9 1.6 Constraints...... 11 1.7 Accessing the Installation Guides and System Copy Guides...... 12 1.8 Accessing the SAP Online Documentation...... 12

2 Planning...... 14

3 Preparation...... 15 3.1 Preparation Checklist...... 15 3.2 General Technical Preparations ...... 16 3.3 Maintaining Users and Groups...... 17 3.4 Deleting Additional Application Server Instances...... 17 3.5 Performing SAP HANA Database-Specific Preparation Steps...... 19 3.6 Performing IBM i - Specific Preparation Steps...... 19 3.7 Configuring TCP/IP...... 21 3.8 Adjusting the Relational Database Name...... 28 3.9 Downloading and Extracting the Software Provisioning Manager 2.0 Archive...... 29 Copying the Installation Media Manually to Your IBM i...... 30 3.10 Preparing the SAP Installation User on IBM i...... 33 3.11 Enable the User QSECOFR...... 34

4 System Rename Procedure...... 36 4.1 System Rename Procedure Checklist...... 36 4.2 Prerequisites for Running the Installer...... 37 4.3 Running the Installer...... 39 4.4 Additional Information about the Installer...... 44 Useful Information about the Installer...... 45 System Provisioning Using a Parameter Input File...... 47 Interrupted Processing of the Installer...... 51 Troubleshooting with the Installer...... 54 Removing the Installer Installation Files...... 55

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 2 PUBLIC Content Using the Step State Editor (SAP Support Experts Only)...... 56

5 Follow-Up Activities...... 58 5.1 Follow-Up Activities Checklist...... 58 5.2 General Follow-Up Activities...... 59 5.3 Performing Follow-Up Activities in the Source System...... 60 5.4 Performing Follow-Up Activities in the Target System...... 60 Performing Follow-Up Activities for ABAP...... 60 Performing Product-Specific Follow-Up Activities...... 66 5.5 Configuring the Transport Management System...... 67 5.6 Performing Follow-Up Activities for SAP HANA Database...... 67 5.7 Starting the SAP System...... 68 5.8 Changing the IGS Destination...... 68

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 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://help.sap.com/viewer/swpm20guides

The following table provides an overview on the most important document changes:

Version Date Description

1.9.0 2021-06-21 Updated version for Software Provisioning Manager 2.0 SP09 (SL Toolset 1.0 SP32)

1.8.0 2021-02-15 Updated version for Software Provisioning Manager 2.0 SP08 (SL Toolset 1.0 SP31)

1.7.0 2020-10-05 Updated version for Software Provisioning Manager 2.0 SP07 (SL Toolset 1.0 SP30)

1.6.0 2020-06-08 Updated version for Software Provisioning Manager 2.0 SP06 (SL Toolset 1.0 SP29)

1.5.0 2020-01-20 Updated version for Software Provisioning Manager 2.0 SP05 (SL Toolset 1.0 SP28)

1.4.0 2019-09-16 Updated version for Software Provisioning Manager 2.0 SP04 (SL Toolset 1.0 SP27)

1.3.0 2019-05-27 Updated version for Software Provisioning Manager 2.0 SP03 (SL Toolset 1.0 SP26)

1.2.0 2019-01-21 Updated version for Software Provisioning Manager 2.0 SP02 (SL Toolset 1.0 SP25)

1.1.0 2018-09-17 Updated version for Software Provisioning Manager 2.0 SP01 (SL Toolset 1.0 SP24)

1.0.0 2018-04-23 Initial version for Software Provisioning Manager 2.0 SP00 (SL Toolset 1.0 SP23)

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 4 PUBLIC Document History 1 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0

This documentation describes how to rename SAP Appliaction Server ABAP systems using Provisioning Manager 2.0 SP09 (the “installer” for short) on IBM i.

It covers the following SAP ABAP system product releases (see also SAP Products Supported by Software Provisioning Manager 2.0 [page 7]):

● SAP BW/4HANA 1.0 Support Release 1 (based on SAP BW/4HANA Server 1.0 Support Release 1)

For information about supported operating system and database platforms, see the Product Availability Matrix at https://support.sap.com/pam .

Software Provisioning Manager 2.0 SP09 [page 6] is part of Software Logistics Toolset 1.0 SP32.

 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 2.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.

About Software Provisioning Manager 2.0 [page 6]

Use Cases of System Rename [page 8]

How to Use this Guide [page 8]

Naming Conventions [page 9]

New Features [page 9]

Constraints [page 11]

Accessing the Installation Guides and System Copy Guides [page 12]

Accessing the SAP Online Documentation [page 12]

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 PUBLIC 5 1.1 About Software Provisioning Manager 2.0

Software Provisioning Manager 2.0 is the new release of Software Provisioning Manager 1.0. Software Provisioning Manager as such is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst and R3setup.

Make sure that you read the most recent version of SAP Note 2568783 (Release Note for Software Provisioning Manager 2.0).

Before you run Software Provisioning Manager 2.0, we recommend that you always download the latest version of it. Software Provisioning Manager 2.0 is - as Software Provisioning Manager 1.0 - part of the Software Logistics Toolset 1.0 (“SL Toolset” for short) which is quarterly shipped. This way, you automatically get the latest fixes and supported processes. For more information about Software Provisioning Manager 2.0 as well as products and releases supported by it, see SAP Note 2568783 and http://scn.sap.com/docs/DOC-30236 .

Software Provisioning Manager 2.0 Versus Software Provisioning Manager 1.0

The Software Provisioning Manager 2.0 SP09 exists in parallel to Software Provisioning Manager 1.0 SP32. Both Software Provisioning Manager versions are part of Software Logistics Toolset 1.0 SP 32. However, they cover system provisioning for different product versions. The decision matrix is as follows:

● Software Provisioning Manager 2.0 is used for: ○ Installation, system copy, and system rename of ABAP single stack systems on SAP HANA 2.0 database, based on the following products: ○ SAP BW/4HANA 1.0 Support Release 1 ○ SAP Web Dispatcher installation and rename.

 Note

For SAP Web Dispatcher, you can either use Software Provisioning Manager 2.0 or Software Provisioning Manager 1.0.

○ SAP Host Agent standalone installation.

 Note

For SAP Host Agent standalone installation, you can either use Software Provisioning Manager 2.0 or Software Provisioning Manager 1.0.

● Software Provisioning Manager 1.0 is used for: ○ Installation, system copy, system rename of SAP Solution Manager 7.X and Diagnostics Agent. ○ Installation of standalone engines and clients.

 Note

For SAP Web Dispatcher or SAP Host Agent standalone installation, you can either use Software Provisioning Manager 1.0 or Software Provisioning Manager 2.0.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 6 PUBLIC 2.0 Database - Using Software Provisioning Manager 2.0 ○ Installation, system copy, system rename, and dual-stack split of SAP systems whose database is not SAP HANA. ○ Installation, system copy, and system rename of Dual-stack and Java single stack systems. ○ Installation, system copy, and system rename of ABAP single stack systems whose database is SAP HANA database, but whose release is one of the following: ○ SAP BW/4HANA 1.0 or lower ○ SAP S/4HANA 1709 or lower ○ SAP NetWeaver AS for ABAP 7.52 or lower

For more information, see https://blogs.sap.com/2018/05/15/software-provisioning-manager-1.0-vs.- software-provisioning-manager-2.0/ .

Naming Conventions

“SAPinst” has been renamed to “Software Provisioning Manager” (“installer” for short), 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 ● 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

In this documentation, we generally refer to Software Provisioning Manager as the “installer”. We only use the term “Software Provisioning Manager” if this is required for technical reasons, and “Software Provisioning Manager 2.0” if there is a significant difference compared to “Software Provisioning Manager 1.0”.

1.1.1 SAP Products Supported by Software Provisioning Manager 2.0

Here you can find the list of SAP products supported by Software Provisioning Manager 2.0.

SAP Product Based on

SAP BW/4HANA 1.0 Support Release 1 SAP NetWeaver 7.5

More Information

For more information about recommended application server platforms, see SAP Note 2620910 .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 PUBLIC 7 1.2 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 () ● Instance numbers of the instances on the SAP system ● Host names

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 .

1.3 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 12].

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].

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 8 PUBLIC 2.0 Database - Using Software Provisioning Manager 2.0 2. You follow the steps in each phase: ○ Planning [page 14] ○ Preparation [page 15] ○ Renaming [page 36] ○ Follow-Up Activities [page 58]

1.4 Naming Conventions

● “installer” refers to “Software Provisioning Manager 2.0” and to “Software Provisioning Manager” in general. ● “SAP system” or “ABAP system” refers to SAP systems based on: ○ SAP BW/4HANA 1.0 Support Release 1.

 Note

For the sake of simplicity, in the following we abbreviate this product as SAP BW/4HANA.

● Since - from a Software Provisioning Manager 2.0 perspective - the “Standalone Enqueue Server 2” is installed with the ASCS instance the same way as the classic “Standalone Enqueue Server”, both are addressed as “Standalone Enqueue Server” in this documentation. ● Since - from a Software Provisioning Manager 2.0 perspective - the “Enqueue Replicator 2” is installed with the ERS instance the same way as the classic “Enqueue Replication Server”, both are abbreviated as “ERS instance” in this documentation. ● Operating System Names As of operating system version IBM i 5.4, the operating system has been renamed from “IBM i5/OS” to “IBM i” (short form: “i”). The names of previous operating system versions remain unchanged. In this document, the name“IBM i” is used if we do not refer to a specific operating system version. If we refer to a specific version, we use the relevant operating system name.

1.5 New Features

The sections below provide an overview of the new features in Software Provisioning Manager 2.0 (the“ installer” for short).

Make sure that you also read the Release Notes for your SAP product at https://help.sap.com

What’s New .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 PUBLIC 9 Feature Description Availability

Support of SAP HANA SSL Certifi- Software Provisioning Manager 2.0 supports SAP HANA Software Provisioning Man­ cates ager 2.0 SP06 (SL Toolset SSL Certificates for configuring secure access to the 1.0 SP29) SAP HANA database.

For more information, see the installation guide [page 12].

Support of Secure Connection to Software Provisioning Manager 2.0 supports configuring Software Provisioning Man­ SAP HANA database. ager 2.0 SP03 (SL Toolset the SAP system to be installed to access the SAP HANA 1.0 SP26) database using encryption.

For more information, see the installation guide [page 12].

New Look and Feel of SL Common As of version 2.0 SP01 Patch Level (PL) 5, Software Pro­ Software Provisioning Man­ GUI visioning Manager comes with a new look and feel of the ager 2.0 SP01, PL05 (SL SL Common GUI. For more information, see https:// Toolset 1.0 SP24) blogs.sap.com/2018/11/10/new-look-for-software-provi­ sioning-manager/ .

Support of Standalone Enqueue For SAP systems based on ABAP Platform 1809 and Software Provisioning Man­ ager 2.0 SP01 (SL Toolset Server 2 and Enqueue Replicator 2 higher, Software Provisioning Manager 2.0 installs the 1.0 SP24) ASCS instance by default with the new Standalone En­ queue Server 2, and the ERS instance with the new En­ queue Replicator 2.

For more information about the Standalone Enqueue Server 2 and the Enqueue Replicator 2, see the SAP On­

line Documentation [page 12] at Application Server

ABAP Infrastructure Components of the Application

Server for ABAP SAP Lock Concept Standalone

Enqueue Server 2 .

ABAP Platform 1809 or higher: Ar­ For SAP systems based on ABAP Platform 1809 or Software Provisioning Man­ ager 2.0 SP01 (SL Toolset chive-Based Installation of all In­ higher, the database server and client software is pro­ 1.0 SP24) stallation Software vided as installation archives. which you can download from https://launchpad.support.sap.com/#/software­ center . Physical SAP HANA 2.0 database server and client media, as well as physical database installation ex­ port media and language media are no longer required for the installation.

Homogeneous System Copy Software Provisioning Manager 2.0 only supports homo­ Software Provisioning Man­ ager 2.0 SP00 (SL Toolset geneous system copy using a SAP HANA database 1.0 SP23) backup.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 10 PUBLIC 2.0 Database - Using Software Provisioning Manager 2.0 Feature Description Availability

New Installer Option Download If you perform an installation using a stack configuration Software Provisioning Man­ Software Packages for Maintenance file, you can now download the required software pack­ ager 2.0 SP00 (SL Toolset Planner Transaction ages according to a Maintenance Plan. For more infor­ 1.0 SP23) mation, see https://blogs.sap.com/2018/06/01/soft­ ware-provisioning-manager-new-option-for-standalone- download-service/ .

Software Provisioning Man­ Validity Check for SUM*.SAR Ar­ If you perform an installation using a stack configuration ager 2.0 SP00 (SL Toolset chive file and choose to extract the SUM*.SAR archive, the val­ 1.0 SP23) idity of this archive is now checked by the installer.

1.6 Constraints

● Software Provisioning Manager 2.0 is only supported for SAP HANA 2.0 database.

● SAP System ID Make sure that your SAP system ID: ○ Is unique throughout your organization. Do not use an existing . ○ 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 . ● Database ID The identifies the database instance. It is always the same as the . Make sure that your database ID: ○ Is unique throughout your organization ○ Consists of exactly three alphanumeric characters ○ Contains only uppercase letters ○ Has a letter for the first character ○ Does not include any of the reserved IDs listed in SAP Note 1979280 . ● 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. ● The installer currently does not support the independent auxiliary storage pool (IASP). If your SAP system is installed on an IASP, you must use system copy to rename it. For more information, see the system copy guides at http://support.sap.com/sltoolset System Provisioning System Copy Option of Software Provisioning Manager 2.0 .

Database-Specific Restrictions

SAP HANA Rename of the SAP HANA database schema is not supported.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 PUBLIC 11 You can only rename the DBSID of the SAP HANA database, but you cannot rename the schema of the SAP HANA database.

More Information

For more constraints, see SAP Note 1619720 .

1.7 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:

● The “ installation guide” for your operating system platform at: https://support.sap.com/sltoolset System Provisioning Install a System using Software Provisioning Manager Installation Option of Software Provisioning Manager 2.0 SP Installation Guides - Application Server Systems Installation Guides - Application Server Systems - Software Provisioning Manager 2.0 ● The “system copy guide” for your operating system platform at:. https://support.sap.com/sltoolset System Provisioning Copy a System using Software Provisioning Manager System Copy Option of Software Provisioning Manager 2.0 SP System Copy Guides - Software Provisioning Manager 2.0

1.8 Accessing the SAP Online Documentation

This section contains the paths for the product-specific online documentation referenced from this documentation.

The references to the SAP Online Documentation in this guide always refer to the following on the SAP Help Portal:

● SAP systems based on SAP S/4HANA Foundation 2020 (“ABAP Platform 2020” for short): https://help.sap.com/s4hana <2020 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform ● SAP systems based on SAP S/4HANA Foundation 1909 (“ABAP Platform 1909” for short): https://help.sap.com/s4hana <1909 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 12 PUBLIC 2.0 Database - Using Software Provisioning Manager 2.0 ● SAP systems based on foundation on ABAP Platform 1809, version for SAP HANA (“ABAP Platform 1809” for short): https://help.sap.com/s4hana <1809 Latest> Discover Product Assistance SAP S/4HANA Enterprise Technology ABAP Platform ● SAP systems based on SAP BW/4HANA 2.0: https://help.sap.com/viewer/p/SAP_BW4HANA 2.0 Application Help SAP BW/ 4HANA Application Server for ABAP ABAP Platform ● SAP systems based on SAP BW/4HANA 1.0 SR1 (): https://help.sap.com/viewer/p/SAP_BW4HANA 1.0 Application Help SAP BW/4HANA Application Server for ABAP SAP NetWeaver Library: Function-Oriented View

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 About this Document - System Rename for SAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 PUBLIC 13 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 ● 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 12] for your operating system platform: ○ 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 17] from the system before the system rename. 2. Reinstall the additional application server instances on the system after the system rename.

○ Host names ● 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 12] for your operating system platform). ● 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 12] for your operating system platform.

 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. .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 14 PUBLIC Planning 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 , make sure that all open transport, repair, and customizing requests have been released in the source system before you start the system rename procedure. Otherwise you will not be able to access them in the renamed target system. 2. 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. For more information, see Maintaining Users and Groups [page 17]. 3. If additional application server instances are installed on your system, delete them before you start the rename procedure. For more information, see Deleting Additional Application Server Instances [page 17]. 4. You perform IBM i-specific preparation steps. For more information, see Performing IBM i - Specific Preparation Steps [page 19]. 5. Make sure that your IBM i is integrated into your TCP/IP network. For more information, see Configuring TCP/IP [page 21]. 6. You adjust the local relational database name (RDB name) so it is the same as the TCP/IP host name. For more information, see Adjusting the Relational Database Name [page 28] 7. Prepare the media required for the system rename. For more information, see Downloading and Extracting the Software Provisioning Manager 2.0 Archive [page 29]. For more information about a secure way to copy the required installation media from your Windows PC to your IBM i, see Copying the Installation Media Manually to Your IBM i [page 30]. 8. Make sure that there is a user account on the target IBM i. For more information, see Preparing an IBM i User Profile [page 33] 9. Make sure that the user QSECOFR is enabled on the target IBM i. For more information, see Enable the User QSECOFR [page 34] 10. We strongly recommend that you perform a full system backup before starting the rename procedure, if you do not have other means to restore the original system in case of problems.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 15 3.2 General Technical Preparations

To perform a consistent system rename, you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run.

Context

The following section describes important preparations on the source system before you perform a system rename.

● SAP systems based on SAP S/4HANA 1809 or higher: For more information about SAP System Administration, see the Administrating the ABAP Platform section in the Online Documentation [page 12] . ● SAP systems based on SAP BW/4HANA<1.0 SR1 or higher>: For more information about SAP System Administration, see the Administration section in the Online Documentation [page 12] .

Procedure

1. Before you start a system rename, check the minimum kernel patch level required by the support package level of the source system.

It might be necessary to replace the SAP kernel delivered with the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the primary application server instance. 2. Check if canceled or pending update requests exist in the system. If canceled or pending updates exist, you must update these again or delete them from all clients. Proceed as follows: a. Call transaction SM13. b. Delete the default values for the client, user, and time. c. Choose all update requests. d. Check if table VBDATA contains any entries. If there are entries, update or delete the corresponding update requests. e. To check whether this action was successful, call transaction SE16 for table VBDATA. 3. Stop scheduling of all released jobs.

Go to transaction SE38 and run report BTCTRNS1. For more information, see SAP Note 37425 . 4. Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being renamed (transaction SM63). 5. Write down the logical system names of all clients: ○ If you plan to overwrite an existing system with a system copy, make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4).

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 16 PUBLIC Preparation Since the logical system names will be overwritten, in the event of differences, you must change them back to their original names (as they existed in the system that is overwritten) in the follow-up actions after the system rename.

3.3 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 39].

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.4 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 33].

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 17  Caution

Do not use the user adm to delete the SAP system.

● 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.

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 39].

2. On the Welcome screen, choose Software Life-Cycle Options Uninstall . 3. Follow the instructions in the input dialogs to delete an additional application server instance.

 Note

For more information about the input parameters, place the cursor on the relevant field and press F1 .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 18 PUBLIC Preparation 3.5 Performing SAP HANA Database-Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform forSAP HANA database before starting the system rename procedure.

Context

You can use the installer only for renaming the application server instances, and the ABAP central services instance , but you can not rename the SAP HANA database with this tool. If you want to rename the SAP HANA database, you have to do this as a separate step in advance .

Procedure

You perform the rename for the SAP HANA database as described in section Changing the SAP HANA System in the SAP HANA Administration Guide at http://help.sap.com/hana_platform System Administration .

3.6 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 ADM and enter the following command:

STOPSAP SID() INSTANCE(*ALL) STARTUPSRV(*ALL) XDNLISTEN(*YES) WAIT(*YES) WAITTIME(600) ENDSBS(*YES) 2. Log off the user ADM and check if the kernel library and the database library of your SAP system are still locked. a. To check the kernel library, log on as QSECOFR or your installation user and enter the following command:

WRKOBJLCK OBJ(SAPIND) OBJTYPE(*LIB)

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 19 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 ADM.

b. To check the database library, log on as QSECOFR or your installation user and enter the following command:

WRKOBJLCK OBJ(R3DATA) OBJTYPE(*LIB) (for an ABAP database)

and/or

WRKOBJLCK OBJ(SAPDB) OBJTYPE(*LIB) (for a Java database)

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 ( or ) depends on if the instances on the remote were already renamed or not.

You must enter the following commands on the remote host only, not on the global host:

1. Change the link /sapmnt/: 1. RMVLNK '/sapmnt/' 2. ADDLNK OBJ('/QFileSvr.400//sapmnt/') NEWLNK('/ sapmnt/') 3. CHGOWN OBJ('/sapmnt/') NEWOWN(ADM) SYMLNK(*YES)

 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

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 20 PUBLIC Preparation cannot be resolved. is now the same as . You must do the three commands as described above.

2. Change the link /usr/sap//SYS/exe/run: 1. RMVLNK '/usr/sap//SYS/exe/run' 2. ADDLNK OBJ('/sapmnt//exe//as400_pase_64') NEWLNK('/usr/sap//SYS/exe/run') 3. CHGOWN OBJ('/usr/sap//SYS/exe/run') NEWOWN(ADM) SYMLNK(*YES)

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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 21 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 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 22 PUBLIC Preparation On the Create Line Desc (Ethernet) (CRTLINETH) screen, make sure the autocreate controller is set to *yes.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 23 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 24 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 25 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 26 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 , and once ..

 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 27 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 , enter the following command: CHGRDBDIRE RMTLOCNAME(*LOCAL *IP) PORT(*DRDA) RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC) RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA) ○ If an entry for RDB name does not exist and a different entry exists with Remote Location *LOCAL you have to delete it using RMVRDBDIRE RDB(). Afterwards go to the next step and add the required RDB name. ○ If an entry for RDB name does not exist, you have to add one with the correct name .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 28 PUBLIC Preparation To do this, enter the following command: ADDRDBDIRE RDB() RMTLOCNAME(*LOCAL *IP) PORT(*DRDA) RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC) RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA) 6. If you are planning to use an independent ASP, make sure there is an entry for it in the RDB directory.

3.9 Downloading and Extracting the Software Provisioning Manager 2.0 Archive

You must always download and extract the Software Provisioning Manager 2.0 archive from the SAP Software Download Center because you must use the latest version.

Context

You require the SAPCAR tool to be able to unpack and verify software component archives (*.SAR files). *.SAR is the format of software lifecycle media and tools that you can download from the SAP Software Download Center. For more information about how to get this tool, see the Procedure section below.

Procedure

1. Download the latest version of the Software Provisioning Manager 2.0 archive SWPM20SP_.SAR from:

https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager 2. We recommend that you copy the Software Provisioning Manager 2.0 archive to the IFS of the IBM i host. 3. If you did not do so already, make sure you have configured your TCP/IP as described in SAP Note 92589 . Do not forget afterwards 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. 4. 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:

a. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Category SAP TECHNOLOGY COMPONENTS SAPCAR .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 29 b. Select the archive file for your operating system and download it to an empty directory. c. Rename the executable to sapcar.exe.

For more information about SAPCAR, see SAP Note 212876 . 5. Using the latest version of SAPCAR, you can verify the signature of the downloaded SWPM20SP_.SAR archive as follows: a. Get the latest version of the SAPCRYPTOLIB archive to your Windows PC as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcryptolib”. 2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable. 3. Go to the SAPCAR directory and use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable: ./sapcar –xvf sapcryptolibp_84…sar 4. Download the Certificate Revocation List from https://tcs.mysap.com/crl/ crlbag.p7s and move it to the SAPCAR directory. b. Verify the signature of the downloaded SWPM20SP_.SAR archive by executing the following command:

 Note

Check SAP Notes 2178665 and 2568783 whether additional information is available.

\sapcar.exe -tvVf \SWPM20SP_.SAR -crl 6. Unpack the Software Provisioning Manager 2.0 archive to a local directory on your Windows PC using the following command:

\sapcar.exe -xvf \SWPM20SP_.SAR -R

 Note

Make sure that all users have read permissions for the directory where you want to 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 or archives.

3.9.1 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 30 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 31 All network connections to shared resources are displayed. 5. Only valid for 'Software Component': SAP ERP, SAP NetWeaver Check if you have a connection to your IBM i. If you find \\\TMPSAP in the Remote column and a drive directory letter in the Local column, you have already established the required connection to your IBM i. Otherwise, you have to establish this connection. To do this, enter: net use X: \\\TMPSAP SAP /USER:SAPIUSR X: is now your new network drive to share \\\TMPSAP to your IFS on the IBM i. If X: is already in use, choose another drive letter that is free.

 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 33].

End of 'Software Component': SAP ERP, SAP NetWeaver 6. To change to the new network drive, enter X: in the command prompt. 7. Create the subdirectories in your IFS where you want to copy the required media. For each media, enter: mkdir /tmp/SAP// or mkdir /tmp/SAP//

 Note

You must avoid blanks or commas in the media path name.

8. 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:\\ /E or xcopy C:\tmp\download\ X:\\ /E

 Note

You must copy the root directory of the media respectively of the and all required subdirectories to the IFS of your IBM i.

9. For each required media, create a subdirectory and copy the required media.

 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___OS400_PPC64 ● EXP* ● SL_CONTROLLER_

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 32 PUBLIC Preparation 3.10 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.

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.

 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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 33  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.11 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.

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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 34 PUBLIC Preparation  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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Preparation PUBLIC 35 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 19].

Central System

You check the Prerequisites for Running the Installer [page 37] and run the installer to rename the system as described in Running the Installer [page 39].

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 36 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 39].

1. If your SAP system has an ASCS instance, you check the Prerequisites for Running the Installer [page 37] and run the installer to rename the ASCS instance as described in Running the Installer [page 39]. 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 37] and run the installer to rename the database instance as described in Running the Installer [page 39]. 4. You check the Prerequisites for Running the Installer [page 37] and run the installer to rename the primary application server instance as described in Running the Installer [page 39]. 5. Optional: You check the Prerequisites for Running the Installer [page 37] and run the installer to rename existing standalone Gateway instances as described in Running the Installer [page 39]. 6. Optional: You check the Prerequisites for Running the Installer [page 37] and run the installer to rename the SAP Web Dispatcher instance as described in Running the Installer [page 39].

Next Steps

You perform follow-up activities [page 58]

4.2 Prerequisites for Running the Installer

Make sure you fulfil the following prerequisites before running the installer.

● For the SL Common GUI, make sure that the following web browser requirements are met: ○ You have one of the following supported browsers on the device where you want to run the SL Common GUI: ○ Google Chrome (recommended) ○ Mozilla Firefox ○ Microsoft Edge ○ Microsoft Internet Explorer 11 or higher. Always use the latest version of these web browsers. ○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 37 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 39]. 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 45].

● 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 33]. ● 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 45]. ● 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 38 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 21] and Adjusting the Relational Database Name [page 28].

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 37].

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 45].

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 33].

 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 39 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 installer available.

For more information, see Downloading and Extracting the Software Provisioning Manager 2.0 Archive [page 29]. 3. Start the installer as follows:

Open a command prompt and enter the following command:

CD DIR('')

CALL PGM(QP2TERM) PARM(’./sapinst’)

 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://[]:4237/sapinst/docs/index.html

Logon users: []

************************************************************************ ...

 Note

If the host specified by cannot be reached due to a special network configuration, proceed as follows: 1. Terminate the installer as described in Useful Information about the Installer [page 45]. 2. Restart the installer from the command line with the SAPINST_GUI_HOSTNAME= property. 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 37]).

 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 40 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//.sapinst 2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the command line option get_my_name -p. As a result, you get the server fingerprint or thumbprint from the server certificate. 3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not be verified.

The SL Common GUI opens in the browser by displaying the Welcome screen. 5. In the Welcome screen, proceed according to your system variant :

○ If your system is a standard system , choose System Rename Standard System System Rename . ○ If your system is a distributed system, choose System Rename Distributed System . Choose the system rename options as required and in the order they appear.

System Rename Options and Sequence how to Execute Them

Option Description When to Execute Execution Order

System Rename for ASCS Executes system rename If your system does not First step for systems with Instance for the ASCS instance have an ASCS instance, AS ABAP, if they have an skip this option. ASCS instance

System Rename for ERS Executes system rename If your system does not Execute this option after Instance for the ERS instance have an ERS instance, skip you have performed the re­ this option. name option for the ASCS instance (if available) above, as required

System Rename for 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 SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 41 Option Description When to Execute Execution Order

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.

 Caution

When performing a rename of a distributed SAP system, the UID of the user ADM has to be the same on all involved IBM i hosts.

The installer asks you in the Define Parameters phase of the ASCS instance for the password of the user ADM.

In this screen, you must also set an appropriate UID for the ADM that is not used on any of the related IBM i hosts. 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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 42 PUBLIC System Rename Procedure 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 ADM on a remote IBM i host put also the UID number of the ADM into the input screen when it is not set already. You can get this number from the global host where the SCS or ASCS instance is already installed using following command:

DSPUSRPRF USRPRF(ADM) or

CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' 'ADM')

The SCS or ASCS installation is the installation which initially determinates the UID of the user ADM.

 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. 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 has completed. 10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished. Sometimes these remain in the temporary directory.

 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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 43 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 55].

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//.sapinst 13. For security reasons, we recommend that you remove the group SAPINST from the operating system users after you have completed the installation.

 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 45].

Related Information

Useful Information about the Installer [page 45] Interrupted Processing of the Installer [page 51] Troubleshooting with the Installer [page 54]

4.4 Additional Information about the Installer

The following sections provide additional information about the installer.

Useful Information about the Installer [page 45]

System Provisioning Using a Parameter Input File [page 47]

Interrupted Processing of the Installer [page 51]

Troubleshooting with the Installer [page 54]

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 44 PUBLIC System Rename Procedure Removing the Installer Installation Files [page 55]

Using the Step State Editor (SAP Support Experts Only) [page 56]

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 2.0 SP01 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 37]. If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of your web browser.

● As soon as you have started the sapinst executable, the installer creates a .sapinst directory underneath the /home/ directory where it keeps its log files. is the user with which you have started the installer. After you have reached the Welcome screen and selected the relevant installer option for the SAP system to be renamed , the installer creates a directory sapinst_instdir where it keeps its log files, and which is located directly below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp by default. All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir directory as soon as the latter has been created. If you want the sapinst_instdir directory to be created in another directory than /tmp, set the environment variable TEMP, TMP, or TMPDIR to this directory before you start the installer.

Shell Used Command

Command prompt ADDENVVAR ENVVAR(TEMP) VALUE('') REPLACE(*YES)

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 45 Shell Used Command

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.

 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('') CALL PGM(QP2TERM) PARM('./sapinst' '-p')

● 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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 46 PUBLIC System Rename Procedure 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 45]) was introduced in 2017 there are two ways to run the unattended mode: “observer mode” and “non-observer mode”.

Observer Mode If you are running an installation in unattended mode but you are sitting in front of the screen, you might want to check the progress from time to time. In this case the “observer mode” makes sense.

Start the installation as described below in the Solution section, using the following parameters:

SAPINST_INPUT_PARAMETERS_URL=

SAPINST_EXECUTE_PRODUCT_ID=

SAPINST_SKIP_DIALOGS=true

The Software Provisioning Manager will start the installation in the background AND start a Web Dispatcher and provide an URL to access the SL Common GUI. The user who has started the installation can now connect to the URL and observe the progress of the installation, for example to look at the logfiles in the Web browser. However, all parameters will be taken from the parameter input file and can not be changed in the Web browser.

Non-Observer Mode Choose that mode if you want to run a “scripted” or by other means automated scenario, for example overnight. In that case it is crucial that the process is started without a Web Dispatcher and therefore without a GUI. Otherwise, the automation could be stuck if the installer encounters a situation that requires user interaction.

Start the installation as described below in the Solution section, using the following parameters (use the same parameters like for Observer Mode, but provide SAPINST_START_GUISERVER=false in addition):

SAPINST_INPUT_PARAMETERS_URL=

SAPINST_EXECUTE_PRODUCT_ID=

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 47 SAPINST_SKIP_DIALOGS=true

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

 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:

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 48 PUBLIC System Rename Procedure  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_.SAR

Procedure

1. You plan and prepare the run as described in Planning [page 14] and Preparation Checklist [page 15]. 2. Create a text file that has “.params” as a suffix as follows: 1. Start the installer as described in Running the Installer [page 39]. 2. Choose the option you want to run, and follow the instructions on the screens by entering all parameter values 3. Stop after the Parameter Summary screen has been displayed 4. Find the parameter input file named “inifile.params” in the installation directory 5. Rename the “inifile.params” file. For example, you can rename it to “my_inifile.params”. 3. Adjust the values of the parameter input file as follows: 1. Edit the parameter input file (“my_inifile.params”) file and modify the parameters according to your needs. 2. Add required media or archives information line by line. 4. Identify the Product-ID: ○ To start in unattended mode, you need to know the component ID for the option that are required for your provisioning scenario. Proceed as follows: 1. Open the sapinst_dev.log in the installation directory. 2. Check for the “product-id”

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 49  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 39] 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= SAPINST_SKIP_DIALOGS=true SAPINST_START_GUISERVER=false

6. After the installer has completed, perform follow-up activities as described in Follow-Up Activities Checklist [page 58].

Related Information

SAP Note 2849054 SAP Note 2742212 SAP Note 2626837 SAP Note 2669183

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 50 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 51 Procedure

1. Log on to the installation host as a user with the required permissions as described in Running the Installer [page 39] . 2. Make sure that the software required for the system rename is still available.

For more information, see .

 Recommendation

Make the installation software 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 software mounted with NFS might fail.

3. Restart the installer from the installation software 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://[]:4237/sapinst/docs/index.html

Logon users: []

************************************************************************ ...

 Note

If the host specified by cannot be reached due to a special network configuration, proceed as follows: 1. Terminate the installer as described in Useful Information about the Installer [page 45]. 2. Restart the installer from the command line with the SAPINST_GUI_HOSTNAME= property. 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 37]).

 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 52 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//.sapinst 2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the command line option get_my_name -p. As a result, you get the server fingerprint or thumbprint from the server certificate. 3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not be verified.

The SL Common GUI opens in the browser by displaying the Welcome screen. 5. 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 53 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/ directory, where is the user that you used to start the installer.

For more information, see Useful Information about the Installer [page 45].

○ To check the log and trace files of the installer GUI for errors, go to the directory /home/ /.sapinst/ ○ Then continue by choosing Retry. ○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more information, see Interrupted Processing of the Installer [page 51]. 3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*. For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 54 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('') SUBTREE(*ALL) 2. Parallel to the installer in the installation directory a library SAP is created containing the ILE load tools for the database. When the installer installation directory is deleted, you can also remove this library using the following command: DLTLIB LIB(SAPLOAD) 3. To remove temporary SAPINST files, enter the following command: RMVDIR DIR('/tmp/sapinst_exe*') SUBTREE(*ALL)

 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 45], you must use this temporary directory instead of '/tmp'.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 55 4. To remove the downloaded and/or copied installation media, enter the following command: RMVDIR DIR('/tmp/sap/') SUBTREE(*ALL)

To disconnect your mapped drive from the IBM i, enter the following command on your Windows PC: net use : /DELETE

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 37].

Procedure

1. Start the installer from the command line as described in Running the Installer [page 39] 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 56 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 System Rename Procedure PUBLIC 57 5 Follow-Up Activities

Here you find information about follow-up tasks to be done after the system copy has been completed.

 Note

You can perform some of the ABAP system configuration tasks listed in this section in an automated way by using predefined task lists. For more information, see the installation and configuration guides for ABAP post-copy automation at https://help.sap.com/viewer/p/ABAP_POST-COPY_AUTOMATION.

Related Information

Follow-Up Activities Checklist [page 58] Performing Follow-Up Activities in the Source System [page 60] Performing Follow-Up Activities in the Target System [page 60] Configuring the Transport Management System [page 67] Performing Follow-Up Activities for SAP HANA Database [page 67] Starting the SAP System [page 68] Changing the IGS Destination [page 68]

5.1 Follow-Up Activities Checklist

Procedure

1. Start the primary application server instance.

For more information, see Starting the SAP System [page 68].

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

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 58 PUBLIC Follow-Up Activities 2. Perform follow-up activities in the source system [page 60]. 3. Perform follow-up activities in the target system [page 60]. 4. Configure the transport management system.

For more information, see Configuring the Transport Management System [page 67]. 5. Perform follow-up activities for your database.

For more information, see Performing Follow-Up Activities for SAP HANA Database [page 67]. 6. Restart the renamed SAP system completely.

For more information, see Starting the SAP System [page 68]. 7. Change the IGS destination.

For more information, see Changing the IGS Destination [page 68].

Related Information

General Follow-Up Activities [page 59] Configuring the Transport Management System [page 67] Changing the IGS Destination [page 68] Starting the SAP System [page 68] Removing the Installer Installation Files [page 55]

5.2 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 Performing Follow-Up Activities in the Source System [page 60] and Performing Follow- Up Activities in the Target System [page 60]. 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?

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Follow-Up Activities PUBLIC 59 The default convention is CLNT, but it might have been adapted individually. If your logical system names contain attributes that were renamed as part of this procedure, see SAP Note 121163 for information about how to convert logical system names.

● 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.3 Performing Follow-Up Activities in the Source System

This section describes the follow-up steps that you have to perform in the source system after the target system installation has completed.

Procedure

1. Reschedule released jobs.

If you stopped scheduling of released jobs and of jobs that must run periodically before you started the system copy procedure, release them again by running report BTCTRNS2. For more information, see General Technical Preparations [page 16]. 2. Using CCMS, adapt your operation mode timetable to the original status (transaction SM37).

5.4 Performing Follow-Up Activities in the Target System

Related Information

Performing Follow-Up Activities for ABAP [page 60] Performing Product-Specific Follow-Up Activities [page 66]

5.4.1 Performing Follow-Up Activities for ABAP

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 60 PUBLIC Follow-Up Activities Related Information

Activities at Operating System Level [page 61] Activities at Database Level [page 61] Activities at SAP System Level [page 62] Checking the Target System [page 66]

5.4.1.1 Activities at Operating System Level

This section includes the adaptations that you have to make at operating system level in your target system.

Procedure

1. Adapt the configuration files at operating system level to meet network and SAP requirements. 2. Adapt additional SAP software components (for example, RFC, CPIC, SAP ArchiveLink) if required. 3. Adapt additional non-SAP software components (for example, archiving systems, monitoring tools, job schedulers) if required. 4. Adapt backup programs (for example, BRBACKUP, BRARCHIVE, BACKINT) if required. 5. Adapt non-SAP directories, file systems, NFS mounts, and so on, if required. 6. Check the SAP parameters of the default and instance profiles. 7. Check the Job Scheduler (WRKJOBSCDE). 8. Check operating system files . 9. Check operating system printers. 10. If the spool requests are stored at file system level, you must copy the subdirectories with the spool files to the new global directory. For more information, see SAP Note 20176 .

5.4.1.2 Activities at Database Level

This section includes the adaptations that you have to make at database level in your target system.

Procedure

1. Before starting the SAP system, make sure that the logging mechanism of the database is active. 2. Check the parameters in the database profiles. 3. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAP, SDBAR.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Follow-Up Activities PUBLIC 61 4. Delete entries in the table DDLOG for buffer synchronization.

5.4.1.3 Activities at SAP System Level

This section includes the adaptations that you have to make at SAP system level in your target system.

 Note

You can use ABAP post-copy automation (PCA) to automatically perform follow-up activities at system level . ABAP post-copy automation (PCA) provides task lists with a predefined sequence of configuration tasks to configure extensive technical scenarios automatically. For more information, see SAP Note 1614266 .

To be able to use PCA, you must install the license for SAP Landscape Virtualization Management Enterprise Edition. For more information, see SAP Note 1912110 .

Procedure

1. If you performed a Unicode conversion using as target system ID the same as the source system ID and the (local or NIS-mounted) operating system users of the target system still have the environment of the operating system users of the source system, you need to update the user environment for the operating system users of the target system as follows:

Update the PATH variable so that it points to the platform-specific directory for Unicode.

 Example

Update the PATH value /usr/sap//SYS/exe/nuc/linuxx86_64 to /usr/sap/ /SYS/exe/uc/linuxx86_64

2. Run an installation check (transaction SM28). 3. Delete all entries from the tables TPFET and TPFHT (transaction SE14).

These tables contain information about changes made to the profile of your source system.

Use the commands CLRPFM R3DATA/TPFET and CLRPFM R3DATA/TPFHT. 4. Import the system profiles into the database (transaction RZ10). 5. If you changed the SAP system ID during the system copy, delete all entries from table TLOCK, which holds the repair requests from your source system. 6. Maintain the operation modes. a. Create new operation modes and instance definitions (transaction RZ04). b. Maintain the time table using the new operation modes (transaction SM63). c. Delete the old operation modes and old instance definitions. 7. Adapt other CCMS settings (for example, alert thresholds, reorganization parameters of CCMS table MONI) if required.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 62 PUBLIC Follow-Up Activities 8. Check the logon groups and the assignment of the application servers to the logon groups (transaction SMLG). If required, create new logon groups and assign the new application servers to these logon groups.

9. Define or remove the SAP system users and revise the authorizations of the system users: Tools Administration User maintenance Users (transaction SU01). 10. Synchronize the buffers as described in SAP Note 36283 and adapt the client information for the logical system. 11. Configure the spool server. a. Adapt the definition of the printers to meet the new system requirements (transaction SPAD): ○ Device types and character set definitions ○ Spool server ○ Output management systems (OMS) b. Delete obsolete spool requests and spool inconsistencies while executing the ABAP program RSPO0041 (transaction SE38). c. Call transaction SP12 and run report RSPO1043 for a spool data consistency check. For more information, see SAP Notes 98065 and 48400 . 12. Configure batch jobs. a. Delete canceled and finished batch jobs while executing the RSBTCDEL ABAP program, selecting Delete with forced mode (transaction SE38). b. Adapt all jobs needed in the target system. 13. If you have used the DBA Calendar in the source system, redefine database actions (backup, update statistics, and so on) (transaction DB13). 14. Maintain the security configuration. a. Call transaction STRUST. b. Replace all existing PSE files in the target system with new ones, which contain the new system’s information.

For more information, see the SAP Online Documentation [page 12] at Security System Security System Security for SAP NetWeaver AS ABAP Only Trust Manager Creating PSEs and Maintaining the PSE Infrastructure Creating or Replacing a PSE 15. Adapt RFC server groups. Call transaction RZ12 and change the instance name of RFC server groups under Group assignment. 16. Adapt RFC destinations copied from the source system to the target system.

 Caution

Before you delete RFC destinations, make sure that they are not needed in the target system.

a. To check and adapt qRFC destination, call transaction SMQR. b. To check and adapt tRFC destination, call transaction SM58. c. To delete obsolete RFC destinations, call transaction SM59. 17. Check the ABAP Secure Store [page 65] 18. Configure the Transport Management System (TMS). a. Reschedule the transport dispatcher (RDDIMPDP) in client 000:

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Follow-Up Activities PUBLIC 63 1. Log on as user DDIC. 2. Call transaction SE38. 3. Run program RDDNEWPP and set the priority to high. b. Adapt the transport parameters and transport routes in the TMS as follows: 1. Call transaction STMS. 2. To adapt the transport parameters, choose Overview Systems Transport Tool . 3. To adapt the transport routes, choose Overview Transport Routes . 4. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS.

 Note

If you did not change the SAP system ID during the system copy, all open transport, repair, and customizing requests that have not been released in the source system will not be released automatically.

19. Make data archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) accessible in the target system. Adapt the file residence information in the target system. For more information, see and the SAP Online Documentation [page 12] at Solution Life Cycle Management Data Archiving . 20.Check self-defined external commands (transaction SM69). 21. Check the logical system names. If you need to change logical system names in the system that results from the system rename, change the logical system names at this time, as described in SAP Notes 103228 and 544509 . Follow your corporate naming strategy for logical systems when making this change.

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 CLNT, but it might have been adapted individually. If your logical system names contain attributes that were renamed as part of this procedure, see SAP Note 121163 for information about how to convert logical system names. If you have renamed an SAP BW system, see SAP Note 886102 . 22.For every client in your SAP system check the detail settings (client role, changes and transports for client- dependent objects, changes for client-independent objects, protection level, restrictions) (transaction SCC4). 23. Check if you can delete clients that are no longer used in the target system (transaction SCC5). 24. Check the contexts and segments of remote application servers for the SAP Monitoring Infrastructure if required (transaction RZ21). 25. Post-processing for customer objects:

○ If customer objects are not original in the new system, use transaction SE06 to modify the corresponding entries in table TADIR. ○ If you encounter problems modifying a customer development class using transaction STMS or SM31, try using the option Validate (ENTER) instead of the option Save to save your changes.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 64 PUBLIC Follow-Up Activities 26.BW only: Start program RS_BW_POST_MIGRATION in the background. Program RS_BW_POST_MIGRATION performs necessary modifications on database-specific objects (mainly BW objects).

If you changed the database management system (for example, IBM i to MaxDB) when copying the system, you have to start program RS_BW_POST_MIGRATION in the background with variant SAP&POSTMGRDB 27. Generate the ABAP load.

The ABAP loads are platform-dependent programs that are generated during runtime and stored in database tables. They are not exported when you use the R3load procedure to copy your SAP system. The ABAP loads are generated in the target system when they are first used.

 Note

Make sure that you have sufficient space available on your database. The generation of all existing objects requires about 2 to 9 GB of free space.

For a detailed description about how to generate the ABAP load, call transaction SGEN and choose Information about the SAP Load Generator.

Related Information

Checking the ABAP Secure Store [page 65]

5.4.1.3.1 Checking the ABAP Secure Store

Procedure

1. Start transaction SECSTORE. 2. Choose Check Entries and Execute. 3. Filter the result by error messages. ○ If you see at least one error message of type SECSTORE 089 (“Key … for entry … is missing in the secure storage in the file system”), proceed as follows: 1. Reimport encryption keys that were used in the source system and stored in the secure storage in the file system You can find information about this process in the Online Documentation [page 12] at: Function-Oriented View Security System Security System Security for SAP NetWeaver AS ABAP Only Secure Storage (ABAP) Key Management Using Individual Encryption Keys Importing Missing Encryption Keys 2. Repeat the check. ○ If you see at least one error message of type SECSTORE 030 (“Incorrect global key for entry …”), you need to restore a legacy key-file that was used in the source system.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Follow-Up Activities PUBLIC 65 You can find information about this process in the Online Documentation [page 12] at: Function-Oriented View Security System Security System Security for SAP NetWeaver AS ABAP Only Secure Storage (ABAP) Key Management Legacy Method for Using Individual Encryption Key Importing Keys after a System Copy ○ If you see at least one error message of type SECSTORE 031 (“System-dependent data for entry … changed: …”), you must perform a record migration. You can find information about this process in SAP Note 816861 .

5.4.1.4 Checking the Target System

The following actions are required for checking the consistency of the target system.

Procedure

1. Perform an initial consistency check (transaction SM28). 2. Check the system log on all application servers (transaction SM21). In case of warnings, see SAP Note 43434 . 3. Check the consistency of the database (transaction DB02). 4. Perform a server check (transaction SM51). 5. FI customers: Run the job SAPF190 (accounting reconciliation) and compare the results to those gained on the source system before the system copy ( Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Comparison ). 6. FI customers: Run the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), andRAABGA01 (fixed asset retirements) and compare the results to those gained on the source system before the system copy. 7. CO customers: Run the report group 1SIP and compare the results to those gained on the source system before the system copy.

5.4.2 Performing Product-Specific Follow-Up Activities

Related Information

Business Warehouse (BW) Specific Follow-Up Activities [page 67]

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 66 PUBLIC Follow-Up Activities 5.4.2.1 Business Warehouse (BW) Specific Follow-Up Activities

This section provides references to documentation describing how to perform BW-specific follow-up activities.

Perform the BW-specific follow-up activities as described at https://blogs.sap.com/2016/10/11/software- application-lifecycle-management-sap-bw/ .

5.5 Configuring the Transport Management System

You have to perform some steps to be able to use the Transport Management System.

Procedure

1. Reschedule the transport dispatcher (RDDIMPDP) in client 000: a. Log on as user DDIC. b. Call transaction SE38. c. Run program RDDNEWPP and set the priority to normal. 2. Adapt the transport parameters and transport routes in the TMS as follows: a. Call transaction STMS. b. Select Change Configuration. c. To adapt the transport parameters, choose Overview Transport Tool d. To adapt the transport routes, choose Overview Transport Routes . e. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS.

5.6 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.

System Rename for SAP ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Follow-Up Activities PUBLIC 67 5.7 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 12] for your operating system platform or the SAP Online Documentation [page 12] at:

Application Help Function-Oriented View Solution Life Cycle Management Starting and Stopping SAP Systems Based on SAP NetWeaver

5.8 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 68 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 ABAP Systems Based on IBM i: SAP HANA 2.0 Database - Using Software Provisioning Manager 2.0 Important Disclaimers and Legal Information PUBLIC 69 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