36
Installation Guide SAP Library Installation and Update on Windows For SAP systems based on SAP NetWeaver 7.3 (including SAP Business Suite Java Hubs on SAP NetWeaver 7.3) SAP NetWeaver 7.3 SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0) Java Hubs on SAP NetWeaver 7.3 SAP Business Suite 7i 2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1) Java Hubs on SAP NetWeaver 7.3 SAP Business Suite 7i 2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SRM 7.0 EHP2) Java Hubs on SAP NetWeaver 7.3 Target Audience System Administrators Technical Consultants PUBLIC Document version: 1.10 – 2011-11-08

SAP Library Windows Netweaver 7.30

Embed Size (px)

DESCRIPTION

SAP Library Windows Netweaver 7.30

Citation preview

Page 1: SAP Library Windows Netweaver 7.30

Installation GuideSAP Library Installation and Update on WindowsFor SAP systems based on SAP NetWeaver 7.3 (including SAP Business Suite Java Hubs on SAP NetWeaver 7.3)

■ SAP NetWeaver 7.3■ SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0) Java

Hubs on SAP NetWeaver 7.3■ SAP Business Suite 7i 2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1)

Java Hubs on SAP NetWeaver 7.3■ SAP Business Suite 7i 2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SRM 7.0 EHP2)

Java Hubs on SAP NetWeaver 7.3

Target Audience ■ System Administrators ■ Technical Consultants

PUBLICDocument version: 1.10 – 2011-11-08

Page 2: SAP Library Windows Netweaver 7.30

Document History

The following table provides an overview of the most important document changes.

Version Date Description

1.10 2011-11-08 Updated Version

1.0 2010-11-29 Initial Version

2/36 PUBLIC 2011-11-08

Page 3: SAP Library Windows Netweaver 7.30

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 Variants of SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 HtmlHelpFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 PlainHtmlHttp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3 PlainHtmlFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4 DynamicHelp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.5 Criteria for Selecting the Help Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1 Installing HtmlHelpFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.2 Installing PlainHtmlHttp and PlainHtmlFile . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.3 Installation of Help Files Using SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3.1 Preparations for the Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3.1.1 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3.1.2 Required Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.3.2 Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.3.2.1 Installing and Updating SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.3.2.2 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1 Using a Web Browser or Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.2 Offline Access to Help Files - SAP Library Navigation . . . . . . . . . . . . . . . . . . . . 20

4.3 Setting Variants for SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 5 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1 About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1.1 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1.2 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.1.3 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

5.1.4 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5.1.5 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2011-11-08 PUBLIC 3/36

Page 4: SAP Library Windows Netweaver 7.30

5.2 Local Override of Help Settings on Front Ends . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.2.1 File sapdoccd.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.2.2 Parameters in File sapdoccd.ini . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.2.3 Logging of Help Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4/36 PUBLIC 2011-11-08

Page 5: SAP Library Windows Netweaver 7.30

1 Introduction

This document explains how to install or update SAP Library for SAP systems based on SAP NetWeaver

7.3:

■ SAP NetWeaver 7.3

■ SAP Business Suite 7 (SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0) Java Hubs on

SAP NetWeaver 7.3

■ SAP Business Suite 7i 2010 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1) Java Hubs

on SAP NetWeaver 7.3

■ SAP Business Suite 7i 2011 (SAP ERP 6.0 EHP6, SAP CRM 7.0 EHP2, SAP SRM 7.0 EHP2) Java Hubs

on SAP NetWeaver 7.3

SAP Library is an HTML-based solution for online documentation. It provides the basis for context-

sensitive application help and also includes the SAP glossary. The contents of SAP Library can be

displayed in a Web browser on all front-end platforms supported by SAP. SAP Library is available in

several different variants; the installation of each of these variants is described in its own topic:

■ Installing HtmlHelpFile [page 11]

■ Installing PlainHtmlHttp and PlainHtmlFile [page 12]

■ Separately from the installation, you can also override the help settings on the front end:

Local Override of Help Settings on Front Ends [page 29]

Prerequisites

You have received the DVD/CD set of SAP Library. We deliver the online help on these DVDs/CDs in

two formats: standard HTML (Plain HTML) and compiled HTML (HTML help). Subdirectories contain

the different language versions.

Implementation Considerations

On Microsoft Windows front ends, at least SAP GUI 7.10 must be installed to enable access to the

documentation from the SAP system. For more information, see SAP Note 66971.

NOTE

See also the information in the README.TXT file on the Documentation DVD (see Required Installation

DVDs [page 14]).

If you have any problems installing or displaying SAP Library, create a customer message on SAP Service

