Operations Guide CUSTOMER

Software Provisioning Manager 1.0 SP21
Document Version: 2.2 – 2017-09-11

System Rename for SAP Systems Based on the
Application Server of SAP NetWeaver 7.1 to 7.5
ABAP on IBM i

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 Use Cases of System Rename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 About Software Provisioning Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.5 New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
1.6 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.7 SAP Notes for the System Rename. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.8 Accessing the SAP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.9 How to Use this Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
3.1 Preparation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 Maintaining Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Deleting Additional Application Server Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.4 Performing IBM i - Specific Preparation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5 Configuring TCP/IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6 Adjusting the Relational Database Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
3.7 Preparing the System Rename Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Downloading and Extracting the Software Provisioning Manager Archive. . . . . . . . . . . . . . . . . . 28
3.8 Copying the Installation Media Manually to Your IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.9 Preparing an IBM i User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
3.10 Enable the User QSECOFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 System Rename Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1 System Rename Procedure Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Prerequisites for Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.4 Additional Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Useful Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Performing Remote Processing of the Installer (Java SDT GUI only). . . . . . . . . . . . . . . . . . . . . .50
Starting the Java SDT GUI Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Running the Installer in Accessibility Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Removing the Installer Installation Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to
7.5 ABAP on IBM i
2 CUSTOMER Content

5 Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.1 Follow-Up Activities Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
General Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Database-Specific Follow-Up Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring the Transport Management System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Changing the IGS Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Starting the SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to
7.5 ABAP on IBM i
Content CUSTOMER 3

