standalone gateway on windows for sap systems

Installation and Rename GuideDocument version: 2.0 – 2015-10-12

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverValid for SAP NetWeaver 7.1 to 7.5

CUSTOMER

Typographic Conventions

Table 1

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved.

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverTypographic Conventions

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D123456%26_NLANG%3Den%26_NVERS%3D0


Document History

CautionBefore you start the implementation, make sure you have the latest version of this document that is available

on the SAP Service Marketplace at service.sap.com/instguides .

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

Table 2

Version Date Description

2.0 2015-10-12 Updated version for software provisioning manager 1.0 SP09 (SL Toolset 1.0 SP14)





1.5 2014-04-11 Updated Version




1.1 2013-04-17 Minor Updates

1.0 2013-04-12 Initial version

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverDocument History

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved. 3

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 About Software Provisioning Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . 8 Hardware and Software Requirements Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 Basic Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Checking the Windows File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.2 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Required User Authorization for Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 Performing a Domain Installation Without Being a Domain Administrator . . . . . . . . . . . . . . . . . . . . . 173.5 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.6 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.7 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Prerequisites for Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.2 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.3 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 How to Avoid Automatic Logoff by the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Interrupted Processing of the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5 Post-Installation Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.1 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.2 Checking and Changing the Paging File Settings on Windows Server 2012 (R2) . . . . . . . . . . . . . . . . . 396.3 Starting and Stopping with the SAP Microsoft Management Console (SAP MMC) . . . . . . . . . . . . . . . 416.4 Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4


Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverContent

1 Introduction

1.1 About this Document

This documentation describes how to install a standalone gateway for SAP system products based on SAP NetWeaver 7.1 and higher using the installation tool software provisioning manager 1.0 SP09 (“installer” for short), which is part of SL Toolset 1.0 SP14.

You can find a complete list of supported SAP system products in SAP Note 1680045 .

Each instance of an SAP system with an ABAP application server has a gateway. The gateway enables communication between work processes and external programs, as well as communication between work processes from different instances of SAP systems.

You can also install a standalone gateway. With the standalone gateway, you can install the gateway service separately from the SAP system. In this case, the SAP system can access each external gateway under a different RFC connection.

NoteThere is no difference between a standalone gateway instance for a Unicode system and a standalone gateway for a non-Unicode system.

1.2 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 (see Preparing the Dual-Stack Split Media [external document]). 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 . As a result, “SAPinst” has 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.exeIn 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.

1.3 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation.

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverIntroduction





Make sure that you have the up-to-date version of each SAP Note which you can find in the SAP Service

Marketplace at service.sap.com/notes .

Table 3: SAP Notes for the Installation

SAP Note Number Title Description

1680045 Release Note for Software Provisioning Manager 1.0

Remarks, annotations, and corrections discovered after publication of the documentation Software Provisioning Manager

1708600 Standalone Gateway Installation for SAP Systems Based on SAP NetWeaver 7.1 and higher

Additional Information about standalone gateway installation.

1.4 Accessing the SAP Library

The references to SAP NetWeaver Library documentation in this installation guide always refer to the following on SAP Help Portal:

Table 4

Product and Release SAP Library Path

SAP NetWeaver 7.0 help.sap.com/nw70 Application Help

SAP NetWeaver 7.0 including Enhancement Package 1

help.sap.com/nw701 Application Help





● SAP NetWeaver Mobile 7.1

● SAP NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0

help.sap.com/nwmobile71 Application Help

NoteSince the SAP NetWeaver Mobile 7.1 Library is the only available SAP Library for ABAP systems based on SAP NetWeaver 7.1, in this guide we always refer to it also for SAP NetWeaver 7.1 for Banking Services from SAP 5.0 and 6.0.

6



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fnotes



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw70




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnwmobile71

Product and Release SAP Library Path

● SAP NetWeaver Mobile 7.1 including Enhancement Package 1

● SAP NetWeaver 7.1 including Enhancement Package 1 for Banking Services from SAP 5.0 and 6.0

help.sap.com/nwmobile711 Application Help

NoteSince the SAP NetWeaver Mobile 7.1 Library including Enhancement Package 1 is the only available SAP Library for ABAP systems based on SAP NetWeaver 7.1 including Enhancement Package 1, in this guide we always refer to it also for SAP NetWeaver 7.1 including Enhancement Package 1 for Banking Services from SAP 5.0 and 6.0.

SAP systems based on SAP NetWeaver Application Server ABAP 7.4

help.sap.com/soh <Product_and_Release> Application Help SAP

Library: English SAP NetWeaver

SAP systems based on SAP NetWeaver 7.4 help.sap.com/nw74 Application Help Function-Oriented View:

English

SAP systems based on SAP NetWeaver 7.5 help.sap.com/nw75 Application Help Function-Oriented View:

English

1.5 Naming Conventions

In this documentation, the following naming conventions apply:

NoteFrom a technical point of view, the standalone gateway is set up like an SAP system with its own SAP system ID (SAPSID), its own operating system users, and its own directory structure.

● installer refers to software provisioning manager 1.0.

● SAP system refers to standalone gateway.

● instance refers to astandalone gateway instance.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnwmobile711

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsoh



2 Planning

2.1 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system and the Gateway.

CautionIf your hosts do not fully meet the requirements, you might experience problems when working with the SAP system.

Process Flow

1. Check the Product Availability Matrix at service.sap.com/pam for supported operating system releases.

2. Check the hardware and software requirements using the Prerequisite Checker:

○ Standalone (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 8].

○ Integrated in the installer (mandatory) as part of the installation process

For more information, see Running the Installer [page 25].

NoteFor the most recent updates to the Prerequisite Checker, always check SAP Note 855498 .

3. If you want to use the standalone Gateway for a production system, the values provided by the Prerequisite Checker and the hardware and software requirements checklists are not sufficient. In addition, do the following:

○ You use the hardware sizing information available at service.sap.com/sizing .

○ You contact your hardware vendor, who can analyze the load and calculate suitable hardware sizing depending on:

○ The set of applications to be deployed

○ How intensively the applications are to be used

○ The number of users

2.1.1 Running the Prerequisites Check in Standalone Mode (Optional)

When you install an SAP system, the installer automatically starts the prerequisites check and checks the hardware and software requirements in the background. As an optional step during planning, you can also run the