Marketplace under the quick link message. Use the component BC-DOC-IWB-DIS for any issues relating

to static help or the component KM-KW for any issues relating to dynamic help.

1 Introduction

2011-11-08 PUBLIC 5/36

Page 6: SAP Library Windows Netweaver 7.30

SAP Notes for the Installation

You must read SAP Note 1261881before you start the installation. This SAP Note contains 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 at http://

service.sap.com/notes.

1 Introduction

6/36 PUBLIC 2011-11-08

Page 7: SAP Library Windows Netweaver 7.30

2 Variants of SAP Library

To handle the demands and features presented by different front-end platforms, the HTML-based

online help is provided in several variants (help types). The main differences between the help types

are the storage format (Standard HTML or Compiled HTML), the way you access the help documents

(Web server or file server), and the search and print functions.

Help Types

HtmlHelpFile PlainHtmlHttp PlainHtmlFile

Front-end platforms

All Windows platforms supported by Microsoft

All All Windows platforms supported by Microsoft

File format Compiled HTML Standard HTML Standard HTML

Accessed from File server Web server File server

Displayed in HTML Help Viewer (installation of Microsoft Internet Explorer required)

Web browser (Microsoft Internet Explorer or Netscape)

Web browser (Microsoft Internet Explorer or Netscape)

Global full-text search

