Installation of SAP Library for SAP ... - SAP Help Portal€¦ · Installation of SAP Library for...

Installation Guide PUBLIC

Software Provisioning Manager 1.0 SP23Document Version: 2.8 – 2018-05-07

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIX

Content

1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

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

2.1 PlainHtmlHttp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.2 PlainHtmlFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3 DynamicHelp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.4 Criteria for Selecting the Help Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

3.1 Installing PlainHtmlHttp and PlainHtmlFile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.2 Installation of Help Files Using Software Provisioning Manager 1.0. . . . . . . . . . . . . . . . . . . . . . . . . . 13

Preparations for the Installation with Software Provisioning Manager 1.0. . . . . . . . . . . . . . . . . . . 13

Installing and Updating SAP Library Using Software Provisioning Manager 1.0. . . . . . . . . . . . . . . 18

4 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

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

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

4.3 Setting Variants for SAP Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

4.4 Providing Reading Permissions for Installed Help Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5.1 About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Useful Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Performing a Remote Installation (Java SDT GUI only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Starting the Java SDT GUI Separately. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Running the Installer in Accessibility Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

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

File sapdoccd.ini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Parameters in File sapdoccd.ini. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Logging of Help Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2 P U B L I CInstallation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIX

Content

Document History

NoteBefore you start the implementation, make sure you have the latest version of this document, which is available at https://support.sap.com/sltoolset System Provisioning Installation Option of Software Provisioning Manager 1.0 .

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

Version Date Description

2.8 2018-05-07 Updated version for Software Provisioning Manager 1.0 SP23 (SL Toolset 1.0 SP23)










Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXDocument History P U B L I C 3

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

Version Date Description




1.51 2014-04-11 Updated version for Software Provisioning Manager 1.0 SP05 (SL Toolset 1.0 SP10 )

1.5 2014-03-17 Updated version for Software Provisioning Manager 1.0 SP05 (SL Toolset 1.0 SP10 )

1.4 2013-07-23 Updated Version

1.3 2013-07-15 Updated version



1.0 2012-08-06 Initial version


Document History

1 About this Document

This guide explains how to install or update SAP Library for SAP systems based on SAP NetWeaver using the installation tool software provisioning manager 1.0 SP23 (“installer” for short), which is part of SL Toolset 1.0 SP23.

The SAP NetWeaver-based system products and releases for which this documentation is valid are listed in SAP Note 1680045 .

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 PlainHtmlHttp and PlainHtmlFile [page 11]● Separately from the installation, you can also override the help settings on the front end:

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

Software Provisioning Manager 1.0

Software provisioning manager is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend that you always download the latest version of the software provisioning manager [page 14] which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045 .

As a result, SAPinst has been renamed to software provisioning manager (“installer” for short) in this documentation.

However, the term “SAPinst” is still used in:

● Texts and screen elements in the software provisioning manager GUI● Naming of executables, for example sapinst.● Naming of Command line parameters, for example SAPINST_USE_HOSTNAME● Operating system user groups, for example additional group sapinst

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.

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXAbout this Document P U B L I C 5

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1680045


Implementation Considerations

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.

SAP Notes for the Installation

You must read SAP Note 1261881 before 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 https://support.sap.com/notes .


About this Document


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

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

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

NoteCustomers using SAP Knowledge Warehouse can call both SAP documentation and their own custom-made documentation dynamically from SAP KW (help type DynamicHelp).

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXVariants of SAP Library P U B L I C 7

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

Related Information

PlainHtmlHttp [page 8]PlainHtmlFile [page 8]DynamicHelp [page 9]Criteria for Selecting the Help Type [page 9]

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

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


Variants of SAP Library

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

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

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

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXVariants of SAP Library P U B L I C 9


NoteIf 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 39] 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:


Variants of SAP Library

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 online documentation medium for your SAP product. We deliver the online help on this medium in the following 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 PlainHtmlHttp and PlainHtmlFile using software provisioning manager 1.0 as described in Installing PlainHtmlHttp and PlainHtmlFile [page 11].