8


Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverPlanning

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fpam


http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsizing

prerequisites check in standalone mode to check the hardware and software requirements for your operating system and the SAP instances before the actual installation.

RecommendationWe recommend that you use both the prerequisites check and the requirements tables for reference.

Procedure

1. Copy the installer to the host where you want to run the prerequisites check as follows:

1. Download the latest version of the Software Provisioning Manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR from:

support.sap.com/swdc Support Packages and Patches A - Z Index S SL Toolset SL Toolset <Release> Entry by Component Software Provisioning Manager Software Provisioning Mgr 1.0Support Package Patches <OS>

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

SAPCAR -xvf <Path_To_Download_Directory>\<Archive>.SAR -R <Unpack_Directory>2. Start the installer as described in Running the Installer [page 25].

3. On the Welcome screen, choose <SAP_Product> <Database> Preparations Prerequisites Check .

4. Follow the instructions in the installer dialogs and enter the required parameters.

NoteFor more information about each parameter, position the cursor on the parameter field and choose F1 in the installer.

After you have finished, the Parameter Summary screen appears. This screen summarizes all parameters that you have entered and that you want to have checked. If you want to make a change, select the relevant parameters and choose Revise.

5. To start the prerequisites check, choose Next.

Result

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results in file prerequisite_checker_results.html, which you can find in the installation directory.

2.1.2 Hardware and Software Requirements Tables

The standalone gateway host must meet the following requirements:

Table 5: Hardware Requirements

Hardware Requirement Requirement How to Check

Minimum disk space ● x64: 2.5 GB (not including paging file) To check disk space:




http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc


● (IA64): 5 GB (not including paging file)

● Temporary disk space for every required installation medium that you have to copy to a local hard disk:

4.3 GB

● Windows Server 2012 (R2):

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

get-volume2. Check the value SizeRemaining of

the disk you want to install on.


1. Choose Start All Programs

Administrative Tools Storage

Computer Management Disk

Management .

2. Right-click the drive and choose Properties.

● Windows Server 2003:


Administrative Tools Computer

Management Disk

Management .

2. Right-click the drive and choose Properties.

Minimum RAM 4 GB To check RAM:


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

Get-WmiObject Win32_ComputerSystem

● Windows Server 2008 (R2) or Windows Server 2003:

Choose Start Control Panel

System .

NoteWindows Server 2008 R2:

If System is not visible, change View by: from Category into Large icons.

Paging file size For more information, see SAP Note 1518419 . To check paging file size:


For more information, see Checking and Changing the Paging File Settings on Windows Server 2012 (R2) [page 39]


10





1. Choose Start Control Panel

System .

NoteWindows Server 2008 (R2)

If System is not visible, change View by: from Category into Large icons.

2. Windows Server 2008 (R2)

Choose Advanced system settings.

3. Windows Server 2003:

Choose Advanced.

4. In section Performance, select

Settings... Advanced .

5. If required, in section Virtual memory, choose Change.

NoteDo not select Automatically managed paging file size for all drives.

Processing units The number of physical or virtual processing units usable by the operating system image must be equal to or greater than 2.

Examples of processing units are processor cores or hardware threads (multithreading).

In a virtualized environment, ensure that adequate processor resources are available to support the workloads of the running SAP systems.

Suitable backup system

Table 6: Software Requirements

Software Requirement Requirement How to Check

Windows operating system

● 64-bit version of one of the following Windows Server Editions:

○ Windows Server 2012 (R2):

○ Windows Server Standard Edition

○ Windows Server Datacenter Edition

○ Windows Server 2008 (R2) or Windows Server 2003:

To check your Windows version:



Get-WmiObject Win32_OperatingSystem | select caption




Software Requirement Requirement How to Check

○ Windows Server Standard Edition

○ Windows Server Enterprise Edition

○ Windows Server Datacenter Edition

○ Windows Server 2008 (R2) only:

Windows Server 2008 (R2) for Itanium-Based Systems Edition

CautionFor up-to-date information on the released and supported operating system versions for your SAP product and database, see the Product Availability

Matrix (PAM) at support.sap.com/pam

.

CautionMake sure that you install the English language pack so that your support requests can be handled quickly.

● For any version of Windows Server, you need the latest supported service pack



Accessories Command Prompt

2. Enter the command winver

2.2 Basic Installation Parameters

The table below lists the basic input parameters that are prompted by the installer. For all other SAP system parameters, use the F1 help in the installer screens.

Standalone Gateway ParametersTable 7

Parameters Description

SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.

CautionChoose your SAP system ID carefully. You cannot change the SAP system ID after the installation.

Make sure that your SAP system ID:

● Is unique throughout your organization

● Consists of exactly three alphanumeric characters

● Contains only uppercase letters

12



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam


● Has a letter for the first character

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

CautionYou must choose an SAP system ID that is different from the SAP system ID of the central instance of the SAP system the Gateway belongs to.

Instance Number for the standalone gateway

Instance Number:

Technical identifier for internal processes. Consists of a two-digit number from 00 to 97. The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers.

CautionDo not use 43, 60, 89 for the instance number of the standalone gateway.

Virtual Host Name Virtual host name (network name) of the SAP<SAPSID> cluster group

If you provide a virtual host name in the <Instance_Name> Virtual Host field of the

screen of an instance, this instance is installed with the given virtual host name. After the installation has completed, all application servers can use this virtual host name to connect to the instance. The virtual host name is also a global host name. If you do not provide the virtual host name, the instance is installed automatically using its physical host name.

You must have already reserved the virtual host name (network name) and its IP address on a DNS server before you run the installer. For more information, see Using Virtual Host Names [page 22].

NoteFully qualified host names, IPv4, IPv6 are not accepted as virtual host names.

Alternatively you can assign virtual host names also by starting the installer with the SAPINST_USE_HOSTNAME property. For more information, see Running the

Installer [page 25].

Operating System Users The passwords of the operating system users must comply with the Windows password policy. The installer processes the passwords of operating system users as follows:

● If the operating system users do not exist, SAP creates the following users:

○ <sapsid>admThis user is the SAP system administrator user. It is a member of the local Administrators group.

○ SAPService<SAPSID>This user is the Windows account to run the SAP system. It is not a member of the local Administrators group.

○ sapadm






The host agent user sapadm is used for central monitoring services. The

