You are on page 1of 66

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

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

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

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

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

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

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

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

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

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

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

1 to 7. ○ 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.5 ABAP on IBM i 14 CUSTOMER Introduction .

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

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

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

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

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

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

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

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

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

The following screen appears:

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

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

The following screen appears:

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

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

The following screen appears:

Note
It is important that you enclose your host name entry in single quotation marks. If you do not, the
IBM i interprets the characters as uppercase characters.

If you have one or more remote name servers, you need to define the IP address here. Note that the Host name
server priority must be set to *LOCAL.

Testing the TCP/IP Connection

Before proceeding with the SAP installation (that is, the installation of the executable programs), check that
this TCP/IP connection has been set up correctly. To do so, enter the command ping (Network Connection)
specifying your own system as Remote system. Do this twice, once specifying only <Host_Name>, and once
<Host_Name>.<Domain_Name>.

Example
In this example we assume that the host name is as0008 and the domain name is wdf.sap.corp. In this
case, your entries are the following:

● ping 'as0008'

● ping 'as0008.wdf.sap.corp'

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

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

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

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

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

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

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

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

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

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.5 ABAP on IBM i System Rename Procedure CUSTOMER 35 . The system parameters are adapted offline. Make sure that no object of the to be renamed SAP system is locked. see Perfoming IBM i-Specific Preparation Steps [page 18]. Note The installer is not able to change objects that are locked.1 to 7. For more information.1 System Rename Procedure Checklist This section includes the renaming steps that you have to perform for the following options: ● Standard system ● Distributed system The installer adapts the SAP system on an operating system level. the database is always up and running. the installer does not have to rename or change the database library and the journal receiver library.4 System Rename Procedure 4.20 kernel or higher. The installer automatically starts the following instances during the system rename: ● Database Note For IBM i. 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]. which are using the SAP NetWeaver 7.

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

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

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

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

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

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

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

You can get this number from the global host where the SCS or ASCS instance is already installed using following command: DSPUSRPRF USRPRF(<SAPSID>ADM) or CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/id' '<SAPSID>ADM') The SCS or ASCS installation is the installation which initially determinates the UID of the user <SAPSID>ADM.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. After you have entered all requested input parameters. See also the description of this new security feature in SAP Note 2393060 . Then a dialog opens with the available help text. If required. Caution The signature of media is checked automatically during the Define Parameters phase while processing the Media Browser screens. 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. skip this option. 8. Choose Next. choose F1 .1 to 7. 9. 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. To start the execution. choose either F1 or the HELP tab. position the cursor on the required parameter input field : ○ If you use the SL Common GUI. This screen shows both the parameters that you entered and those that the installer set by default. System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7. Follow the instructions in the installer input screens and enter the required parameters. Then the available help text is displayed in the HELP tab. 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 . 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.5 ABAP on IBM i System Rename Procedure CUSTOMER 43 . ○ If you use the Java SDT GUI. 7. 6. you can revise the parameters before starting the system rename procedure. the installer displays the Parameter Summary screen. choose Next.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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