This document explains how to rename an SAP system using Software Provisioning Manager 1.0 SP21, which is part of SL Toolset 1.0 SP21. It is valid for SAP systems based on the application server Java of SAP

NetWeaver 7.1 and higher. For a detailed list of supported SAP system products and releases, see SAP Note

1619720 . For information about supported operating system and database platforms, see the Product

Availability Matrix at http://support.sap.com/pam .

Caution

You should only perform a system rename using the Software Provisioning Manager 1.0 if your SAP system is installed with standard SAP tools according to the installation documentation available at http:// service.sap.com/instguides .

Any deviations from this documentation are at your own risk. Be aware that additional consulting effort might be necessary.

Related Information

Use Cases of System Rename [page 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 13]

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 (

), Database ID (

<DBSID>

), instance numbers of the instances on the SAP system, host names

You can adapt one or more of the following parameters of an SAP system using the system rename procedure:

●

SAP system ID (

)

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

●

Database ID (

<DBSID>

)

●

Instance numbers of the instances on the SAP system

●

Host names

You can rename the following SAP systems:

●

Systems installed by using the standard SAP tools.

●

Systems copied by using classical system copy (R3load/Jload or DB-specific procedure).

●

Systems created by using backup or restore with procedures offered by Microsoft Windows

●

Systems created by using SAP Landscape Management

●

Cloned systems (virtual to virtual, virtual to physical, or physical to virtual)

Note

For production systems, the rename procedure should only be performed by experienced system administrators or consultants and should be tested beforehand – especially for the conversion of logic system names, the corresponding aspects outlined in SAP Note 121163 have to be considered.

More Information

For more information about offerings, methods, use cases and technical details of the system rename procedure, see http://scn.sap.com/docs/DOC-32851 .

1.3 About Software Provisioning Manager

Software Provisioning Manager 1.0 is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst. Before you run it, we recommend that you always download the latest version of Software Provisioning Manager 1.0. Software Provisioning Manager 1.0 is part of the Software

Logistics Toolset 1.0 (“SL Toolset” for short). This way, you automatically get the latest fixes and supported processes. For more information about Software Provisioning Manager as well as products and releases supported by it, see SAP Note 1680045 and http://scn.sap.com/docs/DOC-30236 . “SAPinst” has therefore been renamed to “Software Provisioning Manager 1.0” in this documentation. However, the term

“SAPinst” is still used in:

●

Texts and screen elements in the Software Provisioning Manager GUI

●

Naming of executables, for example sapinst.exe

In the following, we generally refer to Software Provisioning Manager 1.0 as the “installer”. We only use the term “Software Provisioning Manager 1.0” if this is required for technical reasons.

Related Information

Preparing the System Rename Media [page 31]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

C U S T O M E R

1.4 Naming Conventions

●

“usage type”, “technical usage”, and “product instance”

As of Software Provisioning Manager 1.0 SP07 (SL Toolset 1.0 SP12), the term “product instance” replaces the terms “ usage type” and “technical usage” for SAP systems based on SAP NetWeaver 7.3 including enhancement package 1 and higher. For more information, see SAP Note 1877731 . Note that there is no terminology change for older releases and all mentioned terms can be used as synonyms. As this guide is a generic document, the currently used terms remain but only “product instance” is going to be used from now on when referring to SAP NetWeaver 7.3 EHP1 and higher.

For more information, see

New Features [page 8]

●

“SAP system” refers to “SAP NetWeaver system” or “SAP system based on SAP NetWeaver”.

●

Only valid for Microsoft Failover Clustering : As of Windows Server 2008 the cluster feature is called

Failover Clustering

. For practical reasons we are continuing to use the previous terminology

Microsoft

Cluster Service

and abbreviation

MSCS

in some sections of this guide and the corresponding installation documentation of your release.

1.5 New Features

The table below provides an overview of the new features in Software Provisioning Manager.

Make sure that you also read the release notes for your SAP product at http://help.sap.com

Area> <Product> <Release>

What’s New – Release Notes

Table 2:

Feature

Media Signature

Check

<Product

Description

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media

Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

For more information, see

Preparing the System Rename Media

[page 31]

and Running the Installer [page 38] .

Availability

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

Feature

Support of Oracle

Database Vault

Description

Caution

Although Oracle Database Vault is already available in the in staller and documented in this guide, it is not yet released to customers until further notice. For more information, see the

Current Restrictions

section in SAP Note 1680045 .

Availability

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

Oracle Database Vault 12c has been certified for SAP products that are based on SAP NetWeaver technology.

You can now rename an SAP system with Oracle Database 12c and configure Oracle Database Vault in the database of the target system.

For more information, see

Implementing Oracle Database Vault with the Installer [page 64]

Support of Oracle

12.2

Software Provisioning Manager (the “installer”) now supports system rename for SAP systems with Oracle 12.2.

Software Provisioning Manager

1.0 SP21 (SL Toolset 1.0 SP21)

SL Common GUI with SAPINST 7.49

With the new installer framework version SAPINST 7.49, you can now use the new SAPUI5-based graphical user interface (GUI)

“SL Common GUI”. For more information, see Useful Information

About the Installer [page 43]

, Running the Installer [page 38] ,

and SAP Note 2336746 .

Software Provisioning Manager

1.0 SP20 (SL Toolset 1.0 SP20)

Verification of Integ rity of Data Units in

Software Provision ing Manager

The integrity of data units extracted from the Software Provision ing Manager archive is verified. For more information, see

Down loading and Extracting the Software Provisioning Manager Ar chive [page 31] .

Software Provisioning Manager

1.0 SP19 (SL Toolset 1.0 SP19)

In addition, check SAP Note 1680045 whether additional in formation is available.

System Provision ing for SAP

NetWeaver 7.5 and

SAP NetWeaver 7.5based Products

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP NetWeaver 7.5 release.

The Dual Stack option, which integrates an AS ABAP and AS Java in a single system (common System ID

, common startup framework, common database), is no longer supported in

SAP systems based on SAP NetWeaver 7.5.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

After upgrading to SAP NetWeaver 7.5 PI, you first have to split the still existing dual stack-system before you can use SAP

NetWeaver 7.5 PI productively.

For more information, see the

Upgrade Master Guide - SAP Net

Weaver 7.5

at: http://help.sap.com/nw75

Installation and

Upgrade

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

C U S T O M E R

Feature Description Availability

System Provision ing for SAP Solution

Manager 7.2

All system provisioning tasks (installation, system copy, system rename) are available for the new SAP Solution Manager 7.2 re lease. Compared to previous SAP Solution Manager releases,

SAP Solution Manager 7.2 is no longer provided as a classical dual-stack system (ABAP system with Java Add-in), but consists of a separate ABAP and Java stack.

Software Provisioning Manager

1.0 SP09 (SL Toolset 1.0 SP15)

Usage Type Library

Deprecation for

SAP Systems Based on SAP NetWeaver

7.3 EHP1 and Higher

Software Provisioning Manager 1.0 no longer uses the “Usage

Types” definitions in its business logic for SAP systems based on

SAP NetWeaver 7.3 EHP1 and higher. This is done to unify model ing and terminology across all SAP tools used during the plan ning, installation and maintenance activities. The “Product In stance” definition replaces “Usage Types” regarding product modeling. For more information, see SAP Notes 1970349 and

1877731 .

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Feedback Evalua tion Form

SAP SE’s aim is to provide fast and efficient procedures. To eval uate the procedure you just carried out, we need information gen erated by the tool during process execution and your experience with the tool itself. A new evaluation form contains a simple ques tionnaire and XML data generated during the procedure.

Software Provisioning Manager

1.0 SP07 (SL Toolset 1.0 SP12)

Port 4239 is used for displaying the feedback evaluation form.

For more information, see

Prerequisites for Running the Installer

[page 37] .

Option

Verify Signed

Media

The digital signature ensures that the signatory of a digital docu ment can be identified unambiguously and signatory’s name is documented together with the signed document, the date, and the time.

For more information, see SAP Note 1979965 .

Software Provisioning Manager

1.0 SP06 (SL Toolset 1.0 SP11)

1.6 Constraints

●

System Rename is only supported for SAP systems based on SAP NetWeaver 7.0 and higher: SAP ERP

6.0 and higher, SAP CRM 7.0 and higher, SAP SRM 7.0 and higher, SAP SCM 7.0 and higher.

●

System Rename is supported for SAP Web Dispatcher and SAP Gateway of systems based on SAP

NetWeaver 7.0 and higher. For more information, see the documentations

Installation Guide - Installation of SAP Web Dispatcher for SAP Systems Based on SAP NetWeaver 7.0 and Higher on

<OS>

and

Installation

Guide - Installation of a Standalone SAP Gateway Instance for SAP Systems Based on SAP NetWeaver 7.1 to

7.5 on

<OS>

at http://support.sap.com/sltoolset

System Provisioning Installation Option

●

System rename is not supported for the Diagnostics Agent.

For more information and guidance see the

Diagnostics Agent Maintenance Procedures

article at http:// wiki.scn.sap.com/wiki/x/n4efFg .

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

●

SAP System ID

Make sure that your SAP system ID:

○

Is unique throughout your organization. Do not use an existing

○

Consists of exactly three alphanumeric characters

○

Contains only uppercase letters

○

Has a letter for the first character

○

Does not include any of the reserved IDs listed in SAP Note 1979280 .

●

Database ID

<DBSID>

The

<DBSID>

identifies the database instance. It can be the same as the

Note

MS SQL Server only :

The

<DBSID>

must always be the same as the

Make sure that your database ID:

○

Is unique throughout your organization

○

Consists of exactly three alphanumeric characters

○

Contains only uppercase letters

○

Has a letter for the first character

○

Does not include any of the reserved IDs listed in SAP Note 1979280 .

●

The rename of a high availability system is not supported.

●

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

Oracle Database

●

System Rename is only partially supported for ASM database installations

System Rename does only partly work for an Automatic Storage Management (ASM) installation of the

Oracle database. You cannot use system rename to change the

or the

<DBSID>

– in addition, using System Rename for changing only the host name, the instance name, or the instance number for an

ASM installation of the Oracle database only works as of SL Toolset 1.0 SP11 (Software Provisioning

Manager 1.0 SP06). This is because there is a different

ORACLE_HOME

and the ora <dbsid>