installer creates this user by default as a local user although it is not a member of the local Administrators group.

If required, you can change this user to become a domain user on the parameter summary screen. For more information, see Performing a Domain Installation Without Being a Domain Administrator [page 17]. For security reasons, however, SAP strongly recommends you to create this user as a local user.

The installer sets the master password for these users by default. You can overwrite and change the passwords either by using the parameter mode Custom or by changing them on the parameter summary screen.

● If the operating system users already exist, the installer prompts you for the existing password, except the password of these users is the same as the master password.

CautionMake sure that you have the required user authorization [page 16] for these accounts before you start the installation.

14



3 Preparation

3.1 Checking the Windows File System

You need to check that you are using the Windows file system NTFS on hosts where you want to install the SAP system and database. NTFS supports full Windows security and long file names.

NoteYou must use NTFS for an SAP system installation. Do not install the SAP directories on a FAT partition.

Procedure

1. Open the Windows Explorer.

2. Select the relevant disk.

3. Choose Properties General .

The system displays the type of file system in use.

4. Check that the file system is NTFS.

3.2 Reducing the Size of the File Cache

NoteThis step is not required if you use Windows Server 2008.

The Windows file cache competes directly with SAP programs for memory. Therefore, you need to adjust the file cache as described below.

Procedure

1. Choose Start Control Panel Network Connections Local Area Connections .

2. In the Local Area Connection Status dialog box, choose Properties.

3. In the Local Area Connection Properties dialog box, double-click File and Printer Sharing for Microsoft Networks.

4. Select Maximize data throughput for network applications.

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverPreparation



CautionIf you cannot select File and Printer Sharing for Microsoft Networks, this option has not yet been installed. To install it, you need the Windows Server CDs.

5. To confirm your entries, choose OK.

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

Procedure

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

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.

16



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

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.

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

NoteThe installer creates the operating system users for the SAP Host Agent and the Diagnostics Agent by default as local users that are not members of the local Administrators group. If you want to create these users manually as domain users, 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.

● Creating the Diagnostics Agent Users and Group Manually:

1. Create the new global group SAP_<DASID>_GlobalAdmin.

2. Create the two new SAP system users <dasid>adm and SAPService<DASID>.

3. Add the users <dasid>adm and SAPService<DASID> to the newly created group SAPService<DASID>.

However, for security reasons we strongly recommend you to create these users as local users.




Prerequisites

● You must be domain administrator to perform the required steps.

● Windows Server 2008 (R2) and Windows Server 2012 (R2):

You must have installed the feature Remote Server Administration Tools as follows:

○ Windows Server 2012 (R2):


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

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

Creating the New Global Group SAP_<SAPSID>_GlobalAdmin

Perform the following steps:



net group SAP_<SAPSID>_GlobalAdmin /add /domain● Windows Server 2003 or 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 .

NoteWindows Server 2003:

If you cannot find Active Directory Users and Computers, start it as follows:

1. Choose Start Run and enter mmc.

2. Choose Console Add/Remove Snap-in... Add .

18



3. Select Active Directory Users and Computers.

4. Choose Add .

5. Choose Close OK

3. Right-click Users in Tree, and choose New Group .

4. Enter the following:

Group name: SAP_<SAPSID>_GlobalAdmin5. Select the following:

1. Group scope: Global

2. Group type: Security

6. Choose OK.

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

Perform the following steps:


1. Open PowerShell in elevated mode.

2. Create the <sapsid>adm user with the following command:

net user <sapsid>adm <Password> /add /domain3. Create the SAPService<SAPSID> user with the following command:

net user SAPService<SAPSID> <Password> /add /domain● Windows Server 2003 or Windows Server 2008 (R2):

1. In Active Directory Users and Computers Console, right-click Users in Tree and choose:

New User

2. Enter the following:

Table 8

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

First name: None None

Initials: None None

Last name: None None

3. Choose Next and enter the following:

Password: <Password>Confirm password: <Password>

4. Select Password never expires.

NoteMake sure that no other options are selected.

5. Choose Next Finish .




Adding the Manually Created Users to Groups

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

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



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.

NoteBy default, the user is also a member of the Domain Users group.

4. Choose OK twice.

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



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

5. Choose OK to close SAPService<SAPSID> Properties.

6. Close the Active Directory Users and Computers Management Console.

3.5 SAP Directories

The installer automatically creates the directories listed in the following figures and tables. Before running the installation, you have to set up the required file systems manually. In addition, you have to make sure that the required disk space for the directories to be installed is available on the relevant hard disks. The figure below assumes that you have set up one file system for the SAP system mount directory <sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which directories you want to set up separate file

20



systems. If you do not set up any file system on your installation host, the installer creates all directories in the root directory /. The installer prompts you only for the <sapmnt> directory during the installation.

Figure 1

The <INSTANCE> of the Gateway instance is G<Instance_Number>, for example G00.

SAP File Directories in Detail

NoteThe listed file system sizes are initial SAP requirements.

Depending on your operating system, you might also have to add space for administrative purposes.

Table 9

Directory Name Description Space Required

<Drive>:\usr\sap\<SAPSID>

\usr\sap is created and shared with the network share

sapmnt.

The \usr\sap directory contains general SAP software, global

and local (instance-specific) data.

For this, the following directories are created in usr\sap\<SAPSID>\SYS:

● global (contains globally shared data)

● profile (contains the profiles of the instance)

● exe (contains executable kernel programs)

The directory usr\sap\<SAPSID>\<INSTANCE> is the

directory of the instance:

The instance name (instance ID) of the Gateway instance is G<Instance_Number>, for example G00.

500 MB




Directory Name Description Space Required

<Drive>:\usr\sap\trans

\usr\sap\transThis directory contains SAP software for the transport of objects between SAP systems .

This value heavily depends on the use of your SAP system.

For the installation, it is sufficient to use 200 MB for each SAP system instance. You can enlarge the file system afterwards.

3.6 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to hide 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.

Prerequisites

● Make sure that the virtual host name can be correctly 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 .

Procedure

To install a non-high-availability system, proceed as described in SAP Note 1564275 .

3.7 Preparing the Installation Media

This section describes how to prepare the installation media, which are available as follows:

● The Software Provisioning Manager 1.0 archive containing the installer.

You always have to download the latest version of the Software Provisioning Manager 1.0 archive.