NoteFor the sake of simplicity we refer to software provisioning manager 1.0 as “software provisioning manager” or – if suitable – simply as “installer” in the following.

2. You maintain setting variants for the online help in transaction SR13 as described in Setting Variants for SAP Library [page 25].

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 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 PLAINHTML.SAR on the DVD. They cannot be viewed directly from the DVD but must first be unpacked to the

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXInstallation P U B L I C 11

local hard drive or on a file server. To install the help files, you must use software provisioning manager as described in Installation of Help Files Using the Software Provisioning Manager [page 13].

CautionThe 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 up to 2 GB 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 24].

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

NoteIf 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 Netscape 4.06 (or later), choose Edit Preferences Advanced Enable JavaScript

Procedure

Install PlainHtmlHttp and PlainHtmlFile using software provisioning manager as described in Installation of Help Files Using Software Provisioning Manager [page 13].

Result

The archive PLAINHTML.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>


Installation

- PLAINHTML

+ EN (help files, English version)

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

3.2 Installation of Help Files Using Software Provisioning Manager 1.0

Related Information

Preparations for the Installation with Software Provisioning Manager 1.0 [page 13]Installing and Updating SAP Library Using Software Provisioning Manager 1.0 [page 18]

3.2.1 Preparations for the Installation with Software Provisioning Manager 1.0

You have to perform the following steps to prepare the installation or update of the SAP Library with software provisioning manager (“installer” for short).

Procedure

1. Check that your installation host meets the hardware and software requirements [page 14].2. Make sure that the required installation media [page 14] are available.


3.2.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 medium 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 https://support.sap.com/pam .

3.2.1.2 Preparing the Installation Media

This section describes how to prepare the installation media.

Installation media are available as follows:

● The Software Provisioning Manager 1.0 archive containing the installerYou always have to download the latest version of the Software Provisioning Manager 1.0 archive.For more information, see Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 15].

● The Documentation Installation Media<SAP_Product> Support Package Stack <Number> HTML-Help for <OS> Standard HTML (Plain HTML) Number <Material_Number>

ExampleSAP NetWeaver 7.5 Support Package Stack 04 HTML-Help for Windows Standard HTML (Plain HTML) Number 50108701

You can provide it in one of the following ways:○ Use the physical Documentation medium as part of the installation package of your SAP system.○ Download the Documentation medium from the SAP Software Center.

For more information, see Downloading Installation Media [page 16].

Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 15]Downloading Installation Media [page 16]


Installation

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

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

3.2.1.2.1 Downloading and Extracting the Software Provisioning Manager 1.0 Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software Download Center because you must use the latest version.

Procedure

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

○ Valid for SAP systems based on SAP NetWeaver 7.0 and SAP NetWeaver 7.0 including enhancement package <Number>:Download the 70SWPM10SP<Support_Package_Number>_<Version_Number>.SAR

○ Valid for SAP systems based on SAP NetWeaver 7.1 and higher:Download the SWPM10SP<Support_Package_Number>_<Version_Number>.SAR

https://support.sap.com/sltoolset System Provisioning Download Software Provisioning Manager

2. Make sure that you use the latest version of the SAPCAR tool when manually extracting the Software Provisioning Manager archive.

NoteAn older SAPCAR version might extract archive files in a wrong way and this could prevent the installer from working consistently.

Proceed as follows to get the latest version of SAPCAR:

a. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcar”.

b. Select the archive file for your operating system and download it to an empty directory.c. Rename the executable to sapcar.exe.

For more information about SAPCAR, see SAP Note 212876 .

3. Using the latest version of SAPCAR, you can verify the signature of the downloaded [70]SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive as follows:

a. Get the latest version of the SAPCRYPTOLIB archive to your installation host as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter SUPPORT PACKAGES & PATCHES and search for “sapcryptolib”.

2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable.

3. Use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable:sapcar –xvf sapcryptolibp_84…sar –R <target directory>



http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fsoftwarecenter



4. Download the Certificate Revocation List from https://tcs.mysap.com/crl/crlbag.p7s and move it to the same directory.

b. Verify the signature of the downloaded [70]SWPM10SP<Support_Package_Number>_<Version_Number>.SAR archive by executing the following command:

NoteCheck SAP Notes 2178665 and 1680045 whether additional information is available.

/<Path to SAPCAR>/sapcar -tvVf <Path to Download Directory>/[70]SWPM10SP<Support_Package_Number>_<Version_Number>.SAR -crl<file name of revocation list>

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

/<Path to SAPCAR>/sapcar -xvf <Path to Download Directory>/[70]SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack Directory>

NoteMake sure that all users have read permissions for the directory where you want to unpack the installer.

CautionMake sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.

3.2.1.2.2 Downloading Installation Media

This section describes how you can download media from the SAP Software Download Center.

Procedure

1. Download and unpack the latest version of Software Provisioning Manager as described in Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 15].

2. You identify the required media als listed in Preparing the Installation Media [page 14] .3. Identify all download objects that belong to one medium according to one of the following:

NoteInstallation media might be split into several files. In this case, you have to reassemble the required files after the download.


Installation

http://help.sap.com/disclaimer?site=https%3A%2F%2Ftcs.mysap.com%2Fcrl%2Fcrlbag.p7s



○ Download path or location:

○ To download the complete kernel media, go to https://support.sap.com/sltoolset System Provisioning Software Provisioning Manager 1.0 SP<Current Version> Download Kernel releases delivered for SL Toolset SL TOOLSET 1.0 (INSTALLATIONS AND UPGRADES) KERNEL FOR INSTALLATION/SWPM .

○ To download all media required for your SAP product, you can use one of the following navigation paths:

○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADESBy Category SAP NETWEAVER AND COMPLEMENTARY PRODUCTS <Product><Product Release>

○ https://launchpad.support.sap.com/#/softwarecenter INSTALLATIONS & UPGRADESBy Alphabetical Index (A-Z) <First Letter of Product> <Product> <Product Release>

○ Material numberAll download objects that are part of an installation medium have the same material number and an individual sequence number:<Material_Number>_<Sequence_Number>

Example51031387_1

51031387_2

...

○ TitleAll 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.

4. Download the objects to the download directory.5. To correctly re-combine the media that are split into small parts, 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 .

CautionMake sure that you unpack each installation media to a separate folder. Do not unpack installation media to the same folder where you unpack the Software Provisioning Manager archive.

Do not unpack installation media to the same folder where you unpack the SAP kernel archives for archive-based installation.






3.2.2 Installing and Updating SAP Library Using Software Provisioning Manager 1.0

This procedure tells you how to install and update SAP Library with software provisioning manager (“installer” for short).

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 media are available on the installation host as described in Preparing the Installation Media [page 14].

Context

● Install means that you install SAP Library from scratch.● Update means that you update an existing version of SAP Library.

Procedure

1. Make sure that the installation host meets the prerequisites for running the installer.

Fore more information, see Prerequisites for Running the Installer [page 18].2. Run the installation or update.

Fore more information, see Running the Installer (Software Provisioning Manager) [page 21]

3.2.2.1 Prerequisites for Running the Installer

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

● For the SL Common GUI, make sure that the following web browser requirements are met:○ You have one of the following supported browsers on the device where you want to run the SL

Common GUI:○ Google Chrome (recommended)○ Mozilla Firefox○ Microsoft Edge○ Microsoft Internet Explorer 11 or higher.

Always use the latest version of these web browsers.


Installation

○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

For more information about the SL Common GUI, see Useful Information About the Installer [page 28].

● If you want to enable Internet Protocol Version 6 (IPv6), make sure that you set SAP_IPv6_ACTIVE=1 in the environment of the user with root authorization which you use to start the installer. While running the installer, this setting is then also added to the environment of the <sapsid>adm user.

NoteBy applying this setting the SAP system administrator is responsible for configuring the IP version on each host of the system landscape, before installing any additional instance to it.

● We recommend that you use the csh shell for the installation. If you want to use another shell, make sure that you have read SAP Note 202227 .

● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.Make sure that the temporary directory has the permissions 777.

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables.You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 28].