user is missing in the ASM environment.

●

Renaming the database schema is not supported

If you want to rename the database schema, perform a system copy.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

C U S T O M E R

SAP MaxDB

System Rename is not supported for SAP MaxDB versions lower than 7.8

If you try to rename an SAP system with an SAP MaxDB version lower than 7.8, several errors are reported.

There is no workaround to overcome this restriction. Instead, you first have to upgrade to SAP MaxDB version

7.8 or 7.9. For more information about the upgrade, see SAP Notes 1353266 or 1492467 , depending on your SAP MaxDB target release.

SAP HANA

Rename of the database schema not supported

You can only rename the DBSID of the SAP HANA database, but you cannot rename the schema of the SAP

HANA database.

IBM DB2 for Linux, UNIX, 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.

More Information

For more restrictions, see SAP Note 1619720 .

1.7 SAP Notes for the System Rename

Read the following SAP Notes before you start the system rename procedure. These SAP Notes contain the most recent information on system rename as well as corrections to the relevant documentation. Make sure that you have the most recent version of each SAP Note. You can find all SAP Notes at http:// service.sap.com/notes .

Table 3: SAP Notes for System Rename

SAP Note Number Title Description

1680045

1619720

Release Note for Software Provisioning

Manager 1.0

Software provisioning manager 1.0 with installation, system copy, system re name and dual-stack split for SAP

NetWeaver-based systems

System Rename for SAP Systems based on SAP NetWeaver

Problems discovered after the publica tion of the System Rename guide

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

1.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 Composition Environment 7.1: http://help.sap.com/nwce71

Application Help SAP Library: English

●

SAP systems based on SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1: http://help.sap.com/nwce71

Application Help SAP Library: English

●

SAP systems based on SAP NetWeaver Composition Environment 7.2: http://help.sap.com/nwce72

Application Help SAP Library: English

●

SAP systems based on SAP NetWeaver 7.3: http://help.sap.com/nw73

Application Help Function-Oriented View: English

●

SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1: http://help.sap.com/nw731

Application Help Function-Oriented View: English

●

SAP systems based on SAP NetWeaver 7.4: http://help.sap.com/nw74

Application Help Function-Oriented View: English

●

SAP systems based on SAP NetWeaver 7.5: http://help.sap.com/nw75

Application Help Function-Oriented View: English

1.9 How to Use this Guide

This documentation comprises the description of the system rename procedure and system rename-specific steps.

Context

For general installation or system copy-specific information, see the installation or system copy guides:

●

The “ installation guide” for your operating system platform and database at https://help.sap.com/ sltoolset

Area System Provisioning Guide for Installation of Systems Based on SAP NetWeaver 7.1 and Higher Installation Guides by Database

In the following, we refer to this documentation as “installation guide”.

●

The “system copy guide” for your operating system platform at https://help.sap.com/sltoolset

Area

System Provisioning Guide for System Copy for Systems Based on SAP NetWeaver 7.1 & Higher

<OS

Platform>

In the following, we refer to this documentation as “system copy guide”.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

C U S T O M E R

Procedure

1. You decide on the system parameters you want to change in the rename process.

For more information, see

Use Cases of System Rename [page 6]

2. You follow the steps in each phase:

○

Planning [page 15]

○

Preparation [page 17]

○

Renaming [page 36]

○

Follow-Up Activities [page 55]

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Introduction

2 Planning

This section includes the planning steps that you have to perform when you want to rename an SAP system.

●

Check the product version and platform coverage using the product availability matrix of

SL Toolset

SAP Service Marketplace at: https://support.sap.com/pam

●

The system rename procedure is valid for the following environments:

○

ABAP

○

Java

○

Dual-stack (ABAP and Java)

●

You can perform the system rename on both central and distributed systems.

●

