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

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

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

1 Introduction 1. instance numbers of the instances on the SAP system. For a detailed list of supported SAP system products and releases. which is part of SL Toolset 1. 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. For information about supported operating system and database platforms. Any deviations from this documentation are at your own risk.com/pam .0 if your SAP system is installed with standard SAP tools according to the installation documentation available at http:// service.sap. see the Product Availability Matrix at http://support.1 and higher. 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 SP21.sap.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>). Database ID (<DBSID>). Be aware that additional consulting effort might be necessary.com/instguides . Caution You should only perform a system rename using the Software Provisioning Manager 1.0 SP21.1 to 7. see SAP Note 1619720 .5 ABAP on IBM i 6 CUSTOMER Introduction .1 About this Document This document explains how to rename an SAP system using Software Provisioning Manager 1. It is valid for SAP systems based on the application server ABAP of SAP NetWeaver 7.

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

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

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

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

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

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. UNIX. IBM DB2 for Linux. Make sure that you have the most recent version of each SAP Note. system copy. English ● SAP systems based on SAP NetWeaver Mobile 7. You can find all SAP Notes at http:// service. UNIX.7 SAP Notes for the System Rename Read the following SAP Notes before you start the system rename procedure.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.com/notes . but you cannot rename the schema of the SAP HANA database.1: http://help.sap.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.com/banking Banking Services from SAP <Release> Application Help SAP Library: SAP NetWeaver. More Information For more restrictions. 1.1 to 7.You can only rename the DBSID of the SAP HANA database.0 installation.sap. and Windows database.5 ABAP on IBM i 12 CUSTOMER Introduction . see SAP Note 1619720 .0 with Manager 1.sap. Table 3: SAP Notes for System Rename SAP Note Number Title Description 1680045 Release Note for Software Provisioning Software provisioning manager 1. These SAP Notes contain the most recent information on system rename as well as corrections to the relevant documentation. and Windows Rename of the database schema is not supported You cannot rename the schema of the IBM DB2 for Linux.

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

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.

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. you have to do the following: 1. ● Check the product version and platform coverage using the product availability matrix of SL Toolset in SAP Service Marketplace at: https://support.com/sltoolset Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7. Reinstall the additional application server instances on the system after the system rename. ● 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. ● If a required user does not exist.sap. If you have installed additional application server instances.com/sltoolset Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7.1 to 7. ○ Host names ● SAP systems based on SAP NetWeaver AS for ABAP 7.sap.sap.2 Planning This section includes the planning steps that you have to perform when you want to rename an SAP system. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. ● Users that already exist in the SAP system are not deleted. it is created during the system rename procedure. They are available after the rename of your system.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.1 and Higher Installation Guides by Database <Database> <OS Platform> ).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.5 ABAP on IBM i Planning CUSTOMER 15 . Delete the additional application server instances manually [page 17] from the system before 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.

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

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

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

a. 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. 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.1 to 7. b. Next Steps Distributed systems only: After the file system has been renamed on the global host. To check the kernel library. you must stop all jobs which have locked the database library using option 4 (End job). not on the global host: 1. you must adjust the link of the remote host to the global directories of the SAPGLOBALHOST. Results Now most likely no objects are locking any object of the SAP system anymore and the installer will run without any locking problem. You must enter the following commands on the remote host only.400/<SAPGLOBALHOST>/sapmnt/<Target_SAPSID>') NEWLNK('/ sapmnt/<Current_Remote_SAPSID>') 3. 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. To check the database library. 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.5 ABAP on IBM i Preparation CUSTOMER 19 . ADDLNK OBJ('/QFileSvr. Change the link /sapmnt/<SAPSID>: 1. Note The kernel library of an SAP system is normally locked when someone is logged on as <SAPSID>ADM. you must stop all jobs which have locked the kernel library using option 4 (End job). RMVLNK '/sapmnt/<Current_Remote_SAPSID>' 2.

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