● Make sure that umask is set to 022 for the user with root permissions that you want to use for running the installer.As the user with root permissions that you want to use for running the installer, enter the following command: umask 022

● Only valid for 'Platform': AIXAIX: Make sure that you have set the limits for operating system users as described in SAP Note 323816

.End of 'Platform': AIX

● Only valid for 'Platform': Linux, HP-UX, Oracle SolarisHP-UX, Linux, Oracle-Solaris: Make sure that you have set the limits for operating system users root, <sapsid>adm, and your database-specific operating system users (see also section "Creating Operating System Users and Groups" and "Running the Installer" in the installation guide).

CautionCaution: the limit mechanism supports hard- and soft-limits. The soft-limit cannot be bigger than the hard-limit. The hard-limit can be set/increased by the root user like: limit -h <limit> <new_value>, for example limit -h datasize unlimited .





○ Using csh shell, the output of command limit needs to be at least as follows:

ExampleThe following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Output Properties

cputime unlimited

filesize unlimited

datasize unlimited

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memoryuse unlimited

○ Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

ExampleThe following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Output sh Output ksh Properties

cpu time (seconds) cpu time (seconds) unlimited

file size (blocks) file size (blocks) unlimited

data seg size (kbytes) data size (Kibytes) unlimited

stack size (kbytes) stack size (Kibytes) 8192 KB

core file size (blocks) core file size (blocks) unlimited

open files nofile 8192

max memory size (kbytes) max memory size (Kibytes) unlimited

End of 'Platform': Linux, HP-UX, Oracle Solaris

● Make sure that the following ports are not used by other processes:○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL

Common GUI.


Installation

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:SAPINST_HTTPS_PORT=<Free Port Number>

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.The filled-out evaluation form is then sent to SAP using HTTPS.If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:SAPINST_HTTP_PORT=<Free Port Number>

3.2.2.2 Running the Installer

This section describes how to run the installer.

Prerequisites

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

Context

The installer has a web browser-based GUI named “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.

This procedure describes an installation where you run the installer and use the SL Common GUI, that is you can control the processing of the installer from a browser running on any device.

For more information about the SL Common GUI, see Useful Information About the Installer [page 28].

Procedure

1. Log on to the installation host as a user with root permissions.

CautionMake sure that the user with root permissions that you want to use for running the installer has not set any environment variables for a different SAP system or database.

If your security policy requires that the person running the installer is not allowed to know the credentials of a user with root permissions on the installation host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting


the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

2. Start the installer from the directory to which you unpacked the Software Provisioning Manager archive by entering the following commands:

<Path_To_Unpack_Directory>/sapinst

3. The installer is starting up.

The installer now starts and waits for the connection with the SL Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

...************************************************************************Open your browser and paste the following URL address to access the GUI https://[<hostname>]:4237/sapinst/docs/index.html Logon users: [<users>] ************************************************************************...

If you have a supported web browser (see Prerequisites for Running the Installer [page 18]) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the Welcome screen.

NoteBefore you reach the Welcome screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

4. On the Welcome screen, choose the required option:○ If you are using the 70SWPM*.SAR:

Choose your product, then go to Software Life-Cycle Options SAP Library Installation and Update and choose: Install/Update SAP Library

○ If you are using the SWPM*.SAR:Go to Generic Options <Database> SAP Library Installation and Update and choose: Install/Update SAP Library

5. Choose Next.

NoteIf there are errors during the self-extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.

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


Installation


NoteTo find more information on each parameter during the Define Parameters phase, position the cursor on the required parameter input field , and choose either F1 or the HELP tab. Then the available help text is displayed in the HELP tab.

CautionThe signature of media and installation archives is checked automatically during the Define Parameters phase while processing the Media Browser and - if you perform an archive-based installation - the Software Package Browser screens.

Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts such as SAR archives or files on the media after the initial check has been done. This means that - if you modify artefacts later on either during the remaining Define Parameters phase or later on during the Execute Service phase - the signature is not checked again.

See also the description of this new security feature in SAP Note 2393060 .

After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation.

7. To start the installation, choose Next.

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

8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished. Sometimes these directories remain in the temporary directory.

