Installation Guide Web Dispatcher on Windows For SAP Systems Based on SAP NetWeaver 7.3
description
Transcript of Installation Guide Web Dispatcher on Windows For SAP Systems Based on SAP NetWeaver 7.3
Installation GuideWeb Dispatcher on WindowsFor SAP Systems Based on SAP NetWeaver 7.3
Target Audience ■ Technology consultants ■ System administrators
PUBLICDocument version: 1.10 – 2011-04-28
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version on SAP Service Marketplace http://service.sap.com/
instguides.
The following table provides an overview on the most important document changes:
Version Date Description
1.10 2011-04-28 Updated version
1.0 2010-11-29 Initial version
2/46 PUBLIC 2011-04-28
Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Web Dispatcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.1 Running the Prerequisite Checker in Standalone Mode
(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.2 Hardware and Software Requirements Tables . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 Basic Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 Checking the Windows File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Reducing the Size of the File Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.3 Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . 18
3.4 Performing a Domain Installation Without Being a Domain
Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.5 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.6 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 5 Post-Installation Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.1 Logging on to the Web Dispatcher Management Console . . . . . . . . . . . . . . . . 31
5.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.1 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.1.1 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2011-04-28 PUBLIC 3/46
6.1.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6.1.3 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.1.6 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
6.2 Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4/46 PUBLIC 2011-04-28
1 Introduction
This documentation describes how to install a Web Dispatcher for SAP systems based on SAP NetWeaver
7.3.
We recommend that you use a Web Dispatcher [page 5] when you run an SAP system with several
application servers for web applications.
1.1 Web Dispatcher
The Web dispatcher is situated between the Internet and your SAP system. It is the entry point for HTTP
(s) requests into your system, which consists of one or more SAP NetWeaver application servers.
Figure 1:
As a “software web switch”, the Web dispatcher can reject or accept connections. When it accepts a
connection, it balances the load to ensure an even distribution across the servers.
You can use the Web dispatcher in ABAP+Java systems as well as in pure Java systems and in pure ABAP
systems.
1 Introduction
1.1 Web Dispatcher
2011-04-28 PUBLIC 5/46
RECOMMENDATION
The Web dispatcher is recommended when you use an SAP system with several SAP NetWeaver
application servers for Web applications.
The Web dispatcher can run on the machine that is connected directly to the Internet and requires
minimal configuration. You only have to enter the following data in the profile file:
■ Port on which the HTTP(s) requests are to be received
Parameter icm/server_port_<xx>
■ Host and HTTP port of the SAP message server
Parameters rdisp/mshost and ms/http_port)
EXAMPLE
If you need to be able to call the Web application externally — for example using the URL
www.shop.acme.com — this host name must be mapped internally to the Web dispatcher, which
then forwards the HTTP(S) request to a suitable application server.
More Information
RECOMMENDATION
For more information, see the Web Dispatcher documentation in theSAP Library [page 6] at:
Administrator's Guide Configuration of SAP NetWeaver CE Configuration Tasks after Your System Landscape
Is Set Up SAP Web Dispatcher .
1.2 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.
Make sure that you have the up-to-date version of each SAP Note which you can find in the SAP Service
Marketplace at http://service.sap.com/notes.
SAP Notes for the Installation
SAP Note Number Title Description
1460151 Web Dispatcher Installation for SAP Systems Based on Kernel 7.3
Additional Information about Web Dispatcher installation.
855498 Installation Prerequisite Checker Checking OS Dependencies for UNIX, Windows and IBM eServer iSeries
1.3 Accessing the SAP Library
The references to SAP NetWeaver Library documentation in this documentation always refer to the
following entry point on the SAP Help Portal:
1 Introduction
1.2 SAP Notes for the Installation
6/46 PUBLIC 2011-04-28
■ SAP NetWeaver Composition Environment Library:
http://help.sap.com/nw73 SAP NetWeaver 7.3 SAP NetWeaver 7.3 Library
1.4 Naming Conventions
In this documentation, the following naming conventions apply:
SAP system refers to web dispatcher .
instance refers to a web dispatcher Instance.
Variables
Variables Description
<host_name> Name of the corresponding host
<INSTDIR> Installation directory for the SAP system
<INSTANCE> Instance directory of an SAP system
<Instance_Number> Instance number of an SAP system
<DVD_DIR> Directory on which a DVD is mounted
<OS> Operating system name within a path
The following example shows how the variables are used:
EXAMPLE
Log on as user <sapsid>adm and change to the directory \usr\sap\<SAPSID>.
If your SAP system ID is C11, log on as user c11adm and change to the directory
\usr\sap\C11.
1 Introduction
1.4 Naming Conventions
2011-04-28 PUBLIC 7/46
This page is left blank for documents that are printed on both sides.
2 Planning
You check that your hosts meet the hardware and software requirements for your operating system
and the Web Dispatcher.
CAUTION
If 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 http://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 10].
● Integrated in SAPinst (mandatory) as part of the installation process
For more information, see Running SAPinst [page 27].
NOTE
For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
3. If you want to use the Web Dispatcher 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 http://service.sap.com/sizing.
For the Web Dispatcher, there is a sizing guideline available at http://service.sap.com/
sizing Sizing Guidelines Solutions & Platform Sizing the SAP Web Dispatcher
■ 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 Hardware and Software Requirements
You check that your hosts meet the hardware and software requirements for your operating system
and the Web Dispatcher.
2 Planning
2.1 Hardware and Software Requirements
2011-04-28 PUBLIC 9/46
CAUTION
If 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 http://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 10].
● Integrated in SAPinst (mandatory) as part of the installation process
For more information, see Running SAPinst [page 27].
NOTE
For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
3. If you want to use the Web Dispatcher 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 http://service.sap.com/sizing.
For the Web Dispatcher, there is a sizing guideline available at http://service.sap.com/
sizing Sizing Guidelines Solutions & Platform Sizing the SAP Web Dispatcher
■ 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 Prerequisite Checker in Standalone Mode (Optional)
Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the
hardware and software requirements for your operating system (OS) and the SAP instances.
RECOMMENDATION
We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
NOTE
When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks
the hardware and software requirements in the background.
2 Planning
2.1 Hardware and Software Requirements
10/46 PUBLIC 2011-04-28
Procedure
1. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the
installation host. For more information, see Preparing the Installation Media [page 23].
2. Start SAPinst [page 27].
3. On the Welcome screen, choose <SAP System> Preparations Prerequisites Check .
4. Follow the instructions in the SAPinst dialogs and enter the required parameters.
NOTE
For more information about each parameter, position the cursor on the parameter field and
choose F1 in SAPinst.
When you have finished, the Parameter Summary screen appears summarizing all parameters you have
entered and 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 Web Dispatcher host must meet the following requirements:
NOTE
The information here is not intended to replace the operating system documentation. For more
information, see your operating system documentation.
Requirement Type Requirement
Hardware ■ Suitable backup system ■ Minimum disk space (not including paging file):
2.5 GB (x64)5 GB (IA64) ● 4.3 GB of temporary disk space for every required
installation media that you have to copy to a local hard disk.To check disk space:1. Windows Server 2003:
Choose Start All Programs Administrative Tools Computer Management Disk Management .
2. Windows Server 2008 (R2):Choose Start All Programs Administrative Tools Storage
Computer Management Disk Management .3. Right-click the drive and choose Properties.
■ Minimum RAM:4 GB
2 Planning
2.1 Hardware and Software Requirements
2011-04-28 PUBLIC 11/46
Requirement Type RequirementTo check RAM:Choose Start Control Panel System .
NOTE
Windows Server 2008 R2:If System is not visible, change View by: from Category into Large icons.
■ Paging File Size:1 times RAM plus 14 GBTo check paging file size:1. Choose Start Control Panel System .
NOTE
Windows Server 2008 R2:If System is not visible, change View by: from Category into Large icons.
2. Windows Server 2003:Choose Advanced.
3. Windows Server 2008 (R2):Choose Advanced system settings.
4. In section Performance, select Settings... Advanced .5. If required, in section Virtual memory, choose Change.
NOTE
Do not select Automatically managed paging file size for all drives.
Software ■ English international 64-bit version of one of the following Windows Server Editions: ● Windows Server 2003
◆ Windows Server 2003 Standard Edition ◆ Windows Server 2003 Enterprise Edition ◆ Windows Server 2003 Datacenter Edition
● Windows Server 2008 (R2) ◆ Windows Server 2008 (R2) Standard Edition ◆ Windows Server 2008 (R2) Enterprise Edition ◆ Windows Server 2008 (R2) Datacenter Edition
■ For any version of Windows Server, you need the latest supported service pack
■ Windows Server 2003: A suitable Windows Resource Kit is strongly recommended.
■ Windows Server 2003: Updated CPU driversFor more information, see SAP Note 1036194.
2.2 Basic Installation Parameters
The table below lists the basic input parameters that are prompted by SAPinst during the installation.
For all other SAP system parameters, use the F1 help in the SAPinst screens.
2 Planning
2.2 Basic Installation Parameters
12/46 PUBLIC 2011-04-28
Web Dispatcher Parameters
Parameters Description
SAP System ID <SAPSID> The SAP System ID <SAPSID> identifies the whole SAP system.
CAUTION
Choose 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 ■ Has a letter for the first character ■ Does not include any of the following, which are reserved IDs:
ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT
KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA
SHG SID SQL SYS TMP UID USR VAR
Instance Number for the Web Dispatcher
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.
CAUTION
Do not use 43, 60, 89 for the instance number of the Web Dispatcher.
Operating System Users The passwords of the operating system users must comply with the Windows password policy. SAPinst processes the passwords of operating system users as follows: ■ If the operating system users do not exist, SAP creates the following
users: ● <sapsid>adm
This 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. SAPinst 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 19]. For security reasons, however, SAP strongly recommends you to create this user as a local user.
● <dasid>adm
The diagnostics agent user <dasid>adm is used to manage the diagnostics agent system. It is created on the primary application server instance host and on every additional application server instance host. SAPinst creates this user by
2 Planning
2.2 Basic Installation Parameters
2011-04-28 PUBLIC 13/46
Parameters Descriptiondefault 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 19]. For security reasons, however, SAP strongly recommends you to create this user as a local user.
● SAPService<DASID>
This user is the Windows account to run the diagnostics agent system.
SAPinst 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, SAPinst prompts you for the existing password, except the password of these users is the same as the master password.
CAUTION
Make sure that you have the required user authorization [page 18] for these accounts before you start the installation.
Message Server Host The host on which the message server is located (profile parameter rdisp/mshost)
Message Server HTTP Port HTTP port of the message server (profile parameter ms/server_port_<xx>)
Password for the Internet Communication Management (ICM) user
In order to use the web administration interface for the Internet Communication Manager (ICM) and SAP Web Dispatcher, an administration user webadm is created by SAPinst.You have to assign a password for this user.
Path to SAPCRYPTO.SAR The SAP Cryptographic Library is required to enable Secure Sockets Layer (SSL) encryption of HTTP connections. If you do not have SAPCRYPTO.SAR available, you can download it from:http://service.sap.com/swdc Installations and Upgrades Search for the
term “SAP Cryptogaphic Software”This software product is subject to export control regulations in Germany as the country of origin and import regulations of your own country. SAP may not yet have a corresponding export license for your user or company. Contact the contract department in your local SAP company. To download the SAP Cryptographic Software from the SAP Service Marketplace, you need a customer user ID. Before any transfer of these software products to persons, companies or other organizations outside your company, in particular in the case of any re-export of the software products, authorization is required from the German export control authorities. This might also be required from your responsible national export control authorities. This also applies to transfers to affiliated companies. Corresponding laws and regulations in the recipient country may also exist which restrict the import or the use of these software products.
2 Planning
2.2 Basic Installation Parameters
14/46 PUBLIC 2011-04-28
Parameters Description
Activate ICF nodes The Web Dispatcher uses ICF services of SAP ABAP system's application servers to retrieve information about server groups and URL mappings. By default, all ICF services are inactive. For more information, see SAP Note 552286.
Diagnostics Agent Parameters
The diagnostics agent is installed automatically with the Web Dispatcher.
Parameters Description
System ID of Diagnostics Agent <DASID>
SAPinst sets the system ID of the diagnostics agent, <DASID>, to DAA by default.If DAA is already used, SAPinst assigns another default system ID. You can overwrite the default system ID as required.
CAUTION
Choose the <DASID> carefully. Renaming is difficult and requires you to reinstall the diagnostics agent.
Make sure that the <DASID>: ■ Either does not yet exist on the local installation host or does already exist
but was only used for a diagnostics agent installation ■ Consists of exactly three alphanumeric characters ■ Contains only uppercase letters ■ Has a letter for the first character ■ Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR
GET GID IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS
OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID
USE USR VAR
SLD Destination You can choose between the following options: ■ Register in existing central SLD
SAPinst only prompts you for the parameters listed below in this table if you select this option.
RECOMMENDATION
We recommend that you select this option. ■ No SLD destination
If you select this option: ● You have to configure the SLD destination for the diagnostics agent
manually after the installation with SAPinst has finished. ● SAPinst does not prompt you for the parameters listed below in this
table.
SLD HTTP Host The host name of the System Landscape Directory (SLD)
SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming convention applies:5<instance_number>00.
EXAMPLE
If the instance number of your Java system is 01, the SLD HTTP Port is 50100.
2 Planning
2.2 Basic Installation Parameters
2011-04-28 PUBLIC 15/46
Parameters Description
SLD Data Supplier User and password
You have to enter the existing SLD Data Supplier User and password of the central SLD.
2 Planning
2.2 Basic Installation Parameters
16/46 PUBLIC 2011-04-28
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.
NOTE
You 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
NOTE
This 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.
CAUTION
If 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 Preparation
3.1 Checking the Windows File System
2011-04-28 PUBLIC 17/46
3.3 Required User Authorization for Running SAPinst
Although SAPinst 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
CAUTION
Do not use the user <sapsid>adm for the installation of the SAP system.
Domain Installation
For a domain installation the account used for the installation needs to be a member of the local
Administrators and the domain Admins group of the relevant domain. All machines in the system
must belong to the same domain. In a domain installation, the user information is stored centrally on
the domain controller and is accessible to all hosts in the system.
If the SAP system is to be distributed across more than one machine, SAP strongly recommends you
to perform a domain installation to avoid authorization problems.
CAUTION
■ If you install a distributed system as a local installation, this can lead to authorization problems
for the operating system users <sapsid>adm and SAPService<SAPSID>. It can also lead to
problems with the transport directory, which is usually shared by several SAP systems.
Therefore, we do not support a local installation for a distributed system. We recommend
you to install a distributed system as a domain installation.
If you still want to perform a local installation for a distributed system, make sure that:
● You use the same password for the <sapsid>adm or the SAPService<SAPSID> user on all
hosts.
The password for the <sapsid>adm and SAPService<SAPSID> user can differ.
● You use the same master password on all hosts.
● All hosts belong to the same Windows work group.
■ For performance and security reasons, SAP does not support an SAP system installation on
a domain controller.
■ If for any reason, the account used for the installation is not a member of the domain
Admins group, you can perform the installation with a domain user who is a member of the
local Administrators group. However, the domain administrator has to prepare the system
appropriately for you.
3 Preparation
3.3 Required User Authorization for Running SAPinst
18/46 PUBLIC 2011-04-28
For more information, see Performing a Domain Installation without being a Domain Administrator [page
19].
For a domain installation, you need to:
1. Check that the account used for the installation is a member of the domain Admins group.
2. If required, obtain these rights by asking the system administrator to enter the account as a member
of the domain Admins group.
Local Installation
For a local installation the account used for the installation needs to be a member of the local
Administrators group of the machine involved. In a local installation, all Windows account
information is stored locally on one host and is not visible to any other hosts in the system.
If the SAP system is to run on a single machine, you can perform a local installation.
CAUTION
Do not use the Windows built-in account Administrator or the renamed built-in account to
install your SAP system with SAPinst. The built-in account only has restricted network access
rights that are required by SAPinst. 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.
More Information
Performing a Domain Installation Without Being a Domain Administrator [page 19]
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 SAPinst [page 18]. 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 SAPinst or manually:
1. Create the new domain group SAP_<SAPSID>_GlobalAdmin.
2. Create the two new SAP system users <sapsid>adm and SAPService<SAPSID>.
3 Preparation
3.4 Performing a Domain Installation Without Being a Domain Administrator
2011-04-28 PUBLIC 19/46
3. Add the users <sapsid>adm and SAPService<SAPSID> to the newly created group
SAP_<SAPSID>_GlobalAdmin.
NOTE
SAPinst creates the operating system users for the host agent and the diagnostic 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 Host Agent User and Group Manually
1. Create the new domain 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 Diagnostic Agent Users and Group Manually:
1. Create the new domain 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.
■ You must have installed the feature Remote Server Administration Tools as follows:
1. Choose Start Administrative Tools Server Manager .
2. In the Server Manager windows, 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 SAPinst
On the host where the SAP system is to be installed, the domain administrator starts SAPinst as described
in Running SAPinst [page 27] and chooses Preparations Operating System and Users to have the group and
users created automatically.
Creating the Required Users and Groups Manually
Creating the New Domain Group SAP_<SAPSID>_GlobalAdmin
1. Log on as domain administrator.
2. To start the Active Directory Users and Computers Console, choose:
Start Control Panel Administrative Tools Active Directory Users and Computers
3. Right-click Users in Tree, and choose New Group .
4. Enter the following:
3 Preparation
3.4 Performing a Domain Installation Without Being a Domain Administrator
20/46 PUBLIC 2011-04-28
Group name: SAP_<SAPSID>_GlobalAdmin
NOTE
Enter the SAP_<SAPSID>_GlobalAdmin group exactly as specified in the correct uppercase and
lowercase.
5. 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>
1. In Active Directory Users and Computers Console, right-click Users in Tree and choose:
New User
2. Enter the following:
NOTE
Enter the <sapsid>adm and SAPService<SAPSID> user exactly as specified in the correct
uppercase and lowercase.
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
NOTE
Make sure that no other options are selected.
5. Choose Next Finish .
Adding the <sapsid>adm User to the SAP_<SAPSID>_GlobalAdmin Group
1. In the Users folder, double-click the newly created user account <sapsid>adm in the list on the
right.
2. Choose Member Add .
3. Select the new SAP_<SAPSID>_GlobalAdmin group and choose Add to add it to the list.
NOTE
By default, the user is also a member of the Domain Users group.
4. Choose OK twice.
3 Preparation
3.4 Performing a Domain Installation Without Being a Domain Administrator
2011-04-28 PUBLIC 21/46
Adding the SAPService<SAPSID> User to the SAP_<SAPSID>_GlobalAdmin Group
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
SAPinst 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 systems. If you do not set up any file system on your
installation host, SAPinst creates all directories in the root directory /. SAPinst prompts you only for
the <sapmnt> directory during the installation.
The instance name (instance ID) of the Web Dispatcher instance is W<Instance_Number>, for example
W00.
SAP File Directories in Detail
NOTE
The listed file system sizes are initial SAP requirements.
Depending on your operating system, you might also have to add space for administrative
purposes.
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 Web Dispatcher instance is W<Instance_Number>, for example W00.
500 MB
3 Preparation
3.5 SAP Directories
22/46 PUBLIC 2011-04-28
Directory Name Description Space Required
<Drive>:\usr\sap
\trans
\usr\sap\trans
This 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 Preparing the Installation Media
This section describes how to prepare the installation media, 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 from SAP Service Marketplace, as described at the
end of this section.
Procedure
1. Identify the required media for your installation as listed below.
NOTE
You can find the full names of all media shipped with SAP NetWeaver 7.3 in the document
Media List – SAP NetWeaver 7.3 on SAP Service Marketplace at:
http://service.sap.com/installnw73
Installation Required Folder of Software Packages from Media
Web Dispatcher Installation ■ Installation Master:Folder <Product>_IM_<OS>_<DB>
■ SAP Kernel:Make sure that both the UC kernel and NUC kernel software are available: ● UC Kernel: Folder K_U_<Version>_<OS>
where U means Unicode. ● NUC Kernel: Folder K_N_<Version>_<OS>
where N means non-Unicode. ● SL_CONTROLLER_720 ● SL_CONTROLLER_700
2. Make the required installation media available on each installation host.
You can do this in one of the following ways:
■ Copy the required media folders directly to the installation hosts.
■ Mount media on a central media server that can be accessed from the installation hosts.
CAUTION
■ If you copy the media to disk, make sure that the paths to the destination location of the
copied media do not contain any blanks.
3 Preparation
3.6 Preparing the Installation Media
2011-04-28 PUBLIC 23/46
■ If you perform a domain installation and do not want to copy the media but use network
drives for mapping the installation media, make sure that the <sapsid>adm user has access
to the UNC paths of the network drives. If the user does not yet exist, you have to create
the user manually before you install the SAP system.
Downloading Installation Media from SAP Service Marketplace
You normally obtain the installation media as part of the installation package from SAP.
However, you can also download installation media from the software distribution center on SAP
Service Marketplace using one of the following paths:
■ http://service.sap.com/swdc Installations and Upgrades My companys application components
<your product> <your product version>
■ http://service.sap.com/swdc Installations and Upgrades A-Z index <first letter of your product>
<your product version>
NOTE
If you download installation media, note that they might be split into several files. In this case,
you have to reassemble the required files after the download.
CAUTION
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which
you can also download from http://service.sap.com/swdc. You need at least SAPCAR 700. For
more information, see SAP Note 212876.
1. Identify all download objects that belong to one installation medium according to one or both of
the following:
■ Material number
All download objects that are part of an installation medium have the same material number
and an individual sequence number:
<material_number>_<sequence_number>
EXAMPLE
51031387_1
51031387_2
...
■ Title
All objects that are part of an installation medium have the same title, such as
<solution><media_name><OS> or <database>RDBMS<OS> for database media.
2. Download the objects to the download directory.
3. Extract the individual download objects using SAPCAR, starting with the lowest sequence number
– for example 51031387_1, then 51031387_2, and so on.
3 Preparation
3.6 Preparing the Installation Media
24/46 PUBLIC 2011-04-28
NOTE
SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept
with Yes.
3 Preparation
3.6 Preparing the Installation Media
2011-04-28 PUBLIC 25/46
This page is left blank for documents that are printed on both sides.
4 Installation
4.1 Running SAPinst
This section describes how to run the installation tool SAPinst. SAPinst includes a GUI client and a GUI
server, which both use Java. In the following, GUI client and GUI server are called “SAPinst GUI”.
This procedure describes an installation where SAPinst and SAPinst GUI are running on the same host.
Useful Information About SAPinst
■ SAPinst creates the installation directory sapinst_instdir, where it keeps its log files, and which
is located directly in the %ProgramFiles% directory. If SAPinst is not able to create
sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the
environment variable TEMP.
■ SAPinst creates a subdirectory for each installation option called <sapinst_instdir>
\<installation_option_directory>, which is located in %ProgramFiles%.
■ SAPinst extracts itself to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These
executables are deleted after SAPinst has stopped running.
Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You
can safely delete them.
The temporary directory also contains the log file dev_selfex.out from the extraction process,
which might be useful if an error occurs.
CAUTION
If SAPinst cannot find a temporary directory, the installation terminates with the error
FCO-00058.
■ During the installation, the default ports 21200, 21212, and 4239 are used for communication
between SAPinst, GUI server, SAPinst GUI, and HTTP server, as follows:
● SAPinst uses port 21200 to communicate with the GUI server.
● The GUI server uses port 21212 to communicate with the GUI client.
● 4239 is the port of the HTTP server, which is part of the GUI server.
If these ports are already in use, SAPinst automatically searches for free port numbers. If the search
fails, you see an error message and SAPinst exits.
In this case or if you want SAPinst to use specific ports, open a command prompt and change to
the required directory as follows:
Execute sapinst.exe with the following commands:
● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>
4 Installation
4.1 Running SAPinst
2011-04-28 PUBLIC 27/46
● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>
● GUISERVER_HTTP_PORT=<port_number_http_server>
■ To see a list of all available SAPinst properties, go to the directory (%TEMP%
\sapinst_exe.xxxxxx.xxxx) after you have started SAPinst, and enter the following command:
sapinst.exe -p
■ If you need to run SAPinst in accessibility mode, proceed as described in Running SAPinst in Accessibility
Mode [page 38].
■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.
NOTE
If you need to terminate SAPinst you can do this by choosing File Exit in the menu of
the Program Starter window.
Prerequisites
■ You need at least 300 MB of free space in the installation directory for each installation option. In
addition, you need 60 - 200 MB free space for the SAPinst 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 hosts meets the requirements for the installation options that you
want to install. For more information, see Running the Prerequisite Checker [page 10].
Procedure
1. Log on to the installation host using an account with the required user authorization to run SAPinst [page
18].
CAUTION
Do not use an existing <sapsid>adm user.
2. Make the installation media available on the installation host.
3. Start SAPinst from the installation media by double-clicking sapinst.exe from the directory:
SAPinst GUI starts automatically by displaying the Welcome screen.
NOTE
If you need to perform the installation in accessibility mode, open a command prompt, change
to the directory <IM_WINDOWS_<your platform>_<your DB>, and execute sapinst.exe –
accessible.
For more information, see Running SAPinst in Accessibility Mode [page 38].
4. In the Welcome screen, choose the required installation option:
■ To install a new web dispatcher instance, choose SAP NetWeaver 7.3 SAP Systems Standalone
Engines Web Dispatcher Web Dispatcher Installation .
5. Choose Next.
6. If SAPinst prompts you to log off from your system, log off and log on again.
SAPinst restarts automatically.
4 Installation
4.1 Running SAPinst
28/46 PUBLIC 2011-04-28
7. Follow the instructions in the SAPinst screens and enter the required parameters.
NOTE
To 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, SAPinst displays the Parameter Summary screen.
This screen shows both the parameters that you entered and those that SAPinst set by default. If
required, you can revise the parameters before starting the installation.
8. To start the installation, choose Start.
SAPinst starts the installation and displays the progress of the installation. When the installation
has finished, SAPinst 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 installation media to your hard disk, you can delete these files when the installation
has successfully completed.
More Information
■ Interrupted Installation with SAPinst [page 34]
■ How to Avoid Automatic Logoff by SAPinst [page 33]
■ Performing a Remote Installation with SAPinst [page 35]
■ Starting SAPinst GUI Separately [page 36].
■ Running SAPinst in Accessibility Mode [page 38]
■ Troubleshooting with SAPinst [page 39]
4 Installation
4.1 Running SAPinst
2011-04-28 PUBLIC 29/46
This page is left blank for documents that are printed on both sides.
5 Post-Installation Activities
5.1 Logging on to the Web Dispatcher Management Console
You have to log on to the Web Dispatcher Management Console
■ to check whether the Web Dispatcher was installed successfully,
■ to change the password of the webadm user,
■ to access monitoring and administration tools.
Procedure
1. Open a web browser.
2. Enter the following URL:
http://<web_dispatcher_host>:<web_dispatcher_port>/sap/admin
If you did not enter a specific port number, <web_dispatcher_port> is by default
81<instance_number>.
3. Log on as user webadm with the password that you entered during the input phase of the installation.
The SAP Web Dispatcher Monitor screen appears.
4. We recommend that you change the password of webadm immediately after the installation for
security reasons.
For more information on how to change passwords of existing users using the Admin Handler, see
the SAP Library [page 6] at Administrator's Guide Configuration of SAP NetWeaver CE Configuration Tasks
after Your System Landscape Is Set Up SAP Web Dispatcher Administration of the SAP Web Dispatcher Using
the Web Administration Interface Area menu Section “HTTP Handler”
5.2 Configuration
After installing the Web Dispatcher you have to configure and operate it.
You can find the configuration documentation the SAP Library [page 6] at:
Function-Oriented View Application Server Application Server Infrastructure SAP Web Dispatcher
5 Post-Installation Activities
5.1 Logging on to the Web Dispatcher Management Console
2011-04-28 PUBLIC 31/46
This page is left blank for documents that are printed on both sides.
6 Additional Information
6.1 Additional Information About SAPinst
The following sections provide additional information about SAPinst:
■ How to Avoid Automatic Logoff by SAPinst [page 33]
■ Interrupted Installation with SAPinst [page 34]
■ Performing a Remote Installation with SAPinst [page 35]
■ Starting SAPinst GUI Separately [page 36].
■ Running SAPinst in Accessibility Mode [page 38]
■ Troubleshooting with SAPinst [page 39]
6.1.1 How to Avoid Automatic Logoff by SAPinst
When you install the SAP system with SAPinst, the SAPinst 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
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, SAPinst assigns them and automatically logs
the account off to activate them. To avoid SAPinst 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.
CAUTION
Be 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. Choose Start Settings Control Panel Administrative Tools Local Security Policy
6 Additional Information
6.1 Additional Information About SAPinst
2011-04-28 PUBLIC 33/46
2. In the Local Security Settings window, choose Local Policies User Rights Assignment.
3. Double-click the required right under Policy and choose Add User or Group.
4. In the Select Users and Groups window, choose the required user and choose Add.
The selected user appears in the box below.
5. Confirm your entry and then repeat the steps for each remaining policy that the user requires for
the installation.
6. Log off and log on again to apply the changes.
More Information
Required User Authorization for Running SAPinst [page 18]
6.1.2 Interrupted Installation with SAPinst
The SAP system installation might be interrupted for one of the following reasons:
■ An error occurred during the Define Parameters or Execute phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description of the choices listed in the
table below as well as a path to a log file that contains detailed information about the error.
■ You interrupted the installation by choosing Cancel in the SAPinst menu.
CAUTION
If you stop an option in the Execute phase, any system or component installed by this option
is incomplete and not ready to be used. Any system or component uninstalled by this option
is not completely uninstalled.
The following table describes the options in the dialog box:
Option Definition
Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps.This is possible because SAPinst 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, SAPinst displays the same dialog box again.
Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst 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 SAPinst continues the installation from the current point.
View Log Access installation log files.
6 Additional Information
6.1 Additional Information About SAPinst
34/46 PUBLIC 2011-04-28
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 your remote host as a user who is a member of the local administrators group.
2. Make available the installation master media.
3. Restart SAPinst by double-clicking sapinst.exe. You can also start SAPinst by entering the
following commands at the Windows command prompt:
cd /d <media_drive>:\IM_WINDOWS<platform>
sapinst.exe
4. From the tree structure in 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. In the What do you want to do? screen, decide between the following alternatives and continue with
Next:
Alternative Behavior
Run a new option SAPinst 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.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>.
EXAMPLE
log_01_Oct_2008_13_47_56
CAUTION
SAPinst 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 SAPinst continues the interrupted installation from the point of failure.
6.1.3 Performing a Remote Installation with SAPinst
You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the GUI
server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from
which you control the installation with SAPinst GUI.
If your security policy requires that the person performing the installation by running the SAPinst 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.
6 Additional Information
6.1 Additional Information About SAPinst
2011-04-28 PUBLIC 35/46
As an alternative to remote installation you can use an X server for Microsoft Windows or other remote
desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open
source – for remote access to SAPinst GUI on Windows workstations. We recommend that you use the
Hummingbird Exceed X Server, which we use to validate installations with SAPinst. For more
information, see SAP Note 1170809.
You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host.
For more information, see Starting SAPinst GUI Separately [page 36].
Prerequisites
■ The remote host meets the prerequisites for starting SAPinst as described in Running SAPinst. [page
27]
■ Both computers are in the same network and can ping each other.
To test this:
1. Log on to your remote host and enter the command ping <local host>.
2. Log on to the local host and enter the command ping <remote host>.
■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER
command line parameter, make sure that this user exists on the remote host.
Procedure
1. Log on to your remote host as a user that is a member of the local administrators group.
2. Make the installation master media available on your remote host.
3. Open a command prompt and enter the following commands:
cd \d <media drive>:\DATA_UNITS\<product>_IM_WINDOWS_<platform>_<DB>
Run sapinst.exe -nogui
NOTE
If 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>
4. Execute the following command: sapinst.exe -nogui
SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the
command prompt:
guiengine: no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation
5. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 36].
6.1.4 Starting SAPinst GUI Separately
You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI separately
in the following cases:
6 Additional Information
6.1 Additional Information About SAPinst
36/46 PUBLIC 2011-04-28
■ You closed SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still running.
■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from
SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 35].
Prerequisites
The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as
described in Running SAPinst [page 27].
Procedure
Starting SAPinst GUI on Windows
1. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the
host on which you want to start the SAPinst GUI.
For more information, see Preparing the Installation Media [page 23].
2. Change to the directory of the sapinstgui executable:
<product>_IM_<your OS>_<your DB>
NOTE
If you want to start SAPinst GUI on a Windows 32-bit operating system, change to the
following directory:
<product>_IM_SAPINSTGUI_WINDOWS_I386
3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant
command line parameters:
■ If you want to perform a remote installation, execute the following command:
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
– where <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).
■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
● If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
sapinstgui.exe -standalone -port <port_number_gui_server_to_gui_client>
– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
sapinstgui.exe -host <remote_host> -port
<port_number_gui_server_to_gui_client>
6 Additional Information
6.1 Additional Information About SAPinst
2011-04-28 PUBLIC 37/46
– where <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).
The SAPinst GUI starts and connects to SAPinst.
Starting SAPinst GUI on UNIX
1. Make the medium for the installation master (folder <Product>_IM_<OS>_<DB>) available on the
host on which you want to start the SAPinst GUI.
For more information, see Preparing the Installation Media [page 23].
2. ■ If you want to start the SAPinst GUI on a Linux 32-bit platform, change to the directory
<product>_IM_SAPINSTGUI_LINUX_I386.
■ If you want to perform a remote installation, execute the following command:
./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client>
– where <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).
■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, proceed
as follows:
● If you are performing a local installation with SAPinst and SAPinst GUI running on the
same host, execute the following command:
./sapinstgui -port <port_number_gui_server_to_gui>
– where <port_number_gui_server_to_gui> is the port the GUI server uses to
communicate with the GUI client (21212 by default).
● If you are performing a remote installation with SAPinst and SAPinst GUI running on
different hosts, execute the following command:
./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui>
– where <remote_host> is the name of the remote host, and
<port_number_gui_server_to_gui> is the port the GUI server uses to communicate with
the GUI client (21212 by default).
The SAPinst GUI starts and connects to SAPinst.
6.1.5 Running SAPinst in Accessibility Mode
You can also run SAPinst in accessibility mode. The following features are available:
■ Keyboard access:
This feature is available for all operating systems.
■ High-contrast color:
6 Additional Information
6.1 Additional Information About SAPinst
38/46 PUBLIC 2011-04-28
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 SAPinst or the SAPinst GUI.
NOTE
The 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 SAPinst in Accessibility Mode
You can either perform a local installation, where SAPinst and SAPinst GUI are running on the same
host, or a remote installation, where SAPinst and SAPinst GUI are running on different hosts.
■ Local installation:
Start SAPinst as described in Running SAPinst [page 27] by executing the following command:
sapinst.exe –accessible
■ Remote installation:
1. Start SAPinst on the remote host by executing the following command from the command
line as described in Performing a Remote Installation with SAPinst [page 35]:
sapinst.exe –nogui
2. Start SAPinst GUI on the local host by executing the following command from the command
line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 36]:
sapinstgui.exe -accessible –host <remote_host> -port
<port_number_gui_server_to_gui_client>
6.1.6 Troubleshooting with SAPinst
This section tells you how to proceed when errors occur during the installation with SAPinst.
6 Additional Information
6.1 Additional Information About SAPinst
2011-04-28 PUBLIC 39/46
If an error occurs, SAPinst:
■ Stops the installation
■ Displays a dialog informing you about the error
Procedure
1. Check SAP Note 1548438 for known SAPinst 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 installation with Exit.
For more information, see Interrupted Installation with SAPinst [page 34].
■ Continue the installation by choosing Retry.
4. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%
\.sdtgui\ for errors.
■ If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current %
userprofile% directory.
■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI
as described in Starting SAPinst GUI Separately [page 36].
5. If you cannot resolve the problem, create a customer message using component BC-INS.
6.2 Uninstall
The following procedure describes how to uninstall a Web Dispatcher using SAPinst.
Procedure
1. Start SAPinst [page 27].
2. On the Welcome screen, choose Software Life-Cycle Tasks Uninstall Uninstall SAP Systems or Single
Instances .
3. Follow the instructions in the SAPinst screens.
6.3 Troubleshooting with SAPinst
This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
■ Stops the installation
■ Displays a dialog informing you about the error
Procedure
1. Check SAP Note 1548438 for known SAPinst issues.
6 Additional Information
6.2 Uninstall
40/46 PUBLIC 2011-04-28
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 installation with Exit.
For more information, see Interrupted Installation with SAPinst [page 34].
■ Continue the installation by choosing Retry.
4. Check the log and trace files of the GUI server and SAPinst GUI in the directory %userprofile%
\.sdtgui\ for errors.
■ If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current %
userprofile% directory.
■ If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI
as described in Starting SAPinst GUI Separately [page 36].
5. If you cannot resolve the problem, create a customer message using component BC-INS.
6 Additional Information
6.3 Troubleshooting with SAPinst
2011-04-28 PUBLIC 41/46
Typographic Conventions
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>”.
ExampleExample
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
http://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
42/46 PUBLIC 2011-04-28
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34F +49/18 05/34 34 20
www.sap.com
© Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
2011-04-28 PUBLIC 43/46
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply.1. This software was developed using ANTLR.2. SAP License Agreement for STLport
SAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingNeurottstrasse 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)1. Subject Matter of the Agreement
1. SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee.
2. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.
3. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions.
4. Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG
5. The Customer may distribute original or modified STLport sources, provided that: ■ The conditions indicated in the above permissions notice are met; ■ The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:Coypright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes 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 purposes 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 makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. 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.
44/46 PUBLIC 2011-04-28
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes 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. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.
2. Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.
3. Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.
4. Limited Liability1. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this
(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.
2. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software.
3. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit.
4. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.
5. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.
6. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.
3. Adobe Document ServicesAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.
Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides
2011-04-28 PUBLIC 45/46
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com
© Copyright 2011 SAP AG. 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 AG. The information contained herein may be changed without prior notice.