● The media containing the software to be installed, which are available as follows:

○ 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, as described at the end of this section.

For more information about which kernel version to use, see SAP Note 1680045 . In addition, check the Product

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

22






http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam

We also recommend that you read the document Understanding Kernel Releases for the SAP NetWeaver AS ABAP

at scn.sap.com/docs/DOC-54170 .

Prerequisites

Make sure the latest version of the SAPCAR archiving tool is available on each installation host.

You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files), which is the format of software lifecycle media and tools that you can download from the SAP software distribution center.

If required, you can download the latest version of SAPCAR from:

support.sap.com/swdc Support Packages and Patches A - Z Index S SAPCAR .

For more information about SAPCAR, see SAP Note 212876 .

The installer requests the related kernel media during the corresponding procedure. For more information about release and road map information around the kernel versions and their relationship to SAP NetWeaver support packages including important notes on downward compatibility and release dates, see the document

Understanding Kernel Releases for the SAP NetWeaver AS ABAP at scn.sap.com/docs/DOC-54170 .

Procedure

1. Identify the required media for your installation as listed below.

Table 10

Installation Installation Media

Standalone Gateway Installation ● Software provisioning manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR

● SAP Kernel:

Make sure that both the UC kernel and NUC kernel software are available:

○ UC Kernel: Folder K_<Version>_<N or U>_<OS> where U means Unicode and N means

non-Unicode.

2. Make the installation media available on the installation host as follows:

1. Download the latest version of the Software Provisioning Manager 1.0 archive SWPM10SP<Support_Package_Number>_<Version_Number>.SAR from:

support.sap.com/swdc Support Packages and Patches A – Z Index S SL Toolset SL Toolset <Release> Entry by Component Software Provisioning Manager Software Provisioning Manager 1.0 Support Package Patches <OS>

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

SAPCAR -xvf <Path_To_Download_Directory>\<Archive>.SAR -R <Unpack_Directory>3. Make the media containing the software to be installed available.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-54170



http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-54170


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.

○ If the user does not yet exist, you have to create the user manually before you install the SAP system.

3. If you want to perform target system installation in the context of a heterogeneous system copy you need a

migration key. You can generate it at support.sap.com/migrationkey .

24



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fmigrationkey

4 Installation

4.1 Prerequisites for Running the Installer

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

● 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 you have defined the most important SAP system parameters as described in Basic Installation Parameters [page 12] before you start the installation.

● Check that your installation host meets the requirements for the installation options that you want to install.

For more information, see Running the Prerequisite Checker [page 8].

● Make sure that the following ports are not used by other processes:

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

GUISERVER_DIALOG_PORT=<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=<Port_Number>

4.2 Running the Installer

This section describes how to run the installation tool Software Provisioning Manager 1.0 (the “installer” for short). Software Provisioning Manager 1.0 includes a GUI client and a GUI server, which both use Java. In the following, GUI client and GUI server are called the “installer GUI”.

This procedure describes an installation where the installer and the installer GUI are running on the same host.

Prerequisites

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

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverInstallation



Procedure

1. Log on to the installation host using an account with the required user authorization to run the Installer [page 16].

2. Make the installation media available.

For more information, see Preparing the Installation Media [page 22].

3. Start the installer by double-clicking sapinst.exe from the directory to which you unpacked the file SWPM10SP<Support_Package_Number>_<Version_Number>.SAR.

The installer GUI starts automatically by displaying the Welcome screen.

NoteIf you need to assign a virtual host name to the instance to be installed and you do not want to assign it by entering it as a parameter using the installer screens (see Basic Installation Parameters [page 12]), you can alternatively assign it as follows:

1. Open a command prompt or PowerShell window in elevated mode and change to the directory to which you unpacked the Software Provisioning Manager archive.

2. Start the installer with the following command:

sapinst.exe SAPINST_USE_HOSTNAME=<Virtual_Host_Name> (in a command prompt)

.\sapinst.exe SAPINST_USE_HOSTNAME=<Virtual_Host_Name> (in PowerShell)

For more information, see Using Virtual Host Names [page 22].

4. On the Welcome screen, execute the following options in the following sequence:

○ Perform the following recommended preparations:

○ Go to Generic Installation Options and choose:

Table 11

Option Description

Verify Signed Media The digital signature ensures that the signatory of a digital document can be identified unambiguously and the name of the signatory is documented together with the signed document, the date, and the time. It is recommended to check the software integrity by performing a digital signature check for downloaded media and packages before using it with Software Provisioning Manager.

For more information, see SAP Note 1979965 .

○ To install a new standalone gateway instance, go to <Product> <Database> and choose:

Table 12

Option Description

Prerequisites Check Checks your hardware and software requirements before you start the installation.

For more information, see Running the Prerequisites Checker in Standalone Mode [page 8].

SAP Systems

Standalone Engines

Gateway

Installs a standalone gateway instance on this host

26




Option Description

With the standalone gateway, you can install the gateway separately from the SAP system. In this case, the SAP system can access each external gateway under a different RFC connection.

○ To rename an existing standalone gateway instance, go to System Rename and choose:

Table 13

Option Description

PreparationsOperating System Users

and Groups

Creates all operating system accounts for the standalone gateway instance to be renamed

In most cases this is optional. However, you have to execute this option if you want to use global accounts that are configured on a separate host or if you want to install an instance on HP-UX.

Preparations Run Prerequisites Check for

System Rename

Runs the pre-install phase and prerequisite checks

For more information, see Running the Prerequisites Checker in Standalone Mode [page 8].

Distributed SystemSystem Rename for

Gateway Instance

Executes system rename for an existing standalone gateway instance.

○ To uninstall an existing standalone gateway instance, go to Generic Installation Options<Database> Uninstall and choose:

Table 14

Option Description

Uninstall - SAP Systems or

Single Instances

Choose this option to uninstall a standalone gateway instance.

For more information, see Uninstall [page 42].

5. Choose Next.

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

The installer restarts automatically.

7. Follow the instructions on the installer screens and enter the required parameters.

NoteTo find more information on each parameter during the input phase of the installation, position the cursor on the required parameter and press F1 .

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

8. To start the installation, choose Start.

The installer starts the installation and displays the progress of the installation. When the installation has finished, the installer shows the message: Execution of <Option_Name> has completed.

9. We recommend deleting all files in the directory %userprofile%\.sdtgui.

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