Preparing the Installation Media. docu­ mented in: New Features. Downloading and Extracting the Software Provisioning Manager Archive ○ Simplified additional application server instance installation.0 SP20 (SL Toolset 1.sap. documented in: New Features.6 2015-10-12 Updated version for software provisioning manager 1.0 SP19 (SL Toolset 1. Downloading the Software Provisioning Manager Archive 1. Preparing the System Rename Media . Useful In­ formation About the Installer ○ Cleanup of operating system users.5 ABAP on IBM i 4 CUSTOMER Document History .1 2017-05-22 Updated version for software provisioning manager 1.0 SP20) ● New Features: ○ New SAPUI5-based graphical user interface (GUI) “SL Common GUI”.0 SP17) 1. Creating Operating System Users and Groups 2. documented in: SAP System Parameters.0 SP09 (SL Toolset 1.7 2016-02-15 Updated version for software provisioning manager 1.0 SP18 (SL Toolset 1.0 SP15) 1.0 SP09 (SL Toolset 1. documented in: New Features.0 SP10 (SL Toolset 1.61 2015-11-13 Updated version for software provisioning manager 1.0 SP17 (SL Toolset 1.0 SP21 (SL Toolset 1.SAR in the Software Provisioning Manager archive.0 SP21) ● New Features: ○ Media Signature Check.com/sltoolset System Provisioning Rename Option of Software Provisioning Manager .0 2017-02-06 Updated version for software provisioning manager 1.2 2017-09-11 Updated version for software provisioning manager 1.0 SP18) 1. ○ Load tools are now available as LOADTOOLS. Downloading SAP Kernel Ar­ chives (Archive-Based Installation) 2.8 2016-06-06 Updated version for software provisioning manager 1.0 SP15) System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. make sure you have the latest version of this document. docu­ mented in: Prerequisites for Running the Installer. Running the Installer.1 to 7.9 2016-10-07 Updated version for software provisioning manager 1.0 SP19) ● New Features: Verification of the integrity of data units in Software Provisioning Manager. The following table provides an overview on the most important document changes: Table 1: Version Date Description 2. documented in: New Features. which is available at https://support.0 SP16) 1. Running the Installer.Document History Note Before you start the implementation.

0 SP14) 1.0 SP08 (SL Toolset 1.1 2014-03-17 Updated version for software provisioning manager 1. Version Date Description 1.0 SP12) 1.0 SP10 ) 1.2 2014-07-07 Updated version for software provisioning manager 1.0 SP13) 1.5 2015-09-14 Updated version for software provisioning manager 1.0 2013-10-28 Initial version System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to 7.3 2014-11-24 Updated version for software provisioning manager 1.4 2015-04-27 Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP11) 1.5 ABAP on IBM i Document History CUSTOMER 5 .0 SP06 (SL Toolset 1.0 SP05 (SL Toolset 1.0 SP07 (SL Toolset 1.

Database ID (<DBSID>). Caution You should only perform a system rename using the Software Provisioning Manager 1.5 ABAP on IBM i 6 CUSTOMER Introduction . see the Product Availability Matrix at http://support. which is part of SL Toolset 1. Any deviations from this documentation are at your own risk.1 About this Document This document explains how to rename an SAP system using Software Provisioning Manager 1.1 Introduction 1. For a detailed list of supported SAP system products and releases.com/pam .1 to 7. host names You can adapt one or more of the following parameters of an SAP system using the system rename procedure: ● SAP system ID (<SAPSID>) System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.0 if your SAP system is installed with standard SAP tools according to the installation documentation available at http:// service.0 SP21.0 SP21.1 and higher. see SAP Note 1619720 .sap. Related Information Use Cases of System Rename [page 6] About Software Provisioning Manager [page 7] Naming Conventions [page 8] New Features [page 8] Constraints [page 10] SAP Notes for the System Rename [page 12] Accessing the SAP Library [page 12] How to Use this Guide [page 13] 1. It is valid for SAP systems based on the application server ABAP of SAP NetWeaver 7. For information about supported operating system and database platforms.sap.com/instguides .2 Use Cases of System Rename You can adapt one or more of the following parameters of an SAP system using the system rename procedure: SAP system ID (<SAPSID>). Be aware that additional consulting effort might be necessary. instance numbers of the instances on the SAP system.

3 About Software Provisioning Manager Software Provisioning Manager 1. More Information For more information about offerings.0” in this documentation. for example sapinst.sap. “SAPinst” has therefore been renamed to “Software Provisioning Manager 1. Software Provisioning Manager 1.1 to 7.exe In the following. the term “SAPinst” is still used in: ● Texts and screen elements in the Software Provisioning Manager GUI ● Naming of executables.0” if this is required for technical reasons. However. you automatically get the latest fixes and supported processes. we recommend that you always download the latest version of Software Provisioning Manager 1. the corresponding aspects outlined in SAP Note 121163 have to be considered. For more information about Software Provisioning Manager as well as products and releases supported by it. methods. such as SAPinst. 1. use cases and technical details of the system rename procedure. Note For production systems.0 is the successor of the product.and release-specific delivery of provisioning tools. ● 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. Before you run it. see http://scn.0 is part of the Software Logistics Toolset 1. This way. we generally refer to Software Provisioning Manager 1.5 ABAP on IBM i Introduction CUSTOMER 7 . We only use the term “Software Provisioning Manager 1.com/docs/DOC-30236 .0. Related Information Preparing the System Rename Media [page 28] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.sap. see SAP Note 1680045 and http://scn.0 (“SL Toolset” for short).com/docs/DOC-32851 .0 as the “installer”. 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.

3 EHP1 and higher. the currently used terms remain but only “product instance” is going to be used from now on when referring to SAP NetWeaver 7.1. For more information.0 SP20 (SL Toolset 1. ● “SAP system” refers to “SAP NetWeaver system” or “SAP system based on SAP NetWeaver”.0 SP20 (SL Toolset 1.0 SP20) group SAPINST is to be removed from the operating system users after the execution of the installer has completed.3 including enhancement package 1 and higher. “technical usage”. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. See also the description of this new security feature in SAP Note 2393060 .0 SP21 (SL Toolset 1. see Preparing the System Rename Media [page 28] and Running the Installer [page 39]. As this guide is a generic document.5 ABAP on IBM i 8 CUSTOMER Introduction .49 now use the new SAPUI5-based graphical user interface (GUI) 1. you can Software Provisioning Manager with SAPINST 7. see New Features [page 8].0 SP07 (SL Toolset 1. For more information. the term “product instance” replaces the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7. As of now the installer only accepts media whose signature has been checked. Cleanup of Operat­ You can now specify during the Define Parameters phase that the Software Provisioning Manager ing System Users 1.0 SP21 (SL Toolset 1. For more information. 1.0 SP20) “SL Common GUI”.5 New Features The table below provides an overview of the new features in Software Provisioning Manager.2 system rename for SAP systems with Oracle 12. see Useful Information About the Installer [page 45]. and SAP Note 2336746 . Running the Installer [page 39].0 SP12).0 SP21) Check during the Define Parameters phase while processing the Media Browser screens.com <Product Area> <Product> <Release> What’s New – Release Notes .49. Make sure that you also read the release notes for your SAP product at http://help. Table 2: Feature Description Availability Media Signature The signature of media is checked automatically by the installer Software Provisioning Manager 1.1 to 7. Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. and “product instance” As of Software Provisioning Manager 1.4 Naming Conventions ● “usage type”. Support of Oracle Software Provisioning Manager (the “installer”) now supports Software Provisioning Manager 1.sap.2. see SAP Note 1877731 . For more information. SL Common GUI With the new installer framework version SAPINST 7.0 SP21) 12.

5 and The Dual Stack option.5 ABAP on IBM i Introduction CUSTOMER 9 .0 SP19) ing Manager archive is verified.0 SP19 (SL Toolset 1.1 to 7. system copy.0. For more information. which integrates an AS ABAP and AS Java SAP NetWeaver 7.1 1. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Compared to previous SAP Solution Manager releases.1 EHP1 for Banking Services from SAP 5.2).2 lease.com/nw75 Installation and Upgrade ● SAP NetWeaver 7. 1. system Software Provisioning Manager ing for SAP rename) are available for the new SAP NetWeaver 7. but consists of a separate ABAP and Java stack.1 EHP1 . SAP NetWeaver 7.0 and 6. System Provision­ All system provisioning tasks (installation.0 SP09 (SL Toolset 1.0. see Down­ Software Provision­ loading and Extracting the Software Provisioning Manager Ar­ ing Manager chive [page 28] . system Software Provisioning Manager ing for SAP Solution rename) are available for the new SAP Solution Manager 7. Composition Environment 7.5 is Unicode only ● The primary application server instance directory has been renamed from /usr/sap/<SAPSID>/ DVEBMGS<Instance_Number> to /usr/sap/<SAPSID>/ D<Instance_Number>. and 7.0 SP15) NetWeaver 7. check SAP Note 1680045 whether additional in­ formation is available. ● After upgrading to SAP NetWeaver 7. SAP Solution Manager 7.1 EHP1 (SAP NetWeaver Mobile 7. common database).5- in a single system (common System ID <SAPSID>.5 PI productively.0 SP15) Manager 7.5 PI.0 SP09 (SL Toolset 1. For more information. For more information. Feature Description Availability Verification of Integ­ The integrity of data units extracted from the Software Provision­ Software Provisioning Manager rity of Data Units in 1. you first have to split the still existing dual stack-system before you can use SAP NetWeaver 7. see SAP Note 1892354 .1 EHP1 . 7.2 re­ 1. system copy.1 (SAP NetWeaver Mobile 7. System Rename System rename is supported for SAP systems based on SAP Software Provisioning Manager Supported for SAP NetWeaver 7. and 7. In addition.1 .2 (SAP NetWeaver Composition Environment 7.5 release.2.1 EHP1 ).0 SP08 (SL Toolset 1. 7. SAP NetWeaver 7.SAP NetWeaver 7.sap. is no longer supported in SAP systems based on SAP NetWeaver 7.2 is no longer provided as a classical dual-stack system (ABAP system with Java Add-in).5 at: http://help. SAP NetWeaver SAP NetWeaver 7. common based Products startup framework.1) .0 and 6. see the Upgrade Master Guide . ● Declustering and depooling of tables during the installation is enabled by default. SAP NetWeaver Composition Environment 7.1.5.0 SP13) systems based on for Banking Services from SAP 5. System Provision­ All system provisioning tasks (installation.

Only if the installer detects an 1. installation and maintenance activities. SAP SCM 7. Port 4239 is used for displaying the feedback evaluation form.3 EHP1 and higher.sap.0 and higher. For more information. For more information. SAP CRM 7. A new evaluation form contains a simple ques­ tionnaire and XML data generated during the procedure. SAP SRM 7. This is done to unify model­ on SAP NetWeaver ing and terminology across all SAP tools used during the plan­ 7.0 and higher.com/wiki/x/n4efFg . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.0 SP20 (SL Toolset 1.5 on <OS> at http://support.com/sltoolset System Provisioning Installation Option ● System rename is not supported for the Diagnostics Agent. then a dialog screen appears.Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP NetWeaver 7.0 SP07 (SL Toolset 1.3 EHP1 and Higher ning. Feedback Evalua­ SAP SE’s aim is to provide fast and efficient procedures.0 SP20) QSECOFR and the inconsistency. we need information gen­ 1. Option Verify Signed The digital signature ensures that the signatory of a digital docu­ Software Provisioning Manager Media ment can be identified unambiguously and signatory’s name is 1.0 SP07 (SL Toolset 1.1 to 7.0 SP11) documented together with the signed document. see SAP Note 1979965 . The “Product In­ stance” definition replaces “Usage Types” regarding product modeling. see the documentations Installation Guide .0 no longer uses the “Usage Software Provisioning Manager Deprecation for Types” definitions in its business logic for SAP systems based on 1.1 to 7. and the time. For more information.0 SP06 (SL Toolset 1. ● System Rename is supported for SAP Web Dispatcher and SAP Gateway of systems based on SAP NetWeaver 7.scn. see Pre­ user paring an IBM i User Profile [page 32] and Enable the User QSE­ COFR [page 34] .5 ABAP on IBM i 10 CUSTOMER Introduction .Feature Description Availability Usage Type Library Software Provisioning Manager 1. Automatic user The installer checks if the user QSECOFR and the IBM i installa­ Software Provisioning Manager check of the tion user are prepared correctly.0 SP12) erated by the tool during process execution and your experience with the tool itself.sap. 1. For more information.0 and higher.0 and higher. see SAP Notes 1970349 and 1877731 . To eval­ Software Provisioning Manager tion Form uate the procedure you just carried out. see Prerequisites for Running the Installer [page 36].0 and higher. IBM i installation For more information about how to prepare these users.0 and Higher on <OS> and Installation Guide . For more information and guidance see the Diagnostics Agent Maintenance Procedures article at http:// wiki.0 SP12) SAP Systems Based SAP NetWeaver 7.0 and higher: SAP ERP 6. the date.Installation of SAP Web Dispatcher for SAP Systems Based on SAP NetWeaver 7.6 Constraints ● System Rename is only supported for SAP systems based on SAP NetWeaver 7.

several errors are reported.20 or higher. or the instance number for an ASM installation of the Oracle database only works as of SL Toolset 1. see the system copy guides at http://support. For more information about the upgrade. Instead. the instance name. There is no workaround to overcome this restriction.com/sltoolset System Provisioning System Copy Option .sap. If your SAP system is installed on an IASP. ● Database ID <DBSID> The <DBSID> identifies the database instance. ● Renaming the database schema is not supported If you want to rename the database schema. ● SAP System ID <SAPSID> Make sure that your SAP system ID: ○ Is unique throughout your organization.8. see SAP Notes 1353266 or 1492467 . For more information. This is because there is a different ORACLE_HOME and the ora<dbsid> user is missing in the ASM environment.8 If you try to rename an SAP system with an SAP MaxDB version lower than 7. using System Rename for changing only the host name.0 SP06). ● You can only rename SAP systems that are using the SAP NetWeaver kernel 7. It is always the same as the <SAPSID>. 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 . depending on your SAP MaxDB target release.8 or 7. SAP HANA Rename of the database schema not supported System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Database-Specific Restrictions Oracle Database ● System Rename is only partially supported for ASM database installations System Rename does only partly work for an Automatic Storage Management (ASM) installation of the Oracle database. You cannot use system rename to change the <SAPSID> or the <DBSID> – in addition.0 SP11 (Software Provisioning Manager 1. ● The installer currently does not support the independent auxiliary storage pool (IASP).1 or higher.1 to 7.9. SAP MaxDB System Rename is not supported for SAP MaxDB versions lower than 7. you must use system copy to rename it. Do not use an existing <SAPSID>. ● The installer only runs on IBM i 6. perform a system copy. you first have to upgrade to SAP MaxDB version 7.5 ABAP on IBM i Introduction CUSTOMER 11 . ○ Consists of exactly three alphanumeric characters ○ Contains only uppercase letters ○ Has a letter for the first character ○ Does not include any of the reserved IDs listed in SAP Note 1979280 .

system copy.1 to 7. These SAP Notes contain the most recent information on system rename as well as corrections to the relevant documentation. UNIX. Table 3: SAP Notes for System Rename SAP Note Number Title Description 1680045 Release Note for Software Provisioning Software provisioning manager 1. Make sure that you have the most recent version of each SAP Note.sap. system re­ name and dual-stack split for SAP NetWeaver-based systems 1619720 System Rename for SAP Systems Problems discovered after the publica­ based on SAP NetWeaver tion of the System Rename guide 1.5 ABAP on IBM i 12 CUSTOMER Introduction .You can only rename the DBSID of the SAP HANA database. but you cannot rename the schema of the SAP HANA database.8 Accessing the SAP Library The references to the SAP NetWeaver Library documentation in this guide always refer to the following on SAP Help Portal: ● SAP systems based on SAP NetWeaver for Banking Services from SAP: http://help. and Windows Rename of the database schema is not supported You cannot rename the schema of the IBM DB2 for Linux. UNIX. and Windows database. You can find all SAP Notes at http:// service. 1.sap.com/banking Banking Services from SAP <Release> Application Help SAP Library: SAP NetWeaver.com/notes .1: http://help. English ● SAP systems based on SAP NetWeaver Mobile 7.com/nwmobile71 Application Help SAP Library: English SAP NetWeaver Mobile Library System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.0 with Manager 1.7 SAP Notes for the System Rename Read the following SAP Notes before you start the system rename procedure.sap. IBM DB2 for Linux. More Information For more restrictions. see SAP Note 1619720 .0 installation.

sap.5 ABAP on IBM i Introduction CUSTOMER 13 .com/ sltoolset Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7.3: http://help.4: http://help. see Use Cases of System Rename [page 6].com/nw73 Application Help Function-Oriented View: English ● SAP systems based on SAP NetWeaver 7.5: http://help.sap.sap.com/nw74 Application Help Function-Oriented View: English ● SAP systems based on SAP NetWeaver 7. ● SAP systems based on SAP NetWeaver Mobile 7. In the following.1 to 7.com/nwmobile711 Application Help SAP Library: English SAP NetWeaver Mobile Library ● SAP systems based on SAP NetWeaver 7.com/sltoolset Area System Provisioning Guide for System Copy for Systems Based on SAP NetWeaver 7. You follow the steps in each phase: ○ Planning [page 15] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 and Higher Installation Guides by Database <Database> <OS Platform> ). ● The “system copy guide” for your operating system platform at https://help. Procedure 1. we refer to this documentation as “installation guide”.sap.sap. 2. we refer to this documentation as “system copy guide”.com/soh <Release> Application Help SAP Library: English SAP NetWeaver ● SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.com/nw75 Application Help Function-Oriented View: English 1.1 including Enhancement Package 1: http://help.sap.9 How to Use this Guide This documentation comprises the description of the system rename procedure and system rename-specific steps.com/nw731 Application Help Function-Oriented View: English ● SAP systems based on SAP NetWeaver Application Server for ABAP 7.sap.4: http://help. see the installation or system copy guides: ● The “ installation guide” for your operating system platform and database at https://help. In the following. For more information. You decide on the system parameters you want to change in the rename process.sap. Context For general installation or system copy-specific information.1 & Higher <OS Platform> .

1 to 7.5 ABAP on IBM i 14 CUSTOMER Introduction . ○ Preparation [page 16] ○ Renaming [page 35] ○ Follow-Up Activities [page 60] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.

sap. If you have installed additional application server instances.1 to 7. ○ Host names ● SAP systems based on SAP NetWeaver AS for ABAP 7.5 ABAP on IBM i Planning CUSTOMER 15 . ● 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 for your operating system platform and database at https://support.sap. Delete the additional application server instances manually [page 17] from the system before the system rename. Reinstall the additional application server instances on the system after the system rename.40 and higher: You can set an Individual Encryption Key for the Secure Storage (see section Basic SAP System Installation Parameters in the installation guide for your release and database at https://support.com/sltoolset Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7. you have to do the following: 1.1 and Higher Installation Guides by Database <Database> <OS Platform> ). ● If a required user does not exist. They are available after the rename of your system. ● Users that already exist in the SAP system are not deleted.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.1 and Higher Installation Guides by Database <Database> <OS Platform> ): ○ SAP system ID ○ Instance numbers of the instances on the SAP system With the system rename procedure. 2. it is created during the system rename procedure.sap. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. you can rename the following instances: ○ Database instance ○ Primary application server instance ○ ABAP Central Services instance (ASCS instance) ○ Enqueue Replication Server Note You cannot use the installer to rename additional application server instances.com/pam ● The system rename procedure is valid for the following environments: ○ ABAP ○ Java ○ Dual-stack (ABAP and Java) ● You can perform the system rename on both central and distributed systems.com/sltoolset Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7.

For more information. if you do not have other means to restore the original system in case of problems. see Deleting Additional Application Server Instances [page 17]. make sure that all open transport. it creates new users and groups as necessary.Specific Preparation Steps [page 18]. Make sure that your IBM i is integrated into your TCP/IP network. delete them before you start the rename procedure. 6. Make sure that there is a user account on the target IBM i. see Enable the User QSECOFR [page 34] 10.5 ABAP on IBM i 16 CUSTOMER Preparation . repair. For more information. 4. 8. If additional application server instances are installed on your system. For more information.3 Preparation 3. The installer checks whether the required users and groups already exist. You adjust the local relational database name (RDB name) so it is the same as the TCP/IP host name. 2. you can choose to create them before running the system rename procedure. Make sure that the user QSECOFR is enabled on the target IBM i. Prepare the media required for the system rename.1 Preparation Checklist This section includes the preparation steps that you have to perform when you want to rename an SAP system. and customizing requests have been released in the source system before you start the system rename procedure. For more information. For more information. see Copying the Installation Media Manually to Your IBM i [page 30]. We strongly recommend that you perform a full system backup before starting the rename procedure.1 to 7. If not. see Preparing an IBM i User Profile [page 32] 9. see Preparing the System Rename Media [page 28]. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. You perform IBM i-specific preparation steps. see Configuring TCP/IP [page 20]. Otherwise you will not be able to access them in the renamed target system. see Adjusting the Relational Database Name [page 27] 7. For more information about a secure way to copy the required installation media from your Windows PC to your IBM i. For more information. If you want to change the <SAPSID>. 5. see Performing IBM i . 1. see Maintaining Users and Groups [page 17]. For more information. 3. If you do not want the installer to create operating system users and groups automatically. For more information.

Procedure 1. Therefore.5 ABAP on IBM i Preparation CUSTOMER 17 . it creates new users and groups as necessary. 2. delete them before you start the rename procedure. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Follow the instructions in the input screens and specify the target system IDs (SAP system ID. Context This step is only mandatory if you want to use global accounts that are configured on separate hosts. For more information. ● You are logged on with a user account that has the required authorization to run the tool. Database ID) when creating users and groups.2 Maintaining Users and Groups The installer checks whether the required users and groups already exist. In all other cases. If you do not want the installer to create operating system users and groups automatically. Prerequisites ● You have installed your SAP system with standard SAP tools according to the installation documentation. Caution Do not use the user <sapsid>adm to delete the SAP system. 3. On the Welcome screen. you can choose to create them before running the system rename procedure. see Preparing an IBM i User Profile [page 32]. choose System Rename Preparations Operating System Users and Groups 3. If not.3. and reinstall additional application server instances as required after the system rename. this step is optional.3 Deleting Additional Application Server Instances The system rename procedure does not implicate additional application server instances.1 to 7. Log on to your SAP system as described in Running the Installer [page 39]. if additional application server instances are installed on your 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.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Follow the instructions in the input dialogs to delete an additional application server instance. 2. locked objects are not changeable this can break the renaming process.Specific Preparation Steps In general. the uninstall process continues. 3. On the Welcome screen. the installer changes objects which are already existing. If an item cannot be removed. place the cursor on the relevant field and press F1 . a message informs you that you have to remove this item manually. Procedure 1. 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. choose <SAP_Product> Software Life-Cycle Options Uninstall . To do this. Note For more information about the input parameters. Since.5 ABAP on IBM i 18 CUSTOMER Preparation . This means you must stop also the sapstart services. Start the tool as described in Running the Installer [page 39].4 Performing IBM i . 3. Log off the user <SAPSID>ADM and check if the kernel library and the database library of your SAP system are still locked. The best way to unlock the objects of a running SAP system is to shut the system down completely. As soon as you confirm the message. All file systems and subdirectories of the selected additional application server instance are deleted during the uninstall process.1 to 7. You have to run the tool to delete them locally on each additional application server instance host. Procedure 1. log on as user <SAPSID>ADM and enter the following command: STOPSAP SID(<SAPSID>) INSTANCE(*ALL) STARTUPSRV(*ALL) XDNLISTEN(*YES) WAIT(*YES) WAITTIME(600) ENDSBS(*YES) 2. The uninstall process is designed to remove as much of the additional application server instance as possible. the XDN server and the subsystems.Context Note You cannot delete an additional application server instance remotely.

To check the database library. Change the link /sapmnt/<SAPSID>: 1. log on as QSECOFR or your installation user and enter the following command: WRKOBJLCK OBJ(SAP<SAPSID>IND) OBJTYPE(*LIB) If the command WRKOBJLCK gives you a list of jobs. RMVLNK '/sapmnt/<Current_Remote_SAPSID>' 2. To check the kernel library. Results Now most likely no objects are locking any object of the SAP system anymore and the installer will run without any locking problem. log on as QSECOFR or your installation user and enter the following command: WRKOBJLCK OBJ(R3<SAPSID>DATA) OBJTYPE(*LIB) (for an ABAP database) and/or WRKOBJLCK OBJ(SAP<SAPSID>DB) OBJTYPE(*LIB) (for a Java database) If the command WRKOBJLCK gives you a list of jobs. CHGOWN OBJ('/sapmnt/<Current_Remote_SAPSID>') NEWOWN(<Current_Remote_SAPSID>ADM) SYMLNK(*YES) System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. you must stop all jobs which have locked the kernel library using option 4 (End job). a. You must enter the following commands on the remote host only. b. ADDLNK OBJ('/QFileSvr. Note The kernel library of an SAP system is normally locked when someone is logged on as <SAPSID>ADM. you must adjust the link of the remote host to the global directories of the SAPGLOBALHOST.5 ABAP on IBM i Preparation CUSTOMER 19 . not on the global host: 1. The following steps are not required for the rename of a standard system. The name of the current remote <SAPSID> (<Source_SAPSID> or <Target_SAPSID>) depends on if the instances on the remote were already renamed or not. Next Steps Distributed systems only: After the file system has been renamed on the global host.400/<SAPGLOBALHOST>/sapmnt/<Target_SAPSID>') NEWLNK('/ sapmnt/<Current_Remote_SAPSID>') 3.1 to 7. you must stop all jobs which have locked the database library using option 4 (End job).

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. You must do the three commands as described above. Otherwise. 2. the IBM i interprets the characters as uppercase characters. subnet mask. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. ADDLNK OBJ('/sapmnt/<Current_Remote_SAPSID>/exe/<uc_Or_nuc>/as400_pase_64') NEWLNK('/usr/sap/<Current_Remote_SAPSID>/SYS/exe/run') 3.6. 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.<Current_Remote_SAPSID> is now the same as <Target_SAPSID>. Prerequisites Before configuring TCP/IP. CHGOWN OBJ('/usr/sap/<Current_Remote_SAPSID>/SYS/exe/run') NEWOWN(<Current_Remote_SAPSID>ADM) SYMLNK(*YES) 3. the link to the SAPGLOBALHOST has to be newly set even if the file system on the SAPGLOBALHOST is not already renamed and the new link cannot be resolved. Do not enter your host name once in uppercase and then in lowercase characters. and router or Gateway ○ The local domain name ○ The IBM i host name ● Decide on your IBM i host name.5 Configuring TCP/IP Use This section describes how to integrate IBM i into your TCP/IP network. The host name cannot be longer than eight characters although SAP allows 13 characters as of Release 4. For more information. It is important that you enclose your host name entry in single quotation marks. see SAP Note 611361 .1 to 7. Change the link /usr/sap/<SAPSID>/SYS/exe/run: 1.5 ABAP on IBM i 20 CUSTOMER Preparation . Note The TCP/IP configuration on IBM i is case sensitive. RMVLNK '/usr/sap/<Current_Remote_SAPSID>/SYS/exe/run' 2.

2. enter the line speed and duplex and then press F10 and page down two screens. enter the command chgneta and prompt F4 . To set up the description line. On the following screen.Procedure Note An IP address is a unique address in a TCP/IP network for a particular IBM i. enter option 1 (Create) to enter the description gigaline or ethline and choose ENTER . 1. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. enter the command WRKHDWRSC TYPE(*CMN) and proceed as follows: 1. enter option 5 (Work with configuration descriptions) for the port and choose ENTER .1 to 7. You must then enter the following information and choose ENTER : ○ System name ○ Local network ID ○ Default local location name The following screen appears: 2. On the Work with Configurations Description screen. On the Work with Communication Resources screen. To change the name of the computer. A subnet mask is a mask used to divide a single network address into multiple logical networks.5 ABAP on IBM i Preparation CUSTOMER 21 .

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. make sure the autocreate controller is set to *yes. On the Create Line Desc (Ethernet) (CRTLINETH) screen.1 to 7.5 ABAP on IBM i 22 CUSTOMER Preparation .

5 ABAP on IBM i Preparation CUSTOMER 23 . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. To call the TCP/IP configuration menu. To work with interfaces. enter option 1 (Work with TCP/IP interfaces).1 to 7. 3. enter the command CFGTCP and proceed as follows: 1.

The following screen appears:

You need at least two entries: one for the loopback entry and one for the IP address of your IBM i.
The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 and line
description *LOOPBACK.
To add an entry, enter option 1 (ADD) and choose ENTER .
Add entries for the first three fields and accept the default values for the other fields.
2. To work with routes, enter option 2 (Work with TCP/IP routes).

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to
7.5 ABAP on IBM i
24 CUSTOMER Preparation

The following screen appears:

If the route to the remote host, in this case the PC workstation, is through a Gateway or if the remote
host resides in a different network or subnetwork to the local host, you need to configure a route.
3. To change the domain information, enter option 12 (Change TCP/IP domain information).

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to
7.5 ABAP on IBM i
Preparation CUSTOMER 25

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 <Host_Name>, and once
<Host_Name>.<Domain_Name>.

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'

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to
7.5 ABAP on IBM i
26 CUSTOMER Preparation

Log on to your database host as user QSECOFR. check the TCP/IP connection again with the command: WRKLNK '/QFileSvr. enter the following command and press F4 : CHGTCPDMN 3. Search for the contents of HOSTNAME. for example. Procedure 1. For more information about TCP/IP configuration. see the IBM documentation in the IBM Knowledge Center. 4. as0008 for the host in the example given above.After installing the SAP system kernel. Result The IBM i is integrated into your TCP/IP network.5 ABAP on IBM i Preparation CUSTOMER 27 . To do this. you have to check if the entry remote location equals *Local exists. This is your TCP/IP host name. 3.1 to 7. enter the following command: WRKRDBDIRE 5. Before you can adjust the local RDB name. proceed as follows: ○ If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name <TCP_Host_Name>.400/<Host_Name>' Your host name should be displayed under Object link.6 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. Depending on the outcome. 2. Note The *Local database name must match the TCP/IP host name for the SAP system to work properly. enter the following command: CHGRDBDIRE RMTLOCNAME(*LOCAL *IP) PORT(*DRDA) RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC) RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA) System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. To display your TCP/IP host name.

7. ○ 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(<Current_RDB_*LOCAL>). If you are planning to use an independent ASP. make sure there is an entry for it in the RDB directory. As of now the installer only accepts media whose signature has been checked.5 ABAP on IBM i 28 CUSTOMER Preparation .0 archive SWPM10SP<Support_Package_Number>_<Version_Number>. Download the latest version of the Software Provisioning Manager 1. See also the description of this new security feature in SAP Note 2393060 . Procedure 1. To do this. Related Information Downloading and Extracting the Software Provisioning Manager Archive [page 28] 3. enter the following command: ADDRDBDIRE RDB(<TCP_Host_Name>) RMTLOCNAME(*LOCAL *IP) PORT(*DRDA) RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC) RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA) 6. Note The signature of media is checked automatically by the installer during the Define Parameters phase while processing the Media Browser screens. 3. ○ If an entry for RDB name does not exist.SAR from: https://launchpad. you have to add one with the correct name <TCP_Host_Name>.com/#/softwarecenter SUPPORT PACKAGES & PATCHES By Alphabetical Index (A-Z) S SOFTWARE PROVISIONING MANAGER System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 Downloading and Extracting the Software Provisioning Manager Archive You must always download and extract the Software Provisioning Manager 1.7 Preparing the System Rename Media This section describes how to prepare the media required for the system rename procedure. Afterwards go to the next step and add the required RDB name.support.1 to 7.sap.0 archive from the SAP Software Download Center because you must use the latest version.

mysap. c.SAR <Path to Unpack Directory> Note Make sure that all users have read permissions for the directory where you want to unpack the installer. Verify the signature of the downloaded SWPM10SP<Support_Package_Number>_<Version_Number>. 4. For more information about SAPCAR.sap. If you did not do so already. Select the archive file for your operating system and download it to an empty directory. 2. We recommend that you copy the software provisioning manager 1. Get the latest version of the SAPCRYPTOLIB archive to your Windows PC as follows: 1.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcryptolib”. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 3. see SAP Note 212876 . Go to https://launchpad.SAR archive by executing the following command: Note Check SAP Notes 2178665 and 1680045 whether additional information is available. Do not forget afterwards to perform an IPL to make the change effective.support. Unpack the Software Provisioning Manager archive to a local directory on your Windows PC using the following command: <Path to SAPCAR>\sapcar.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcar”. Download the Certificate Revocation List from https://tcs. Otherwise. make sure you have configured your TCP/IP as described in SAP Note 92589 .exe -xvf <Path to Download Directory> \SWPM10SP<Support_Package_Number>_<Version_Number>.0 archive to the IFS of the IBM i host.com/crl/ crlbag.sap.support.exe. Rename the executable to sapcar. Using the latest version of SAPCAR.1 to 7. b. 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 –R <target directory> 4. 2. <Path to SAPCAR>\sapcar. 5. Go to https://launchpad.5 ABAP on IBM i Preparation CUSTOMER 29 . you can verify the signature of the downloaded SWPM10SP<Support_Package_Number>_<Version_Number>.exe -tvVf<Path to Download Directory> \SWPM10SP<Support_Package_Number>_<Version_Number>. the file copying is very slow from your local Windows optical media drive or Windows file system to the IFS on your IBM i. b. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable. 3.SAR archive as follows: a. Get the latest version of the SAPCAR tool on the host where you want to run the installer: a.SAR -crl<file name of revocation list> 6.p7s and move it into the same directory.

Note The share TMPSAP must have the access permission Read/Write and the path name should be /tmp/ SAP. Note This procedure should not be used on a V7R1 IBM i host. Click the folder Shared Objects to see the shares. Caution Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. 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.1 to 7. you have to create this share manually using the IBM Systems Director Navigator for i. No copied content is corrupted. Do not unpack it to the same folder as other installation media. 3. and you want to copy manually media from your Windows PC into the IFS of your IBM i. A new screen i5/OS Netserver appears. and no copied files with longer file names are shortened by a converting share. right-click New File . 5.8 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. Start the IBM Systems Director Navigator for i on your Windows PC. To copy the media. 2.5 ABAP on IBM i 30 CUSTOMER Preparation . To check the already existing share TMPSAP or create a new share TMPSAP. 6. Right-click File Shares Open i5/OS Netserver . We do not recommend this because it is not considered secure anymore. 3. To do so. Note In the past. On V7R1. Procedure Creating a Binary Share on IBM i If you do not already have a binary share TMPSAP on your IBM i. proceed as follows: 1. choose File Systems File Shares . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 4. To create or change the share TMPSAP. we suggested to create a binary share pointing to the root directory / on your IBM i host. Connect to your IBM i using My Connections. you must use an alternative method such as FTP.

5 ABAP on IBM i Preparation CUSTOMER 31 . To save the share TMPSAP. If X: is already in use. 7. To change to the new network drive. On the Text Conversion tab. 8. do not select Allow file text conversion. Enter cmd. SAP NetWeaver. 3. Otherwise. To do this. you have already established the required connection to your IBM i. Create the subdirectories in your IFS where you want to copy the required media. SAP SRM 6. SAP ERP. see Preparing an IBM i User Profile [page 32]. To open the command prompt on Windows. In the command prompt. Otherwise. Now you have created the share TMPSAP on your IBM i. 5. All network connections to shared resources are displayed. SAP NetWeaver. you have already established the required connection to your IBM i. SAP SRM Check if you have a connection to your IBM i. you have to establish this connection. choose another drive letter that is free. SAP ERP. For more information about how to create the installation user SAPIUSR. enter: net use X: \<IBM_i_Host_Name>\TMPSAP SAP /USER:SAPIUSR X: is now your new network drive to share \<IBM_i_Host_Name>\TMPSAP to your IFS on the IBM i. you have to establish this connection. Note For more information about how to prepare the user QSECOFR. Note We use the user name SAPIUSR and the password SAP as examples. 2. To do this. enter net use. If you find \<IBM_i_Host_Name>\TMPSAP in the Remote column and a drive directory letter in the Local column. choose another drive letter that is free. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. End of 'Software Component': SAP SCM 7.exe. 4. see Preparing an IBM i User Profile [page 32]. enter: net use X: \<IBM_i_Host_Name>\TMPSAP <QSECOFR_Password> /USER:QSECOFR X: is now your new network drive to share \<IBM_i_Host_Name>\TMPSAP to your IFS on the IBM i: If X: is already in use. 8. Only valid for 'Software Component': SAP CRM. choose Start Run . Press OK. enter X: in the command prompt. press OK. End of 'Software Component': SAP CRM. Copying the Installation Media Manually Using the Binary Share TMPSAP 1. If the directory /tmp/SAP does not exist directly create it manually as QSECOFR or installation user using the following command: mkdir /tmp/SAP .1 to 7. Only valid for 'Software Component': SAP SCM Check if you have a connection to your IBM i. The command prompt appears. If you find \<IBM_i_Host_Name>\TMPSAP in the Remote column and a drive directory letter in the Local column.

However for SCM.9 Preparing an IBM i User Profile For running the installer you must create a user account on the IBM i host. you need to use the user QSECOFR because the liveCache client software has to be installed by this special user. enter: mkdir /tmp/SAP/<SAPSID>/<Media_Name> or mkdir /tmp/SAP/<SAPSID>/<Unpack_Directory> Note You must avoid blanks or commas in the media path name. we recommended that you create user SAPIUSR. For other installations.1 to 7. 9. ● SCM Only: The IBM i installation user profile must be the user QSECOFR. For each required media. The following requirement applies: ● The IBM i installation user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR. 10. Note This is different to other installations on IBM i. For IBM i the following directories have to be copied: ● K_<Version>_<U or N>_OS400_PPC64 ● EXP* ● SL_CONTROLLER_<nnn> 3. For each 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. 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:###BOT_TEXT###lt;SAPSID>###BOT_TEXT###lt;Media_Name> /E or xcopy C:\tmp\download###BOT_TEXT###lt;Unpack_Directory> X:###BOT_TEXT###lt;SAPSID>###BOT_TEXT###lt;Unpack_Directory> /E Note You must copy the root directory of the media respectively of the <Unpack_Directory> and all required subdirectories to the IFS of your IBM i. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.5 ABAP on IBM i 32 CUSTOMER Preparation .

End of 'Software Component': SAP SCM Caution You should not set the system variable QIBM_PASE_CCSID. you must delete this user.5 ABAP on IBM i Preparation CUSTOMER 33 . In the current release. 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. you can revert the user profile QSECOFR back to the old values. you must add to the user profile SAPINST the feature of a group by adding SAPINST to the group of a different user profile such as SAPIUSR. If you do not want to delete this user for any reason. use the following command: CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST) Now the user SAPINST can also be used as a group by the installer. 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.Procedure Note The user name SAPIUSR and the password SAP are used as examples in the procedures. we recommended that you create the user SAPINST on IBM i to install the SAP system. a group SAPINST is created generically on all platforms and is used for the installation of the SAP system. enter the following command: Only valid for 'Software Component': SAP SCM CHGUSRPRF USRPRF(QSECOFR) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE) End of 'Software Component': SAP SCM Only valid for 'Software Component': SAP SCM After the installation. call the following command: CHGUSRPRF USRPRF(SAPIUSR) USRCLS(*SECOFR) TEXT('SAP installation user') SPCAUT(*USRCLS) OWNER(*USRPRF) LANGID(ENU) CNTRYID(US) CCSID(500) LOCALE(*NONE) System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. If the user SAPINST already exists on your system. Note If you have already an old installation user and you want to make sure this user is configured correctly for your next SAP system installation. To do this. Do not leave this variable empty.1 to 7.