X (from SAP Help Portal at http://help.sap.com; launched, for example, from the banner of the DVD)

Local full-text search

X (in CHM file)

Printing of single topics

X X X

Printing of multiple topics

X

Supported operating systems for the help installation

Microsoft Windows ■ IBM AIX ■ HP-UX ■ Sun Solaris ■ Linux ■ Microsoft Windows

■ IBM AIX ■ HP-UX ■ Sun Solaris ■ Linux ■ Microsoft Windows

NOTE

Customers using SAP Knowledge Warehouse can call both SAP documentation and their own

custom-made documentation dynamically from SAP KW (help type DynamicHelp).

For more information about selecting a help type, see Criteria for Selecting the Help Type [page 10].

2 Variants of SAP Library

2011-11-08 PUBLIC 7/36

Page 8: SAP Library Windows Netweaver 7.30

2.1 HtmlHelpFile

This help type stores documents in Compiled HTML format (*.CHM). They are accessed from a file

server and displayed in the HTML Help Viewer. Compiled HTML is a format developed by Microsoft

for storing HTML files in compressed form. CHM files require about one-tenth of the disk space required

for uncompressed HTML files and about the same space as required for WinHelp files. HTML Help

Viewer was introduced by Microsoft as a successor to WinHelp. It is based on the Internet Explorer.

Features

■ Can be used only on Windows front-end platforms

■ Documents can be accessed directly from the DVD

■ Documents are displayed in HTML Help Viewer (requires Microsoft Internet Explorer)

■ Navigation in structures and from hyperlinks

■ Full text search in the documents in the current help file (local search)

■ Multiple documents within the same structure can be printed simultaneously.

System Requirements

Front-End Requirements for HtmlHelpFile

Operating System Requirements

Microsoft Windows 2000 Pentium 233 MHz (300 MHz recommended)1 GB RAM

Microsoft Windows 2003 Pentium 233 MHz (300 MHz recommended)1 GB RAM

Microsoft Windows XP Pentium 233 MHz (300 MHz recommended)1 GB RAM

Microsoft Windows VISTA Pentium 2.00 GHz (3.00 GHz recommended)1 GB RAM (2 GB recommended)

Microsoft Windows 7 Pentium 2.00 GHz (3.00 GHz recommended)1 GB RAM (2 GB recommended)

Server Requirements for HtmlHelpFile

See Hardware and Software Requirements [page 14].

2.2 PlainHtmlHttp

This help type stores documents in Standard HTML format. They are available from a Web server and

can be displayed in a standard Web browser.

Features

Characteristics

■ Can be used on all front-end platforms

2 Variants of SAP Library

2.1 HtmlHelpFile

8/36 PUBLIC 2011-11-08

Page 9: SAP Library Windows Netweaver 7.30

■ Documents displayed with a standard Web browser (Microsoft Internet Explorer or Netscape)

■ Full-text search in all SAP documents from the help portal http://help.sap.com

■ Navigation in structures (tables of contents) and from hyperlinks

■ Printing of single help documents

System Requirements

System Requirements for PlainHtmlHttp

System Requirements

Front end No requirements other than those of the Web browser

Server See Hardware and Software Requirements [page 14].

NOTE

See also SAP Note 563776 (Supported Web Servers for Windows).

2.3 PlainHtmlFile

This help type stores documents in Standard HTML format. They are available from a file server and

can be displayed in a standard Web browser.

Features

Characteristics

■ Can be used on all front-end platforms

■ Documents displayed with a standard Web browser (Microsoft Internet Explorer or Netscape)

■ Navigation in structures (tables of contents) and from hyperlinks

■ Printing of single help documents

System Requirements

System Requirements for PlainHtmlFile

System Requirements

Front end No requirements other than those of the Web browser

Server Between 850 MB (Microsoft Windows NT) and 2 GB (UNIX) of free disk space for each language version, depending on the file system

2.4 DynamicHelp

The help type DynamicHelp can be used on all front-end platforms. Like the PlainHtml help types it uses

a standard HTML file format, and a standard Web browser for viewing. Before you can launch

DynamicHelp, SAP Knowledge Warehouse must be installed in the system landscape. Files are accessed

through SAP IKS (Internet Knowledge Servlet). The content itself is stored on a content server, which

means you do not need to install the help files.

2 Variants of SAP Library

2.3 PlainHtmlFile

2011-11-08 PUBLIC 9/36

Page 10: SAP Library Windows Netweaver 7.30

To display the correct information from DynamicHelp, you must set the correct target context in the

SAP system. For more information, see SAP Note 594231. This context must also be defined in the SAP

Knowledge Warehouse system.

2.5 Criteria for Selecting the Help Type

The decision about which help type to install in a given SAP system mainly depends on the operating

system of the front-end clients.

■ If you use front ends on Microsoft Windows only, we recommend that you install the help type

HtmlHelpFile. This help type offers more extensive search and print functions than the other

two help types. However, you are free to install any help type.

NOTE

If you are using different front-end platforms in parallel, and therefore have to choose a help

type other than HtmlHelpFile, you can still use the help type HtmlHelpFile. For more

information, see Local Override of Help Settings on Front Ends [page 29] on clients running on

Microsoft Windows.

■ If you use front-end platforms other than Microsoft Windows, we also recommend that you install

PlainHtmlHttp, since this help type provides a full-text search function from the SAP help portal.

■ If you do not have a Web server and you use front-end platforms other than Microsoft Windows,

you must use help type PlainHtmlFile.

■ If you want to access SAP documentation from both SAP GUI for Windows (Win GUI) and SAP

GUI for HTML (Web GUI), or from a browser-based SAP application, you cannot use help type

HtmlHelpFile.

The following figure helps you to choose the correct help type:

Figure 1:

2 Variants of SAP Library

2.5 Criteria for Selecting the Help Type

10/36 PUBLIC 2011-11-08

Page 11: SAP Library Windows Netweaver 7.30

3 Installation

When you install the SAP Library, you provide the users of your SAP systems with the entire help

documentation online.

Prerequisites

You have received the SAP Library DVD. We deliver the online help on this DVD in two file formats:

Standard HTML and Compiled HTML (HTMLHelpFile). Subdirectories contain the different language

versions.

Process Flow

For online access from the SAP system, both formats require you to perform the following steps:

1. You install the help files in one of the following ways:

■ You install the HtmlHelpFile either manually or using SAPinst as described in Installing

HtmlHelpFile [page 11].

■ You install the PlainHtmlHttp and PlainHtmlFile using SAPinst as described in Installing

PlainHtmlHttp and PlainHtmlFile [page 12].

2. You maintain setting variants for the online help in transaction SR13 as described in Setting Variants

for SAP Library [page 21].

Result

Once you have completed these steps, you can access SAP Library both online in the SAP system and

offline when you have no connection to the system.

3.1 Installing HtmlHelpFile

This procedure describes how you install HtmlHelpFile. The Compiled HTML files for help type

HtmlHelpFile can be viewed directly from the DVD in Microsoft HTML Help Viewer. For better

performance, copy the help files to your local hard disk or to a file server (as described in the procedure

below).

You can also use SAPinst to install the HtmlHelpFile. If you want to do this, do not follow the procedure

below but instead proceed as described in Installation of Help Files Using SAPinst [page 13].

RECOMMENDATION

We strongly recommend that you install the HtmlHelpFile with SAPinst.

3 Installation

3.1 Installing HtmlHelpFile

2011-11-08 PUBLIC 11/36

Page 12: SAP Library Windows Netweaver 7.30

Prerequisites

To install SAP Library, you require the Documentation DVD (see Required Installation DVDs [page 14]).

To display the documentation, a suitable browser or viewer must be installed on your computer, as

described in Using a Web Browser or Viewer [page 19].

Procedure

1. Create a directory on your file server for the help files.

This called the documentation directory. Approximately 2 GB of disk space is needed for the English

and German language versions.

2. Insert the appropriate DVD into the DVD/CD drive.

3. Copy the directory HTMLHELP\<language key> with all its subdirectories from the DVD to the

documentation directory on the server.

4. Share the directory.

Result

You have installed SAP Library. Once you have maintained the setting variants in transaction SR13,

you can access the documentation both from the SAP system and offline. When you maintain setting

variants, you define which help variants are available to the user. For more information, see Setting

Variants for SAP Library [page 21].

3.2 Installing PlainHtmlHttp and PlainHtmlFile

This procedure describes how to install PlainHtmlHttp or PlainHtmlFile. The Standard HTML files

for help types PlainHtmlHttp and PlainHtmlFile are stored in a packed format in the archive

PLAINHTM.SAR on the DVD. They cannot be viewed directly from the DVD but must first be unpacked

to the local hard drive or on a file server. To install the help files, you must use SAPinst as described in

Installation of Help Files Using SAPinst [page 13].

CAUTION

The complete installation comprises about 200,000 files in about 100,000 directories for one

language version. Depending on the file system and the configuration of the hard disk, they require

they require up to 850 MB of disk space.

Prerequisites

To install SAP Library, you require the Documentation DVD. To display the documentation, a suitable

browser or viewer must be installed on your computer. For more information, see Using a Web Browser

or Viewer [page 19].

3 Installation

3.2 Installing PlainHtmlHttp and PlainHtmlFile

12/36 PUBLIC 2011-11-08

Page 13: SAP Library Windows Netweaver 7.30

NOTE

When you call the search function from the banner of the relevant documentation DVD, an

Internet connection is opened enabling a full text search from the DVD. To use the full text search

function, you need an Internet connection.

NOTE

If Java scripting is not enabled, the button for the full-text search function appears in the browser

banner even though this function is only available with help type PlainHtmlHttp. If you choose

the button, an error message appears. To remove the button from the banner when using

PlainHtmlFile, enable Java scripting in your browser settings as follows:

For Microsoft Internet Explorer 5.01 (or later), choose level Medium or Low from the Internet option

Security in the Local intranet zone.

Procedure

Install PlainHtmlHttp and PlainHtmlFile using SAPinst as described in Installation of Help Files Using

SAPinst [page 13].

Result

The archive PLAINHTM.SAR is unpacked and the help files are written to the Web server. This takes about

30 minutes, depending on the operating system and the data transfer rate of the DVD drive. The

directory tree created on the Web server when you install the English language version has the following

structure:

<InstallDir>

- PLAINHTM

+ EN (help files, English version)

NOTE

For PlainHtmlHttp, you must create the alias /saphelp. Define this alias to point to your installation

directory <InstallDir>. The Web server requires read access for /saphelp.

You have installed SAP Library. Once you have maintained the setting variants in transaction SR13,

you can access the documentation both from the SAP system and offline. When you maintain setting

variants, you define which help variants are available to the user. For more information, see Setting

Variants for SAP Library [page 21]

3.3 Installation of Help Files Using SAPinst

3.3.1 Preparations for the Installation with SAPinst

You have to perform the following steps to prepare the installation or update of the SAP Library with

SAPinst:

3 Installation

3.3 Installation of Help Files Using SAPinst

2011-11-08 PUBLIC 13/36

Page 14: SAP Library Windows Netweaver 7.30

1. Check that your installation host meets the hardware and software requirements [page 14].

2. Make sure that the required installation DVDs [page 14] are available.

3.3.1.1 Hardware and Software Requirements

Make sure that your host meets the hardware and software requirements:

■ Minimum RAM:

0.5 GB

■ Minimum disk space:

● 2.2 GB in the help destination directory

● Approximately 600 MB of disk space are required for one language version (Windows NTFS)

● 4.3 GB of temporary disk space for every required installation DVD that you have to copy to

a local hard disk

● 1.2 GB of temporary disk space for the installation

■ For supported operating system releases, see the Product Availability Matrix at http://

service.sap.com/pam.

CAUTION

You cannot install SAP Library help files on a Microsoft FAT32 file system because this file

system cannot handle the large number of files and directories. If your web server runs on

Microsoft Windows, do not install the help documentation on the system partition. Instead,

choose another partition.

3.3.1.2 Required Installation Media

Make sure that you have the following installation media available:

■ Installation Master (folder <Product>_IM_<OS>_<DB> on SAP NETWEAVER 7.3 OS/DB Dependent

Components) – contains the installation with SAPinst

■ SAP NETWEAVER 7.3 SPS<no> HTML-Help for WindowsOnline Documentation – contains the

SAP Library Help Files

The media names listed above are abbreviated. For the full names, see the Media List SAP NetWeaver

7.3 on SAP Service Marketplace at http://service.sap.com/installnw73.

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>

3 Installation

3.3 Installation of Help Files Using SAPinst

14/36 PUBLIC 2011-11-08

Page 15: SAP Library Windows Netweaver 7.30

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

1. Create a download directory on the host on which you want to run SAPinst.

2. 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 a medium have the same title, such as

<solution><media_name><OS> or <database>RDBMS<OS> for RDBMS media.

3. Download the objects to the download directory.

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

the same directory.

In the unpacking directory, the system creates a subdirectory with a short text describing the

medium and copies the data into it. The data is now all in the correct directory, the same as on the

medium that was physically produced. For more information, see SAP Note 1258173.

3.3.2 Installation with SAPinst

■ Installing and Updating SAP Library [page 15]

■ Running SAPinst [page 16]

3.3.2.1 Installing and Updating SAP Library

This procedure tells you how to install and update SAP Library with SAPinst:

■ Install means that you install SAP Library from scratch.

■ Update means that you update an existing version of SAP Library.

3 Installation

3.3 Installation of Help Files Using SAPinst

2011-11-08 PUBLIC 15/36

Page 16: SAP Library Windows Netweaver 7.30

Prerequisites

■ The installation host meets the hardware and software requirements for the SAP Library

installation as described in Hardware and Software Requirements [page 14].

■ The required installation DVDs are available on the installation host as described in Required

Installation DVDs [page 14].

Procedure

Run the installation or update as described in Running SAPinst [page 16].

More Information

See SAP Note 1272588 for known issues when installing the SAP Library with SAPinst.

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

3 Installation

3.3 Installation of Help Files Using SAPinst

16/36 PUBLIC 2011-11-08

Page 17: SAP Library Windows Netweaver 7.30

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>

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

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

Procedure

1. Log on as a user that is a member of the local administrators group.

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

4. In the Welcome screen, choose SAP Library Installation and Update Install / Update SAP Library .

5. Choose Next.

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

SAPinst restarts automatically.

7. Follow the instructions in the SAPinst screens and enter the required parameters.

3 Installation

3.3 Installation of Help Files Using SAPinst

2011-11-08 PUBLIC 17/36

Page 18: SAP Library Windows Netweaver 7.30

Only valid for: Java |

CAUTION

Adapter Engine (Java EE) only:

We recommend that you choose Use ABAP on the UME Configuration screen.

End of: Java |

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.

3 Installation

3.3 Installation of Help Files Using SAPinst

18/36 PUBLIC 2011-11-08

Page 19: SAP Library Windows Netweaver 7.30

4 Post-Installation

The following sections provide information about activities after the installation of the SAP Library has

finished successfully:

■ Using a Web Browser or Viewer [page 19]

■ Offline Access to Help Files – SAP Library Navigation [page 20]

■ Setting Variants for SAP Library [page 21]

■ Providing Reading Permissions for Installed Help Files [page 0 ]

4.1 Using a Web Browser or Viewer

The HTML-based documentation can be displayed in a Web browser on all front-end platforms

supported by SAP. However, you must observe certain requirements and restrictions depending on the

specific platform. The following table shows which browsers can be used with which front-end

platforms.

Web Browser for Help Documentation

HTML Help Viewer with Microsoft Internet Explorer 5.01 SP 2 (or higher)

Microsoft Internet Explorer 5.01 SP 2 (or higher)

Firefox Mozilla 2.xx

Netscape 4.06 (or higher)

Microsoft Windows platforms

X X X

Note the following points:

■ If you are using HTML Help Viewer in Microsoft Windows, a new instance of the viewer or browser

is opened each time you access help documentation.

■ If you choose help type HtmlHelpFile, you must use HTML Help Viewer, which is based on

Microsoft Internet Explorer and requires it. If you use help types PlainHtmlHttp and

PlainHtmlFile you can use either Microsoft Internet Explorer or Netscape. For the help structure

implemented with JavaScript and displayed as a compressed tree, JavaScript must be activated in

both browsers.

Installation of Microsoft HTML Help Viewer and Microsoft Internet Explorer

Microsoft HTML Help Viewer is installed automatically when you install SAP GUI 7.10 from the DVD

Presentation on your front-end PC (versions of file HH.exe older than 1.32 are overwritten).

4 Post-Installation

4.1 Using a Web Browser or Viewer

2011-11-08 PUBLIC 19/36

Page 20: SAP Library Windows Netweaver 7.30

Note that HH.exe (HTML Help Viewer) is also installed with Microsoft Internet Explorer, and therefore

any version already installed might be overwritten.

Microsoft Internet Explorer is installed with the operating system. You can download updates from

the Microsoft Web site. You can also download Microsoft Internet Explorer for Macintosh from the

Microsoft Web site.

NOTE

To use the HTML Help Viewer, you have to activate ActiveX in the Microsoft Internet Explorer.

In the Internet Explorer, choose security level Medium or Low under the Local intranet zone in the

menu path Tools Internet Options Security .

For more information, see SAP Note 594271 and SAP Note 857216.

To display documentation on how to use HTML Help Viewer, choose Help in the Viewer toolbar.

4.2 Offline Access to Help Files - SAP Library Navigation

To view the documentation offline – that is, without connecting to the SAP system – you need to:

■ Install a suitable browser or viewer on your computer as described in table Web Browser for Help

Documentation in Using a Web Browser or Viewer [page 19].

■ Have access to the help files. For the standard HTML help files, this requires you to unpack the

archive PLAINHTM.SAR from the DVD to your hard drive.

Procedure

HtmlHelpFile: Offline Access to Help Files

1. Navigate to the directory <InstallDir>\HTMLHELP\<language key> using the Microsoft Windows

Explorer.

This is the directory containing the help files.

2. Double-click on file 00000001.chm.

This opens SAP Library. From here you can navigate to all parts of the documentation.

3. Add the documentation homepage to your browser favorites or bookmarks.

PlainHtmlHttp and PlainHtmFile: Offline Access to the Help Files

1. Navigate to the directory <InstallDir>\HTMLHELP\<language key>.

This is the directory containing the help files.

2. Open file Home.htm.

This loads the documentation homepage in your Web browser. From here you can navigate to all

parts of the documentation.

3. Add the documentation homepage to your browser favorites or bookmarks.

4 Post-Installation

4.2 Offline Access to Help Files - SAP Library Navigation

20/36 PUBLIC 2011-11-08

Page 21: SAP Library Windows Netweaver 7.30

4.3 Setting Variants for SAP Library

In the IMG activity (transaction SR13), you specify which help variants you want to make available to

users of the SAP system. For more information about the definition of setting variants, see the SAP

NetWeaver Implementation Guide (IMG).

NOTE

On some front-end platforms, the URLs of the help files displayed in the browser must contain a

local drive identifier assigned to the file server instead of the name of the file server itself (for

example file:///K:/PLAINHTM/710/EN/e1/8e51341a06084de10000009b38f83b/

frameset.htm). In this case, the entry in the Path field must start with a drive letter and not with

the name of the file server. You must also make sure that this drive letter points to the file server

on the front end.

Procedure

Special Features of the Help Types

HtmlHelpFile

The path names specified in the setting variants must not contain special characters such as blanks or

ampersands. In addition, path names must not be longer than 64 characters.

PlainHtmlHttp

■ Enter the name of the Web server including the port.

■ Enter the path in the URL syntax. Path names must not contain special characters such as blanks

or ampersands. In addition, path names must not be longer than 64 characters.

PlainHtmlFile

Use the syntax of the front-end platform when specifying a path name. Path names must not contain

special characters such as blanks or ampersands. In addition, path names must not be longer than 64

characters.

Assignment of the Disk Drive Letter to the File Server

Front End Does the drive letter have to be assigned to the file server? Front End

Microsoft Windows Only if Netscape Navigator is used Microsoft Windows

Apple Macintosh Yes Apple Macintosh

EXAMPLE

Your front-end PC runs on Apple Macintosh and the help files reside in subdirectory PLAINHTM

\710\EN of the shared directory docu on server \\p99999. If the share name \\p99999\docu is

assigned to drive K: on the front ends, then the entry in the Path field must be K:\PLAINHTM

\710.

4 Post-Installation

4.3 Setting Variants for SAP Library

2011-11-08 PUBLIC 21/36

Page 22: SAP Library Windows Netweaver 7.30

ExampleExample for HtmlHelpFile: Setting Variant for the Help Documentation

Variant HTML Help 7.10 English

Platform WN32

Area IWBHELP

Path \\p12345\HTMLHELP710

Language EN

Default Yes

Example for PlainHtmlHttp: Setting Variant for the Help Documentation

Variant HTML (Web) 7.10 English

Platform WN32

Area IWBHELP

Server p12345:1080

Path PlainHttp710

Language EN

Example for PlainHtmlFile: Setting Variant for the Help Documentation

Variant HTML (File) 7.10 English

Platform WN32

Area IWBHELP

Path \\p12345\PlainFile710

Language EN

Default Yes

4 Post-Installation

4.3 Setting Variants for SAP Library

22/36 PUBLIC 2011-11-08

Page 23: SAP Library Windows Netweaver 7.30

5 Additional Information

■ About SAPinst [page 23]

■ Local Override of Help Settings on Front Ends [page 29]

5.1 About SAPinst

The following sections provide additional information about the installation tool SAPinst and about

activities related to the installation process:

■ Performing a Remote Installation with SAPinst [page 23]

■ Starting SAPinst GUI Separately [page 24].

■ Interrupted Installation with SAPinst [page 26]

■ Running SAPinst with Accessibility Mode [page 28]

■ Troubleshooting with SAPinst [page 29]

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

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

Prerequisites

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

5 Additional Information

5.1 About SAPinst

2011-11-08 PUBLIC 23/36

Page 24: SAP Library Windows Netweaver 7.30

■ 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 24].

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