Make sure that you check requirements and restrictions for the SAP system parameters that you want to rename (see section

Basic Installation Parameters

in the installation guide for your operating system platform and database at https://support.sap.com/sltoolset

Area System Provisioning Guide for

Installation of Systems Based on SAP NetWeaver 7.1 and Higher Installation Guides by Database

○

SAP system ID

○

Database ID

○

Instance numbers of the instances on the SAP system

With the system rename procedure, you can rename the following instances:

○

Database instance

○

Primary application server instance

○

Central Services instance (SCS instance)

○

Enqueue Replication Server

Note

You cannot use the installer to rename additional application server instances.

If you have installed additional application server instances, you have to do the following:

Delete the additional application server instances manually [page 18] from the system

before the system rename.

2. Reinstall the additional application server instances on the system after the system rename.

○

Host names

●

Users that already exist in the SAP system are not deleted. They are available after the rename of your system.

●

If a required user does not exist, it is created during the system rename procedure.

●

Windows Domain Organizational Units

You can choose the organizational units (OUs) within the Windows domain where you want to create the

SAP system accounts.

By default, the installer creates the domain users

SAPService <SAPSID>

<SAPSID> adm

, and the domain group

SAP_ <SAPSID> _Globaladmin

in the domain Users container. Here you can specify an optional organizational unit where the installer creates these domain users and group. The user who performs the installation needs read and write permissions to this organizational unit.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Planning

C U S T O M E R

The OU feature is only available when you select

Custom mode

in SWPM and choose

Use Domain of current user

. For more information, see SAP Note 2247673 .

●

Oracle Database only: If your source system to be renamed has Oracle Database Vault, make sure that

you have read section Implementing Oracle Database Vault with the Installer [page 64] .

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Planning

3 Preparation

3.1 Preparation Checklist

This section includes the preparation steps that you have to perform when you want to rename an SAP system.

1. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. If you do not want the installer to create operating system users and groups automatically, you can choose to create them before running the system rename procedure.

For more information, see

Maintaining Users and Groups [page 17]

2. If additional application server instances are installed on your system, delete them before you start the rename procedure.

For more information, see

Deleting Additional Application Server Instances [page 18]

3. Perform the preparation steps required for your database.

For more information, see

Database-Specific Preparation [page 19]

4. Make sure that your user has the required authorization for running the installer to perform the system rename.

For more information, see

Required User Authorization for Running the Installer [page 26] .

5. If you want to change the domain during system rename, perform the steps described in Requirements

[page 28] .

6. Prepare the media required for the system rename.

For more information, see

Preparing the System Rename Media [page 31]

7. You make the global file system with the renamed

available on the instance hosts of the system that you plan to rename.

For more information, see

Preparing the File System [page 35] .

8. We strongly recommend that you perform a full system backup before starting the rename procedure, if you do not have other means to restore the original system in case of problems.

3.2 Maintaining Users and Groups

The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. If you do not want the installer to create operating system users and groups automatically, you can choose to create them before running the system rename procedure.

Context

This step is only mandatory if you want to use global accounts that are configured on separate hosts.

In all other cases, this step is optional.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

Procedure

1. Log on to your SAP system as described in Running the Installer [page 38] .

2. On the

Welcome

screen, choose

System Rename Preparations Operating System Users and

Groups

3. Follow the instructions in the input screens and specify the target system IDs (SAP system ID, Database

ID) when creating users and groups.

3.3 Deleting Additional Application Server Instances

The system rename procedure does not implicate additional application server instances. Therefore, if additional application server instances are installed on your system, delete them before you start the rename procedure, and reinstall additional application server instances as required after the system rename.

Prerequisites

●

You have installed your SAP system with standard SAP tools according to the installation documentation.

●

You have made the media available that you used for installing the system on the additional application server instance host that you want to delete.

Context

Note

You cannot delete an additional application server instance remotely. You have to run the tool to delete them locally on each additional application server instance host.

All file systems and subdirectories of the selected additional application server instance are deleted during the uninstall process.

The uninstall process is designed to remove as much of the additional application server instance as possible.

If an item cannot be removed, a message informs you that you have to remove this item manually. As soon as you confirm the message, the uninstall process continues.

Procedure

1. Start the tool as described in

Running the Installer [page 38] .

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

2. On the

Welcome

screen, choose

<SAP_Product>

Software Life-Cycle Options Uninstall

3. Follow the instructions in the input dialogs to delete an additional application server instance.

Note

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

4. When you have finished, delete the local user group

SAP_ <SAPSID> _LocalAdmin

manually as follows: a. Choose

Start Programs Administrative Tools Computer Management

b. Choose

Local Users

and

Groups Groups

c. Right-click the local group

SAP_ <SAPSID> _LocalAdmin

and choose

Delete

3.4 Database-Specific Preparation

You have to do some preparation steps in the database of the system you want to rename.

Make sure you have completed the preparation steps for your database as described in the relevant section below.

Performing Preparation Steps for IBM DB2 for Linux, UNIX, and Windows [page 19]

Performing IBM DB2 for z/OS – Specific Preparation Steps [page 21]

Performing Oracle-Specific Preparation Steps [page 23]

Performing Microsoft SQL Server-Specific Preparation Steps [page 24]

Performing SAP ASE -Specific Preparation Steps [page 25]

Performing SAP MaxDB-Specific Preparation Steps [page 25]

Performing SAP HANA Database-Specific Preparation Steps [page 26]

3.4.1 Performing Preparation Steps for IBM DB2 for Linux,

UNIX, and Windows

This section describes prerequisites and preparation steps that you have to perform for IBM DB2 for Linux,

UNIX, and Windows before starting the system rename procedure.

Prerequisites

●

The database is up and running.

●

The patch level of the brdb6brt

tool is patch level 32 or higher.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

If tool brdb6brt

does not exist within the

\sapmnt\ <SAPSID> \exe

directory, download and install it as described in SAP Note 511323 . Information about the latest patches of tool brdb6brt

you can find in

SAP Note 867914 .

●

IBM DB2 for Linux, UNIX, and Windows V10.1 and Higher only:

Make sure that your

<sapsid> adm

user has execute permission for function sysproc.admin_get_storage_paths

by running the following command on your source system as user db2 <dbsid>

db2 "grant execute on specific function sysproc.admin_get_storage_paths to user

<sapsid>adm"

●

The version of SAP Host Agent must be 7.21 PL 1 or higher.

Procedure

1. If the user that you use to run the tool does not have the required authorizations to create users and groups, you must create all required groups and users before you start the system rename process.

2. Create the relocate.template

file as described below. This file is required in the tool dialog phase. All actions have to be performed on the database host of your SAP source system landscape.

a. Log on as an administrator on the database host of your source system.

b. Create the directory sapdbctrl-config

under a temporary directory, for example

<drive> :\temp

This does not apply if the directory already exists.

Note

If directory

\temp

does not exist, you have to create it before you perform the steps listed below.>

Proceed as follows:

1. Execute

cd <drive>:\temp

2. Execute

md .\sapdbctrl-config

c. Execute

cd <drive>:\program files\sap\hostctrl\exe

d. Execute

saphostctrl.exe -function PrepareDatabaseCopy -dbname <DBSID> -dbtype db6 -dbconfdir <drive>:\temp\sapdbctrl-config -dbuser <sid>adm -dbpass

<password of <sid>adm> -copymethod Offline

The system creates the relocate.template

file in directory

<drive> :\temp\sapdbctrlconfig

Check if the file relocate.template

contains one or more entries for

CONT_PATH

STORAGE_PATH

. If not you must not start the system rename procedure.

This is an example of the files created in the sapdbctrl-config

directory:

C:\temp\sapdbctrl-config > dir

Volume in drive C has no label.

Volume Serial Number is <number>

Directory of C:\temp\sapdbctrl-config

05/31/2012 09:07 AM <DIR>

05/21/2012 01:52 PM 2495 db2ph5.cfg

05/21/2012 01:52 PM 913 db2ph5.net

05/21/2012 01:52 PM 8119 relocate.template

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

3 File(s) 11527 bytes

2 Dir(s) 119644123136 bytes free

3. Make sure the contents of the db6_update_db.SAR

archive attached to SAP Note 1365982 are available in the sapdbctrl-config

directory.

4. Make sure that you stop the SAP system and the database. You also have to make sure that all SAP and database related services are offline by checking that the

SAP*

and

DB2*

services are stopped.

Note

Keep all directories at their current locations. The tool will find and move them to the correct directory and set the required ownerships and permissions.

3.4.2 Performing IBM DB2 for z/OS – Specific Preparation

Steps

This section describes the prerequisites and preparation steps that you have to perform for IBM DB2 for z/OS before starting the system rename procedure.

Context

No rename actions are performed on the database subsystem itself.

There are two types of renaming:

Procedure

●

Rename of an SAP system without copying the IBM DB2 for z/OS subsystem:

○

The application server is renamed; no changes are made on the IBM DB2 for z/OS subsystem.

○

The renamed SAP system stays connected to the original IBM DB2 for z/OS subsystem

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

Figure 1: Rename of an SAP System without copying the IBM DB2 for z/OS Subsystem

●

Rename of an SAP system after copying the IBM DB2 for z/OS subsystem.

Before running the tool , you have to copy your IBM DB2 for z/OS database using the offline system copy method.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

Figure 2: Rename of an SAP System after copying the IBM DB2 for z/OS Subsystem

For more information about the system copy procedure, see the SAP Note 680746 .

3.4.3 Performing Oracle-Specific Preparation Steps

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

Procedure

1. If you use one Oracle software installation for more than one SAP system instance installations, make sure that no other Oracle services are running with this

ORACLE_HOME

software before you start the system rename process.

2. For the offline backup method, we recommend that you shut down the database. Alternatively, the installer can also make an instance recovery of the database if it has not been shut down before the copy process. For the online backup method, you have to set the database to a backup mode and the backup control files and the Oracle archives will be copied to an existing shared directory. You can set the database to a backup mode using the following command:

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

saphostctrl -user sapadm <Password> -function PrepareDatabaseCopy -dbname

<DBSID> -dbtype ora -dbconfdir <shared_directory> -copymethod Online -timeout -1

After the database backup has finished, you have to set the database back to a normal mode using the following command:

saphostctrl -user sapadm <password> -function FinalizeDatabaseCopy -dbname

<DBSID> -dbtype ora -dbconfdir <shared_directory> -copymethod Online -timeout -1

3. You can copy the database from the source to the target system but alternatively, you can also install the

Oracle database software in the target system.

It is possible to rename the Oracle database software automatically with the installer when the database software has the same

<DBSID>

as the database

<DBSID>

Example

<Source_DBSID> = C11

<Target_DBSID> = T11

The Oracle software is under c:\oracle\C11\112

and the Oracle database files are under c:

\oracle\C11

and d:\oracle\C11

The installer moves c:\oracle\C11

to c:\oracle\T11

and d:\oracle\C11

to d:\oracle\T11 with all subdirectories.

If there are database files under the directory that contains the Oracle software and you do not want to move the Oracle software, you have to move the database directory manually.

For more information about how to install the Oracle database software, see the installation documentation of your release and stack at http://service.sap.com/instguides .

3.4.4 Performing Microsoft SQL Server-Specific Preparation

Steps

This section describes the prerequisites and preparation steps that you have to perform for MS SQL Server before starting the system rename procedure.

Procedure

Currently, there are no MS SQL Server-specific preparation steps.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

3.4.5 Performing SAP ASE -Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP ASE before starting the system rename procedure.

Procedure

Currently, there are no SAP ASE-specific preparation steps.

3.4.6 Performing SAP MaxDB-Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB before starting the system rename procedure.

Procedure

1. Create a database-specific configuration file sapdbConfig.txt

, which describes the software of the source system and store it locally on the host.

The database-specific configuration file sapdbConfig.txt

for SAP MaxDB 7.8 and higher looks as shown below:

○

Default:

IndepDataPath=c:/sapdb/data

GlobalProgramsPath=c:/sapdb/programs

<source_DBSID> =c:/sapdb/ <source_DBSID> /db

<source_DBSID> /PrivateDataPath=c:/sapdb/ <source_DBSID> /data

CL_ <source_SAPSID> /PrivateDataPath=c:/sapdb/clients/ <source_SAPSID> /data

○

Distributed installation with the database and the primary application server instance on different hosts.

On the primary application serverl instance host:

IndepDataPath=c:/sapdb/data

GlobalProgramsPath=c:/sapdb/programs

CL_ <source_SAPSID> /PrivateDataPath=c:/sapdb/clients/ <source_SAPSID> /data

On the database instance host:

IndepDataPath=c:/sapdb/data

GlobalProgramsPath=c:/sapdb/programs

<source_DBSID> =c:/sapdb/ <source_DBSID> /db

<source_DBSID> /PrivateDataPath=c:/sapdb/ <source_DBSID> /data

CL_ <source_SAPSID> /PrivateDataPath=c:/sapdb/clients/ <source_SAPSID> /data

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

2. Make sure that you shut down the SAP system including the database and that all SAP and SAP MaxDB related services are offline before your start the system rename procedure. To check this, verify that the services

Xserver*

and

MaxDB*

are stopped.

3.4.7 Performing SAP HANA Database-Specific Preparation

Steps

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

Context

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

Procedure

You perform the rename for the SAP HANA database as described in section

Changing the SAP HANA System

in the

SAP HANA Administration Guide

Administration

at http://help.sap.com/hana_platform

System

3.5 Required User Authorization for Running the Installer

Although the installer automatically grants the rights required for the installation to the user account used for the installation, you have to check whether this account has the required authorization to perform the installation. The authorization required depends on whether you intend to perform a domain or local installation. If necessary, you have to ask the system administrator to grant the account the necessary authorization before you start the installation. If you attempt the installation with an account that does not have the required authorization, the installation aborts.

This section informs you about the authorization required for a domain and a local installation.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

Procedure

Caution

Do not use the user

<sapsid>adm

for the installation of the SAP system.

Domain Installation

For a domain installation the account used for the installation needs to be a member of the local

Administrators

and the domain

Admins

group of the relevant domain. All machines in the system must belong to the same domain. In a domain installation, the user information is stored centrally on the domain controller and is accessible to all hosts in the system.

If the SAP system is to be distributed across more than one machine, SAP strongly recommends you to perform a domain installation to avoid authorization problems.

Caution

●

If you install a distributed system as a local installation, this can lead to authorization problems for the operating system users

<sapsid>adm

and

SAPService<SAPSID>

. It can also lead to problems with the transport directory, which is usually shared by several SAP systems. SAP does not support distributed SAP systems running with local user accounts.

●

In a high-availability configuration, you always have to perform a domain installation.

●

For performance and security reasons, SAP does not support an SAP system installation on a domain controller.

●

If for any reason, the account used for the installation is not a member of the domain

Admins

group, you can perform the installation with a domain user who is a member of the local

Administrators group. However, the domain administrator has to prepare the system appropriately for you.

For more information, see Performing a Domain Installation without being a Domain Administrator

[page 60]

For a domain installation, you need to:

1. Check that the account used for the installation is a member of the domain

Admins

group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member of the domain

Admins

group.

Local Installation

For a local installation the account used for the installation needs to be a member of the local

Administrators

group of the machine involved. In a local installation, all Windows account information is stored locally on one host and is not visible to any other hosts in the system.

If the SAP system is to run on a single machine, you can perform a local installation.

Caution

Do not use the Windows built-in account

Administrator

or the renamed built-in account to install your

SAP system. The built-in account only has restricted network access rights that are required by the installer. If you renamed the built-in account

Administrator

, do not create a new account named

Administrator

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

For a local installation, you need to:

1. Check that the account used for the installation is a member of the local

Administrators

group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member of the local

Administrators

group.

Related Information

Performing a Domain Installation Without Being a Domain Administrator [page 60]

3.6 Changing the Windows Domain

3.6.1 Requirements

Requirements for the SAP System Hosts for Central and Distributed

Systems

To change the domain during system rename, we recommend that you check that all SAP system hosts are members of the target Windows domain. We recommend this for all SAP system setups. We assume that you are familiar with checking Windows domain structures.

For more information, see the Windows documentation.

Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to conceal their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure.

●

Make sure that the virtual host names can correctly be resolved in your Domain Name System (DNS) setup.

●

Make sure that you configured the Windows operating system properly to use virtual host names. For more information, see SAP Note 1564275 .

Required User Authorization for System Rename with Domain Change

1. Check that the account used to execute system rename is a member of the domain

Admins

group in the target domain.

2. If required, obtain these rights by asking the system administrator to enter the account as a member of the domain

Admins

group in the target domain.

3. To execute system rename with a user who is not member of the domain

Admins

group in the target domain, proceed as described in

Maintaining Users and Groups [page 17]

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

Note

To run the tool, do not use user

<SID>adm

Deciding Whether to Use Organizational Units (OUs) in the Windows Domain

Note

You do not need this step for a local installation.

For a domain installation, the installer needs to create certain OS users for SAP and database operations in the

Windows domain, also called the “Active Directory” (AD). These users are created by default in the AD container “Users”.

Depending on a customer's AD landscape and security policy, there are certain restrictions on where to store users and groups in AD. Contact the administrator of your AD infrastructure to understand where to store all

SAP and database-related domain users and domain groups.

The SAP installer offers to define an existing OU in AD to create all needed SAP and database users in this OU.

There are many different scenarios and prerequisites concerning how to use OUs. For more information, see

SAP Note 2247673 , which explains these issues in detail and shows some examples of how to use them.

Caution

The installer does not create OUs. The installer does not move existing domain users or groups. The installer does not delete existing users, groups, OUs, nor any other object in a Windows domain.

The only exception to this rule is the

Uninstall

option in the installer.

3.6.2 Preparing SAP System Hosts for System Rename with

Windows Domain Change

Central System

Before you start the system rename, make sure that the SAP system host is a member in the planned target domain, otherwise stop all SAP instances and their Windows services, remove the auto start parameter of the services and join the host to the target domain and restart the SAP system host.

After the SAP system host is available again, start the system rename.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

Distributed System

Before you start the system rename for a distributed system, make sure that all hosts of the SAP system are members of the future target domain, otherwise stop all SAP instances and their Windows services on the relevant hosts, remove the auto start parameter of the services and join all hosts of this distributed installation to the target domain.

For more information, see the Windows documentation.

After the SAP system host is available again, start system rename procedure.

3.6.3 Procedure for System Rename with Windows Domain

Change

Proceed as follows to perform a system rename with changing the Windows domain.

Prerequisites

Make sure you have completed the preparation steps required for your database (see

Database-Specific

Preparation [page 19] ).

Procedure

1. Change the Windows domain manually on the host.

2. Restart the server.

3. Run the system rename procedure with the Windows domain administrator of the target Windows domain.

Note

If you want to use Organizational Units (OUs) in the Windows domain, make sure that you choose option option

Use domain of current user

on the

Windows Domain

screen.

Related Information

System Rename Procedure [page 36]

Database-Specific Preparation [page 19]

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

3.7 Preparing the System Rename Media

This section describes how to prepare the media required for the system rename procedure.

In addition to the Software Provisioning Manager archive, for the rename of the primary application server instance you also have to provide the Java components media for your SAP system product.

●

You normally obtain the physical installation media as part of the installation package.

●

You can also download the installation media apart from the Software Provisioning Manager 1.0 archive from SAP Service Marketplace.

Note

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

Related Information

Downloading and Extracting the Software Provisioning Manager Archive [page 31]

Using the Physical Media from the Installation Package [page 33]

Downloading Complete Installation Media [page 34]

3.7.1 Downloading and Extracting the Software Provisioning

Manager Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software

Download Center because you must use the latest version.

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR

from: https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES & PATCHES By

Alphabetical Index (A-Z) S SOFTWARE PROVISIONING MANAGER

2. Get the latest version of the

SAPCAR

tool on the host where you want to run the installer: a. Go to https://launchpad.support.sap.com/#/softwarecenter

PATCHES

and search for “

sapcar

”.

SUPPORT PACKAGES &

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

b. Select the archive file for your operating system and download it to an empty directory.

c. To check the validity of the downloaded executable, right-click the executable and choose

Properties

On the

Digital Signatures

tab you can find information about the SAP signature with which the executable was signed.

d. Rename the executable to

sapcar.exe

For more information about

SAPCAR

, see SAP Note 212876 .

3. Using the latest version of SAPCAR, you can verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR

archive as follows: a. Get the latest version of the

SAPCRYPTOLIB

archive to your installation host as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcryptolib

”.

2. Select the archive file for your operating system and download it to the same directory where you have put the

SAPCAR

executable.

3. 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. Download the

Certificate Revocation List

from

https://tcs.mysap.com/crl/ crlbag.p7s

and move it into the same directory.

b. Verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR

archive by executing the following command:

Note

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

<Path to SAPCAR>\sapcar.exe -tvVf<Path to Download Directory>

\SWPM10SP<Support_Package_Number>_<Version_Number>.SAR -crl<file name of revocation list>

4. Unpack the Software Provisioning Manager archive to a local directory using the following command:

<Path to SAPCAR>\sapcar.exe -xvf <Path to Download Directory>

\SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack

Directory>

Note

Make sure that all users have read permissions for the directory where you want to unpack the installer.

Caution

Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

3.7.2 Using the Physical Media from the Installation Package

For the rename of the primary application server instance, you have to provide the Java components media for your SAP system product.

Procedure

1. Identify the required media for the system rename as listed in the following table:

Table 4:

SAP Instance to be Renamed Required Media

Central Services (SCS) in stance, database instance, ad ditional application server in stance

Software Provisioning Manager archive

Primary application server in stance

○

Software Provisioning Manager archive

○

Java Components

2. Make the required media available on each installation host as follows: a. Download and unpack the latest version of Software Provisioning Manager as described in

Downloading and Extracting the Software Provisioning Manager Archive [page 31] .

b. Make the media for the rename of the primary application server instance available.

You can do this in one of the following ways:

○

Copy the required media folders directly to theprimary application server instance host.

○

Mount the media on a central media server that can be accessed from the installation hosts.

Caution

○

If you copy the media to disk, make sure that the paths to the destination location of the copied media do not contain any blanks and commas.

○

If you perform a domain installation and do not want to copy the media but use network drives for mapping the installation media, make sure that the

<sapsid> adm

user has access to the

UNC paths of the network drives.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

3.7.3 Downloading Complete Installation Media

This section describes how you download complete media from the SAP Software Download Center.

Procedure

1. Download and unpack the latest version of Software Provisioning Manager as described in

Downloading and Extracting the Software Provisioning Manager Archive [page 31] .

2. Identify all download objects that belong to one medium according to one of the following:

Note

Installation media might be split into several files. In this case, you have to reassemble the required files after the download.

○

Download path or location:

○

To download the complete kernel media, go to https://support.sap.com/sltoolset

System

Provisioning Software Provisioning Manager 1.0 SP

Download Kernel releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES)