the SAP kernel tools on IBM i need some adopted permissions from the user QSECOFR. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. To do this. For example. To enable the user QSECOFR use the following command using your installation user: CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED) Note In a distributed environment. Note In a distributed environment. Procedure 1. To check the status of the user profile QSECOFR use the following command using your installation user: DSPUSRPRF USRPRF(QSECOFR) 2. the installation user must have the same name and password on all hosts so that the required remote access permissions are available. If the user QSECOFR is disabled this will lead to errors when SAP kernel tools such as CRTR3INST are called. Set a new password and the password of QSECOFR is then no longer expired. the user QSECOFR must be enabled. Recommendation Check also if the password of the user QSECOFR is expired. 3. Only when the password of the QSECOFR is not expired the installation procedure will finish successfully.5 ABAP on IBM i 34 CUSTOMER Preparation . login as QSECOFR. the profile directory on the global host should be accessible to the installation user of a remote additional application server instance. When the password is already expired you will be asked for a new password. the profile directory on the global host should be accessible to the installation user of a remote additional application server instance. the installation user must have the same name and password on all hosts so that the required remote access permissions are available. For running the installer on IBM i. For example. This user has the most authority.10 Enable the User QSECOFR The user QSECOFR is the standard administrator user on IBM i. Although for running the installer you only require the installation user.1 to 7.