9. For security reasons, we recommend that you delete the .sapinst directory within the home directory of the user with which you ran the installer:

<User_Home>/.sapinst/10. If you copied the installer software to your hard disk, you can delete these files when the installation has

successfully completed.11. For security reasons, we recommend that you remove the operating system users from the group sapinst

after you have completed the installation.

NoteThis step is only required, if you did not specify during the Define Parameters phase that the operating system users are to be removed from the group sapinst after the execution of the installer has completed.



4 Post-Installation

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

Related Information

Using a Web Browser or Viewer [page 24]Offline Access to Help Files - SAP Library Navigation [page 25]Setting Variants for SAP Library [page 25]Providing Reading Permissions for Installed Help Files [page 27]

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)

Apple Macintosh X (3.01) X

UNIX X X X

Note the following points:

● If you are using Netscape on UNIX, a new instance of the viewer or browser is opened each time you access help documentation.

● On UNIX, the help processor of the SAP system with the logical file name NETSCAPE calls the Web browser. To adapt this call to your file system, you must define the logical file name and the corresponding logical path NETSCAPE_PATH in transaction FILE. Note that the logical file name NETSCAPE does not determine which Web browser you launch with this name. The name was chosen when the Netscape Navigator 3.0 was the only browser available for UNIX front ends.

● Under UNIX front ends, the symbol used in the SAP Library for describing menu paths () cannot be displayed in the Web browser. A different symbol is displayed instead.

● On UNIX/Linux front ends, you cannot choose < (Previous Topic) button and > (Next Topic) button in the Firefox Web browser for help type Plain HTML.


Post-Installation

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

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

● Have access to the help files. For the standard HTML help files, this requires you to unpack the archive PLAINHTML.SAR from the DVD to your hard drive.

Procedure

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 index.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.3 Setting Variants for SAP Library

Use

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

For more information about the HTTP protocol configuration, see SAP Note 1842462 .

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

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXPost-Installation P U B L I C 25


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

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

Example

Example 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


Post-Installation

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.4 Providing Reading Permissions for Installed Help Files

Use

After the installation has finished, help files are only readable for user root and users belonging to the sapinst authorization group.

You have to change the permissions assigned to these files in order to make them readable for all users.

Procedure

1. Open a command prompt on the machine where you installed SAP Library.2. Change to the directory where you installed the SAP Library files.3. Execute the following command: chmod -R a+r *

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXPost-Installation P U B L I C 27

5 Additional Information

● About the Installer (Software Provisioning Manager) [page 28]● Local Override of Help Settings on Front Ends [page 39]

5.1 About the Installer

5.1.1 Useful Information About the Installer

This section contains some useful technical background information about the installer and the installer GUI.

● Software Provisioning Manager (the “installer” for short) has the web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common GUI” for short.The SL Common GUI uses the SAP UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are:○ Zero foot print, since only a web browser is required on the client○ New controls and functionality, for example, view logs in web browser.

The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there.For more information about supported web browsers see Prerequisites for Running the Installer [page 18].If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of your web browser.

● As soon as you have started the sapinst executable, the installer creates a .sapinst directory underneath the /home/<User> directory where it keeps its log files. <User> is the user with which you have started the installer.After you have reached the Welcome screen and selected the relevant installer option for the SAP system or instance to be installed , the installer creates a directory sapinst_instdir where it keeps its log files, and which is located directly below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp by default.All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir directory as soon as the latter has been created.If you want the sapinst_instdir directory to be created in another directory than /tmp, set the environment variable TEMP, TMP, or TMPDIR to this directory before you start the installer.


Additional Information

Shell Used Command

Bourne shell (sh) TEMP=<Directory>

export TEMP

C shell (csh) setenv TEMP <Directory>

Korn shell (ksh) export TEMP=<Directory>

CautionMake sure that the installation directory is not mounted with NFS, or there might be problems when the Java Virtual Machine is started.

RecommendationWe recommend that you keep all installation directories until the system is completely and correctly installed.

● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory after the installer has finished. You can safely delete them.The temporary directory also contains the log file dev_selfex.out from the self-extraction process of the installer, which might be useful if an error occurs.