KERNEL FOR INSTALLATION/SWPM

○

To download all media required for your SAP product, you can use one of the following navigation paths:

○ https://launchpad.support.sap.com/#/softwarecenter

INSTALLATIONS & UPGRADES

By Category SAP NETWEAVER AND COMPLEMENTARY PRODUCTS

○ https://launchpad.support.sap.com/#/softwarecenter

INSTALLATIONS & UPGRADES

By Alphabetical Index (A-Z)

<First Letter of Product> <Product> <Product

Release>

○

Material number

All download objects that are part of an installation medium have the same material number and an individual sequence number:

<Material_Number> _ <Sequence_Number>

Example

51031387_1

51031387_2

...

○

Title

All objects that are part of an installation medium have the same title, such as

<Database> RDBMS <OS>

for database media.

3. Download the objects to the download directory.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

4. To correctly re-combine the media that are split into small parts, unpack all parts into the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the medium and copies the data into it. The data is now all in the correct directory, the same as on the medium that was physically produced. For more information, see SAP Note 1258173 .

Caution

Make sure that you unpack each installation media to a separate folder. Do not unpack installation media to the same folder where you unpack the Software Provisioning Manager archive.

3.8 Preparing the File System

Use this step to make the file system available on the system that you plan to rename.

Prerequisites

You have performed the database specific preparation steps.

Procedure

●

If you want to perform the system rename on a central system, you can start the system rename procedure without any further preparatory steps.

●

If you want to perform the system rename on a distributed system, you have to prepare the SAP global host. To do this, run the installer and choose

System Rename Distributed System Global Host

Preparation

Related Information

Database-Specific Preparation [page 19]

Running the Installer [page 38]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Preparation

C U S T O M E R

4 System Rename Procedure

4.1 System Rename Procedure Checklist

This section includes the renaming steps that you have to perform for the following options:

●

Standard system

●

Distributed system

The installer adapts the SAP system on an operating system level. The system parameters are adapted offline.

The installer automatically starts the following instances during the system rename:

●

Database

●

Instance services of a Windows operating system

●

Central services instance (SCS instance)

Central System

Caution

If your target system to be installed is based on SAP NetWeaver CE 7.2, SAP NetWeaver 7.3 , or SAP

NetWeaver 7.3 EHP1, and is to be installed with Oracle 12c , follow the instructions in SAP Note 2396282 .

You check the Prerequisites for Running the Installer [page 37]

and run the installer to rename the system as described in

Running the Installer [page 38]

Distributed System

Caution

If your target system to be installed is based on SAP NetWeaver CE 7.2, SAP NetWeaver 7.3 , or SAP

NetWeaver 7.3 EHP1, and is to be installed with Oracle 12c , follow the instructions in SAP Note 2396282 .

Note

4.2 Prerequisites for Running the Installer

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

●

If you want to use the SL Common GUI, make sure that the following web browser requirements are met:

○

You have one of the following supported browsers on the device where you want to run the SL

Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.

Always use the latest version of these web browsers.

Recommendation

We recommend using Google Chrome.

○

If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new

Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

For more information about the SL Common GUI, see Useful Information About the Installer [page 43] .

●

You need at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables.

●

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.

If this port cannot be used, you can assign a free port number by executing sapinst.exe

with the following command line parameter:

SAPINST_HTTPS_PORT=<Free Port Number>

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

○

Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst.exe

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.

If this port cannot be used, you can assign a free port number by executing sapinst.exe

with the following command line parameter:

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.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst.exe

with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

●

If you want to change the host name of your system, change the computer name and the host name on OS level and make sure that the host name resolution and UNC paths work.

For more information, see SAP Note 23538 .

If you want to change the virtual host name, see SAP Note 962955 .

●

SAP ASE : Make sure the system and database are not running when starting the installer.

●

If you are carrying out a domain switch, ensure you have completed all additional actions in section

Changing the Windows Domain [page 28]

before starting the installer.

4.3 Running the Installer

This section describes how to run the installer to perform the system rename .

Prerequisites

For more information, see Prerequisites for Running the Installer [page 37]