Note Only SAP systems are renamed.1 to 7.4 System Rename Procedure 4. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. the database is always up and running. Note The installer is not able to change objects that are locked. which are using the SAP NetWeaver 7.20 kernel or higher. The installer automatically starts the following instances during the system rename: ● Database Note For IBM i. see Perfoming IBM i-Specific Preparation Steps [page 18]. The system parameters are adapted offline. For more information. Central System You check the Prerequisites for Running the Installer [page 36] and run the installer to rename the system as described in Running the Installer [page 39]. ● 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. Make sure that no object of the to be renamed SAP system is locked. the installer does not have to rename or change the database library and the journal receiver library.5 ABAP on IBM i System Rename Procedure CUSTOMER 35 .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. This will speed up the rename process as renaming a database library and stopping or starting the journaling is time consuming.

and – if required – to the additional application server instance hosts of the SAP system to be renamed.2 Prerequisites for Running the Installer Make sure you fulfil the following prerequisites before running the installer. Optional: You check the Prerequisites for Running the Installer [page 36] and run the installer to rename existing standalone Gateway instances as described in Running the Installer [page 39]. If your SAP system has an ASCS instance and the ASCS instance host is the SAP global host of the system. 3. 1. Next Steps You perform follow-up activities [page 59] 4. profile. 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. Microsoft Edge. ○ If you copy the SL Common GUI URL manually in the browser window. Always use the latest version of these web browsers. 2. incognito mode (Chrome) or System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. you export the global directories to the database instance host. If your SAP system has an ASCS instance. to the primary application server instance host. You make sure that the global directories (exe. Recommendation We recommend using Google Chrome. make sure that you open a new Web browser window in private browsing mode (Internet Explorer). Mozilla Firefox. global) are exported to the instance hosts of the SAP system to be renamed. 6. 5. You check the Prerequisites for Running the Installer [page 36] and run the installer to rename the database instance as described in Running the Installer [page 39].1 to 7. 4.Distributed and High-Availability System Note See also table System Rename Options and Sequence how to Execute Them in Running the Installer [page 39]. You check the Prerequisites for Running the Installer [page 36] and run the installer to rename the primary application server instance as described in Running the Installer [page 39]. Optional: You check the Prerequisites for Running the Installer [page 36] and run the installer to rename the SAP Web Dispatcher instance as described in Running the Installer [page 39]. or Microsoft Internet Explorer 11. ● If you want to use the SL Common GUI. you check the Prerequisites for Running the Installer [page 36] and run the installer to rename the ASCS instance as described in Running the Installer [page 39].5 ABAP on IBM i 36 CUSTOMER System Rename Procedure .