4.3 Additional Information About the Installer

The following sections provide additional information about the installer:

● Useful Information About the Installer [page 28]

● How to Avoid Automatic Logoff by the installer [page 29]

● Interrupted Installation [page 30]

● Performing a Remote Installation [page 31]

● Starting the Installer GUI Separately [page 33]

● Running the Installer in Accessibility Mode [page 35]

● Troubleshooting with the Installer [page 36]

4.3.1 Useful Information About the Installer

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

CautionIf 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● If you need to run the installer in accessibility mode, proceed as described in Running the Installer in

Accessibility Mode [page 35].

● If required, stop the installer by choosing SAPinst Exit Process in the installer GUI menu.

NoteIf you need to terminate the installer, choose File Close GUI only in the menu of the Program Starter window.

● If you want to install an SAP system in unattended mode, see SAP Note 950619 .

28




4.3.2 How to Avoid Automatic Logoff by the Installer

When you install the SAP system, the installation tool checks whether the user account used for the installation has the required privileges and authorization.

For a domain installation, the account needs to be both a member of the local Administrators group and the domain Admins group. For a local installation, the account needs to be a member of the local group Administrators group.

In both cases, the user account must be authorized to do the following:

● Act as part of the operating system

● Adjust memory quotas for a process

● Replace a process level token

If the user account does not have these rights assigned, the installer assigns them and automatically logs the account off to activate them. To avoid the installer logging the account off, you can set these rights manually before you start the installation.

Procedure

You perform the following steps to assign these rights to the user account used for the installation.

CautionBe aware that domain policies override locally defined policies. This means that if you want to grant domain administrator rights to a user who belongs to the local Administrators group, make sure that you have also defined domain administrator rights for this user on domain level.

1. Windows Server 2012 (R2): Press Ctrl + Esc and choose Administrative Tools Local Security Policy .

NoteServer Core for Windows Server 2012 (R2): To use and perform this task in a PowerShell, you can copy ntrights.exe from a Windows Server 2003 server to your Windows Server 2012 (R2) system.

2. Windows Server 2003 and Windows Server 2008 (R2): Choose Start Control Panel Administrative Tools Local Security Policy .

3. In the Local Security Settings window, choose Local Policies User Rights Assignment. .

4. Double-click the required right under Policy and choose Add User or Group.

5. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.

6. Confirm your entry and then repeat the steps for each remaining policy that the user requires for the installation.

7. Log off and log on again to apply the changes.

More Information

Required User Authorization for Running the Installer [page 16]




4.3.3 Interrupted Processing of the Installer

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

● An error occurred during the Define Parameters or Execute phase:

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

● You interrupted the installation by choosing Exit Process in the SAPinst menu.

CautionIf 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 15

Option Definition

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

This is possible because the installer records 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.

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

Continue The installer continues the installation from the current point.

View Log Access installation log files.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation.

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

2. Make sure that the installation media are still available on the installation host.


30



RecommendationMake the installation media available locally . For example, if you use 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 file SWPM10SP<Support_Package_Number>_<Version_Number>.SAR.

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

5. On the What do you want to do? screen, decide between the following alternatives and continue with Next:

Table 16

Alternative Behavior

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

The following naming convention is used for the backup directory:

log_<Day>_<Month>_<Year>_<Hours>_<Minutes>_<Seconds>

Examplelog_01_Oct_2008_13_47_56

NoteAll actions taken by the installation before you stopped it (such as creating directories or users) are not revoked.

CautionThe 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 old option The installer continues the interrupted installation from the point of failure.

4.3.4 Performing a Remote Installation

You use this procedure to install your SAP system on a remote host. In this case, the installer and the GUI server run on the remote host, and the installer GUI client (the “installer GUI” for short) runs on the local host. The local host is the host from which you control the installation with the installer GUI.

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


You can run the installer GUI on a PC with 32-bit while the installer is running on a 64-bit installation host. For more information, see Starting the Installer GUI Separately [page 33].

Prerequisites

● The remote host meets the prerequisites for starting the installer as described in Prerequisites for Running the Installer [page 25].

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

● Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Starting the Installer GUI Separately [page 33].

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

Procedure

1. Log on to your remote host as a user that has the required authorization for running the installer [page 16].

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


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

4. Check the version of the sapinst executable by entering the following command:

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

5. Start the installer by executing the following command:

sapinst.exe -nogui

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

sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>

NoteIf you need to assign a virtual host name to the instance to be installed and you do not want to assign it by entering it as a parameter using the installer screens (see Basic Installation Parameters [page 12]), you can alternatively assign it as follows:

32




1. Open a command prompt or PowerShell window in elevated mode and change to the directory to which you unpacked the Software Provisioning Manager 1.0 archive.

2. Start the installer with the following command:

sapinst.exe -nogui SAPINST_USE_HOSTNAME=<Virtual_Host_Name> (in a command prompt)

.\sapinst.exe -nogui SAPINST_USE_HOSTNAME=<Virtual_Host_Name> (in PowerShell)

For more information, see Using Virtual Host Names [page 22].

The installer now starts and waits for the connection to the installer GUI. You see the following in the Program Starter window:

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

4.3.5 Starting the Installer GUI Separately

You use this procedure to start the installer GUI separately. 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 a Remote Installation [page 31].

Prerequisites

● The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in Running the Installer [page 25].

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

● Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Performing a Remote Installation [page 31].

Procedure

In 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).

NoteIf you want to run the installer GUI on a remote host, it is mandatory to start the installer using the -nogui property. If you have already started the installer without the -nogui property and want to run the GUI on a




different host, you have to exit the installation process by choosing SAPinst Exit Process and then follow the steps described in Interrupted Installation [page 30]. Use the - nogui property to restart the installer and start the installer GUI on the intended host.

Starting the Installer GUI on Windows

1. Make the installer software available on the host on which you want to start the installer GUI.


NoteIf you want to start the installer GUI on a Windows operating system that is able to run 32- bit programs, you can use the file SWPM10SP<Support_Package_Number>_<Version_Number>.SAR for Windows I386.

2. 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 -sfxverThe 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 31]).

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>

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

Starting the Installer GUI on UNIX

1. Make the installer software available on the host on which you want to start the installer GUI.