Context

Software Provisioning Manager (the “installer” for short) offers two GUIs:

●

The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

●

The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

Note

If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI.

You then have to start the sapinst

executable with the command line option

SAPINST_SLP_MODE=false

In cases where both GUIs behave the same way, we address them as “installer GUI”.

For more information, see Useful Information About the Installer [page 43] .

This procedure describes an installation where you use one of the following GUI scenarios:

●

You run the installer and use the SL Common GUI. Then you can control the processing of the installer in the browser running on any device.

●

You run the installer and use the Java SDT GUI. Both are running on the same host.

Procedure

1. Log on to the host where you want to run the installer.

Make sure that you log on as a user with the required authorization for running the installer.

For more information, see

Required User Authorization for Running the Installer [page 26] .

Caution

Do not use an existing

<sapsid> adm

user.

SL Common GUI only: If your security policy requires that the person running the installer is not allowed to know administrator credentials on the host where the installer is to perform the system rename , you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER

parameter when starting sapinst.exe

from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

2. Make the required media available.

For more information, see

Preparing the System Rename Media [page 31]

3. Start the installer as follows:

Double-click sapinst.exe

from the directory to which you unpacked the Software Provisioning Manager archive file.

Note

By default, the SL Common GUI uses the default browser defined for the host where you run the installer. However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst

executable with command line option

SAPINST_BROWSER=<Path to Browser Executable>

, for example

SAPINST_BROWSER=firefox.exe

The installer GUI starts automatically by displaying the

Welcome

screen.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

4. The installer is starting up.

Depending on the type of the installer GUI you want to use, do one of the following:

○

If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI. If you have a supported web browser (see Prerequisites for Running the Installer [page

37] ) installed on the host where you run the installer, the SL Common GUI starts automatically by

displaying the

Welcome

screen.

If the SL Common GUI does not open automatically, you can find the URL you require to access the SL

Common GUI at the bottom of the

Program Starter

window of the installer. You find the icon of the

Program Starter

window in the taskbar of your Windows host. Open a supported web browser and run the URL from there.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

*************************************************************************

*******

...

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst

process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○

If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. In the

Welcome

screen, proceed according to your system variant :

○

If your system is a standard system , choose

System Rename Standard System System

Rename

○

If your system is a distributed system , choose

System Rename Distributed System

<System_Rename_Option>

Choose the system rename options as required and in the order they appear.

Table 5: System Rename Options and Sequence how to Execute Them

Option Description When to Execute Execution Order

System Rename for SCS

Instance

Executes system rename for the SCS instance

First option for systems with AS Java

First step for systems with

AS Java

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

Option Description When to Execute Execution Order

System Rename for ERS

Instance

Executes system rename for the ERS instance

If your system does not have an ERS instance, skip this option.

Execute this option after you have performed the rename options for the

SCS instance above, as re quired

System Rename for Data base Instance

Executes system rename for the database instance

Execute in any case (even if you change the SAP sys tem ID, the host name or the instance number)

Execute this option after you have performed the rename options for the

SCS instance and the ERS instance above, as re quired

System Rename for the

Primary Application

Server Instance

System Rename for a

Gateway Instance

Executes system rename for the primary application server instance

Execute this option after renaming the database in stance.

Execute this option after you have performed the rename options for the

SCS instance, the ERS in stance, and the database instance above, as re quired

Executes system rename for a standalone Gateway instance

If your system host does not have a standalone

Gateway instance, skip this option.

Execute this option after you have performed the rename options for the

SCS instance, the ERS in stance, the database in stance, and the primary application server in stance above, as required

System Rename for Web

Dispatcher Instance

Executes system rename for the SAP Web Dis patcher instance

If your system does not have an SAP Web Dis patcher instance, skip this option.

Execute this as last option

6. Choose

Next

7. If the installer prompts you to log off from your system, log off and on again.

The installer restarts automatically.

8. Follow the instructions in the installer input screens and enter the required parameters.

Note

To find more information on each parameter during the

Define Parameters

phase, position the cursor on the required parameter input field :

○

If you use the SL Common GUI, choose either

F1 displayed in the

HELP

tab.

or the

HELP

tab. Then the available help text is

○

If you use the Java SDT GUI, choose

. Then a dialog opens with the available help text.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

Note

○

IBM DB2 for Linux, UNIX, and Windows only :

When you are asked for the security administrator, enter a user that has

DB2 SECADM

authorities.

By default, db2 <DBSID_source>

has these authorities. If you perform the system rename in a domain, enter for the security administrator a user name specified with the related domain name:

<Domain>\<User>

, for example

Domain10\db2td1

○

SAP MaxDB only :

In the

Storage Based Copy Configuration File for SAP MaxDB

screen, enter the path to the database-specific configuration file sapdbConfig.txt

, which you stored locally on the host.

○

MS SQL Server only :

In the

Database System Parameters

screen, make sure that the

Target System

details are correct.

○

Oracle Database only: If your source system has Oracle Database Vault, consider the additional

information in section Implementing Oracle Database Vault with the Installer [page 64] .

Caution

The signature of media is checked automatically during the

Define Parameters

phase while processing the

Media Browser

screens.

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 - that is if you modify artefacts later on either during the remaining

Define Parameters

phase or later on during the

Execute Service

phase the signature is not checked again.

See also the description of this new security feature in SAP Note 2393060 .

9. After you have entered all requested input parameters, the installer displays the

Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by default.

If required, you can revise the parameters before starting the system rename procedure.

10. To start the execution, choose

Next

The installer starts the rename procedure and displays its progress on the

Task Progress

screen.

The installer starts the export and displays its progress of the system copy export during the processing phase.

When the system rename option has finished successfully, the installer displays the message

Execution of

<Rename_Option>

has completed

11. If you copied installation media to your hard disk, you can delete these files when the installer has successfully completed.

12.

Java GUI only: For security reasons, we recommend that you delete the

.sdtgui

directory within the home directory of the user with which you ran the installer:

%userprofile%\.sdtgui\

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

Related Information

Useful Information About the Installer [page 43]

Interrupted Processing of the Installer [page 45]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 48]

Starting the Java SDT GUI Separately [page 49]

Running the Installer in Accessibility Mode [page 51]

Troubleshooting with the Installer [page 53]

4.4 Additional Information About the Installer

The following sections provide additional information about the installer.

Related Information

Useful Information About the Installer [page 43]

Interrupted Processing of the Installer [page 45]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 48]

Starting the Java SDT GUI Separately [page 49]

Running the Installer in Accessibility Mode [page 51]

Troubleshooting with the Installer [page 53]

4.4.1 Useful Information About the Installer

This section contains some useful technical background information about the installer and the installer GUI.

●

Software Provisioning Manager (the installer) offers two GUIs:

○

The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

○

The “classic” Java-based GUI with a CUI client and server - “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 - also known as SAPUI5 - a client-side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are:

○

Zero foot print, since only a web browser is required on the client

○

New controls and functionality, for example, view logs in web browser.

The SL Common GUI connects the web browser on a client with the sapinst

executable - which is part of

Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

For the SL Common GUI, the installer provides a pre-generated URL in the

Program Starter

window. If you have a supported web browser installed on the host where you run the installer, the SL Common GUI starts automatically.

By default, the SL Common GUI uses the default browser defined for the host where you run the installer.

However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst

executable with command line option

SAPINST_BROWSER=<Path to Browser Executable>

, for example

SAPINST_BROWSER=firefox.exe

Alternatively you can open a supported web browser on any device and run the URL from there.

For more information about supported web browsers see

Prerequisites for Running the Installer [page 37] .

If the SL Common GUI does not meet your requirements, you can still use the “classic” Java SDT GUI. To do so, you must start the sapinst

executable with the command line option

SAPINST_SLP_MODE=false

You can switch back to the default installer GUI at any time with the following steps:

1. Stop the installer.

2. Restart the installer with command line option

SAPINST_SLP_MODE=false

3. On the

What do you want to do?

screen choose

Continue with the existing run

●

The installer creates the installation directory sapinst_instdir

, where it keeps its log files, and which is located directly in the

%ProgramFiles%

directory. If the installer is not able to create sapinst_instdir there, it tries to create sapinst_instdir

in the directory defined by the environment variable

TEMP

●

For each option, the installer creates a subdirectory located in the sapinst_instdir

directory.

●

The installer extracts itself to a temporary directory (

TEMP

TMP

TMPDIR

, or

SystemRoot

). These executables are deleted after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx

sometimes remain in the temporary directory. You can safely delete them.

The temporary directory also contains the log file dev_selfex.out

from the extraction process, which might be useful if an error occurs.

Caution

If the installer cannot find a temporary directory, the installation terminates with the error

FCO-00058

●

To see a list of all available installer properties, go to the directory

%TEMP%\sapinst_exe.xxxxxx.xxxx after you have started the installer, and enter the following command:

sapinst.exe -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, proceed as described in

Running the Installer in Accessibility Mode [page 51] .

●

If required, stop the installer by choosing one of the following, depending on the installer GUI you use:

○

In the SL Common GUI, choose the

Cancel

button.

○

In the Java SDT GUI, choose

SAPinst Exit Process

in the Java SDT GUI menu..

Note

If you need to terminate the installer, choose

File Exit

in the menu of the

Program Starter

window.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

4.4.2 Interrupted Processing of the Installer

Here you find information about how to restart the installer if its processing has been interrupted.

Context

The processing of the installer might be interrupted for one of the following reasons:

●

An error occurred during the

Define Parameters

Execute

phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

●

You interrupted the 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, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

The following table describes the options in the dialog box:

Table 6:

Option Definition

Retry

Stop

Continue

View Log

The installer retries the installation from the point of failure without repeating any of the previous steps.

This is possible because the installer records the installation progress in the keydb.xml

file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose

Retry

If the same or a different error occurs, the installer displays the same dialog box again.

The installer stops the installation, closing the dialog box, the installer GUI, and the

GUI server.

The installer records the installation progress in the keydb.xml

file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

The installer continues the installation from the current point.

Access installation log files.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

The following procedure describes the steps to restart an installation, which you stopped by choosing

Stop

, or to continue an interrupted installation after an error situation.

Procedure

1. Log on to the installation host as a user with the required permissions as described in Running the Installer

[page 38] .