0') REPLACE(*YES) Qp2Term export DISPLAY=<Host_Name>:0.0 System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.0. private browsing mode (Firefox). you need 300 MB free space for the installer executables. This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.5 ABAP on IBM i System Rename Procedure CUSTOMER 37 . or TMPDIR to another directory with 300 MB free space for the installer executables. In addition. for example by using a crontab entry. ● The following information is only valid if you use the Java GUI: Note This is optional for advanced users. Make sure that your DISPLAY environment variable is set to <Host_Name>:0. ● Make sure that you have logged on to your host as an installation user with similar authorization rights to QSECOFR. TMP. TMP. For more information about how to create an installation user. ● Check the value of the temporary directory set in the environment if available: Table 4: Shell Command Command prompt WRKENVVAR Qp2Term echo $TEMP. ● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. where <Host_Name> is the host on which you want to display the installer GUI. You can set values for the TEMP. You can set values for the DISPLAY environment variables as follows: Table 5: Shell Used Command Command prompt ADDENVVAR ENVVAR(DISPLAY) VALUE('<Host_Name>: 0. ● Each SAP instance requires a separate installation directory. see Preparing an IBM i User Profile [page 32]. If you cannot provide 300 MB free space in the temporary directory. Recommendation We recommend that you keep all installation directories until the system is completely and correctly installed. you can set one of the environment variables TEMP. TMP.1 to 7. 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. For more information about the SL Common GUI. or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 45]. see Useful Information About the Installer [page 45]. or TMPDIR point.

the installer GUI is directly started on your Windows PC after starting the installer on IBM i. you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTPS_PORT=<Free Port Number> Example CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('. For more information about VNC. you do not have to use the remote installer GUI separately. We do not recommend that you start the installer using the DISPLAY variable as there is no support available. If this port cannot be used. Note For advanced users only: Beside using an XWindows Server and the DISPLAY variable. If your X server for Microsoft Windows or Linux is already configured and running./sapinst' 'SAPINST_HTTPS_PORT=<Free Port Number>') ○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing. you can try to direct the graphical output of the installer to an XWindow by setting the DISPLAY variable. you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=<Free Port Number> ○ When using the Java SDT GUI: ○ Port 21212 is used by default for communication between the installer GUI server and the installer GUI client. you can use VNC.5 ABAP on IBM i 38 CUSTOMER System Rename Procedure . If this port cannot be used. you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_DIALOG_PORT=<Free Port Number> System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. The filled-out evaluation form is then sent to SAP using HTTPS.1 to 7. ● Make sure that the following ports are not used by other processes: ○ When using the SL Common GUI: ○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL Common GUI. When VNC is prepared as described in the IBM i documentation. all changes of the environment variables done by the command export are reverted. which is similar to AIX. see the IBM i documentation. If this works. Note For advanced users only: PASE. If this port cannot be used. allows you to set the DISPLAY variable. Note When you leave your Qp2Term session. VNC also offers a GUI by using IBM i tools.

“SL Common GUI” for short ● The “classic” Java-based GUI with a CUI client and server . If this port cannot be used. The filled-out evaluation form is then sent to SAP using HTTPS. we address them as “installer GUI”.5 ABAP on IBM i System Rename Procedure CUSTOMER 39 . 4. see Prerequisites for Running the Installer [page 36]. For more information. you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=<Free Port Number> ● If you have changed the host name of your system. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7./sapinst' 'SAPINST_DIALOG_PORT=<Free Port Number>') ○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing. You then have to start the sapinst executable with the command line option SAPINST_SLP_MODE=false. Example CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('.“Java SDT GUI” for short Note If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI. Context Software Provisioning Manager (the “installer” for short) offers two GUIs: ● The new web browser-based “SL Common GUI of the Software Provisioning Manager” . Prerequisites For more information.1 to 7. see Useful Information About the Installer [page 45].3 Running the Installer This section describes how to run the installer to perform the system rename . In cases where both GUIs behave the same way. you also have to perform the steps described in sections Configuring TCP/IP [page 20] and Adjusting the Relational Database Name [page 27].

For more information. but this is considered an advanced user option. we recommend that you perform a remote installation with the installer. where the installer GUI is running on a separate host from the installer. you can specify another operating system user for authentication purposes. Then you can control the processing of the installer in the browser running on any device. Log on to the host where you want to run the installer. For more information. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. see SAP Note 1745524 . The section Running the Installer is used only for information. see SAP Note 1170809 . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. For more information. SL Common GUI only: 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 . For more information.5 ABAP on IBM i 40 CUSTOMER System Rename Procedure .This procedure describes an installation where you use one of the following GUI scenarios: ● You run the installer and use the SL Common GUI. ● You run the installer and use the Java SDT GUI. 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. ● Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations.1 to 7. Make the required media available. the remote GUI display (using the DISPLAY environment variable) is possible. For more information. see Preparing an IBM i User Profile [page 32]. see Performing a Remote Installation [page 50] and Starting the Installer GUI Separately [page 52]. You have to confirm that the user is a trusted one. The following information is only valid if you use the Java SDT GUI: ● If you need to see the installation on a remote display. Make sure that you log on as a user with similar authorization rights to QSECOFR. see Preparing the System Rename Media [page 28]. The installer is running on the installation host and the Java SDT GUI on a Windows PC. However. Recommendation The following information is only valid if you use the Java SDT GUI: Since IBM i does not have GUI capabilities. The remote installation is the default installation option on IBM i. 2. Afterwards the installer behaves the same as if started completely on one host. we recommend that you perform a remote installation [page 50]. You first have to start the installer without the installer GUI on the IBM i host using QP2TERM and then you have to start the installer GUI on the Windows installation host. Procedure 1.

Recommendation Make the installation media available locally . if you use Network File System (NFS).. The SL Common GUI opens in the browser by displaying the Welcome screen. start the installer with the installer property SAPINST_USE_HOSTNAME as follows: CALL PGM(QP2TERM) PARM(’. Start the installer as follows: Open a command prompt and enter the following command: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM(’. Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page 36]). ************************************************************************* ******* Open your browser and paste the following URL address to access the GUI https://[<hostname>]:4237/sapinst/docs/index. 4.. Sample Code .5 ABAP on IBM i System Rename Procedure CUSTOMER 41 . even if the certificate could not be verified. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7./sapinst’ ’SAPINST_USE_HOSTNAME=<Virtual_Host_Name>') Caution Make sure that the installation directory is not mounted with NFS. your browser might warn you that the certificate of the sapinst process on this computer could not be verified.html Logon users: [<users>] ************************************************************************* ******* ./sapinst’) Note If you want to use a virtual host name. 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. The installer is starting up. 3. do one of the following: ○ If you use the SL Common GUI. the installer now starts and waits for the connection with the SL Common GUI. reading from media mounted with NFS might fail. For example.. Depending on the type of the installer GUI you want to use.. Note Before you reach the Welcome screen.1 to 7. Accept this warning to inform your browser that it can trust this site. or there might be problems when starting the Java Virtual Machine.

