installation of sap content server on unix - help.sap.com · pdf file1.3 constraints this...

Installation Guide PUBLIC

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

Installation of SAP Content Server on UNIX

Content

1 General Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51.3 Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Description of SAP Content Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 SAP Content Server General Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72.2 Description of SAP Content Server for UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Planning and Sizing of the Database Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 What should you think about before going live?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113.2 What types of objects will be involved?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113.3 By how much is the volume of objects per location likely to increase?. . . . . . . . . . . . . . . . . . . . . . . . 123.4 On average, how many users are likely to access the content server at any one time?. . . . . . . . . . . . .123.5 Further Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.1 Hardware and Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.2 SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.3 Create Users and Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

File system storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16SAP DB storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4 Set Up the Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.5 Install the SAP MaxDB and/or the File System Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Installing the SAP MAX DB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Set Up the File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.6 Basic Installation Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224.7 Preparing the Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Downloading and Extracting the Software Provisioning Manager 1.0 Archive. . . . . . . . . . . . . . . . 24Downloading Installation Media. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

5 Installation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.1 Prerequisites for Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.2 Running the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.3 Additional Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Useful Information About the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Interrupted Processing of the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2 P U B L I CInstallation of SAP Content Server on UNIX

Content

Troubleshooting with the Installer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Using the Step State Editor (SAP Support Experts Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6 Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

7 Installation Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

8 Additional Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448.1 SAP Notes Relevant for SAP Content Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448.2 Appendix: Modifications to httpd.conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Port Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Module Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Module Registration (Only for apache 1.3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Module Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installation of SAP Content Server on UNIXContent P U B L I C 3

Document History

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

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 .

Version Date Description

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

1.1 2018-01-15 Updated version for Software Provisioning Manager 1.0 SP22 (SL Toolset 1.0 SP22)

1.0 2017-09-11 Initial version

Updated version for Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21)


Document History

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

1 General Information

About this Document [page 5]This section describes what this guide is about.

Purpose [page 5]This section describes the purpose of SAP Content Server.

Constraints [page 6]This section lists the constraints valid for SAP Content Server.

Prerequisites [page 6]This section describes the prerequisites required for using this guide.

1.1 About this Document

This section describes what this guide is about.

This installation guide describes how to install an SAP Content Server using the installation tool Software Provisioning Manager 1.0 SP23 (“installer” for short), which is part of SL Toolset 1.0 SP23.

1.2 Purpose

This section describes the purpose of SAP Content Server.

SAP Content Server for UNIX allows users to run SAP’s proven content server technology with the added advantages inherent in UNIX systems: enhanced flexibility, improved resource utilization, platform-independence, and high stability.

The SAP Content Server for UNIX has the following sub-components:

● The SAP Content Server and SAP Cache Server core libraries:mod_sapcs.so, mod_sapcsc.so, libsapsecu.so, mod_sapcs2.so, mod_sapcsc2.so, mod_sapcs22.so, mod_sapcsc22.so

NoteThe file suffixes might vary from platform to platform

● The SAP database (SAP MAX DB)

Installation of SAP Content Server on UNIXGeneral Information P U B L I C 5

1.3 Constraints

This section lists the constraints valid for SAP Content Server.

SAP Content Server is not an alternative to optical storage systems and other storage media for long-term document archiving.

1.4 Prerequisites

This section describes the prerequisites required for using this guide.

This installation guide assumes that you have a thorough knowledge of the following:

● UNIX administration commands● Backup tools and procedures o IP network security● The HTTP protocol● The general principles of client/server communication

SAP MaxDB https://help.sap.com/viewer/p/SAP_MAXDB

Apache Web Server https://httpd.apache.org/

SAP Content Server ● SAP Content Server documentation on the SAP Help

Portal at https://help.sap.com/nw <Choose the SAP NetWeaver Release your SAP product is

based on> SAP NetWeaver Library: Function-

Oriented View Application Server Application

Server ABAP Other Services Services for Business

Users Knowledge Provider (BC-SRV-KPR) Content

Management Service (BC-SRV-KPR) SAP Content

Server SAP Content Server HTTP 4.5 Interface● For a list of SAP Notes that deal with various aspects of

the SAP Content Server, see SAP Notes Relevant for SAP Content Server [page 44].


General Information

https://help.sap.com/viewer/p/SAP_MAXDB

http://help.sap.com/disclaimer?site=https%3A%2F%2Fhttpd.apache.org%2F

https://help.sap.com/nw

2 Description of SAP Content Server

This section contains sub-sections giving a general description of the SAP Content Server, and a specific description of SAP Content Server for UNIX.

SAP Content Server General Description [page 7]

Description of SAP Content Server for UNIX [page 8]

2.1 SAP Content Server General Description

SAP Content Server

The SAP Content Server is the server at the core of SAP’s document storage and management concept. It provides the technical infrastructure for all document-centric applications and business scenarios that do not require a long-term document archiving solution. Because the SAP Content Server is included in every SAP solution, a self-contained content server is always available to SAP customers.

Cache Server

The content server infrastructure also includes the cache server. Like the content server, the cache server stores documents and allows them to be accessed via HTTP. The difference is that the cache server is an interim storage facility located close to the client whose main task is to make access to document content quicker and more efficient. It does this by temporarily storing (‘caching’) requested document content, so that the next time that content is requested by a nearby client; the content can be retrieved from the nearest cache server rather than the content server.

This is most advantageous on very large, dispersed networks, where the client and the content server may be located on different continents. It is also particularly useful if the content is required for fast display, such as in a Web browser. Cache servers also reduce the network load and thus enhance network performance.

Client Applications

SAP applications that use the technical infrastructure of the SAP Content Server include the SAP Business Workplace, ArchiveLink, the Document Management System (DMS), and the SAP Knowledge Warehouse.

Installation of SAP Content Server on UNIXDescription of SAP Content Server P U B L I C 7

More Information

For further information on Knowledge Provider, the SAP Content Server, and the cache server, see the SAP Library at https://help.sap.com/nw <Choose the SAP NetWeaver Release your SAP product is based on> SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP

Other Services Services for Business Users Knowledge Provider (BC-SRV-KPR)

2.2 Description of SAP Content Server for UNIX

Architecture

The graphic below shows the architecture of SAP Content Server for UNIX:

Architecture of the SAP Content Server for UNIX

The basis of the SAP Content Server is the content server engine. The engine is implemented as an Apache module called mod_sapcs.so (for 1.3.xx) / mod_sapcs2.so (for 2.0.xx) /mod_sapcs22.so(for 2.2.xx) and is loaded into the Apache Web server’s process space.

The engine receives all URLs, checks their validity, and triggers the processing of requests.


Description of SAP Content Server


The SAP Content Server saves data to the SAP database (SAP DB) or to the file system. However, the Content Server engine does not communicate directly with the storage medium. Instead, it uses an adapter known as the content storage layer, which is implemented either as the SAP DB storage layer or the file system storage layer, depending on the storage medium. The storage layer “hides” the specific access mechanisms of the storage medium behind a consistent, byte stream-oriented interface. This means that one server engine can support several storage media.

Advantages

The new Content Server for UNIX has a number of advantages. The most important of these are:

● Greatly improved resource utilization (RAM, CPU)Optimized stream-based design allows the minimum memory footprint.

● Platform-independence● Highly stable software, virtually maintenance-free – “set up once, run forever”

The only significant maintenance task is making regular backups.● Fully compatible with the Windows versions of the content server and cache server● High flexibility:

○ Documents can be stored either compressed or uncompressed.○ Both the SAP DB and file system storage are supported.

Constraints

SAP ships only the SAP Content Server module, not the Apache Web server. You can obtain Apache versions from SAP platform partners, or from third-party software vendors, or from the open source. SAP does not provide any Apache support.

A precompiled version of Apache is not supported with Sap Content Server.

The SAP Content Server (both platform versions) is not intended to replace optical storage systems and other storage media for long-term document archiving.

Storage Layer

With the new UNIX version, the SAP Content Server can use either the SAP MaxDB or a file system for document storage. Since the SAP Content Server is integrated via the SAP HTTP Content Server interface, the actual storage medium used remains completely transparent to SAP applications.

SAP MaxDB

The SAP MaxDB storage layer uses the SAP MaxDB client driver to access the database server. The SAP MaxDB administrates the individual repository tables in which the documents are stored.

Installation of SAP Content Server on UNIXDescription of SAP Content Server P U B L I C 9

The main advantages of SAP MaxDB storage are as follows:

● Full SAP support for data recovery.● Full range of SAP MaxDB administrative tools available.● SAP MaxDB most likely outperforms file system storage on high-load servers.● Unlike file system storage, the SAP MaxDB guarantees transactional security (in other words, no junk data

fragments remain on the disk after a transaction has been interrupted).● Consistency of document content is guaranteed if documents are modified exclusively within the SAP

application domain.

File System

The file system storage layer uses the POSIX (portable operating system interface on UNIX) file system API of the underlying UNIX operating system. The file system repositories take the form of a directory hierarchy in which the documents are stored. The system is designed in such a way that the number of documents in the file system is limited only by the number of available inodes (note that some inodes are needed for the directory structure).

Non-standard file systems (that is, file systems other than the UNIX file system (UFS)), such as SAMBA or a virtual FS, can be used, but they must support the UNIX access rights and be accessible via a valid access path beginning with the root file system. You should also expect substantial performance losses if you use a non-standard file system.

The directory structure of the file system repositories has been designed in such a way as to make efficient, fast, and flexible use of your disks. The main features of file system storage are as follows:

● Flat hierarchyThe aim of a flat hierarchy is to keep the number of disk accesses required during document retrieval low and consistent (the flatter the hierarchy, the fewer accesses required). A flat hierarchy also increases the potential number of documents that can be stored.

● Efficient usage ratio of the inodes used for structural objects and content objectsThe ratio between inodes used for structural objects and content object does not substantially limit the overall capacity of the repository.

● Portable layoutFile system repositories are accessible from different server hosts and can be transported as backed-up archives. No file system-specific features are utilized, in order to keep the repositories platform-independent. Therefore, repositories can be mounted onto different computers, and even different operating systems. Also see the next point.

● Self-contained data organizationNo management tables or metadata are required for the following purposes:○ To ensure that the same repositories are accessible from different storage locations (even

concurrently, provided that the NFS locking mechanism works correctly)○ To ensure that the repositories are robust; that is, that they are not prone to crashing


Description of SAP Content Server

3 Planning and Sizing of the Database Instance

What should you think about before going live? [page 11]

What types of objects will be involved? [page 11]

By how much is the volume of objects per location likely to increase? [page 12]

On average, how many users are likely to access the content server at any one time? [page 12]

Further Information [page 13]

3.1 What should you think about before going live?

To dimension your Content Server Database instance as accurately as possible, you should estimate your data volume and log volume requirements. Answer the following questions:

● What types of objects will be involved?(Estimate the existing data volume and compression level.)

● By how much is the volume of objects per location likely to increase?(Estimate the increase in data volume over a specific period of time.)The answers to these first two questions indicate the data volume requirement.

● On average, how many users are likely to access the content server at any one time?The answer to this question indicates the size of main memory, and the CPU and log volume requirements.The following sub-sections go into each of these questions in greater depth.

3.2 What types of objects will be involved?

When stored on the content server, every file is compressed according to its file type, and occupies a specific amount of storage space (data volume). Therefore, it is important to establish what file types are contained in your legacy data volume. You can use the compression percentages in the table below to determine your legacy data volume.

NoteThese percentages are approximate values only and may need to be adjusted according to individual circumstances.

Installation of SAP Content Server on UNIXPlanning and Sizing of the Database Instance P U B L I C 11

MIME Type DOC XLS PPT TIFF GIF JPG CAD ...

Compr. approx.

50 % 50 % 30 % 5 % 5 % 5 % ? ?

File size * percentage = compression File size - compression = amount of data volume occupied

3.3 By how much is the volume of objects per location likely to increase?

The increase in data volume, taking into account the compression levels, has to be estimated for a specific time period. (Make sure that the hard disk capacity is sufficient for the data volume expected during this period.) Once you have calculated the expected increase in data volume, add this to the legacy data volume.

The result can be termed the ‘net‘ data volume required for the time period in question. Then add 20% to 25% more memory space to allow for internal database administration data (‘headroom’). The result is the ‘gross’ data volume requirement.

3.4 On average, how many users are likely to access the content server at any one time?

The goal here is to ensure that the transaction buffer is sufficiently large to allow a number of users to access the content server simultaneously. To this end, the log volume should be approximately 10% of the calculated data volume. In all cases, it should be at least twice the size of the largest expected document. This is so that the content server can handle at least two simultaneous accesses.

Legacy data volume:

File Size File size * percentage = compression

File1.doc

File2.doc

...

File10.doc

10 MB

10 MB

...

10 MB

100 MB * 50 % = 50 MB


Planning and Sizing of the Database Instance

File Size File size * percentage = compression

File1.doc

File2.doc

...

File10.doc

40 MB

10 MB

...

10 MB

130 MB * 30 % = 39 MB

File1.doc

File2.doc

...

File10.doc

10 MB

10 MB

...

10 MB

100 MB * 5 % = 5 MB

File size - compression = data volume requirement

100 MB - 50 MB = 50 MB

130 MB - 39 MB = 91 MB

100 MB - 5 MB = 95 MB

- - - - - -

236 MB "Net" data volume requirement

+ 20 % 47,2 MB

- - - - - -

283,2 MB "Gross" data volume requirement

+ 10 % log space 28,32 MB

However, the largest existing document is 40 MB, or 28 MB when compressed. In accordance with our recommendation, the log volume should be at least twice as large as the largest expected document. Therefore, 10% is not enough in this case. The log space should be at least 56 MB.

For the greatest possible data security, we recommend that you mirror your log file. If you do so, you will then need twice the calculated amount of log space.

3.5 Further Information

For more detailed information on sizing your content server, see the SAP Content Server sizing guide at https://sap.com/sizing Sizing Guidelines Database & Technology SAP NetWeaver

Installation of SAP Content Server on UNIXPlanning and Sizing of the Database Instance P U B L I C 13

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

4 Preparations

This section describes in detail the requirements of an SAP Content Server installation, and the steps you need to take before installing your content server.

Hardware and Software Requirements [page 14]

SAP System [page 15]This section describes the minimum requirements for the back-end system.

Create Users and Groups [page 16]

Set Up the Web Server [page 17]

Install the SAP MaxDB and/or the File System Storage [page 20]

Basic Installation Parameters [page 22]The table in this section lists the basic input parameters that are prompted by the installer. For all remaining input parameters, use the tool help or the descriptions on the installer screens.

Preparing the Installation Media [page 24]This section describes how to prepare the installation media.

4.1 Hardware and Software Requirements

Hardware Requirements

This table shows the main hardware requirements:

Resource Amount Required

Hard disk space for software components ● ca. 100 MB for the Web server plus modules● ca. 350 MB for the SAP DB plus first DB instance

Hard disk space for data files and log files for each partition As much as you specified – see the Planning and Sizing of the Database Instance [page 11] section above.

Main memory At least 512 MB


Preparations

Resource Amount Required

Processor Acceptable: 1 CPU

Recommendation2 CPUs (the DB kernel runs on one CPU and the other CPU is used to process accesses to the content server).

Network protocol TCP/IP

Software Requirements

● Any one of the following operating systems in the correct releases that are listed in section General Information [page 5].

● Apache Web server 1.3.xx /2.0.xx/2.2.xx(must be at least 1.3.14/2.0.52/2.2.22)● SAP DB version

4.2 SAP System

This section describes the minimum requirements for the back-end system.

● For the content server: release 4.5B or higher of the SAP system (Note that certificates can only be used together with an SAP system release 4.6B or higher.

● For the cache server: release 4.6B or higher (4.6B with Support Package 10) of the SAP system or an SAP system with KW 4.0 or higher (KW 4.0 with Support Package 5)

In order to be able to perform administrative tasks (transaction CSADMIN), you may need a higher version of the SAP system:

● For the content server: at least Release 4.6C or KW 4.0● For the cache server: at least Release 4.6C

Installation of SAP Content Server on UNIXPreparations P U B L I C 15

4.3 Create Users and Groups

Procedure

1. Create content server and a cache server user.

We recommend that you use the following schema: <sapsid>cs and <sapsid>csc, respectively. This helps identifying which content server belongs to which SAP system later. However, any other user names are fine.

2. Make both users members of the group sapsys.3. Create a dedicated home directory for each user, where the server configuration profiles and the software

will be installed.

File system storage [page 16]

SAP DB storage [page 16]

4.3.1 File system storage

If you are planning to use a file system as your storage medium, be aware that all objects created in the repositories are owned by the content server and cache server users.

Therefore, assign full access to the repository root directories to these users.

NoteThe repository roots do not necessarily have to be located in the sapcs and sapcsc home directories, but could also be a mounted to a network attached storage device.

4.3.2 SAP DB storage

The installation program automatically creates a user called sqd<DBID> for each database instance, and makes each of these users a member of the group sapsys. For more information, see Install the SAP MaxDB and/or the File System Storage [page 20].


Preparations

4.4 Set Up the Web Server

Prerequisites

The standard Apache version 1.3 binary installations create a directory structure that consists of these subdirectories:

<apache root> /bin /cgi-bin /conf /htdocs/icons/include /libexec /logs/man /proxy

And the standard Apache version 2.0/2.2 binary installation creates a directory structure that consists of these subdirectories:

<apache root> /bin /cgi-bin/error /conf /htdocs/icons/include/modules/logs/manual/build/lib /man

The installation program accesses the subdirectories shown in bold (bin, conf and libexec (modules for apache 2.0. xx/2.2.xx)). The main server configuration file httpd.conf is stored under ./conf, and the loadable server modules are stored under ./libexec. (./modules for apache 2.0/2.2).

During setup, the Apache root directory is referred to as the Web server root for the content server or cache server. The setup program makes the following assumptions about the Apache installation:

The directories . /conf and ./libexec (./modules for apache 2.0/2.2) exist and the setup program has write access to them. (This should not be a problem, however, as the setup should be executed with “root” permissions).

Apache’s configuration profile httpd.conf is located in the ./conf directory.

You need to ensure that these assumptions are fulfilled if you are setting up the Apache binary tree yourself, or are installing a third-party binary distribution. If you want to use an Apache installation that has been integrated into your system already, you have to either manually create or soft link the ./conf and ./libexec (./


modules for apache 2.0/2.2) directories under $HOME for <sid>cs/<sid>csc. You also have to copy or soft link the file httpd.conf to the $HOME/conf directory.

However, we do not recommend that you soft link system directories, as this make it much harder to keep track of the installed packages, and makes system directories prone to access rights violations. It is easier if you maintain separate directories, and an httpd.conf file that belongs exclusively to your content server or cache server installations.

Context

The installation procedure requires a preinstalled Apache Web server on your machine.

The way the Apache Web server software is installed influences both the installation and runtime behavior of the SAP Content Server and cache server software.

We recommend that you prepare two separate Apache server installations in the home directories of the users <sapsid>cs and <sapsid>csc, and that you start the server instances under these users. You are; of course, free to configure a single server instance, so that both modules are loaded into the same process space. However, this approach is contrary to our recommendations and is not described in this installation guide.

If you intend to store your documents in a file system, the files are owned by the user under which the Web server is run. See the recommendations on file permissions in File system storage [page 16].

Procedure

The following steps refer to the SAP Content Server, but are the same for the cache server.1. Install the Apache Web server

The three most common ways of installing a working Apache Web server on your machine are described below. Choose whichever method suits you best.

To make the examples more readable, we assume a content server user named sapcs with a home directory /usr/users/sapcs in the following examples.

Compile and install the Apache Web server software from a source distribution

This method requires you to have downloaded the Apache Web server source distribution from https:// www.apache.org, and preinstalled an ANSI C compiler and a make environment on your machine.

a. Log on as the user sapcs and unpack the source distribution to the home directory:

sapcs:~$ gunzip < apache_1.3.33.tar.gz | tar xvf –

Or

sapcs:~$ gunzip < httpd-2.0.64.tar.gz | tar xvf –

Usually, the Apache source is extracted to the subdirectory ./apache_1.3.26.b. Change to that directory and configure the make files for your system.

Make sure that you enable dynamic shared object (DSO) support and that you compile all the standard modules that come with the distribution. You also need to define Apache’s root directory during the


Preparations

configuration phase. This is the directory where you should install the binary package after successful compilation. So a complete configure command looks like this:

sapcs:~/apache_1.3.26$ configure –prefix=/usr/users/sapcs – enable-shared=max --enable-module=most

Or

sapcs:~/httpd-2.0.52$ configure –prefix=/usr/users/sapcs – -- enable-mods-shared=most –with-mpm=prefork

There are a lot of other options that affect the way you compile your Web server. See the documentation provided with your source distribution for information on all the possibilities. Some platforms require additional compiler or linker switches that are not generated automatically during the configure step. Typically these flags turn on 32 or 64bit code generation, trigger code optimizations and add additional libraries to the link step. Additional flags may be added to the configuration phase with the environment variables CFLAGS and LDFLAGS. Make sure that you export the variables before running the configure script. A prominent example for the LDFLAGS variable on HP-UX is LDFLAGS=-lcl.

c. After you have configured the make files successfully, you can compile the source. You can do this by issuing the command following:

sapcs:~/apache_1.3.26$ maked. Once you have successfully completed the main compilation, you can install the binary distribution to

the final destination, the Apache root directory. Issue this command:

sapcs:~/apache_1.3.26$ make install

Or

sapcs:~/httpd-2.0.52$ make

sapcs:~/httpd-2.0.52$ make install

You should now have an Apache Web server installation under the directory /usr/users/sapcs.

These packages are usually fully integrated into the system directory structure and often adapt your startup scripts (in /etc/rc, etc.) in such a way that a preconfigured Web server instance is launched during system startup. The httpd processes then usually run under the effective user ID “nobody” or as “root”. Running non-administrative processes with administrative privileges is in general not a good idea. So, if you decide to use a preconfigured web server, please make sure that the resulting processes run with an effective user id that has no special system privileges. Especially when the file system storage is used, all file system objects will be owned by the process owner.

2. Set port numbers.

The default port numbers for the servers are 1090 (content server) and 1095 (cache server). You can change these numbers during the installation process, if necessary.

If you are running other Web servers on your machine that listen to one of these ports, specify a different port number (>1023). You will use this port number later when customizing your SAP system.

3. Set network connections.

Make sure that all users, in particular application servers and workstation PCs, can access the content server or cache server system via HTTP.


Users without direct HTTP access will either not be able to execute individual scenarios, or will only have very limited access to individual scenarios.

Additional information: how to start and stop the Apache Web server

A single command is used to start and stop the Web server. This command that can be found in the ./bin directory of your Web server installation. The commands are self-explanatory:

$sapcs:~/bin$ apachectl start

$sapcs:~/bin$ apachectl restart

$sapcs:~/bin$ apachectl stop

apachectl is a wrapper script around the server executable httpd that starts httpd using several command line options.

If you call apachectl as user sapcs or sapcsc, the httpd process is granted the appropriate rights for sapsc or sapcsc. However, if you want to use a system installation of Apache, ordinary users may not be able to execute the apachectl file. In such circumstances, you may be able to start a server instance by issuing the following command:

sapcs:~$ /usr/local/bin/httpd –f $HOME/conf/httpd.conf

We are assuming here that the httpd has been installed in /usr/local/bin and that you have created a copy of /usr/local/conf/httpd.conf in $HOME/conf belonging to sapcs or sapcsc

4.5 Install the SAP MaxDB and/or the File System Storage

The content server supports both storage types simultaneously. That is, you can put one or more repositories into the file system and other repositories into one or more database instances.

Disk space requirements for the database software

Reserve at least 350 MB for the initial software installation and the first database instance. Add 100 MB for each subsequent database instance. Database root directory

Create an SAP MaxDB root directory /sapdb. This can be a real directory on your root partition, a mount point, or a soft link.

Make sure that all users that are members of the group sapsys have full permissions for this directory.

Data and log volumes

Set up the data volumes and the log volumes. SAP MaxDB provides two options for doing this: you can either create them as files inside the file system, or in raw devices.


Preparations

File system

You can create data and log volumes as large files in the file system. This option is generally regarded as more flexible then the raw device option, but you have to expect a loss of I/O performance. This is because every disk access has to pass the kernel’s file system layer.

Raw devices

Directing disk I/O into raw disk devices – that is, addressing partitions directly and not via the kernels file system layer – yields the best performance. If you decide on this option, make sure that you set up enough raw devices (partitions plus the corresponding entries in /dev). Whichever method you choose, do not simply create one large file or raw device. Instead, spread your total volume across several files or raw devices. This will increase the overall I/O throughput of your MAX DB installation. A good divider value is 5. So, if you intend to create a database with a total size of 10 GB, create 5 partitions of 2 GB each.

For information on dimensioning the database instance, see the section Planning and Sizing above, and read the SAP Content Server sizing guide at https://sap.com/sizing Sizing Guidelines Database & Technology

SAP NetWeaver .

Installing the SAP MAX DB [page 21]

Set Up the File System [page 21]

4.5.1 Installing the SAP MAX DB

The installation of the SAP MaxDB for SAP Content Server is included in the main installation program.

When installing the SAP MaxDB, you should also consult your operating system manual as necessary.

4.5.2 Set Up the File System

Set up your file system, taking into account the following points:

● A file system repository may be located on any mounted partition. However, SAP recommends that you set up a separate partition that is exclusively reserved for that purpose.

● To maintain a consistent setup across all content servers, we also recommend that you reserve a common mount point for these partitions within your enterprise (for example, /net/contreps).

NoteThe initial path depth adds to performance. Therefore, you should keep the mount point depth low.

● Make sure that the content server and cache server users have full execution, creation, and read rights for this mount point.


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

As described in File system storage [page 16], all files are owned by the user under which the Apache process is running. We therefore recommend that you run the servers under the user’s sapcs or sapcsc. Also, all files are created with read and write access rights for the owner, group, and others. If you want to restrict the access rights, do so using the UNIX command umask.

● As mentioned above, the file system repositories are designed to yield a good usage ratio of inodes used for structural elements to those used for the documents. You can estimate the number of required inodes using the following formula:8193 + n Documents * ( 1 + m components per document)Therefore, if you want to store 3 million documents with 1 component each, you should reserve at least 6,008,183 inodes for this repository.

4.6 Basic Installation Parameters

The table in this section lists the basic input parameters that are prompted by the installer. For all remaining input parameters, use the tool help or the descriptions on the installer screens.

Parameter Description

Database ID <DBSID>

NoteThis parameter is only prompted if you choose to install a database instance

The <DBSID> identifies the database instance. The installer prompts you for the <DBSID> when you are installing the database instance.

CautionChoose your database ID carefully. Renaming is difficult and requires you to reinstall the SAP system.

● If you want to install a new database:Make sure that your database ID:○ Is unique throughout your organization○ Consists of exactly three alphanumeric characters○ Contains only uppercase letters○ Has a letter for the first character○ Does not include any of the reserved IDs listed in

SAP Note 1979280 .

Database schema


SAP<SAPSID>


Preparations

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

Parameter Description

Database operating system users and groups


SAP MaxDB software owner (default values):

● User: sdb● Group: sdba

SAP MaxDB database owner: sqd<dbsid>

Database Users


Database System Administrator: superdba

Database Manager Operator: control

Data Size for Instance


You can specify the size of the database instance or accept the default value: 2000 MB for the SAP Content Server and 200 MB for the cache server. See also Planning and Sizing of the Database Instance [page 11]

Destination Directory The binaries for Content Server (Cache Server) will be installed in <Destination Directory>\Content Server and (<Destination Directory>\Cache Server).

Content Server User We recommend that you install the Apache server in the home directory of this user account and also run it under this account.

This user owns the libraries which will be installed for SAP Content Server.

For more information, see Create Users and Groups [page 16] and Set Up the Web Server [page 17].

Content Web Server Root

Cache Server User We recommend that you install the Apache server in the home directory of this user account and also run it under this account.

This user owns the libraries which will be installed for SAP Content Server.

For more information, see Create Users and Groups [page 16] and Set Up the Web Server [page 17].

Cache Web Server Root

HTTP Port We recommend that you use HTTP Port number 1090 for th eSAP Content Server and 1095 for the cache server.


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

● SAP Content Server Installation Media

Installation Media Description

Presentation - SAP Content Server <Release> Contains the installation packages for the Content Server and the Cache Server

SAP MaxDB <Release> - SP<Version> Build <Version> <OS>

Contains the SAP MaxDB database software, only required if you install a database instance for the Content Server and / or the Cache Server

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

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

Related Information

Downloading and Extracting the Software Provisioning Manager 1.0 Archive [page 24]Downloading Installation Media [page 26]

4.7.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 :


Preparations

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

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:



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



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



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

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

2. Create a download directory on the host where you want to run the installer.3. You identify the required media als listed in Preparing the Installation Media [page 24] .4. 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.

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


Preparations



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

5. Download the objects to the download directory.6. 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.




5 Installation Process

The following sections provide the steps that you have to perform to install SAP Content Server and / or cache server using the installer.

Prerequisites for Running the Installer [page 28]Make sure you fulfil the following prerequisites before running the installer.

Running the Installer [page 31]This section describes how to run the installer.

Additional Information About the Installer [page 33]The following sections provide additional information about the installer.

5.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.○ 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 34].

● 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 .The installer uses csh scripts during the installation to obtain the environment for user <sapsid>adm. This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the shell


Installation Process


of this user is not csh. Before you start the installer, execute the following command as user <sapsid>adm to make sure that the csh scripts are up-to-date:/bin/csh -c "source /home/<sapsid>adm/.cshrc;env"

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

● 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': HP-UX, Linux, 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

Installation of SAP Content Server on UNIXInstallation Process P U B L I C 29



Output Properties

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': HP-UX, Linux, 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.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>



5.2 Running the Installer

This section describes how to run the installer.

Prerequisites

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

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

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 28]) 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:

To install SAP Content Server and / or Cache Server, choose <SAP Product Version>Standalone Engines Content Server Content Server and / or Cache Server .If you need to create only a database instance and not the complete content server or cache server installation, choose <SAP Product Version> Standalone Engines Content Server MaxDB database instances

○ If you are using the SWPM*.SAR:To install SAP Content Server and / or Cache Server, choose <SAP Product Version>Standalone Engines Content Server Content Server and / or Cache Server .If you need to create only a database instance and not the complete content server or cache server installation, choose <SAP Product Version> Standalone Engines Content Server MaxDB database instances

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.

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.

NoteOnce the installation is complete the installation now requests you to restart the apache web server instances provided for SAP Content Server and SAP Cache server.

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.

5.3 Additional Information About the Installer

The following sections provide additional information about the installer.

Useful Information About the Installer [page 34]



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

Interrupted Processing of the Installer [page 36]Here you find information about how to restart the installer if its processing has been interrupted.

Troubleshooting with the Installer [page 39]This section tells you how to proceed when errors occur while the installer is running.

Using the Step State Editor (SAP Support Experts Only) [page 40]This section describes how to use the Step State Editor available in the installer.

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



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.3.2 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 31] .

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

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

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.

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. Make sure that the installation media are still available.

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

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.

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

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 28]) 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.3.3 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 34].