2. Make sure that the media required for the system rename are still available.

For more information, see

Preparing the System Rename Media [page 31]

Recommendation

Make the installation media available locally . For example, if you use remote file shares on other

Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.

3. Restart the installer by double-clicking

sapinst.exe

from the directory to which you unpacked the

Software Provisioning Manager archive.

By default, the SL Common GUI uses the default browser defined for the host where you run the installer.

However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst

executable with command line option

SAPINST_BROWSER=<Path to Browser Executable>

, for example

SAPINST_BROWSER=firefox.exe

4. The installer is restarting.

Depending on the type of the installer GUI you want to use, do one of the following:

○

If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI. If you have a supported web browser (see Prerequisites for Running the Installer [page

37] ) installed on the host where you run the installer, the SL Common GUI starts automatically by

displaying the

Welcome

screen.

If the SL Common GUI does not open automatically, you can find the URL you require to access the SL

Common GUI at the bottom of the

Program Starter

window of the installer. You find the icon of the

Program Starter

window in the taskbar of your Windows host. Open a supported web browser and run the URL from there.

Sample Code

...

*************************************************************************

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

*************************************************************************

*******

...

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst

process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○

If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. From the tree structure on the

Welcome

screen, select the installation option that you want to continue and choose

Next

The

What do you want to do?

screen appears.

6. On the

What do you want to do?

screen, decide between the following alternatives and continue with

Next

Table 7:

Alternative Behavior

Perform a new run

The installer does not continue the interrupted system rename option. Instead, it moves the content of the old installer directory and all installer-specific files to a backup directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory: log_ <Day> _ <Month> _ <Year> _ <Hours> _ <Minutes> _ <Seconds>

Example log_01_Oct_2016_13_47_56

Note

All actions taken by the system rename before you stopped it (such as cre ating directories or users) are not revoked.

Caution

The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the existing one

The installer continues the interrupted system rename from the point of fail ure.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

4.4.3 Performing Remote Processing of the Installer (Java

SDT GUI only)

Here you find information about how to process the installer on a remote host.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst

executable with command line option

SAPINST_SLP_MODE=false

Prerequisites

●

The remote host meets the prerequisites for starting the installer as described in Prerequisites for

Running the Installer [page 37] .

●

Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command:

ping <Local_Host>

2. Log on to the local host 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, make sure that this user exists on the remote host.

Context

You use this procedure to process the installer on a remote host. In this case, the installer runs on the remote host , and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.

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 administrator credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting sapinst.exe

from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

Procedure

1. Log on to the remote host as a user with the required authorization for running the installer.

For more information, see

Required User Authorization for Running the Installer [page 26] .

2. Make the installation media available on your remote host.

For more information, see

Preparing the System Rename Media [page 31]

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

3. Open a command prompt and change to the directory to which you unpacked the Software Provisioning

Manager archive.

4. Check the version of the sapinst

executable by entering the following command:

sapinst.exe -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 49] ).

5. Start the installer by entering the following command:

sapinst.exe

Note

If you need to specify another operating system user for authentication purposes, enter the following command:

sapinst.exe SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <Host_Name> , port

<Port_Number> to continue with the installation

6. Start the installer GUI on your local host as described in

Starting the Installer GUI Separately [page 49]

4.4.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. That is, you started the sapinst

executable with command line option

SAPINST_SLP_MODE=false

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

Note

If you want to run the installer on a UNIX host, make sure that you meet the prerequisites for the installer listed in the relevant UNIX guide.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

Context

You might need to start the installer GUI separately in the following cases:

●

You closed the installer GUI using

File Close GUI only

from the installer menu while the installer is still running.

●

You want to perform a remote installation, where the installer GUI runs on a different host from the

installer. For more information, see Performing Remote Processing of the Installer (Java SDT GUI only)

[page 48]

In the this procedure, the following variables are used:

<Remote_Host>

is the name of the remote host, and

<Port_Number_Gui_Server_To_Gui_Client>

is the port the GUI server uses to communicate with the GUI client (21212 by default).

Procedure

●

Starting the Installer GUI on Windows a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the System Rename Media [page 31] .

b. Start the installer GUI by executing the sapinstgui

executable with the appropriate command line parameters:

○

If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe

by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.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

48] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

○

If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

●

Starting the Installer GUI on UNIX a. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the System Rename Media [page 31] .

b. Start the installer GUI by executing the sapinstgui

executable with the appropriate command line parameters:

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

○

If you want to perform a remote installation, proceed as follows:

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

48] ).

2. Start the installer GUI by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

○

If you closed the installer GUI using

File Close GUI only

and want to reconnect to the installer, proceed as follows:

1. If you are performing a local installation with the installer and the installer GUI running on the same host, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -port

<Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:

<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port

<Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.

4.4.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode.

Note

The information contained in this section is only valid if you use the Java SDT GUI . That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

If you use the SL Common GUI , apply the standard accessibility functions of your web browser.

Context

The following features are available:

●

Keyboard access:

This feature is generally available for all operating systems.

●

High-contrast color:

This feature is derived from the Windows display properties. You can use it either for a local installation or for a remote installation.

●

Custom font setting:

This feature is derived from the Windows display properties. You can use it either for a local installation or for a remote installation.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

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.

Note

The following procedure applies for Windows Server 2012 and might be different when using another

Windows operating system.

a. Right click on your Windows desktop and choose

Personalize

b. Select

Adjust font size (DPI)

and choose

Larger scale (120 DPI)

To define other font size schemes, choose

Custom DPI

c. In the right-hand pane, select

Window Color and Appearance

Select a color scheme from the

Color scheme

drop-down box.

To define your own color schemes, choose

Advanced

●

Running the Installer in Accessibility Mode

You can either perform a local installation, where the installer and the installer GUI are running on the same host, or a remote installation, where the installer and the installer GUI are running on different hosts.

○

Local installation:

Start the software provisioning manager as described in

Running the Installer [page 38] by executing

the following command:

<Path_To_Unpack_Directory>\sapinst.exe -accessible

○

Remote installation:

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

<Path_To_Unpack_Directory>\sapinst.exe

2. Start the installer GUI on the local host by executing the following command from the command

line as described in Starting the Java SDT GUI Separately [page 49]

<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host>

-port <Port_Number_Gui_Server_To_Gui_Client>

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

4.4.6 Troubleshooting with the Installer

This section tells you how to proceed when errors occur while the installer is running.

Context

If an error occurs, the installer:

●

Stops processing

●

Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known installer issues.

2. If an error occurs during the

Define Parameters

or the

Execute Service

phase, do one of the following:

○

Try to solve the problem:

○

To check the installer log files ( sapinst.log

and sapinst_dev.log

) for errors, choose:

○

The

LOG FILES

tab, if you are using the SL Common GUI.

○

The

View Logs

menu item, if you are using the Java SDT GUI.

○

To check the log and trace files of the installer GUI for errors:

○

If you use the SL Common GUI, you can find them in the directory

%userprofile%

\.sapinst\

○

If you use the Java SDT GUI, you can find them in the directory

%userprofile%\.sdtgui\

○

If the GUI server or the installer GUI do not start, check the file sdtstart.err

in the current

%userprofile%

directory.

○

If the installer GUI aborts without an error message, restart the installer GUI as described in

Starting the Installer GUI Separately [page 49] .

○

High Availability only: If you experience network connection problems, check IPv4 Host name resolution as described in SAP Note 1365796 .

○

Then continue by choosing

Retry

○

If you cannot resolve the problem, abort the installer by choosing one of the following, depending on the type of installer GUI you use:

○

If you use the SL Common GUI, choose

Cancel

in the tool menu.

○

If you use the Java SDT GUI, choose

Stop

from the error message or

SAPinst Exit Process

in the tool menu.

For more information, see Interrupted Processing of the Installer [page 45] .

3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.

For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

System Rename Procedure

C U S T O M E R

5 Follow-Up Activities

5.1 Follow-Up Activities Checklist

Procedure

1. Start the primary application server instance.

For more information, see

Starting the SAP System [page 59]

The installer has only started the following instances during the system rename:

○

Database

○

Instance services of a Windows operating system

○

Central services instance (SCS instance)

2. Perform general follow-up activities.

For more information, see

General Follow-Up Activities [page 55]

Java Systems using ABAP UME only: Reconfigure the UME back-end connection

4. Perform follow-up activities for your database.

For more information, see

Database-Specific Follow-Up Activities [page 56]

5. Restart the renamed SAP system completely.

For more information, see

Starting the SAP System [page 59]

Related Information

General Follow-Up Activities [page 55]

Java Systems Using ABAP UME: Reconfigure UME Back-End Connection [page 55]

Database-Specific Follow-Up Activities [page 56]

Starting the SAP System [page 59]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Follow-Up Activities

C U S T O M E R

5.1.1 General Follow-Up Activities

This section refers to the general follow-up activities that you have to perform after the rename of your SAP system.

●

Potentially, all follow-up activities for a system copy are also valid for the rename of your SAP system and therefore you have to check which of them apply for your special situation and use case. For more information, see the system copy guides at: https://help.sap.com/sltoolset

System Provisioning Guide for System Copy for Systems Based on

SAP NetWeaver 7.1 & Higher

Generally, due to the high variety of use cases, no rule which of the potential follow-up activities are valid can be given .

Example

To identify potential follow-up activities regarding logical system names, answer to the following question:

Does the renamed SAP system use logical system names?

○

If not, this aspect is not relevant for your use case.

○

If yes, answer to the following question:

What naming convention was used for the logical system names?

The default convention is

, but it might have been adapted individually. If your logical system names contain attributes that were renamed as part of this procedure, see SAP Note 121163 for information about how to convert logical system names.

●

Post-copy activities automated as part of SAP Landscape Management (LVM) can also be used to perform the follow-up activities after a system rename, so you can profit from an easier, faster and more reliable process. For more information, see http://scn.sap.com/docs/DOC-25771 .

5.1.2 Java Systems Using ABAP UME: Reconfigure UME

Back-End Connection

If you changed a host name or instance number of an ABAP system that is used for the UME of an AS Java system, you have to reconfigure the User Management Engine (UME) back-end connection as follows:

Procedure

1. Start the

ConfigTool

from the

/usr/sap/ <SAPSID> /

<Primary_Application_Server_Instance_Name> /j2ee/configtool/