enter option 5 (Work with configuration descriptions) for the port and choose ENTER . To set up the description line. On the following screen. On the Work with Communication Resources screen.1 to 7.5 ABAP on IBM i Preparation CUSTOMER 21 . A subnet mask is a mask used to divide a single network address into multiple logical networks.Procedure Note An IP address is a unique address in a TCP/IP network for a particular IBM i. enter the command chgneta and prompt F4 . 1. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. To change the name of the computer. 2. enter option 1 (Create) to enter the description gigaline or ethline and choose ENTER . enter the line speed and duplex and then press F10 and page down two screens. enter the command WRKHDWRSC TYPE(*CMN) and proceed as follows: 1. On the Work with Configurations Description screen. 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 Create Line Desc (Ethernet) (CRTLINETH) screen.5 ABAP on IBM i 22 CUSTOMER Preparation . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to 7. make sure the autocreate controller is set to *yes.

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

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

for example.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.5 ABAP on IBM i Preparation CUSTOMER 27 . 3. as0008 for the host in the example given above. 2.400/<Host_Name>' Your host name should be displayed under Object link. 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. 4.After installing the SAP system kernel. enter the following command and press F4 : CHGTCPDMN 3. see the IBM documentation in the IBM Knowledge Center. To do this. Note The *Local database name must match the TCP/IP host name for the SAP system to work properly. For more information about TCP/IP configuration.1 to 7. Result The IBM i is integrated into your TCP/IP network. Log on to your database host as user QSECOFR. check the TCP/IP connection again with the command: WRKLNK '/QFileSvr. Search for the contents of HOSTNAME. enter the following command: WRKRDBDIRE 5. Depending on the outcome. Procedure 1. This is your TCP/IP host name. you have to check if the entry remote location equals *Local exists. 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>.

To do this. Note The signature of media is checked automatically by the installer during the Define Parameters phase while processing the Media Browser screens.5 ABAP on IBM i 28 CUSTOMER Preparation .7 Preparing the System Rename Media This section describes how to prepare the media required for the system rename procedure. Download the latest version of the Software Provisioning Manager 1. As of now the installer only accepts media whose signature has been checked. ○ 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>).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.sap.1 to 7.1 Downloading and Extracting the Software Provisioning Manager Archive You must always download and extract the Software Provisioning Manager 1. Afterwards go to the next step and add the required RDB name.SAR from: https://launchpad. Related Information Downloading and Extracting the Software Provisioning Manager Archive [page 28] 3.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>. Procedure 1.0 archive from the SAP Software Download Center because you must use the latest version. See also the description of this new security feature in SAP Note 2393060 .support.7. 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. make sure there is an entry for it in the RDB directory. you have to add one with the correct name <TCP_Host_Name>. If you are planning to use an independent ASP. ○ If an entry for RDB name does not exist. 3.

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

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

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

1 to 7. The following requirement applies: ● The IBM i installation user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR. you need to use the user QSECOFR because the liveCache client software has to be installed by this special user. 9. For other installations. we recommended that you create user SAPIUSR.5 ABAP on IBM i 32 CUSTOMER Preparation . 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:\<SAPSID>\<Media_Name> /E or xcopy C:\tmp\download\<Unpack_Directory> X:\<SAPSID>\<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. Note For advanced users only: Instead of copying the complete media you also can copy only dedicated subdirectories. Note This is different to other installations on IBM i. 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. For each required media. ● SCM Only: The IBM i installation user profile must be the user QSECOFR.9 Preparing an IBM i User Profile For running the installer you must create a user account on the IBM i host. create a subdirectory and copy the required media. 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. However for SCM. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 10.

