SAPGUI 6.20 Installation, Patch Application, and Tips

Created: 11/12/2002

Citrix Information Technologies Team

Citrix SAP CC

Table of Contents

SAPGUI 6.20 Installation 3

Installation Process 3

Post-Installation Process 4

SAP Front End Patch Installation to Existing GUI 5

Curent Patch Level 5

How to Apply the Patch to an Existing GUI 5

Tips for Optimizing SAPGUI on MetaFrame 6

Tuning 6

Using Multiple or Central SAP INI files in MetaFrame 7

Printing (How it Works) 8

SAPGUI 6.20 Installation

The SAPGUI 6.20 utilizes both scripted and manual steps. The process for installing the Version SAPGUI 6.20 is described below, utilizing the Citrix Application Packaging and Delivery (Installation Manager).

Installation Process

1. Log on to a local server desktop as a domain administrator.

2. Start Installation Manager - Citrix Packager.

3. Select Create a new project using wizard and then click Next.

4. Select a project wizard, then select Package an installation recording and click Next.

5. Provide a project name and location, and then click Next.

6. Choose an installation program. Browse to Setup.exe in Step E below to begin.

A. Turn off any registry capture or file capture utilities such as RegMon or Filemon.

B. Open a command prompt.

C. Map a network drive (if it’s a network share) for the installation to avoid complications later on; otherwise, utilize the CD-ROM for installation.

D. Type change user /install at the command prompt.

E. Run Setup.exe from your source location (CD-ROM or network share).

F. At the SAP FrontEnd Welcome Screen, click Next.

G. Click Next.

H. Select the destination folder and enter drive letter:\install path.

I. Click Next.

J. Select the necessary components for your specific installation.

K. Click Next.

The following steps are the installation phase — this takes some time.

L. Right-click My Computer and go to Properties.

M. Click the Advanced tab.

N. Click Environment Variables.

O. Under the System Variables subwindow, click New.

• Variable: LP_CMD

• Value: “drive letter:\install path\sapgui\saplpd\saplpd” –f&F –c&C –P&P

Look up the latest version of SAP note 150533 for updates or changes.

P. Click OK twice.

Q. Installation Manager proceeds to analyze, build, and post process.

7. The following steps were performed manually for the sake of time. Each of the steps below can be scripted to comply with the automation of server and application builds and installations.

A. From a command prompt, type change user /install again because the server was restarted.

B. Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\WFShell\TWI

Create following entries:

Key = SAPGUI

Value = ClassName

Datatype = REG_SZ

String = SAP_FRONTEND_SESSION

Value = Type

Datatype = REG_DWORD

String = 1 (use hex, the default)

C. Open the registry editor (regedt32.exe).

D. Navigate to the following registry key:

HKEY_LOCAL+MACHINE\SYSTEM\SAP\SAP Shared

E. Change the SAPworkdir value to the desired path (that is, the user’s home drive)

F. If you want to use local copies of Saplogon.ini, copy the Saplogon.ini, Saproute.ini, and Sapmsg.ini from your source location to os install > point:\WINNT.

G. Rename the Services file in os install point:\SYSTEM32\DRIVERS\ETC to Services.bak.

H. Copy Services from your source location to os install > point:\SYSTEM32\DRIVERS\ETC.

Post-Installation Process

1. Provide change permission for your users to the os install > point:\SYSTEM32\DRIVERS\ETC” and drive letter:\install path\SAPGUI folders.

2. If you want to publish the SAP Easy Acess items in NFuse, the .sap links can be published like this:

drive letter:\install path\sapgui\sapshcut.exe drive letter:\install path\sapgui \SAPGUI\??.sap

3. The easiest solution is to create SAP shortcut files from the MetaFrame server after the installation is complete. Be sure to set the attributes for these .sap files to read-only after creation to avoid any unintentional user changes. Then move these .sap files to an appropriate location on the server.

4.

Go to the R3.Tspoptions table

• Update the table by adding LPRINT_NUM

• Update the table by adding LPRINT_DEST with a value of LOCAL_PRINT

5. Add TCP/IP Print Services (only if you are having problems with front-end printing) and tried Step 10. above first without success. Add TCP/IP printing services:

A. Add / Remove programs.

B. Go to Windows.

C. Add/Remove.