■ 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 23].

Prerequisites

The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as

described in Installing and Updating SAP Library [page 15].

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.

2. Change to the directory of the sapinstgui executable:

<product>_IM_<your OS>_<your DB>

5 Additional Information

5.1 About SAPinst

24/36 PUBLIC 2011-11-08

Page 25: SAP Library Windows Netweaver 7.30

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>

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

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

5 Additional Information

5.1 About SAPinst

2011-11-08 PUBLIC 25/36

Page 26: SAP Library Windows Netweaver 7.30

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

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

5 Additional Information

5.1 About SAPinst

26/36 PUBLIC 2011-11-08

Page 27: SAP Library Windows Netweaver 7.30

Option DefinitionSAPinst 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.

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.

NOTE

All action taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

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.

5 Additional Information

5.1 About SAPinst

2011-11-08 PUBLIC 27/36

Page 28: SAP Library Windows Netweaver 7.30

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

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:

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 23]:

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 24]:

5 Additional Information

5.1 About SAPinst

28/36 PUBLIC 2011-11-08

Page 29: SAP Library Windows Netweaver 7.30

sapinstgui.exe -accessible –host <remote_host> -port

<port_number_gui_server_to_gui_client>

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

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

■ 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 24].

5. If you cannot resolve the problem, create a customer message using component BC-INS.