1 to 7. you can revert the user profile QSECOFR back to the old values. use the following command: CHGUSRPRF USRPRF(SAPIUSR) GRPPRF(SAPINST) Now the user SAPINST can also be used as a group by the installer. Do not leave this variable empty. To do this. 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.Procedure Note The user name SAPIUSR and the password SAP are used as examples in the procedures. If you do not want to delete this user for any reason.5 ABAP on IBM i Preparation CUSTOMER 33 . a group SAPINST is created generically on all platforms and is used for the installation of the SAP 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. 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. 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. In the current release. End of 'Software Component': SAP SCM Caution You should not set the system variable QIBM_PASE_CCSID. we recommended that you create the user SAPINST on IBM i to install the SAP system. you must delete this user. 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. If the user SAPINST already exists on your system. 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.

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

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

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

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

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('. If your X server for Microsoft Windows or Linux is already configured and running. you can use VNC. The filled-out evaluation form is then sent to SAP using HTTPS. When VNC is prepared as described in the IBM i documentation. If this port cannot be used. allows you to set the DISPLAY variable. Note For advanced users only: PASE. all changes of the environment variables done by the command export are reverted. If this works. Note When you leave your Qp2Term session. see the IBM i documentation./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 do not have to use the remote installer GUI separately. If this port cannot be used. If this port cannot be used. you can assign a free port number by executing sapinst with the following command line parameter: SAPINST_HTTP_PORT=<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. VNC also offers a GUI by using IBM i tools. For more information about VNC.5 ABAP on IBM i 38 CUSTOMER System Rename Procedure . the installer GUI is directly started on your Windows PC after starting the installer on IBM i. Note For advanced users only: Beside using an XWindows Server and the DISPLAY variable. We do not recommend that you start the installer using the DISPLAY variable as there is no support available.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. 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. you can try to direct the graphical output of the installer to an XWindow by setting the DISPLAY variable. which is similar to AIX.

we address them as “installer GUI”. In cases where both GUIs behave the same way. The filled-out evaluation form is then sent to SAP using HTTPS. see Useful Information About the Installer [page 45].5 ABAP on IBM i System Rename Procedure CUSTOMER 39 .“SL Common GUI” for short ● The “classic” Java-based GUI with a CUI client and server .1 to 7. You then have to start the sapinst executable with the command line option SAPINST_SLP_MODE=false. Prerequisites For more information. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. see Prerequisites for Running the Installer [page 36].“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. 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. For more information. Context Software Provisioning Manager (the “installer” for short) offers two GUIs: ● The new web browser-based “SL Common GUI of the Software Provisioning Manager” ./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. Example CD DIR('<Path_To_Unpack_Directory>') CALL PGM(QP2TERM) PARM('.3 Running the Installer This section describes how to run the installer to perform the system rename . If this port cannot be used. you also have to perform the steps described in sections Configuring TCP/IP [page 20] and Adjusting the Relational Database Name [page 27]. 4.

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

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

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

6. Then a dialog opens with the available help text.5 ABAP on IBM i System Rename Procedure CUSTOMER 43 . choose F1 . 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. After you have entered all requested input parameters. Follow the instructions in the installer input screens and enter the required parameters. choose either F1 or the HELP tab. the installer displays the Parameter Summary screen. 9. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Note To find more information on each parameter during the Define Parameters phase. The installer starts the rename procedure and displays its progress on the Task Progress screen. To start the execution.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. See also the description of this new security feature in SAP Note 2393060 . position the cursor on the required parameter input field : ○ If you use the SL Common GUI. 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. ○ If you use the Java SDT GUI. 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 . If required. skip this option. 7. choose Next. Caution The signature of media is checked automatically during the Define Parameters phase while processing the Media Browser screens.1 to 7. 8. 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. you can revise the parameters before starting the system rename procedure. Choose Next. Then the available help text is displayed in the HELP tab. This screen shows both the parameters that you entered and those that the installer set by default.

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

open a web browser supported by the SL Common GUI on any device and run the URL from there. If you have a supported web browser installed on the host where you run the installer.1 Useful Information About the Installer This section contains some useful technical background information about the installer and the installer GUI.“SL Common GUI” for short ○ The “classic” Java-based GUI with a CUI client and server . For more information about supported web browsers see Prerequisites for Running the Installer [page 36].also known as SAPUI5 .1 to 7.4.which is part of Software Provisioning Manager .5 ABAP on IBM i System Rename Procedure CUSTOMER 45 . you can start the SL Common GUI directly from this URL. The benefits of this new user interface technology for the user are: ○ Zero foot print. The SL Common GUI connects the web browser on a client with the sapinst executable . since only a web browser is required on the client ○ New controls and functionality.running on the installation host using the standard protocol HTTPS. view logs in web browser. Otherwise. 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.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.4 Additional Information About the Installer The following sections provide additional information about the installer. ● Software Provisioning Manager (the installer) offers two GUIs: ○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” .“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 . System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. for example. 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.

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

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

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

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

Instead. 4. Continue with the existing one The installer continues the interrupted system rename from the point of fail­ ure. Prerequisites ● The remote host meets the prerequisites for starting the installer as described in Prerequisites for Running the Installer [page 36]. it moves the content of the old installer directory and all installer-specific files to a backup directory. even if these files and folders are owned by other users. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. 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.1 to 7. Note This section is only valid if you use the Java SDT GUI. Afterwards. you can no longer continue the old option. If there are any processes currently running on these files and folders. they might no longer function properly. Table 9: Alternative Behavior Perform a new run The installer does not continue the interrupted system rename option. Caution The installer moves all the files and folders to a new log directory.5 ABAP on IBM i 50 CUSTOMER System Rename Procedure .4.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. you started the sapinst executable with command line option SAPINST_SLP_MODE=false. That is.

For more information. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. you can specify another operating system user for authentication purposes. see Preparing the System Rename Media [page 28]. and the installer GUI runs on the local host. 2. 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. 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. In this case. 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. Caution In this section. Context You use this procedure to process the installer on a remote host. and “remote host” refers to the IBM i host where the SAP system is installed. You have to confirm that the user is a trusted one. see SAP Note 1170809 . 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. 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>). Procedure 1. The installer GUI connects using a secure SSL connection to the installer. For more information. “local host” refers to the Windows installation host. the installer runs on the remote host. see Preparing an IBM i User Profile [page 32]. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. For more information. see SAP Note 1745524 . Log on to your remote host (IBM i) and enter the command: PING RMTSYS('<Local_Host>') 2. For more information. ● Both computers are in the same network and can ping each other.5 ABAP on IBM i System Rename Procedure CUSTOMER 51 . The local host is the host from which you control the installation with the installer GUI. Log on to the remote host as the installation user with similar authorization rights to QSECOFR. Make the installation media available on your remote host.1 to 7. To test this: 1.

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

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

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

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

Note The following procedure applies for Windows Server 2012 and might be different when using another Windows operating system. choose Advanced.1 to 7. b.exe -accessible -host <Remote_Host> - port <Port_Number_Gui_Server_To_Gui_Client> You perform a remote installation as follows: a.exe -accessible -host <Remote_Host> - port <Port_Number_Gui_Server_To_Gui_Client> 4. 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('. Select a color scheme from the Color scheme drop-down box. 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. c.5 ABAP on IBM i 56 CUSTOMER System Rename Procedure .6 Troubleshooting with the Installer This section tells you how to proceed when errors occur while the installer is running. 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. select Window Color and Appearance. 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. 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. Select Adjust font size (DPI) and choose Larger scale (120 DPI). ● Running the Installer in Accessibility Mode a. choose Custom DPI. To define your own color schemes. a.4./sapinst') b. Context If an error occurs. In the right-hand pane. Right click on your Windows desktop and choose Personalize.

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

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

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

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

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

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

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

SAP in particular disclaims any liability in relation to this document. 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.sap.com/docs/DOC-42045 for information relating to SAP’s use of third party software with or within SAP NetWeaver. All links are categorized for transparency (see: http://help. Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. and SAP shall not be liable for errors or damages caused by the usage of the Code. the third-person singular cannot be avoided or a gender-neutral noun does not exist. Please refer to https://scn. This is to ensure that the documentation remains comprehensible.com/disclaimer). SAP documentation is gender neutral. This disclaimer. Depending on the context. 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.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. does not apply in cases of willful misconduct or gross negligence of SAP. Gender-Neutral Language As far as possible. SAP reserves the right to use the masculine form of the noun and pronoun. SAP does not warrant the correctness and completeness of the Code given herein. unless damages were caused by SAP intentionally or by SAP's gross negligence.5 ABAP on IBM i 64 CUSTOMER Important Disclaimers and Legal Information . If when referring to members of both sexes. however. the reader is addressed directly with "you". it is in no way intended to be a binding guideline on how to ensure accessibility of software products.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. These hyperlinks are intended to serve as a hint about where to find related information. however. 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. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Open Source Software and Third Party Components Please refer to https://scn.1 to 7. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding.sap.sap. Furthermore.

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

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