as required System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. skip you have performed the this option. the ERS instance. if they have an skip this option. Choose the system rename options as required and in the order they appear. ○ If your system is a distributed system. For more information. rename options for the ASCS instance (if availa­ ble). ASCS instance (if availa­ ble). 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 instance Gateway instance. choose System Rename Distributed System <System_Rename_Option> . rename option for the ASCS instance (if availa­ ble) above. In the Welcome screen.1 to 7. and the primary application server instance above. you still need to start the Java SDT GUI separately on a Windows PC to get the Welcome screen displayed. 5. the database instance. ○ If you use the Java SDT GUI . as required System Rename for the Executes system rename Execute this option after Execute this option after Primary Application for the primary application renaming the database in­ you have performed the Server Instance server instance stance. and the database instance above. skip rename options for the this option. see Starting the Installer GUI Separately [page 52]. AS ABAP. 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 tem ID. 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.5 ABAP on IBM i 42 CUSTOMER System Rename Procedure .that is you started the sapinst executable with command line option SAPINST_SLP_MODE=false. choose System Rename Standard System System Rename . the ERS instance. Table 6: 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. proceed according to your system variant : ○ If your system is a standard system . the host name or rename options for the the instance number) ASCS instance (if availa­ ble) and the ERS instance above.

The installer starts the rename procedure and displays its progress on the Task Progress screen. ○ If you use the Java SDT GUI.1 to 7. You can get this number from the global host where the SCS or ASCS instance is already installed using following command: DSPUSRPRF USRPRF(<SAPSID>ADM) or CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' '<SAPSID>ADM') The SCS or ASCS installation is the installation which initially determinates the UID of the user <SAPSID>ADM. choose Next. 9. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. position the cursor on the required parameter input field : ○ If you use the SL Common GUI. Note To find more information on each parameter during the Define Parameters phase. the installer displays the Parameter Summary screen. choose either F1 or the HELP tab. Then the available help text is displayed in the HELP tab. 7. Then a dialog opens with the available help text.5 ABAP on IBM i System Rename Procedure CUSTOMER 43 .that is 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. Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts such as SAR archives or files on the media after the initial check has been done . 8. choose F1 . Caution The signature of media is checked automatically during the Define Parameters phase while processing the Media Browser screens. Follow the instructions in the installer input screens and enter the required parameters. Choose Next. If required. See also the description of this new security feature in SAP Note 2393060 . skip this option. To start the execution. 6. After you have entered all requested input parameters. This screen shows both the parameters that you entered and those that the installer set by default. Option Description When to Execute Execution Order 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. you can revise the parameters before starting the system rename procedure. Caution Whenever you are asked by the installer for the password of the user <SAPSID>ADM on a remote IBM i host put also the UID number of the <SAPSID>ADM into the input screen when it is not set already.

the installer displays the message Execution of <Rename_Option> has completed. including all instances.1 to 7. The installer starts the export and displays its progress of the system copy export during the processing phase. you can delete these files when the installer has successfully completed. 12. This might be useful for analyzing any issues that might occur later when using the system. we recommend that you delete the .xxxx after the installer has finished. you can find the log file dev_selfex. but make sure that you delete them after saving them separately. do not keep the installer directories on hosts where you processed it. we recommend that you remove the group SAPINST from the operating system users after you have completed the installation. 11. Once the system is completely and correctly installed.out in the temporary directory. 10. If you copied installation media to your hard disk. If required. delete directories with the name sapinst_exe. 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.stdgui 13. Recommendation Keep all installer directories until you are sure that the system. For security reasons. For security reasons. Related Information Useful Information About the Installer [page 45] Interrupted Processing of the Installer [page 47] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Note For more information about how to remove the installer files on IBM i. When the system rename option has finished successfully. Note This step is only required. is completely and correctly installed.xxxxxx.5 ABAP on IBM i 44 CUSTOMER System Rename Procedure .sdtgui directory within the home directory of the user with which you ran the installer: /home/<Installation_User>/. see Removing the Installer Installation Files [page 57]. Sometimes these remain in the temporary directory. make a copy of the installer directories with all their contents. Java GUI only: For security reasons. such as a medium or a USB drive that is separate from your installation hosts. Save the copy to a physically separate medium. Note If there are errors with the installer extraction process.

also known as SAPUI5 . 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 .a client-side HTML5 rendering library based on JavaScript.Performing Remote Processing of the Installer (Java SDT GUI only) [page 50] Starting the Java SDT GUI Separately [page 52] Running the Installer in Accessibility Mode [page 55] Troubleshooting with the Installer [page 56] 4. since only a web browser is required on the client ○ New controls and functionality.“SL Common GUI” for short ○ The “classic” Java-based GUI with a CUI client and server .which is part of Software Provisioning Manager .running on the installation host using the standard protocol HTTPS.4 Additional Information About the Installer The following sections provide additional information about the installer. open a web browser supported by the SL Common GUI on any device and run the URL from there. The SL Common GUI connects the web browser on a client with the sapinst executable . For more information about supported web browsers see Prerequisites for Running the Installer [page 36]. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.4. view logs in web browser.“Java SDT GUI” for short The SL Common GUI of the Software Provisioning Manager (or “SL Common GUI” for short) uses the SAP UI Development Toolkit for HTML5 . Related Information Useful Information About the Installer [page 45] Interrupted Processing of the Installer [page 47] Performing Remote Processing of the Installer (Java SDT GUI only) [page 50] Starting the Java SDT GUI Separately [page 52] Running the Installer in Accessibility Mode [page 55] Troubleshooting with the Installer [page 56] Removing the Installer Installation Files [page 57] 4. for example. If you have a supported web browser installed on the host where you run the installer.5 ABAP on IBM i System Rename Procedure CUSTOMER 45 . you can start the SL Common GUI directly from this URL.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) offers two GUIs: ○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” .1 to 7. Otherwise. The benefits of this new user interface technology for the user are: ○ Zero foot print.

● The installer creates the installation directory sapinst_instdir directly below the temporary directory. To do so. 2. If you want to use an alternative installation directory. proceed as described in Running the Installer in Accessibility Mode [page 55]. The temporary directory also contains the log file dev_selfex.xxxxxx.5 ABAP on IBM i 46 CUSTOMER System Rename Procedure ./sapinst' '-p') ● This information is only relevant if you use the Java GUI of the installer: If you need to run the installer in accessibility mode. TMP. Caution If the installer cannot find a temporary directory.xxxx sometimes remain in the temporary directory. If the SL Common GUI does not meet your requirements. Directories called sapinst_exe. which might be useful if an error occurs. Caution Make sure that the installation directory is not mounted with NFS. These executables are deleted again after the installer has stopped running. or TMPDIR to the required directory before you start the installer. all changes of the environment variables done by the command export are reverted. Restart the installer with command line option SAPINST_SLP_MODE=false. You can switch back to the default installer GUI at any time with the following steps: 1. ● To see a list of all available installer properties. Table 7: Shell Used Command Command prompt ADDENVVAR ENVVAR(TEMP) VALUE('<Directory>') REPLACE(*YES) Qp2Term export TEMP=<Directory> Note When you leave your Qp2Term session. If no value is set for these variables.out from the extraction process. you can still use the “classic” Java SDT GUI. you must start the sapinst executable with the command line option SAPINST_SLP_MODE=false. TMP. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. or TMPDIR environment variable. enter the following commands: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('. You can safely delete them. 3. The installer finds the temporary directory by checking the value of the TEMP. the installation terminates with the error FCO-00058. the installer creates a subdirectory located in the sapinst_instdir directory. Stop the installer. the installer uses /tmp as default installation directory.1 to 7. ● The installer extracts itself to the temporary directory. set the environment variable TEMP. ● For each option. otherwise there might be problems when the Java Virtual Machine is started. On the What do you want to do? screen choose Continue with the existing run.

● If required. the installation pauses and a dialog box appears.. ○ In the Java SDT GUI.1 to 7. 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. If an error occurs. Note If you need to terminate the installer. ● You interrupted the installation by choosing ○ Cancel in the SL Common GUI ○ Exit Process in the SAPinst menu in the Java SDT GUI Caution If you stop an option in the Execute phase. 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.4. any system or component installed by this option is incomplete and not ready to be used.5 ABAP on IBM i System Rename Procedure CUSTOMER 47 . stop the installer by choosing one of the following. press Shift + Esc then 2 on your IBM i host. Any system or component uninstalled by this option is not completely uninstalled. depending on the installer GUI you use: ○ In the SL Common GUI. 4.2 Interrupted Processing of the Installer Here you find information about how to restart the installer if its processing has been interrupted. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. choose SAPinst Exit Process in the installer Java SDT GUI menu on your Windows PC. choose the Cancel button.

The installer records the installation progress in the keydb. This is possible because the installer records the installation progress in the keydb. which you stopped by choosing Stop. reading from media mounted with NFS might fail. View Log Access installation log files. or to continue an interrupted installation after an error situation. For example. or Network File System (NFS). try to solve the problem. Stop The installer stops the installation. you can continue the installation from the point of failure without repeating any of the previous steps. For more information. closing the dialog box. Continue The installer continues the installation from the current point. Enter the following commands: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('. see Preparing the System Rename Media [page 28]./sapinst') System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 2. if you use remote file shares on other Windows hosts. Make sure that the media required for the system rename are still available.1 to 7. Restart the installer from the installation media directory to which you unpacked the Software Provisioning Manager archive. See the procedure below.xml file. Procedure 1. If the same or a different error occurs. Log on to the installation host as a user with the required permissions as described in Running the Installer [page 39] . We recommend that you view the entries in the log files.5 ABAP on IBM i 48 CUSTOMER System Rename Procedure . 3.xml file. and then choose Retry. and the GUI server. Therefore. The following procedure describes the steps to restart an installation. the installer GUI.The following table describes the options in the dialog box: Table 8: Option Definition Retry The installer retries the installation from the point of failure without repeating any of the previous steps. CIFS shares on third-party SMB-servers. the installer displays the same dialog box again. Recommendation Make the installation media available locally.

5 ABAP on IBM i System Rename Procedure CUSTOMER 49 . you still need to start the Java SDT GUI separately on a Windows PC to get the Welcome screen displayed. From the tree structure on the Welcome screen. your browser might warn you that the certificate of the sapinst process on this computer could not be verified. do one of the following: ○ If you use the SL Common GUI. Accept this warning to inform your browser that it can trust this site. decide between the following alternatives and continue with Next: System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 6. the installer now starts and waits for the connection with the SL Common GUI. Sample Code .. even if the certificate could not be verified.1 to 7. 4. 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. 5. ************************************************************************* ******* Open your browser and paste the following URL address to access the GUI https://[<hostname>]:4237/sapinst/docs/index. Note Before you reach the Welcome screen. Depending on the type of the installer GUI you want to use..that is you started the sapinst executable with command line option SAPINST_SLP_MODE=false..html Logon users: [<users>] ************************************************************************* ******* . For more information. On the What do you want to do? screen. see Starting the Installer GUI Separately [page 52]. The What do you want to do? screen appears. The installer is restarting. ○ If you use the Java SDT GUI .. Open the URL on a device with a supported web browser (see Prerequisites for Running the Installer [page 36]). The SL Common GUI opens in the browser by displaying the Welcome screen. select the installation option that you want to continue and choose Next.