5.1.3 Database-Specific Follow-Up Activities

Related Information

Performing Follow-Up Activities for SAP MaxDB [page 56]

Performing Follow-Up Activities for SAP HANA Database [page 57]

Performing Follow-Up Activities for SAP ASE [page 58]

Performing Follow-Up Activities for DB2 for z/OS [page 58]

Performing Follow-Up Activities for the Oracle Database [page 58]

5.1.3.1 Performing Follow-Up Activities for SAP MaxDB

This section contains follow-up steps required for SAP MaxDB after the system rename has completed.

Procedure

Currently there are no follow-up steps required.

5.1.3.2 Performing Follow-Up Activities for IBM DB2 for

Linux, UNIX, and Windows

After system rename has completed, you can change the name and location of your DB2 software copy.

Note

This follow-up step is optional.

Context

The system rename procedure does not reinstall your DB2 software copy. Thus, after performing a successful system rename procedure, the name of your DB2 software copy and its installation location will be the same as for your source system. This DB2 copy name or the installation location path might contain your old DBSID.

The DB2 copy name is referred to under DB2 services, so you might see the old DBSID in your DB2 services.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Follow-Up Activities

If you would like to rename your DB2 software copy or change the installation location, follow the instructions below for installing a new DB2 copy. Note, however, that these steps are purely optional and are not required for the system to run correctly.

Procedure

1. To change the DB2 software path, proceed as follows: a. Copy the file

..\ESE\win_ese.rsp

from the RDBMS medium to a local directory.

b. Edit the file win_ese.rsp

as follows:

○

Replace

@DB2SOFTWAREPATH@

as follows:

<local_drive_for_database_software>:\db2\db2<dbsid>\db2_software

You may also choose a different location for

@DB2SOFTWAREPATH@

○

Replace

@DBSID@

with

<DBSID>

○

Replace

@DOMAIN@

with

<WIN_DOMAIN_NAME>

, where

<WIN_DOMAIN_NAME>

is the Windows domain name of this domain installation.

If your system is installed locally, leave

@DOMAIN@

empty. For example, change it as follows:

DB2_ADMINGROUP_DOMAIN=@DOMAIN@

DB2_ADMINGROUP_DOMAIN= c. Change to the local directory to which you copied file win_ese.rsp

d. Enter the following command:

<Fully_qualified_RDBMS_medium_path>\ESE\image\setup /i en /l db2setup.log /m /u win_ese.rsp

2. To update the DB2 instance to the newly installed DB2 copy, issue the db2iupdt command from the new

DB2 copy:

<Path to new DB2 copy>\bin\db2iupdt.exe <instance name> /u:

<db2sid>,<password> /p: <profile directory> /a: SERVER_ENCRYPT

For example, if your new DBSID is

XXX

and your new DB2 copy is located in

D:\db2\newCopy

\db2_software

, execute the following:

D:\db2\newCopy\db2_software\bin\db2iupdt.exe db2xxx /u: db2xxx,mypassword /p: D:

\db2\db2xxx /a: SERVER_ENCRYPT

5.1.3.3 Performing Follow-Up Activities for SAP HANA

Database

This section contains follow-up steps required for SAP HANA after the system rename has completed.

Procedure

Currently there are no follow-up steps required.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Follow-Up Activities

C U S T O M E R

5.1.3.4 Performing Follow-Up Activities for SAP ASE

After the rename, the connection to transaction

DB02/DBACOCKPIT

might not work. To enable it, perform the steps described below.

Procedure

1. Run transaction

DBCO

and switch to an edit mode.

2. Change the user to sapsa

3. Enter the password for this user and save it.

Next Steps

After performing the steps listed above, you should be able to run transaction

DB02/DBACOCKPIT

5.1.3.5 Performing Follow-Up Activities for DB2 for z/OS

After the system rename, you have to perform the steps listed in this section.

Procedure

After the system rename, you must change the value of the

dbs/db2/dsn_alias

entry in the instance profiles from the source

to the value of the target

5.1.3.6 Performing Follow-Up Activities for the Oracle

Database

This section contains follow-up steps required for Oracle after the system rename has completed.

Procedure

If you have chosen to enable Oracle Database Vault, make sure that you perform the required configuration

steps. For more information, see Implementing Oracle Database Vault with the Installer [page 64]

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Follow-Up Activities

5.1.4 Starting the SAP System

After the system rename procedure has finished you have to start the primary application server instance of the renamed system. Then, after you have performed all follow–up activities, you have to restart all instances of the renamed system.

For more information about how to start and restart an SAP system, see

Additional Information Starting and Stopping the SAP System

in the installation guide for your operating system platform and database at http://support.sap.com/sltoolset

System Provisioning Installation Option

or the SAP Library at:

Table 8:

SAP Release and SAP Library Quick Link SAP Library Path (Continued)

●

SAP NetWeaver Composition Environment 7.1

http://help.sap.com/nwce71

●

SAP NetWeaver Composition Environment 7.1 in cluding Enhancement Package 1 http://help.sap.com/nwce711

●

SAP NetWeaver Composition Environment 7.2

http://help.sap.com/nwce72

System Administration and Maintenance Information

Administrator’s Guide Administration of SAP NetWeaver CE

General System Administration Starting and Stopping the

Application Server Java (AS Java)

●

SAP NetWeaver 7.3

http://help.sap.com/nw73/

●

SAP NetWeaver 7.3 including Enhancement Package

1 http://help.sap.com/nw731

●

SAP NetWeaver 7.4

http://help.sap.com/nw74

●

SAP NetWeaver 7.5

http://help.sap.com/nw75

Application Help Function-Oriented View Solution Life

Cycle Management Starting and Stopping SAP Systems

Based on SAP NetWeaver

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Follow-Up Activities

C U S T O M E R

6 Additional Information

6.1 Performing a Domain Installation Without Being a

Domain Administrator

You normally perform a domain installation of the SAP system with a user who is a member of the domain

Admins

group, as described in

Required User Authorization for Running the Installer [page 26] . If for any

reason, the account used for the installation is not a member of the domain

Admins

group, you can perform the installation with a domain user who is a member of the local

Administrators

group. In this case, the domain administrator has to prepare the system appropriately for you. The domain administrator can perform the following steps either using the installer or manually:

1. Create the new global group

SAP_<SAPSID>_GlobalAdmin

2. Create the two new SAP system users

<sapsid>adm

and

SAPService<SAPSID>

3. Add the users

<sapsid>adm

and

SAPService<SAPSID>

to the newly created group

SAP_<SAPSID>_GlobalAdmin.

4. The following steps are only required for IBM DB2 for Linux, UNIX and Windows:

1. Create the database administration group db<dbsid>adm

, the database control group db<dbsid>ctl

, the database maintenance group db<dbsid>mnt

, and the database monitoring group db<dbsid>mon

2. Create the new DB2 database administrator db2<dbsid>

3. Add users

<sapsid>adm

and

SAPService<SAPSID>

to the group db<dbsid>ctl

. Add the user db2<dbsid>

to the group db<dbsid>adm

4. If you want the database connect user ( sap<sapsid>db

) to be part of the

<sapsid>adm

domain, you have to add it to the group db<dbsid>mon

manually.

Caution

You can specify the name of the Java connect user ( sap<sapsid>db

) independently from the SAP schema name during the dialog phase of the installer.

We recommend, however, that you keep the names of the connect user and the database schema identical in standard use cases. If you are performing a system copy using database means, DB2 is not able to change the schema name and you can then choose a connect user name that is different from the schema name.

Make sure that you choose the correct value during the dialog phase of the installer.

5. Create the database extended security groups

DB2ADMNS_<DBSID>

and

DB2USERS_<DBSID>

6. Add users db2<dbsid>

and

SAPService<SAPSID>

to the database extended security group

DB2ADMNS_<DBSID>

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

C U S T O M E R

Note

The installer creates the operating system user for the SAP Host Agent by default as a local user that is not a member of the local

Administrators

group. If you want to create this user manually as a domain user, you must perform the following steps:

Creating the SAP Host Agent User and Group Manually

1. Create the new global group

SAP_SAP_GlobalAdmin

2. Create the SAP system user sapadm

3. Add the user sapadm

to the newly created group

SAP_SAP_GlobalAdmin

However, for security reasons we strongly recommend you to create this user as a local user.

Prerequisites

●

You must be domain administrator to perform the required steps.

●

You must have installed the feature

Remote Server Administration Tools

as follows:

○

Windows Server 2012 (R2) and higher:

Open PowerShell in elevated mode, and enter the following command:

add-windowsfeature RSAT-ADDS

○

Windows Server 2008 (R2):

1. Choose

Start Administrative Tools Server Manager

2. In the

Server Manager

window, select

Features

3. Select the feature

Remote Server Administration Tools Role Administration Tools Active

Directory Domain Services Tools

Procedure

Creating the Required Users and Groups Using the Installer

On the host where the SAP system is to be installed, the domain administrator starts the installer as described

in Running the Installer [page 38]

and chooses

Generic Installation Options <Database> Preparations

Operating System Users and Groups

to have the group and users created automatically.

Creating the Required Users and Groups Manually

Note

To create the users and groups specific to the SAP Host Agent, you must follow the procedure below, and replace the users and groups with those for the SAP Host Agent.

Creating the New Global Group SAP_<SAPSID>_GlobalAdmin

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

C U S T O M E R

Perform the following steps:

●

Windows Server 2012 (R2) and higher:

Open PowerShell in elevated mode, and enter the following command:

net group SAP_<SAPSID>_GlobalAdmin /add /domain

●

Windows Server 2008 (R2):

1. Log on as domain administrator.

2. Start the

Active Directory Users and Computers Console

by choosing:

Start Control Panel Administrative Tools Active Directory Users and Computers

3. Right-click

Users

Tree

, and choose

New Group

4. Enter the following:

Group name

SAP_<SAPSID>_GlobalAdmin

5. Select the following:

Group scope

: Global

Group type

: Security

6. Choose

Creating the New SAP System Users <sapsid>adm and SAPService<SAPSID>

Perform the following steps:

●

Windows Server 2012 (R2) and higher:

1. Open PowerShell in elevated mode.

2. Create the

<sapsid>adm

user with the following command:

net user <sapsid>adm <Password> /add /domain

3. Create the