5.2 Local Override of Help Settings on Front Ends

You can override the help setting variants configured in the SAP system locally on Microsoft Windows

front ends. This facility enables you to use a different help type and/or call help from a location other

that than defined in the setting variants defined by the system administrator.

NOTE

You can only override the local front ends if you have defined entries for the setting variants in

transaction SR13. You must select a help type in transaction SR13.

5.2.1 File sapdoccd.ini

You enter override information in file sapdoccd.ini. You can store this file in the following locations:

5 Additional Information

5.2 Local Override of Help Settings on Front Ends

2011-11-08 PUBLIC 29/36

Page 30: SAP Library Windows Netweaver 7.30

■ In the Microsoft Windows directory of the front-end PC (c:\Windows or c:\WINNT)

■ In the SAP GUI directory (locally or on a server)

■ In the parent directory of the SAP GUI directory

Order of Evaluation

Each time the user accesses help in the SAP system ( Help Application Help) , the sapdoccd.ini file

is evaluated in the Microsoft Windows directory of the front-end PC. If the file is not there, it is first

searched for in the SAP GUI directory and then in the parent directory of the SAP GUI directory. If the

file cannot be found or if it does not contain any override information for HTML-based help, the help

processor copies the values of the setting variant of the SAP system currently in use. For more

information, see Setting Variants for SAP Library [page 21]. To override the SAP system setting variant, look