Afterwards. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 4.4. they might no longer function properly.5 ABAP on IBM i 50 CUSTOMER System Rename Procedure . Note This section is only valid if you use the Java SDT GUI. it moves the content of the old installer directory and all installer-specific files to a backup directory. Instead. Caution The installer moves all the files and folders to a new log directory.1 to 7. Prerequisites ● The remote host meets the prerequisites for starting the installer as described in Prerequisites for Running the Installer [page 36]. you can no longer continue the old option. even if these files and folders are owned by other users. If there are any processes currently running on these files and folders.3 Performing Remote Processing of the Installer (Java SDT GUI only) Here you find information about how to process the installer on a remote host. That is. you started the sapinst executable with command line option SAPINST_SLP_MODE=false. Table 9: Alternative Behavior Perform a new run The installer does not continue the interrupted system rename option. Continue with the existing one The installer continues the interrupted system rename from the point of fail­ ure. The following naming convention is used for the backup directory: log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds> 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 Make sure that the installation user has not set any environment variables for a different SAP system or database by using the command WRKENVVAR. the installer runs on the remote host. Make the installation media available on your remote host. see SAP Note 1745524 . If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know QSECOFR like credentials on the remote host. To test this: 1. Procedure 1. “local host” refers to the Windows installation host. For more information. Log on to your remote host (IBM i) and enter the command: PING RMTSYS('<Local_Host>') 2.1 to 7. and the installer GUI runs on the local host. Context You use this procedure to process the installer on a remote host. The local host is the host from which you control the installation with the installer GUI. You have to confirm that the user is a trusted one. see Preparing the System Rename Media [page 28]. 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. Log on to the remote host as the installation user with similar authorization rights to QSECOFR. Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information. see SAP Note 1170809 . ● Both computers are in the same network and can ping each other. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. For more information. 2. In this case. The installer GUI connects using a secure SSL connection to the installer.5 ABAP on IBM i System Rename Procedure CUSTOMER 51 . Caution In this section. and “remote host” refers to the IBM i host where the SAP system is installed. make sure that this user exists on the remote host and that this user owns an existing home directory on IBM i (/home/<User_Name>). For more information. see Preparing an IBM i User Profile [page 32]. Log on to the local host (Windows PC) and enter the command: ping <Remote_Host> ● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter.