○ 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 36].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.3.4 Using the Step State Editor (SAP Support Experts Only)

This section describes how to use the Step State Editor available in the installer.

NoteOnly use the Step State Editor if the SAP Support requests you to do so, for example to resolve a customer incident.

Prerequisites

● SAP Support requests you to use the Step State Editor.● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for

Running the Installer [page 28].




Procedure

1. Start the installer from the command line as described in Running the Installer [page 31] with the additional command line parameter SAPINST_SET_STEPSTATE=true

2. Follow the instructions on the installer screens and fill in the parameters prompted during the Define Parameters phase until you reach the Parameter Summary screen.

3. Choose Next.

The Step State Editor opens as an additional dialog. Within this dialog you see a list of all steps to be executed by the installer during the Execute Service phase. By default all steps are in an initial state. Underneath each step, you see the assigned installer component. For each step you have a Skip and a Break option.

○ Mark the checkbox in front of the Break option of the steps where you want the installer to pause.○ Mark the checkbox in front of the Skip option of the steps which you want the installer to skip.

4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step State Editor dialog.

The installer starts processing the Execute Service phase and pauses one after another when reaching each step whose Break option you have marked. You can now choose one of the following:

○ Choose OK to continue with this step.○ Choose Step State Editor to return to the Step State Editor and make changes, for example you