NoteIf you want to start the installer GUI on a Linux 32-bit operating system, make the file SWPM10SP<Support_Package_Number>_<Version_Number>.SAR for Linux I386 available.

2. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters:

34



○ 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 -sfxverThe 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 31]).

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>

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

4.3.6 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode. The following features are available:

● Keyboard access:

This feature is 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.

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.

NoteThe following procedure applies for Windows Server 2008 and might be different when using another Windows operating system.




1. Right click on your Windows desktop and choose Personalize.

2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown 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 installer as described in Running the Installer [page 25] by executing the following command:

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 a Remote Installation [page 31]:

sapinst.exe -nogui2. Start the installer GUI on the local host by executing the following command from the command line as

described in Starting the installer GUI Separately for a Remote Installation [page 33]:

sapinstgui.exe -accessible -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

4.3.7 Troubleshooting with the Installer

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

If an error occurs, the installer:

● Stops the installer

● Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known installer issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the dialog or processing phase, do one of the following:

○ Try to solve the problem.

○ Abort the installer by choosing Stop from the error message or SAPinst Exit Process in the tool menu.

For more information, see Interrupted Installation [page 30].

Continue by choosing Retry.

36




4. Check the log and trace files of the GUI server and the installer GUI in the directory %userprofile%\.sdtgui\ for errors.

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

5. If you cannot resolve the problem, report an incident using component BC-INS.

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





5 Post-Installation Activities

5.1 Configuration

After installing the standalone gateway you have to configure and operate it.

You can find the configuration documentation the SAP Library [page 6] at: Function-Oriented View Application Server Infrastructure Connectivity SAP Gateway

38


Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverPost-Installation Activities

6 Additional Information

6.1 Using Virtual Host Names

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to hide 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.

Prerequisites

● Make sure that the virtual host name can be correctly 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


Procedure

To install a non-high-availability system, proceed as described in SAP Note 1564275 .

6.2 Checking and Changing the Paging File Settings on Windows Server 2012 (R2)

This section describes how to check and change the paging file size on Windows Server 2012 (R2) with PowerShell.

The PowerShell commands also work in previous Windows versions where PowerShell is available.

NoteSome paging file operations require a reboot of the server to activate the changes you made. Wmi-commands do not indicate whether a reboot is required or not. Therefore, we recommend rebooting your system every time you change the paging file settings with PowerShell.

Prerequisites

Always start the PowerShell in elevated mode (run as administrator).

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverAdditional Information





Procedure

Checking the Size of a Paging File

1. Start Windows PowerShell.

2. Check whether the default value Automatic manage pagefile size for all devices is activated.

NoteWe do not support automatically managed page file sizes.

To check this, enter the following command:

(Get-WmiObject Win32_Pagefile) –eq $nullIf Automatic manage pagefile size for all devices is enabled, the output value is True.

If necessary, disable Automatic manage pagefile size for all devices with the following command:

$sys = Get-WmiObject Win32_Computersystem –EnableAllPrivileges$sys.AutomaticManagedPagefile = $false$sys.put()

3. Check the size of the paging files with the following command:

Get-WmiObject WIN32_Pagefile | Select-Object Name, InitialSize, MaximumSize, FileSizeThe output looks like the following:

SyntaxName InitialSize MaximumSize FileSize---- ----------- ----------- --------C:\pagefile.sys 0 0 41943040000E:\pagefile.sys 40000 80000 41943040000

In this example, in the first line, the InitialSize and MaximumSize values of a paging file are 0, which means that the paging file size is system managed (not recommended).

In the second line, the paging file size has a minimum and a maximum size (recommended).

Changing the Size of a Single Paging File

Changing the InitialSize and MaximumSize values of a paging file to a size other than 0, will automatically switch off system managed size.

In the following example, we change the size of the paging file on C: to the InitialSize of 40 GB and to the MaximumSize of 80 GB.

Use the following commands in a PowerShell:

$Pagefile = Get-WmiObject Win32_PagefileSetting | Where-Object {$_.name -eq “C:\pagefile.sys”}$Pagefile.InitialSize = 40000$Pagefile.MaximumSize = 80000$Pagefile.put()Typically, you choose the same value for InitialSize and MaximumSize.

40



NoteThe sum of all paging files InitialSize values must be equal to or higher than the value recommended for your SAP system.

Creating a Second Paging File on Another Disk

You might want to create a second or additional paging files to improve system performance, or if your disk does not have enough space.

To do so, enter the following commands in a PowerShell:

$Pagefile = Get-WmiObject Win32_PagefileSetting$pagefile.Name = “E:\pagefile.sys”$pagefile.Caption = “E:\pagefile.sys”$pagefile.Description = “’pagefile.sys’ @ E:\”$pagefile.SettingID =”pagefile.sys @ E:”$pagefile.InitialSize = 80000$pagefile.MaximumSize = 80000$pagefile.put()

Deleting a Paging File on a Specific Device

To delete a paging file, enter the following commands in a PowerShell:

$pagefile = Get-WmiObject Win32_PagefileSetting | Where-Object {$_.name -eq “E:\pagefile.sys”}$pagefile.delete()

6.3 Starting and Stopping with the SAP Microsoft Management Console (SAP MMC)

You have to check that you can start and stop the standalone gateway after the installation using the SAP Microsoft Management Console (SAP MMC).

You can start and stop the instance by using the SAP MMC in one of the following ways:

● By using the SAP MMC that was installed by the installer automatically on the host of the standalone gateway.

● By using the SAP MMC on another host of your existing SAP system landscape, If the SAP MMC is configured for central system administration.

Procedure

1. Log on as user <sapsid>adm.

2. Start the SAP MMC by choosing Start All Programs SAP Management Console .

3. Right-click the icon of the standalone Gateway instance under the SAP systems node and choose Start or Stop.




More Information

For more information, see the SAP Library [page 6] at:

● SAP systems based on SAP NetWeaver for Banking Services from SAP:

Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the CCMS SAP Microsoft Management Console: Windows

● SAP systems based on SAP NetWeaver Mobile 7.1 / 7.1 including enhancement package 1:

Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the CCMS SAP Microsoft Management Console: Windows

● SAP systems based on SAP NetWeaver Process Integration 7.1 / 7.1 including enhancement package 1:

Function-Oriented View ABAP Technology / Application Server ABAP Administration Tools for AS ABAP Monitoring in the CCMS SAP Microsoft Management Console: Windows