you started the sapinst executable with command line option SAPINST_SLP_MODE=false. There is no GUI on IBM i. 5. reading from media mounted with NFS might fail. Open a command prompt and change to the directory to which you unpacked the Software Provisioning Manager archive./sapinst' 'SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>') The installer now starts and waits for the connection to the installer GUI.1 to 7. For example. you must start the installer GUI separately on a Windows operating system .4. 4. That is./sapinst' '-sfxver') The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 52]). Start the installer by entering the following command: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('./sapinst') Note If you need to specify another operating system user for authentication purposes. Check the version of the sapinst executable by entering the following command: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('. this command is as follows: CALL PGM(QP2TERM) PARM('.4 Starting the Java SDT GUI Separately Here you find information about how to start the Java SDT GUI separately. port <Port_Number> to continue with the installation 6. 4. You see the following at the command prompt: guiengine: no GUI connected. For more information. As a default. if you use Network File System (NFS). System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 3. waiting for a connection on host <Host_Name>. so you do not see the installer Welcome screen. Note This section is only valid if you use the Java SDT GUI.5 ABAP on IBM i 52 CUSTOMER System Rename Procedure . Recommendation Make the installation media available locally . see Starting the Installer GUI Separately [page 52].

see Preparing the System Rename Media [page 28]. For more information. you first start a command prompt using Run as administrator. Procedure ● Starting the Installer GUI on Windows a. and <Port_Number_Gui_Server_To_Gui_Client> is the port the GUI server uses to communicate with the GUI client (21212 by default). the following variables are used: <Remote_Host> is the name of the remote host. b. you have to start the installer GUI separately on a Windows host as described below with the command line parameter -accessible. see Performing Remote Processing of the Installer (Java SDT GUI only) [page 50]. Then in this command prompt.Prerequisites The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in Prerequisites for Running the Installer [page 36]. Since there is no GUI on IBM i. make sure that you meet the prerequisites for the installer listed in the relevant Windows guide. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters: Note If you start the installer GUI executable on Windows 7 or Windows 2008. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. you must start the installer GUI separately. Typically. Note If you want to run the installer on a Windows host. you must use the option Run as administrator. where the installer GUI runs on a different host from the installer. For more information. For more information. Caution This is the default on IBM i. ● You want to run the installer in accessibility mode. you enter the installer GUI command. In this case.1 to 7. see Running the Installer in Accessibility Mode [page 55]. In the this procedure.5 ABAP on IBM i System Rename Procedure CUSTOMER 53 . Context You might need to start the installer GUI separately in the following cases: ● You are running IBM i and did not set a DISPLAY environment variable. Make the installer software available on the host on which you want to start the installer GUI. ● You want to perform a remote installation. ● You closed the installer GUI using File Close GUI only from the installer menu while the installer is still running.

exe is part of the Software Provisioning Manager archive for IBM i. you can start the installer GUI using your copied unpack directory: X:###BOT_TEXT###lt;SAPSID>###BOT_TEXT###lt;Unpack_Directory> For more information. The installer GUI starts and connects to the installer. see Preparing the System Rename Media [page 28]. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters: ○ If you want to perform a remote installation.exe by entering the following command: <Path_To_Unpack_Directory>\sapinstgui. proceed as follows: 1.5 ABAP on IBM i 54 CUSTOMER System Rename Procedure . see Copying the Installation Media Manually to Your IBM i [page 30].exe is missing. Start the installer GUI by entering the following command: <Path_To_Unpack_Directory>\sapinstgui. execute the following command: <Path_To_Unpack_Directory>\sapinstgui. Only when the file sapinstgui.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client> ○ If you closed the installer GUI using File Close GUI only and want to reconnect to the installer.exe -sfxver The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 50]).1 to 7. proceed as follows: 1. you must download the Software Provisioning Manager archive for Windows. 2. Check the version of sapinstgui. Check the version of the sapinstgui executable by entering the following command: <Path_To_Unpack_Directory>/sapinstgui -sfxver The version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 50]). ● Starting the Installer GUI on UNIX a.exe -port <Port_Number_Gui_Server_To_Gui_Client> 2.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client> c. For more information. b. If you are performing a remote installation with the installer and the installer GUI running on different hosts. By default the Windows sapinstgui. Start the installer GUI by entering the following command: <Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client> System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. proceed as follows: 1. ○ If you want to perform a remote installation. execute the following command: <Path_To_Unpack_Directory>\sapinstgui. If you are performing a local installation with the installer and the installer GUI running on the same host. Make the installer software available on the host on which you want to start the installer GUI. Note If you have a share TMPSAP on your IBM i and you have mapped this share to the drive for example X. 2.

If you are performing a local installation with the installer and the installer GUI running on the same host. If you use the SL Common GUI. ● Custom font setting: This feature is derived from the Windows display properties.1 to 7. you started the sapinst executable with command line option SAPINST_SLP_MODE=false. proceed as follows: 1. Note The information contained in this section is only valid if you use the Java SDT GUI. ○ If you closed the installer GUI using File Close GUI only and want to reconnect to the installer. perform a remote installation with the installer GUI running on a Windows host. Context The following features are available: ● Keyboard access: This feature is generally available for all operating systems. to enable this feature. ● High-contrast color: This feature is derived from the Windows display properties. perform a remote installation with the installer GUI running on a Windows host. to enable this feature. Procedure ● Activating and Adjusting Accessibility Settings on Windows You first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.5 Running the Installer in Accessibility Mode You can also run the installer in accessibility mode. apply the standard accessibility functions of your web browser. That is. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.4. Therefore. execute the following command: <Path_To_Unpack_Directory>/sapinstgui -port <Port_Number_Gui_Server_To_Gui_Client> 2. execute the following command: <Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client> c.5 ABAP on IBM i System Rename Procedure CUSTOMER 55 . 4. Therefore. The installer GUI starts and connects to the installer. If you are performing a remote installation with the installer and the installer GUI running on different hosts.

Start the installer on the remote IBM i host by executing the following command from the command line as described in Performing Remote Processing of the Installer (Java SDT GUI only) [page 50]: CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('. To define your own color schemes.1 to 7. Select Adjust font size (DPI) and choose Larger scale (120 DPI). b. To define other font size schemes. Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Java SDT GUI Separately [page 52]: <Path_To_Unpack_Directory>\sapinstgui. ● Running the Installer in Accessibility Mode a. Start the installer on the remote host by executing the following command from the command line as described in Performing Remote Processing of the Installer (Java SDT GUI only) [page 50]: <Path_To_Unpack_Directory>/sapinst b. c. Select a color scheme from the Color scheme drop-down box.4.exe -accessible -host <Remote_Host> - port <Port_Number_Gui_Server_To_Gui_Client> 4.5 ABAP on IBM i 56 CUSTOMER System Rename Procedure . In the right-hand pane. the installer: ● Stops processing ● Displays a dialog informing you about the error System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.exe -accessible -host <Remote_Host> - port <Port_Number_Gui_Server_To_Gui_Client> You perform a remote installation as follows: a. choose Custom DPI. Note The following procedure applies for Windows Server 2012 and might be different when using another Windows operating system./sapinst') b. Context If an error occurs. select Window Color and Appearance.6 Troubleshooting with the Installer This section tells you how to proceed when errors occur while the installer is running. Right click on your Windows desktop and choose Personalize. Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Java SDT GUI Separately [page 52]: <Path_To_Unpack_Directory>\sapinstgui. choose Advanced. a.

○ The View Logs menu item. then you should keep the share. For more information about using subcomponents of BC-INS*. choose: ○ The LOG FILES tab. For more information. 3. ○ If you use the Java SDT GUI. If you cannot resolve the problem. ○ If you use the Java SDT GUI. ○ Then continue by choosing Retry.log and sapinst_dev.1 to 7. Caution You might want to disconnect from the share TMPSAP and remove it from the IBM i. The vendor can give you information about whether this X Server supports Java Swing- based GUIs and also tell you about further requirements and restrictions. and the copied installation media.7 Removing the Installer Installation Files You use this procedure to gain disk space after the installation by deleting the installer.log) for errors. choose Cancel in the tool menu. ○ If the installer GUI aborts without an error message. ○ To check the log and trace files of the installer GUI for errors: ○ If you use the SL Common GUI. see SAP Note 1669327 .4.Procedure 1. However. choose Stop from the error message or SAPinst Exit Process in the tool menu. report an incident using the appropriate subcomponent of BC-INS*. do one of the following: ○ Try to solve the problem: ○ To check the installer log files (sapinst. restart the installer GUI as described in Starting the Installer GUI Separately [page 52]. If an error occurs during the Define Parameters or the Execute Service phase. ○ If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote Access of the Java SDT GUI on Windows workstations and you experience display problems such as missing repaints or refreshes. if you are using the Java SDT GUI. contact your X Server vendor. depending on the type of installer GUI you use: ○ If you use the SL Common GUI. see Interrupted Processing of the Installer [page 47].err in the current /home/<Installation_User> directory. if you want to start tools like the SAP NetWeaver AS for Java EE ConfigTool from the share TMPSAP on your Windows PC. the temporary installer files. abort the installer by choosing one of the following. On the IBM i host. 2. check the file sdtstart. you should remove the installation directory. you can find them in the directory /home/ <Installation_User>/. you can find them in the directory /home/ <Installation_User>/.sdtgui/ ○ If the GUI server or the installer GUI does not start. 4. For more information.sapinst/. if you are using the SL Common GUI. see SAP Note 1170809 .5 ABAP on IBM i System Rename Procedure CUSTOMER 57 . ○ If you cannot resolve the problem. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Check SAP Note 1548438 for known installer issues.

To remove the downloaded and/or copied installation media. When the installer installation directory is deleted. enter the following command: RMVDIR DIR('/tmp/sapinst_exe*') SUBTREE(*ALL) Note If you have chosen one of the three variables: TEMP. If you want to remove the installer installation directory. Procedure Caution Only delete the log files if you are sure that you do not need them again.5 ABAP on IBM i 58 CUSTOMER System Rename Procedure . Do not delete log files other than those in the paths given here. TMP. enter the following command on your Windows PC: net use <Mapped_Drive>: /DELETE System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. On IBM i: 1.1 to 7. Parallel to the installer in the installation directory a library SAP<SAPSID> is created containing the ILE load tools for the database. To remove temporary SAPINST files. enter the following command: RMVDIR DIR('/tmp/sap/<SAPSID>') SUBTREE(*ALL) To disconnect your mapped drive from the IBM i. you can also remove this library using the following command: DLTLIB LIB(SAP<SAPSID>LOAD) 3. you must use this temporary directory instead of '/tmp'. 4. ● The SAP system is up and running. Caution Do not use this procedure until all instances of the SAP system on the IBM i host have been installed. or TMPDIR for your temporary directory in section Useful Information About the Installer [page 45]. Prerequisites ● You have completed the SAP system installation. enter the following command: RMVDIR DIR('<Installation_Directory>') SUBTREE(*ALL) 2.

see Database-Specific Follow-Up Activities [page 60] 4. 6.5 Follow-Up Activities 5. see Changing the IGS Destination [page 62]. 3. Configure the transport management system. Restart the renamed SAP system completely. Change the IGS destination. see Starting the SAP System [page 62]. Perform follow-up activities for your database. For more information. Perform general follow-up activities. For more information.1 Follow-Up Activities Checklist Procedure 1. the database is always up and running. ○ Instance services of an IBM i operating system ○ ABAP Central services instance (ASCS instance) if an ASCS instance is available 2. The installer has only started the following instances during the system rename: ○ Database Note For IBM i.5 ABAP on IBM i Follow-Up Activities CUSTOMER 59 . For more information. For more information. see Starting the SAP System [page 62]. For more information. see Configuring the Transport Management System [page 61]. see General Follow-Up Activities [page 60]. Start the primary application server instance. 5.1 to 7. For more information. Related Information General Follow-Up Activities [page 60] Database-Specific Follow-Up Activities [page 60] Configuring the Transport Management System [page 61] Changing the IGS Destination [page 62] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.

com/docs/DOC-25771 . see the system copy guides at: https://help. For more information.1. this aspect is not relevant for your use case.2 Database-Specific Follow-Up Activities Related Information Performing Follow-Up Activities for SAP HANA Database [page 61] Performing Follow-Up Activities for IBM DB2 for i [page 61] System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.sap. If your logical system names contain attributes that were renamed as part of this procedure. 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. Example To identify potential follow-up activities regarding logical system names.1 General Follow-Up Activities This section refers to the general follow-up activities that you have to perform after the rename of your SAP system.1.5 ABAP on IBM i 60 CUSTOMER Follow-Up Activities . answer to the following question: What naming convention was used for the logical system names? The default convention is <SAPSID>CLNT<Client_Number>.Starting the SAP System [page 62] Removing the Installer Installation Files [page 57] 5. due to the high variety of use cases. ○ If yes. ● Potentially.com/sltoolset System Provisioning Guide for System Copy for Systems Based on SAP NetWeaver 7. but it might have been adapted individually.1 to 7. 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. see http://scn. so you can profit from an easier. no rule which of the potential follow-up activities are valid can be given . 5.1 & Higher <OS Platform> Generally. For more information.sap. answer to the following question: Does the renamed SAP system use logical system names? ○ If not. faster and more reliable process.

Run program RDDNEWPP and set the priority to normal. 2. Procedure Identify and delete the backup of the journal receiver library of the source system. c. Call transaction STMS. b. 5. 5. Reschedule the transport dispatcher (RDDIMPDP) in client 000: a.1. Adapt the transport parameters and transport routes in the TMS as follows: a.1 to 7.1.2 Performing Follow-Up Activities for IBM DB2 for i In addition to the follow-up activities described in the system copy documentation. using the command SAVLIB on the journal receiver library into a SAVE FILE of a backup library. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Call transaction SE38. The backup was created by the installer.3 Configuring the Transport Management System You have to perform some steps to be able to use the Transport Management System. Log on as user DDIC.5.2.5 ABAP on IBM i Follow-Up Activities CUSTOMER 61 .1 Performing Follow-Up Activities for SAP HANA Database This section contains follow-up steps required for SAP HANA after the system rename has completed. Procedure Currently there are no follow-up steps required. you can delete the backup of the journal receiver library of the source system. The naming convention of the backup library is the following: R3<sourceSID>JRN is saved into the SAVEFILE R3<sourceSID>JRN of the back library R3<sourceSID>nn (nn is a number). Procedure 1.1.2.

5. For more information about how to start and restart an SAP system. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.0 and 6. c. b. make sure that you adapt the IGS destination.5 ABAP on IBM i 62 CUSTOMER Follow-Up Activities .0 Since the SAP NetWeaver Mobile 7. Procedure Call transaction SM59 and adapt the IGS destination IGS_RFC_DEST. choose Overview <Your Systems> Transport Tool d. in this guide we always refer to it also for SAP NetWeaver 7.1. see Additional Information Starting and Stopping SAP System Instances in the installation guide for your operating system platform and database at http://support. choose Overview Transport Routes .1 including Enhancement Package Note 1 for Banking Services from SAP 5. To adapt the transport routes.1 for Banking Services from SAP See the SAP NetWeaver Mobile Library 5.1.com/sltoolset System Provisioning Installation Option or the SAP Library at: Table 10: SAP Release and SAP Library Quick Link SAP Library Path (Continued) ● SAP NetWeaver 7.0 and 6. Select Change Configuration. after you have performed all follow–up activities.5 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. To adapt the transport parameters. Configure the domain controller in the Transport Management System (TMS) by using transaction STMS.1 to 7.1 for Banking Services from SAP 5.0 ● SAP NetWeaver 7.1.sap.0 and 6. you have to restart all instances of the renamed system.4 Changing the IGS Destination After renaming your ABAP system. 5.1 Library is the only available SAP Library for ABAP systems based on SAP NetWeaver 7. e.0.

5 ABAP on IBM i Follow-Up Activities CUSTOMER 63 .1 System Administration and Maintenance Information http://help.sap.sap.5 http://help. SAP Release and SAP Library Quick Link SAP Library Path (Continued) ● SAP NetWeaver Mobile 7.1 including Enhancement Administration Tasks Starting and Stopping AS ABAP and Package 1 http://help.3 Application Help Function-Oriented View Solution Life http://help.com/nw731 ● SAP NetWeaver 7.sap.com/nwmobile711 AS Java ● SAP NetWeaver 7.3 including Enhancement Package Based on SAP NetWeaver 1 http://help.sap.com/nw74 ● SAP NetWeaver 7.com/nw73/ Cycle Management Starting and Stopping SAP Systems ● SAP NetWeaver 7.com/nwmobile71 Technical Operations for SAP NetWeaver General ● SAP NetWeaver Mobile 7.4 http://help.sap.sap.com/nw75 System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to 7.

Depending on the context. SAP documentation is gender neutral. These hyperlinks are intended to serve as a hint about where to find related information.sap. does not apply in cases of willful misconduct or gross negligence of SAP. the third-person singular cannot be avoided or a gender-neutral noun does not exist.com/disclaimer). and SAP shall not be liable for errors or damages caused by the usage of the Code. SAP does not warrant the correctness and completeness of the Code given herein. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. All links are categorized for transparency (see: http://help. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet.sap.5 ABAP on IBM i 64 CUSTOMER Important Disclaimers and Legal Information . unless damages were caused by SAP intentionally or by SAP's gross negligence. the reader is addressed directly with "you". however.com/docs/DOC-42045 for information relating to SAP’s use of third party software with or within SAP NetWeaver. Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication. this document does not result in any direct or indirect contractual obligations of SAP. Furthermore.Important Disclaimers and Legal Information Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. Open Source Software and Third Party Components Please refer to https://scn. This is to ensure that the documentation remains comprehensible.1 to 7. it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. or a gender-neutral noun (such as "sales person" or "working days") is used. however. Gender-Neutral Language As far as possible.sap.com/docs/DOC-42044 for information respecting open source software components made available by SAP as part of SAP NetWeaver and any specific conditions that apply to your use of such open source software components. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP in particular disclaims any liability in relation to this document. If when referring to members of both sexes. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. Please refer to https://scn. This disclaimer. SAP reserves the right to use the masculine form of the noun and pronoun.

5 ABAP on IBM i Important Disclaimers and Legal Information CUSTOMER 65 .1 to 7.System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.

go. if any. National product specifications may vary. 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. The information contained herein may be changed without prior notice.epx for additional trademark information and notices. All other product and service names mentioned are the trademarks of their respective companies. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.sap. Please see http://www.com/registration/ contact. All rights reserved. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only. 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.html © 2017 SAP SE or an SAP affiliate company. without representation or warranty of any kind.sap. and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. Nothing herein should be construed as constituting an additional warranty. . 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.com/corporate-en/legal/copyright/ index.