can repeat the step by marking the checkbox in front of the Repeat option.○ Choose Cancel to abort the installer.

5. Continue until you have run through all the steps of the Execute Service phase of the installer.


6 Post-Installation

After the installer has completed successfully, there are a few more things you have to do before you can use your newly-installed SAP Content Server.

Procedure

1. Set up repositories.2. Make the repositories known to your SAP system.3. Issue certificates, if necessary.4. Change the password for the database users.

You do steps 1 – 3 in transaction CSADMIN in your SAP system. For detailed information on CSADMIN and the tasks listed above, go to https://help.sap.com/nw <Choose the SAP NetWeaver Release your SAP product is based on> SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Business Users Knowledge Provider (BC-SRV-KPR) Content Management Service (BC-SRV-KPR) SAP Content Server and see the following documentation:

○ Section Content Server and Cache Server Administration

○ Section Special Measures Changing the Password for Database Access describes clearly how to change the password for the database user SAPR3. However, you should also read SAP Note 212394

that lists all the administrative database users and describes an alternative method of changing passwords. If you change the password for the user SAPR3 in the database instance, you must run the report RSCMSPWS. This report asks for the user/ password combination that the content server should use to access the repositories. After you have entered a new combination, RSCMSPWS encrypts the password and sends the user/password combination to the content server. If you forget to change the password with RSCMSPWS all connection attempts from the content server to the database will fail. The composite SAP note for the SAP Content Server for UNIX contains the link to the appropriate SAP Notes that describe the report RSCMSPWS.