for a sapdoccd.ini file in the locations mentioned above and modify its content according to your

requirements. Otherwise, create a new file with any ASCII editor (for example, Editor). Make sure you

observe the order of evaluation if the file exists in more than one place.

Content and Format of sapdoccd.ini

The sapdoccd.ini file contains entries in Microsoft Windows INI format. The names of sections and

parameters are not case-sensitive, but parameter values are.

NOTE

Apart from the settings for HTML-based help in systems with Release 4.0A and later, the

sapdoccd.ini file can also contain control information for the WinHelp-based help in systems

with Releases 3.xx. These settings do not affect each other.

5.2.2 Parameters in File sapdoccd.ini

The following parameters and parameter values can be used:

HelpType PlainHtmlHttp, PlainHtmlFile, HtmlHelpFile, DynamicHelp, GetFromR3

<HelpType>Server Name of the Web server on which the files for <HelpType> reside

<HelpType>Path-<language> Path to the help files for logon language <language><language> is a two character language key.

<HelpType>Path Path to the help files you want to display if no parameter <HelpType>Path-<language> is specified for the current logon language

NOTE

The help type DynamicHelp can only be used if SAP Knowledge Warehouse is installed. The help

type GetFromR3 is not a proper help type. It is used to copy the values of the currently active

setting variant of the SAP system. If you specify GetFromR3 as the help type