D. Go to the other Windows Components box.

E. Add TCP/IP Print Services.

F. Select the os install point:\I386 folder as the location

6. Restart the server.

SAP Front End Patch Installation to Existing GUI

Curent Patch Level

Locate the SAPgui.exe file in the drive letter:\install path \SAPGUI directory. Right-click the executable and select Properties. From the Version tab, view the file version (for example, 6202.2.19.8920). The patch level is 19 in this example.

How to Apply the Patch to an Existing GUI

A. Open Internet Explorer.

B. Go to http://service.sap.com\patches.

C. Click OK at the prompt.

D. Type the OSS user name and password.

E. Select SAP GUI for Windows.

F. Select SAP GUI for Windows 6.20.

G. Select Win32.

H. The Main menu lists patch downloads along with the patch level.

I. Select the preferred patch by clicking File Name.

J. Save Download.

K. Go to Start > Run and type cmd.

L. Type change user /install.

M. Run the executable GUI620.exe.

N. Click Next on the Patch Wizard screen.

O. The previous SAP version is automatically removed, after which Version 6.20 is installed.

P. Click Finish when installation is complete.

Tips for Optimizing SAPGUI on MetaFrame

Tuning

Removing the Water-Gif

1. You can deactivate the picture globally so that no one sees it with "HIDE_START_IMAGE" "YES" in the table SSM_CUST. User-specific picture display settings are then ignored.

2. The proposed individual solution in text is supplemented by visual aids below.

3. Extras > Settings.

4. Check Do not display picture.

Turning off Enjoy mode

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\General\Enjoy

Key: Active

Set the value to Off.

Due to a higher user acceptance, in most installation this key remains On.

Turning off the SapGui splash screen

HKEY_LOCAL+MACHINE\SOFTWARE\SAP\General\Appearance

Key: SplashOff

Set the value to 1.

Switching off the waiting time animation in enjoy mode

HKEY_LOCAL+MACHINE\SOFTWARE\SAP\General\Appearance

Create a new Value:

Value: Animation

Type: REG_SZ

String: Off

Using Multiple or Central SAP INI files in MetaFrame

1. A user wants to show in SAPLOGON only a subset of all available SAP systems or just wants to use a single file on a network share. The SAP systems are listed in the Saplogon.ini file that is by default stored in the os install point:\winnt\saplogon.ini directory and is valid for all users.

2. Saplogon.exe /INI_FILE=<filename>.

3. For example, saplogon.exe /INI_FILE=c:\winnt\saplogon1.ini.

4. Alternatively, you can use a variable in the user environment.

5. SAPLOGON_INI_FILE

Note: Ensure that the path of <filename> does not contain blanks. See SAP note 38119 for further details and updates.

Printing (How it Works)

Three types of printing are available in SAP: local, SAP-Defined, and operating system-defined.

Local Printing

1. Create a default printer on your local system (it will have a check on it in Start > Settings > Printers).

2. Log on to Metaframe.

3. MetaFrame maps ONLY your default printer into the Metaframe session provided that the print drivers for that printer exist on the server. If it is a locally connected printer (parallel cable), no spaces can be in the printer name.

4. Launche SAP.

5. Go to a transaction and select Print.

6. Select LOCL.

7. The SAP application launches a sub-application (SAPLPD). This is installed on the MetaFrame server.

8. The SAPLPD command launches and creates a new window in MetaFrame. The SAPLPD window spools the SAP information to the MetaFrame server.

9. The MetaFrame server spools the information to the print queue on your local system.

10. Your system passes the print spool to the network printer

SAP Defined Printing

1. Select a SAP defined printer (one that was previously created by the Basis team in SAP).

2. SAP spools the job through it’s spooler on the SAP application server to the
Windows NT print server.

3. The print server takes the spool request and processes it.

Operating System-Based Printing

This is a unique case of SAP defined printing that bypasses the normal print server. This allows added security and a consistent format.

The printer is defined in a UNIX print queue or a print queue local to the SAP system. This queue bypasses the normal print queue available for printers in your enterprise.

Create the SAP-defined printer to this new queue.

Additional SAP Notes

SAP notes are available over the SAP Service Marketplace only.

The SAP Service Marketplace is not a public system but open to SAP customers and partners only.

Link: http://service.sap.com/notes