5. On a more general level, you should also consult the complete operating manual for SAP Content Server at https://help.sap.com/nw <Choose the SAP NetWeaver Release your SAP product is based on> SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Business Users Knowledge Provider (BC-SRV-KPR) Content Management Service (BC-SRV-KPR) SAP Content Server to learn how to prepare backups, observe and monitor the server, and relocate repositories, among other things. The sections Content Server and Cache Server Administration, Content Server and Cache Server Monitoring, and the SAP Content Server Security Guide are of particular relevance here.


Post-Installation





7 Installation Check

This section describes how you can perform an installation check

Context

After you have created your repositories (see Post-Installation [page 42] ), you might want to run report RSCMST to check that your repositories can be accessed from the SAP system.

Installation of SAP Content Server on UNIXInstallation Check P U B L I C 43

8 Additional Information

SAP Notes Relevant for SAP Content Server [page 44]

Appendix: Modifications to httpd.conf [page 45]This appendix briefly describes the modifications made to httpd.conf by the SAP Content Server installation program.

8.1 SAP Notes Relevant for SAP Content Server

Number Content

0586895 SAP Content Server for UNIX (Composite SAP Note)

0093042 Problems with SAPFTP

0119863 SAP DB: Backup Tools

0164203 Problems with SAPHTTP