(HelpType=GetFromR3), the settings from the SAP system are used. If you also specify the server

and/or path in sapdoccd.ini, these settings override the settings in the SAP system. The paths

used to override help settings locally must include the language key.

5 Additional Information

5.2 Local Override of Help Settings on Front Ends

30/36 PUBLIC 2011-11-08

Page 31: SAP Library Windows Netweaver 7.30

Validity Range of Parameters

You can specify the SAP systems to which the override applies by entering parameter values in the

relevant sections in sapdoccd.ini. Entries for overriding the HTML-based help can apply to:

■ All SAP systems

Entries in section [HTMLHELP] apply to all SAP systems.

■ SAP systems with a specific release

Entries in sections [HTMLHELP-<Release>] apply to all SAP systems with this release. They

override the entries in section [HTMLHELP].

■ Individual SAP systems

Entries in sections [SystemId-<SAP System>] apply to <SAP system> and override both the global

entries in section [HTMLHELP] and the release-specific entries in sections HTMLHELP-<Release>].

■ If an entry for a particular release (for example, Release 7.10) specifies a language-specific path

(<HelpType>Path<Language>), while an entry for a particular system with the same release

specifies a generic path (<HelpType>Path), the release-specific entry applies.

EXAMPLE

[HTMLHELP] HelpType=PlainHtmlHttp

