Installing/Upgrading the SAP Frontend Software 

You must install the SAP frontend software (SAPgui) on all hosts whose users log on directly to the SAP System. Installing and upgrading this software can require a lot of time and effort to administrate. The SAP frontend installation programs let you install and upgrade the SAP frontend software with as little effort as possible.

Users who access Web-based SAP applications exclusively (for example, Employee Self Service or Electronic Commerce) only require a Web browser. You also need a Web browser for the SAP Online Help.

The installation of the SAP frontend software was fundamentally changed with R/3 Release 4.5A. This new installation is explained here. For more information, see the installation guide Installing SAP Frontend Software for PCs.

Installation Options and Attributes

You can install the SAP frontend software in two ways:

There are two types of installation procedures:

 

The tasks of the SAP installation programs are:

Planning the SAP Frontend Installation

If several PCs are connected over a local network, use fixed frontend servers to distribute and administrate the software instead of installing the software on all the workstations individually from the CD. This also applies to the SAP frontend software. The SAP frontend installation programs simplifies the setup of frontend servers.

Before the installation, the administrator must consider the following:

The Installation in Detail

You can install the frontend software from a CD or by using a frontend server. The frontend server can be a pure file server that makes the installation CD data available to the PCs. You can also install a SAPgui installation server that offers the end user predefined software packages.

Installing the Installation Server

To use a host as a frontend installation server for the SAP software, the relevant contents of the SAP presentation CD must be sent to the hard disk. You can do this by using the setup program on the installation CD. You then have to release the directory to which the software is copied as a shared directory in the network.

After you have installed the installation server, you choose the installation package by calling the administration program. This program also installs the Windows NT installation service, if this is needed.

The Windows NT installation service makes sure that the installation program is always executed with the user ID of the person who has logged on. This security mechanism prevents specific installation steps from being executed by non-authorized users, depending on the configuration of the workstation. In this case, the installation program searches for an installation service within the domain. The service takes over the relevant installation step and then gives back control to the installation program that runs under the normal user ID.

An installation package contains a selection of SAPgui and Desktop components. Certain installation parameters, such as the installation directory and work directory, can be predefined on the workstation. You can also use computer- and user-specific placeholders, for example, for the system directory. Furthermore, you can release packages for specific user groups, and choose different packages for various operating systems.

Local Installation from the CD or Network Drive

The local installation is always interactive, where you run the SAP installation program on the client PC. The user can choose the required components that are available. You must also specify the target directory and work directory on the client PC.

To perform the local installation, the presentation CD must be inserted in the workstation CD drive or the workstation must have access to the installation software on the frontend server using a drive connection.

After the installation, the SAP frontend software is located on the hard disk of the client PC. You do not need the connection to the frontend server anymore when using the SAPgui.

(1) Frontend is installed

(2) SAPgui is started

(3) Communication with the R/3 System

 

Advantages:

Disadvantages:

Local Installation from a Frontend Server with Installation Package

You install installation packages on the workstation by using the program NetSetup. In interactive mode, the user can choose the package needed from the ones available. If you enter the relevant command line parameters, which specify the installation package, the installation can run without any dialogs.

Another program option is a check to see if an installation is required. If all the components of the package are up-to-date and available on the workstation, the program ends immediately; otherwise the installation begins without any dialogs. This is particularly useful for automatically distributing the SAP frontend software in logon scripts.

After the installation, the SAP frontend software is located on the hard disk of the client PC. You do not need the connection to the frontend server anymore when using the SAPgui.

(1) Installation package is created

(2) SAP frontend software is installed on the workstation

(3) SAPgui is started

(4) Communication with the SAP System

Advantages:

Disadvantages:

Server-Based Installation from Frontend Server with Installation Package

You can only perform the server-based installation with installation packages from a frontend server. When choosing the installation package by using the administration program, you have to specify that the installation is to be server-based. The software has to be installed on each workstation and corresponds directly to a local installation with installation packages. This installation is much faster since fewer files have to be copied.

The SAP frontend software is loaded each time the frontend server is started. Only a few system files and ActiveX controls, which have to be registered locally on the frontend computer, are stored on the PC. This saves a large amount of hard disk space on each workstation.

Each time the SAPgui is started, approximately 3 MB of data is transmitted. Additional data traffic is created when desktop components are used, such as SAP Business Graphics, the graphical Screenpainter, and so on.

(1) Installation package is created

(2) SAP frontend software is installed on the workstation

(3) SAPgui is started over the network from the frontend server

(4) Communication with the SAP System

Advantages:

Disadvantages:

Remote Networks

For physically remote locations, you need to consider the same factors that were covered in the previous sections about a purely local network solution. When distributing the software to the client PCs, consider each location as an individual unit. When providing new versions for the decentralized locations, you should do this centrally (see graphic).

Install one or several frontend servers at each location - depending on the number of clients connected there. For locations with less than 5 PCs, a peer-to-peer solution can also be used. You can implement all of the described approaches at the locations.

We recommend controlling the software distribution using a central server, since this ensures consistency for all locations.

The current frontend software is installed from the SAP installation CD on the central server, and then it can be distributed to the servers at the decentralized locations. The new version of the software is distributed only once for each location.

Laptops

The SAPgui communication protocol has been optimized to keep network loads to a minimum. This means that it is suited to connections with a narrow bandwidth (for example, telephone lines with a modem. See SAPgui in Wide Area Networks).

When you install frontend components, you must install the SAP frontend software locally (depending on the chosen components, approximately 25 to 150 MB) on the hard disk of your laptop. A server-based installation is usually not an option since the programs used must be transmitted each time before you use them. There are several methods for installing the SAPgui on laptops, three of which are described in the following section.

Installing Software over Wide Area Network (WAN)

Field sales employees may need to get the newest version of the SAP frontend software from a remote connection. If your laptop is connected to a WAN corporate network, you can install the software like a local installation. When choosing installation packages, consider the available telephone line transmission speed and the amount of data to be transmitted.

If you cannot establish a direct connection to a corporate network, you can also use the file transfer protocol (FTP) to transmit the installation directories and files to the laptop. Then the software is installed locally. If you do not need all of the files from the installation CD, ensure that you can actually install the files that you want to transmit. We recommend the installation of software using WAN connections for minimal installations only (SAPgui without additional components), since the amount of data can grow significantly with additional components.

Installing Software from a CD

If your laptop has a CD drive, you may want to install the software locally directly from the CD.

Installing Software over a Temporary LAN Connection

You can install the software if your laptop is connected temporarily to a LAN (for example, using a docking station) while you are at a corporate branch. The SAP frontend software is installed or updated in a few minutes just like the installation on a normal workstation.

(1) Installation using a WAN connection

(2) Installation from a CD

(3) Installation using a temporary connection to the LAN