0181696 Caching

0212394 Initial Password for DBM, DBA, and Domain User

0216419 Multilevel caching and content server proxies

0315604 Customizing the Content Repositories

0319332 Content Server Backup Strategies

0203721 Content Server: Backup Tools

0350067 Administration Content Server/SAP DB

0351647 Cache Server Administration

0352518 Using the SAP Content Server Cache

0354819 Composite note SAPSECULIB

0361123 SAP Content Server and Security


Additional Information
















Number Content

0376033 Cache Server Knowledge Warehouse 5.1

0389366 Relocating Documents

0308977 Repositories BIE_QMM, BIE_NET and HME_CONTENT

0392242 Multiple Entries in Application Log

0407520 Information on the Cache Server

0842424 Content Disposition Header

0664384 Generating apache Web Server

8.2 Appendix: Modifications to httpd.conf

This appendix briefly describes the modifications made to httpd.conf by the SAP Content Server installation program.

The httpd.conf file is the general configuration profile that defines the runtime behavior of the Apache Web server.

Be aware that due to the virtually limitless number of installation scenarios, your individual httpd.conf file may differ from the examples used here. Also, a good understanding of the overall structure of the httpd.conf file is essential, in case you decide to alter the settings manually. Refer to the reference materials listed under General Information above for further reading.