PlainHtmlHttpServer=p99999.sap-ag.de:1080

PlainHtmlHttpPath-DE=saphelp/DE

PlainHtmlHttpPath=saphelp/EN

[HTMLHELP-710] HelpType=HtmlHelpFile

HtmlHelpFilePath-DE=\\DWDF042\docu\710\HTMLHELP\DE

HtmlHelpFilePath-EN=\\DWDF042\docu\710\HTMLHELP\EN

HtmlHelpFilePath=\\DWDF042\docu\710\HTMLHELP\EN

[SystemId-B20] HelpType=HtmlHelpFile

HtmlHelpFilePath-DE=\\p12345\HTMLHELP\DE

HtmlHelpFilePath=\\p12345\HTMLHELP\EN

[SystemId-B40] HelpType=PlainHtmlFile

PlainHtmlFilePath-DE=\\p44444\PLAINHTM\DE

PlainHtmlFilePath=\\p44444\PLAINHTM\EN

[SystemId-B60] HelpType=GetFromR3

HtmlHelpFilePath-DE=\\p99999\HTMLHELP\DE

HtmlHelpFilePath=\\p99999\HTMLHELP\EN

5.2.3 Logging of Help Calls

A log for each call is written to the file sapdoccd.log.

The log file contains the following information, separated by spaces:

5 Additional Information

5.2 Local Override of Help Settings on Front Ends

2011-11-08 PUBLIC 31/36

Page 32: SAP Library Windows Netweaver 7.30

■ Command line used to launch the start program for help (SHH.EXE) from the SAP system

■ Default parameters (transaction SR13) extracted from the command line

■ Parameters extracted from the file sapdoccd.ini

■ Start parameters resulting from the previous two points

■ Browser/viewer version (for help type HtmlHelpFile only)

The following is an example of a log produced when application help is launched from an SAP system

called B20:

EXAMPLE

Figure 2:

In the example, help type HtmlHelpFile is used and the help files are accessed from the directory

\HTMLHELP\EN on the file server \\p12345. If you launched the help documentation from the SAP

system B40, the help type PlainHtmlFile is used. In all other SAP systems, the default help type

PlainHtmlHttp (defined in transaction SR13) is used.

5 Additional Information

5.2 Local Override of Help Settings on Front Ends

32/36 PUBLIC 2011-11-08

Page 33: SAP Library Windows Netweaver 7.30

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

2011-11-08 PUBLIC 33/36

Page 34: SAP Library Windows Netweaver 7.30

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 and Java are registered trademarks of Oracle.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.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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. Business Objects is an SAP companySybase 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.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

34/36 PUBLIC 2011-11-08

Page 35: SAP Library Windows Netweaver 7.30
Page 36: SAP Library Windows Netweaver 7.30

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.