SAPService<SAPSID>

user with the following command:

net user SAPService<SAPSID> <Password> /add /domain

●

Windows Server 2008 (R2):

1. In

Active Directory Users and Computers Console

, right-click

Users

Tree

and choose:

New User

2. Enter the following:

Table 9:

Field Input for <sapsid>adm Input for SAPService<SAPSID>

First name:

None None

Initials:

Last name:

None

3. Choose

Next

and enter the following:

Password

<Password>

Confirm password

<Password>

4. Select

Password never expires

Note

Make sure that no other options are selected.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

5. Choose

Next Finish

Adding the Manually Created Users to Groups

Note

To add the users specific to the SAP Host Agent to the relevant groups, you must follow the procedure below, and replace the users and groups with those for the SAP Host Agent.

Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group

●

Windows Server 2012 (R2) and higher:

Open PowerShell in elevated mode, and enter the following command:

net group SAP_<SAPSID>_GlobalAdmin <sapsid>adm /add /domain

●

Windows Server 2008 (R2):

1. In the

Users

folder, double-click the newly created user account

<sapsid>adm

in the list on the right.

2. Choose

Member Add

3. Select the new

SAP_<SAPSID>_GlobalAdmin

group and choose

Add

to add it to the list.

Note

By default, the user is also a member of the

Domain Users

group.

4. Choose

twice.

Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group

●

Windows Server 2012 (R2) and higher:

Open PowerShell in elevated mode, and enter the following command:

net group SAP_<SAPSID>_GlobalAdmin SAPService<SAPSID> /add /domain

●

Windows Server 2008 (R2):

1. In the

Users

folder, double-click the newly created user account

SAPService<SAPSID>

in the list on the right.

2. Choose

Member Add

3. Select the new

SAP_<SAPSID>_GlobalAdmin

group.

4. Choose

Add

to add it to the list, and then

5. Choose

to close

SAPService<SAPSID>Properties

6. Close the

Active Directory Users and Computers Management Console

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

C U S T O M E R

6.2 Implementing Oracle Database Vault with the Installer

The installer supports Oracle Database Vault. This section provides information about implementing Oracle

Database Vault (DV) with the installer.

Caution

Although Oracle Database Vault is already available in the installer and documented in this guide, it is not yet released to customers until further notice. For more information, see the

Current Restrictions

section in

SAP Note 1680045 .

Prerequisites

●

Your Oracle database version must be 12.1 or higher.

●

Check the prerequisites, restrictions, and patch requirements as listed in SAP Note 2218115 .

Context

For system rename, the DV is already installed in the source database and must be first disabled to complete the procedure. It can be enabled before the scenario is completed.

DV requires the following addional users:

● secadmin

● secacctmgr

These users are created by the installer.

For more information about Oracle Database Vault, see the Oracle Database documentation referred to in SAP

Note 2218115 .

Procedure

1. Start the installer and choose the system rename option for your system variant as described in

Running the Installer [page 38]

2. On the

Oracle Database Configuration

screen - if DV is installed on the source system - mark the checkbox

Oracle Database Vault is installed and enabled

Later during the system rename, the installer disables the DV. For this you have to provide the password of the secadmin

user. The secadmin

user grants some rights to the sysdba

user. After the rename is finished, these rights are revoked again from the sysdba

user and the DV is enabled again if this checkbox is set. Otherwise DV is installed but not enabled.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

Next Steps

Configure Oracle Database Vault as described in SAP Note 2218115 .

6.3 Using PowerShell

SAP uses Windows PowerShell to run and describe Windows commands.

For Windows Server 2012 (R2) and higher, SAP only uses Windows PowerShell to run and describe Windows commands.

Windows PowerShell is a powerful tool integrated in the Windows operating system. It uses object-oriented methodology, which allows fast and stable script development.

For more information about the Windows PowerShell, see: http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx

There you can find links to the online help, online documentation, scripting repository, downloads, and blogs.

If you want to use the PowerShell feature, note the following:

●

Windows Server 2016

Windows Server 2016 contains PowerShell 5.0

You can update to PowerShell 5.0 (search the internet for

Windows Management Framework 5.0

●

Windows Server 2012 R2

Windows Server 2012 R2 contains PowerShell 4.0.

●

Windows Server 2012

Windows Server 2012 contains PowerShell 3.0.

You can update to PowerShell 4.0 (search the internet for

Windows Management Framework 4.0

●

Windows Server 2008 R2

Windows Server 2008 R2 contains PowerShell 2.0.

For more information about PowerShell 2.0, see http://support.microsoft.com/kb/968929 .

You can update to PowerShell 3.0 or 4.0 (search the internet for

Windows Management Framework 3.0

Windows Management Framework 4.0

●

Windows Server 2008

You have to activate the PowerShell feature with

Start Administrative Tools Server Manager

Features

On Windows Server 2008, you can update to PowerShell 3.0 (search the internet for

Windows

Management Framework 3.0

How to Start PowerShell

Caution

Make sure that you start the PowerShell in administrator mode.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

C U S T O M E R

●

Windows Server 2012 (R2) and higher

Open the command prompt and enter the command:

powershell.exe

To start PowerShell on Windows Server 2008 (R2), you have the following options:

●

From the command prompt, by entering the command:

powershell.exe

●

From the

Start

Menu:

○

PowerShell 1.0:

Choose

Start All Programs Windows PowerShell 1.0

Windows PowerShell

○

PowerShell 2.0:

Choose

Start All Programs Windows PowerShell Windows PowerShell

How to Work with PowerShell

Most commands that are used in cmd.exe

are also available in the PowerShell (defined as aliases).

You can use well-known commands, such as cd

, type

, copy

, move

, mkdir

, delete

, rmdir

. There is also online help available, which you can access by typing the command:

help

(or

help <command>

This is a list of differences between PowerShell and cmd.exe

●

Before you can run PowerShells scripts (text files with the file extension

.ps1

that contain PowerShell statements), you might have to change the default security setting to allow the execution of non-signed scripts as follows:

set-executionpolicy ("unrestricted")

●

By default, when double-clicking PowerShell scripts (

.PS1

files) in the Windows explorer, this does not execute the script as is the default for

.cmd

files, but opens the script in an editor. If you want to activate automatic script execution after a double-click, you have to change the value

HKEY_CLASSES_ROOT

\Microsoft.Powershellscript.1\Shell\Open\Command

from notepad.exe

to the full path of the

PowerShell executable.

●

The output of PIPE commands is not just a stream of characters (strings) but a stream of objects. You can easily access the properties and methods for these objects (see the process list DLL example below).

●

The current working directory is not part of the directory search path that the PowerShell looks at for scripts and programs. The PowerShell only searches directories listed in the environment variable path.

Therefore, you might have to run a local program with

./sapcontrol.exe

or specify its full path.

●

You can use the UNIX-like directory delimiters, such as cd /usr/sap/C11

●

You can have your current working directory in a UNC path ( cd \\sapglobalhost\sapmnt

●

The shell distinguishes between environment variables and shell variables:

○

Use of shell variables:

Definition:

$x="hello"

Reference:

write-host $x

○

Use of an environment variable:

Definition:

$env:x="hello"

Reference:

write-host $env:x

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

●

The PowerShell has an interesting container concept called ps-drives

. Within ps-drives

you can navigate in other objects, such as the registry or shell internal lists in the same way as you typically navigate in a file system ( cd, dir, del

, and so on).

dir env

: to get a list of environment variables dir variable

: to get the list of shell variables dir HKLM

: to get a list of registry keys in HKEY_LOCAL_MACHINE get-psdrive

to get a list of available ps-drives

●

Windows PowerShell has full access to the .NET runtime. You can directly access missing functions in the

PowerShell via .NET.

●

With Windows PowerShell, you can create GUI-class user interfaces using Windows forms.

PowerShell Commands

The following table lists some PowerShell commands that are available on Windows Server 2012 (R2) and higher:

Table 10:

Command Explanation

stop-service sap*

Stops all Windows services with service name starting with

“SAP”

Lists currently started processes on your system

get-process get-process | sort starttime | select last 1

Lists the last started process on your computer

get-process | sort starttime | select last 1 | format-list -proper *

Lists all properties of the last started process

get-process | sort starttime | select last 1 | get-member

Lists all process class members (properties and methods) of the last started process

get-process | %{$_.name;"-----------";

$_.modules}

$processes = (get-process | sort starttime)

Lists all processes, and the executables and DLLs the proc esses loaded

Defines a shell variable

$processes

, which contains an ar ray of process objects

$processes.length

$processes[$processes.length-1].kill()

(dir a.txt).set_attributes("readonly")

The number of processes in the array (is equivalent to the number of processes on your computer)

Invokes the kill method (terminate process) of the last started process

Sets the file a.txt

to “read-only”

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Additional Information

C U S T O M E R

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. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

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 in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language

As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as

"sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. 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.sap.com/disclaimer ).

Open Source Software and Third Party Components

Please refer to https://scn.sap.com/docs/DOC-42044 for information respecting open source software components made available by SAP as part of SAP

NetWeaver and any specific conditions that apply to your use of such open source software components. Please refer to https://scn.sap.com/docs/DOC-42045 for information relating to SAP’s use of third party software with or within SAP NetWeaver.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Important Disclaimers and Legal Information

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 Java on Windows

Important Disclaimers and Legal Information

C U S T O M E R

go.sap.com/registration/ contact.html

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx

for additional trademark information and notices.

Bonjour ! Je suis un chatbot IA spécialement formé pour vous aider avec le SAP Software Provisioning Manager Manuel d'exploitation. J'ai soigneusement étudié le document et je peux vous aider à trouver les informations dont vous avez besoin ou expliquer le contenu en termes clairs et simples. Que vous recherchiez des conseils sur des fonctionnalités spécifiques, des étapes de dépannage ou une utilisation générale, n'hésitez pas à poser vos questions. Plus vous fournissez de détails sur vos préoccupations ou besoins, plus je pourrai vous aider avec précision et efficacité.

Assistant en train d''écrire

L''assistant n''est plus disponible. Veuillez réessayer plus tard.

Il semble que vous ayez accédé à un document rédigé en plusieurs langues, dont une qui n''est pas votre langue maternelle. Vous pouvez utiliser les liens suivants pour masquer temporairement les pages sans la langue que vous préférez.