httpd.conf is usually located in the directory ./conf under your Web server root directory. Only the points in the file that may be subject to a modification are listed here. Locate the lines in question using your editor’s search function.

8.2.1 Port Number

This section is about the port numbers used for the content and cache servers.

The default port for the Apache installation is 8080. During the installation, you are asked for port numbers for the content and cache servers. The default ports are 1090 and 1095 respectively. So the port line reads: Port 1090.

Installation of SAP Content Server on UNIXAdditional Information P U B L I C 45








8.2.2 Module Loader

Apache has to load the content server and cache server modules during startup. The corresponding Apache command is LoadModule. Apache loads all specified modules in reverse order. The content server and cache server module load lines appear first in the list, therefore they are loaded last.

LoadModule sapcs_module libexec/mod_sapcs.so

(FOR Apache 2.0 LoadModule sapcs_module modules/mod_sapcs2.so)

Or

LoadModule sapcsc_module libexec/mod_sapcsc.so

(FOR Apache 2.0 LoadModule sapcsc_module modules/mod_sapcsc2.so)

A server profile should contain only one module load directive, in order to avoid port number conflicts.

8.2.3 Module Registration (Only for apache 1.3)

After the modules have been loaded into the process space of the Apache Web server, they have to be ‘registered’ – that is, added to the module handler list. This is done using the AddModule command. The sequence of module registration should be the same as during module loading, so that the content server and cache server modules appear at the top of the list.