● SAP systems based on SAP NetWeaver 7.3 and higher:

Solution Life Cycle Management Solution Monitoring Monitoring in the CCMS SAP Microsoft Management Console: Windows

6.4 Uninstall

The following procedure describes how to uninstall a standalone Gateway using the installer.

Procedure

1. Start the Installer [page 25].

2. On the Welcome screen, choose Generic Installation Options <Database> Uninstall Uninstall SAP Systems or Single Instances .

3. Follow the instructions in the installer screens.

42



Legal Software Terms

Terms for Included Open Source Software

This document contains information respecting free and open-source software (collectively, “FOSS”) included in or provided with the product (“Product”) that this document accompanies. Any terms, conditions, and restrictions governing the use or distribution of FOSS that are offered or imposed by SAP and are not contained within the FOSS license(s) governing the use and distribution of the FOSS, are offered and imposed by SAP alone. The authors, licensors, and distributors of the FOSS have disclaimed all warranties relating to any liability arising from the use and distribution of the FOSS.

While SAP has sought to provide a complete and accurate listing of the FOSS components included in or provided with the Product, SAP does not represent or warrant that the listing of FOSS components and associated notices and licensing information provided herein are complete or error-free. Recipients of the Product should investigate the listed FOSS components to confirm the accuracy of the notices and licensing information provided herein. Recipients are encouraged to notify SAP of any inaccurate information or errors found in this document.

If you have any questions or concerns please contact SAP by email at [email protected] or via mail at Dietmar Hopp Allee 16, 69190 Walldorf, Germany, Attn: Global Legal.

● Mozilla SpiderMonkey

Licensor: Mozilla Developer Network and individual contributors

Website: developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey

License: Mozilla Public License version 2.0

1. Definitions

1. “Contributor”

means each individual or legal entity that creates, contributes to the creation of, or owns Covered Software.

2. “Contributor Version”

means the combination of the Contributions of others (if any) used by a Contributor and that particular Contributor’s Contribution.

3. “Contribution”

means Covered Software of a particular Contributor.

4. “Covered Software”

means Source Code Form to which the initial Contributor has attached the notice in Exhibit A, the Executable Form of such Source Code Form, and Modifications of such Source Code Form, in each case including portions thereof.

5. “Incompatible With Secondary Licenses” means

1. that the initial Contributor has attached the notice described in Exhibit B to the Covered Software; or

2. that the Covered Software was made available under the terms of version 1.1 or earlier of the License, but not also under the terms of a Secondary License.

6. “Executable Form”

means any form of the work other than Source Code Form.

Standalone Gateway on Windows for SAP Systems Based on SAP NetWeaverLegal Software Terms



https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey

7. “Larger Work”

means a work that combines Covered Software with other material, in a separate file or files, that is not Covered Software.

8. “License”

means this document.

9. “Licensable”

means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently, any and all of the rights conveyed by this License.

10. “Modifications”

means any of the following:

1. any file in Source Code Form that results from an addition to, deletion from, or modification of the contents of Covered Software; or

2. any new file in Source Code Form that contains any Covered Software.

11. “Patent Claims” of a Contributor

means any patent claim(s), including without limitation, method, process, and apparatus claims, in any patent Licensable by such Contributor that would be infringed, but for the grant of the License, by the making, using, selling, offering for sale, having made, import, or transfer of either its Contributions or its Contributor Version.

12. “Secondary License”

means either the GNU General Public License, Version 2.0, the GNU Lesser General Public License, Version 2.1, the GNU Affero General Public License, Version 3.0, or any later versions of those licenses.

13. “Source Code Form”

means the form of the work preferred for making modifications.

14. “You” (or “Your”)

means an individual or a legal entity exercising rights under this License. For legal entities, “You” includes any entity that controls, is controlled by, or is under common control with You. For purposes of this definition, “control” means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. License Grants and Conditions

1. Grants

Each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:

1. under intellectual property rights (other than patent or trademark) Licensable by such Contributor to use, reproduce, make available, modify, display, perform, distribute, and otherwise exploit its Contributions, either on an unmodified basis, with Modifications, or as part of a Larger Work; and

2. under Patent Claims of such Contributor to make, use, sell, offer for sale, have made, import, and otherwise transfer either its Contributions or its Contributor Version.

2. Effective Date

The licenses granted in Section 2.1 with respect to any Contribution become effective for each Contribution on the date the Contributor first distributes such Contribution.

3. Limitations on Grant Scope

44



The licenses granted in this Section 2 are the only rights granted under this License. No additional rights or licenses will be implied from the distribution or licensing of Covered Software under this License. Notwithstanding Section 2.1.2 above, no patent license is granted by a Contributor:

1. for any code that a Contributor has removed from Covered Software; or

2. for infringements caused by: (i) Your and any other third party’s modifications of Covered Software, or (ii) the combination of its Contributions with other software (except as part of its Contributor Version); or

3. under Patent Claims infringed by Covered Software in the absence of its Contributions.

This License does not grant any rights in the trademarks, service marks, or logos of any Contributor (except as may be necessary to comply with the notice requirements in Section 3.4).

4. Subsequent Licenses

No Contributor makes additional grants as a result of Your choice to distribute the Covered Software under a subsequent version of this License (see Section 10.2) or under the terms of a Secondary License (if permitted under the terms of Section 3.3).

5. Representation

Each Contributor represents that the Contributor believes its Contributions are its original creation(s) or it has sufficient rights to grant the rights to its Contributions conveyed by this License.

6. Fair Use

This License is not intended to limit any rights You have under applicable copyright doctrines of fair use, fair dealing, or other equivalents.

7. Conditions

Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted in Section 2.1.

3. Responsibilities

1. Distribution of Source Form

All distribution of Covered Software in Source Code Form, including any Modifications that You create or to which You contribute, must be under the terms of this License. You must inform recipients that the Source Code Form of the Covered Software is governed by the terms of this License, and how they can obtain a copy of this License. You may not attempt to alter or restrict the recipients’ rights in the Source Code Form.

2. Distribution of Executable Form

If You distribute Covered Software in Executable Form then:

1. such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; and

2. You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients’ rights in the Source Code Form under this License.

3. Distribution of a Larger Work