CautionIf the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.

● To see a list of all available installer properties, start the installer as described above with the option -p:./sapinst -p

● If required, stop the installer by choosing the Cancel button.

NoteIf you need to terminate the installer, press Ctrl + C .

5.1.2 Performing a Remote Installation (Java SDT GUI only)

Here you find information about how to install your SAP system on a remote host.

NoteThis section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option SAPINST_SLP_MODE=false.

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXAdditional Information P U B L I C 29

Prerequisites

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

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

Context

You use this procedure to install your SAP system on a remote host. In this case, the installer runs on the remote host, and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know the credentials of a user with root permissions 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 the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Procedure

1. Log on to the remote host as a user with root permissions.

CautionMake sure that this user has not set any environment variables for a different SAP system or database.

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

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

RecommendationMake the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.





Only valid for 'Platform': Oracle Solaris

NoteOracle Solaris: If you mount installation media, make sure that you do this with option nomaplcase.

End of 'Platform': Oracle Solaris

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

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

<Path_To_Unpack_Directory>/sapinst -sfxver

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 31]).

5. Start the installer by entering the following command:

<Path_To_Unpack_Directory>/sapinst

The installer now starts and waits for the connection to the installer 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

6. Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page 31].

5.1.3 Starting the Java SDT GUI Separately

Here you find information about how to start the Java SDT GUI separately.

NoteThis section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option SAPINST_SLP_MODE=false.

Prerequisites

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

NoteIf you want to run the installer on a Windows host, make sure that you meet the prerequisites for the installer listed in the relevant Windows guide.


Context

You might need to start the installer GUI separately in the following cases:

● You closed the installer GUI using File Close GUI only from the installer menu while the installer is still running.

● You want to perform a remote installation, where the installer GUI runs on a different host from the installer. For more information, see Performing a Remote Installation (Java SDT GUI only) [page 29].

● You want to run the installer in accessibility mode. In this case, you have to start the installer GUI separately on a Windows host as described below with the command line parameter -accessible.For more information, see Running the Installer in Accessibility Mode [page 36].

In the this procedure, the following variables are used: <Remote_Host> is the name of the remote host, and <Port_Number_Gui_Server_To_Gui_Client> is the port the GUI server uses to communicate with the GUI client (21212 by default).

Procedure

● Starting the Installer GUI on Windowsa. Make the installer software available on the host on which you want to start the installer GUI.b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line

parameters:○ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:<Path_To_Unpack_Directory>\sapinstgui.exe -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 29]).

2. Start the installer GUI by entering the following command:<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using File Close GUI only and want to reconnect to the installer, proceed as follows:1. If you are performing a local installation with the installer and the installer GUI running on the

same host, execute the following command:<Path_To_Unpack_Directory>\sapinstgui.exe -port <Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:<Path_To_Unpack_Directory>\sapinstgui.exe -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

c. The installer GUI starts and connects to the installer.● Starting the Installer GUI on UNIX

a. Make the installer software available on the host on which you want to start the installer GUI.b. Start the installer GUI by executing the sapinstgui executable with the appropriate command line

parameters:



○ If you want to perform a remote installation, proceed as follows:1. Check the version of the sapinstgui executable by entering the following command:

<Path_To_Unpack_Directory>/sapinstgui -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 29]).

2. Start the installer GUI by entering the following command:<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

○ If you closed the installer GUI using File Close GUI only and want to reconnect to the installer, proceed as follows:1. If you are performing a local installation with the installer and the installer GUI running on the

same host, execute the following command:<Path_To_Unpack_Directory>/sapinstgui -port <Port_Number_Gui_Server_To_Gui_Client>

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:<Path_To_Unpack_Directory>/sapinstgui -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>

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

5.1.4 Interrupted Processing of the Installer

Here you find information about how to restart the installer if its processing has been interrupted.

Context

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

● An error occurred during the Define Parameters or Execute phase:The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

● You interrupted the processing of the installer by choosing Cancel in the SL Common GUI.

CautionIf you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.


The following table describes the options in the dialog box:

Option Definition

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

This is possible because the installer records the installation progress in the keydb.xml file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.

If the same or a different error occurs, the installer displays the same dialog box again.

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.

The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue The installer continues the installation from the current point.

View Log Access installation log files.

NoteYou can also terminate the installer by choosing Ctrl + C but we do not recommend this because it kills the process immediately.

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

Procedure

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

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

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

RecommendationMake the installation media available locally. For example, if you use remote file shares on other Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.






3. Make sure that the installation media are still available.

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

RecommendationMake the installation media available locally. For example, if you use remote file shares on other Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.




4. Restart the installer from the directory to which you unpacked the Software Provisioning Manager archive by executing the following command:<Path_To_Unpack_Directory>/sapinst

5. The installer is restarting.

The installer now starts and waits for the connection with the SL Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

...************************************************************************Open your browser and paste the following URL address to access the GUI https://[<hostname>]:4237/sapinst/docs/index.html Logon users: [<users>] ************************************************************************...

If you have a supported web browser (see Prerequisites for Running the Installer [page 18]) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the Welcome screen.

NoteBefore you reach the Welcome screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

6. From the tree structure on the Welcome screen, select the installation option that you want to continue and choose Next.


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

Alternative Behavior

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

The following naming convention is used for the backup directory:

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

Examplelog_01_Oct_2016_13_47_56

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

CautionThe installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the existing one The installer continues the interrupted installation from the point of failure.

5.1.5 Running the Installer in Accessibility Mode

You can also run the installer in accessibility mode.

NoteThe information contained in this section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option SAPINST_SLP_MODE=false.

If you use the SL Common GUI, apply the standard accessibility functions of your web browser.



Context

The following features are available:

● Keyboard access:This feature is generally available for all operating systems.

● High-contrast color:This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

● Custom font setting:This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

Procedure

● Activating and Adjusting Accessibility Settings on Windows

You first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.

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

a. Right click on your Windows desktop and choose Personalize.b. Select Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.c. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme drop-down box.

To define your own color schemes, choose Advanced.● Running the Installer in Accessibility Mode

You perform a remote installation as follows:

a. Start the installer on the remote host by executing the following command from the command line as described in Performing a Remote Installation (Java SDT GUI only) [page 29]:<Path_To_Unpack_Directory>/sapinst

b. Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Java SDT GUI Separately [page 31]:<Path_To_Unpack_Directory>\sapinstgui.exe -accessible -host <Remote_Host> -port <Port_Number_Gui_Server_To_Gui_Client>


5.1.6 Troubleshooting with the Installer

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

Context

If an error occurs, the installer:

● Stops processing● Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known installer issues.2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:

○ Try to solve the problem:○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose the LOG

FILES tab.

NoteThe LOG FILES tab is only available if you have selected on the Welcome screen the relevant installer option for the SAP product to be installed .

If you need to access the log files before you have done this selection, you can find them in the .sapinst directory underneath the /home/<User> directory, where <User> is the user which you used to start the installer.

Fore more information, see Useful Information About the Installer [page 28].

○ To check the log and trace files of the installer GUI for errors, go to the directory <User_Home>/.sapinst/

○ Then continue by choosing Retry.○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more

information, see Interrupted Processing of the Installer [page 33].3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.

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





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.

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

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

NoteApart 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

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

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 systemsEntries in section [HTMLHELP] apply to all SAP systems.

● SAP systems with a specific releaseEntries in sections [HTMLHELP-<Release>] apply to all SAP systems with this release. They override the entries in section [HTMLHELP].

● Individual SAP systemsEntries 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:

● 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

Log Example

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.



Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Installation of SAP Library for SAP systems based on SAP NetWeaver 7.0 to 7.52 on UNIXImportant Disclaimers and Legal Information P U B L I C 43

go.sap.com/registration/contact.html

© 2018 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/about/legal/trademark.html

Installation of SAP Library for SAP ... - SAP Help Portal€¦ · Installation of SAP Library for...

Documents

Transcript of Installation of SAP Library for SAP ... - SAP Help Portal€¦ · Installation of SAP Library for...