AddModule mod_sapcs.cpp or AddModule mod_sapcsc.cpp

8.2.4 Module Configuration

Almost every module has its own a specific configuration section in httpd.conf. This allows an administrator to influence the way this module behaves while it is being used in a particular HTTP request. Both the content server and the cache server require such a section. The configuration sections for the content server and the cache server are not part of the standard httpd.conf file, so they are simply added to the end of the file. Both configurations are very similar, and differ only in a few (but important) lines. These sections are shown below.

Content Server Configuration Section

Code Syntax

<IfModule mod_sapcs.cpp> AddModuleInfo sapcs "SAP Content Server (C) SAP AG 1998,2003" CSConfigPath /usr/users/sapcs/cs.conf<Location /sapcs>SetHandlersapcs_module Allow


Additional Information

from all </Location><Location /ContentServer/ContentServer.dll> SetHandler sapcs_moduleAllow from all</Location><Location /contentserver/contentserver.dll> SetHandler sapcs_moduleAllow from all</Location> </IfModule>

Cache Server Configuration Section

Code Syntax

<IfModule mod_sapcs.cpp> AddModuleInfo sapcsc "SAP Content Server Cache (C) SAP AG 1998, 2003"CSCConfigPath /usr/users/sapcsc/csc.conf<Location /sapcsc>SetHandlersapcsc_module Allowfrom all </Location><Location /CacheServer/CacheServer.dll>SetHandler sapcsc_moduleAllow from all</Location><Location /cacheserver/cacheserver.dll>SetHandler sapcsc_moduleAllow from all</Location><Location /Cache/CSProxyCache.dll>SetHandler sapcsc_moduleAllow from all</Location><Location /cache/csproxycache.dll>SetHandler sapcsc_moduleAllow from all</Location> </IfModule>

Each module configuration consists of a generic “header” block and a handler directive. The header block consists of the variable CSConfigPath/CSCConfigPath, which points either to the content server or cache server configuration profile, and a copyright notice. Then, several URL prefixes are defined. Each prefix triggers the Apache Web server to pass the request to the module. A number of compatibility prefixes have also been added. The keywords “Allow from“and “Deny from“are standard client access modifiers, which you could adjust in order to fine-tune the accessibility of your server instance.

Installation of SAP Content Server on UNIXAdditional Information P U B L I C 47

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.


Important Disclaimers and Legal Information

Installation of SAP Content Server on UNIXImportant Disclaimers and Legal Information P U B L I C 49

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