You may create and distribute a Larger Work under terms of Your choice, provided that You also comply with the requirements of this License for the Covered Software. If the Larger Work is a combination of Covered Software with a work governed by one or more Secondary Licenses, and the Covered Software is not Incompatible With Secondary Licenses, this License permits You to additionally distribute such Covered Software under the terms of such Secondary License(s), so that




the recipient of the Larger Work may, at their option, further distribute the Covered Software under the terms of either this License or such Secondary License(s).

4. Notices

You may not remove or alter the substance of any license notices (including copyright notices, patent notices, disclaimers of warranty, or limitations of liability) contained within the Source Code Form of the Covered Software, except that You may alter any license notices to the extent required to remedy known factual inaccuracies.

5. Application of Additional Terms

You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Software. However, You may do so only on Your own behalf, and not on behalf of any Contributor. You must make it absolutely clear that any such warranty, support, indemnity, or liability obligation is offered by You alone, and You hereby agree to indemnify every Contributor for any liability incurred by such Contributor as a result of warranty, support, indemnity or liability terms You offer. You may include additional disclaimers of warranty and limitations of liability specific to any jurisdiction.

4. Inability to Comply Due to Statute or Regulation

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Software due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be placed in a text file included with all distributions of the Covered Software under this License. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Termination

1. The rights granted under this License will terminate automatically if You fail to comply with any of its terms. However, if You become compliant, then the rights granted under this License from a particular Contributor are reinstated (a) provisionally, unless and until such Contributor explicitly and finally terminates Your grants, and (b) on an ongoing basis, if such Contributor fails to notify You of the non-compliance by some reasonable means prior to 60 days after You have come back into compliance. Moreover, Your grants from a particular Contributor are reinstated on an ongoing basis if such Contributor notifies You of the non-compliance by some reasonable means, this is the first time You have received notice of non-compliance with this License from such Contributor, and You become compliant prior to 30 days after Your receipt of the notice.

2. If You initiate litigation against any entity by asserting a patent infringement claim (excluding declaratory judgment actions, counter-claims, and cross-claims) alleging that a Contributor Version directly or indirectly infringes any patent, then the rights granted to You by any and all Contributors for the Covered Software under Section 2.1 of this License shall terminate.

3. In the event of termination under Sections 5.1 or 5.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or Your distributors under this License prior to termination shall survive termination.

6. Disclaimer of Warranty

Covered Software is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer.

46



7. Limitation of Liability

Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall any Contributor, or anyone who distributes Covered Software as permitted above, be liable to You for any direct, indirect, special, incidental, or consequential damages of any character including, without limitation, damages for lost profits, loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party’s negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to You.

8. Litigation

Any litigation relating to this License may be brought only in the courts of a jurisdiction where the defendant maintains its principal place of business and such litigation shall be governed by laws of that jurisdiction, without reference to its conflict-of-law provisions. Nothing in this Section shall prevent a party’s ability to bring cross-claims or counter-claims.

9. Miscellaneous

This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor.

10. Versions of the License

1. This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not be used to construe this License against a Contributor. 10. Versions of the License 10.1. New Versions Mozilla Foundation is the license steward. Except as provided in Section 10.3, no one other than the license steward has the right to modify or publish new versions of this License. Each version will be given a distinguishing version number.

2. Effect of New Versions

You may distribute the Covered Software under the terms of the version of the License under which You originally received the Covered Software, or under the terms of any subsequent version published by the license steward.

3. Modified Versions

If you create software not governed by this License, and you want to create a new license for such software, you may create and use a modified version of this License if you rename the license and remove any references to the name of the license steward (except to note that such modified license differs from this License).

4. Distributing Source Code Form that is Incompatible With Secondary Licenses

If You choose to distribute Source Code Form that is Incompatible With Secondary Licenses under the terms of this version of the License, the notice described in Exhibit B of this License must be attached.

Exhibit A – Source Code Form License Notice

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at mozilla.org/MPL/2.0/.




http://mozilla.org/MPL/2.0/

If it is not possible or desirable to put the notice in a particular file, then You may include the notice in a location (such as a LICENSE file in a relevant directory) where a recipient would be likely to look for such a notice.

5. You may add additional accurate notices of copyright ownership.

6. Exhibit B – “Incompatible With Secondary Licenses” Notice This Source Code Form is “Incompatible With Secondary Licenses”, as defined by the Mozilla Public License, v. 2.0.

● zlib

Licensor: Jean-loup Gailly and Mark Adler

Website: www.zlib.net/

License: Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

zlib.h – interface of the “zlib” general purpose compression library version 1.2.8, April 28th, 2013

Copyright (C) 1995-2013 Jean-loup Gailly and Mark Adler

This software is provided “as-is”, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Jean-loup Gailly ([email protected])

Mark Adler ([email protected])

● STLPort

Licensor: Boris Fomitchev

WebSite: www.stlport.org/

License Agreement

Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-free license to use STLport and its documentation without fee.

By downloading, using, or copying STLport or any portion thereof, Licensee agrees to abide by the intellectual property laws and all other applicable laws of the United States of America, and to all of the terms and conditions of this Agreement.

Licensee shall maintain the following copyright and permission notices on STLport sources and its documentation unchanged:

Copyright 1999,2000 Boris Fomitchev

This material is provided “as is”, with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. The Licensee may distribute original or modified STLport sources, provided that:

○ The conditions indicated in the above permission notice are met;

48



http://www.zlib.net/

http://www.stlport.org/

○ The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met:

Copyright 1994 Hewlett-Packard Company

Copyright 1996,97 Silicon Graphics Computer Systems, Inc.

Copyright 1997 Moscow Center for SPARC Technology.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

● Flexler 1.18

Copyright (c) 1993 The Regents of the University of California.

All rights reserved.

This code is derived from software contributed to Berkeley by Kent Williams and Tom Epperly.

Redistribution and use in source and binary forms are permitted provided that: (1) source distributions retain this entire copyright notice and comment, and (2) distributions including binaries display the following acknowledgement: “This product includes software developed by the University of California, Berkeley and its contributors” in the documentation or other materials provided with the distribution and in all advertising materials mentioning features or use of this software. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.




www.sap.com

© Copyright 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.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 www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

standalone gateway on windows for sap systems

Documents

sap systems

sap netweavervalid

sap notes

sap library

software provisioning

sap affiliate company

example example arrows

sap service marketplace