Symptom
Apache 2.4.xx version was not supported with SAP Content Server / Cache Server.

Other Terms
SAP Content server, SAP Cache server, 6.50, Apache 2.4

Reason and Prerequisites
Please compile and install the Apache 2.4 as per the steps 2648298.

Solution
Please refer to the note 514500 and download the latest build of SAP Content Server.

After the succesfull installation of Apache and Content Server, do the below manual changes in the httpd.conf file.

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.

1. Port Number: The default port for the Apache installation is 80. 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.

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 modules/mod_sapcs24.so

or for Cache Server

LoadModule sapcsc_module modules/mod_sapcsc24.so

For AIX:

LoadModule sapcs_module modules/mod_sapcs24.o

or

LoadModule sapcsc_module modules/mod_sapcsc24.so

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

<IfModule mod_sapcs.cpp>
CSConfigPath /usr/users/sapcs/conf/cs.conf
<Location /sapcs>
SetHandler sapcs_module
Allow from all
</Location>
<Location /ContentServer/ContentServer.dll>
SetHandler sapcs_module
Allow from all
</Location>
<Location /contentserver/contentserver.dll>
SetHandler sapcs_module
Allow from all
</Location>
</IfModule>

 

Cache Server configuration section

<IfModule mod_sapcsc.cpp> 
CSCConfigPath /usr/users/sapcsc/csc.conf 
<Location /sapcsc>
SetHandler sapcsc_module Allow from all 
</Location> 
<Location /CacheServer/CacheServer.dll> 
SetHandler sapcsc_module Allow from all 
</Location> 
<Location /cacheserver/cacheserver.dll> 
SetHandler sapcsc_module Allow from all 
</Location>  
<Location /Cache/CSProxyCache.dll> SetHandler sapcsc_module 
Allow from all 
</Location> 
<Location /cache/csproxycache.dll>
SetHandler sapcsc_module Allow from all 
</Location>  
</IfModule>

配置底层存储驱动

StorageDriver
Type: Text
Range: SAPDBStorage, FSStorage

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.

sapcs@dms-prd01:/usr/sap/sapcs/conf> cat cs.conf
;----------------------------------------------------------------------------
; This is the configuration profile for the
; SAP HTTP Content Server/Content Server Cache on UNIX
; $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ind/contentServer/6.40/unix/cs.conf#1 $
;----------------------------------------------------------------------------
;
; GENERAL INFORMATION
; -------------------
;
; This file is made up of several sections in which a number of
; parameter/value pairs are defined.
;
; Each section starts with a heading enclosed in square brackets.
;
; For each server type there must be exactly one global section
; defined, named either [ContentServer] or [ContentServerCache].
;
; Any number of repository sections may follow, each headed by
; [contRep-<NAME>]. <NAME> identifies the repository name.
; Repository names are case sensitive.
;
; IMPORTANCE OF BACKUP
; --------------------
;
; As this file defines the access profiles for all of your repositories.
; SAP stronly recommends you make a backup after each modification.
;
;----------------------------------------------------------------------------
;
; PARAMETERS
; ----------
;
; Parameters that have been defined under the global section either
; define the overall behaviour of the server (such as tracing or security),
; or define default values that are merged into all subsequent
; repository sections (such as StorageDriver). All globally defined
; parameters can be redefined in any repository section. Then the
; redefinition is valid only for that repository, all other repositories
; remain unaffected. All parameters as well as the values specified
; in "range" are case sensitive.
;
; VALUES
; ------
;
; Two types of values can be used depending on the type of parameter.
; BOOLEAN: The values true and false are indicated by the value "1" or "0".
; TEXT:    Any number of ascii characters.
;
;----------------------------------------------------------------------------
;
; GLOBAL PARAMETERS
; -----------------
;
; AdminSecurity
; -------------
; Type: BOOLEAN
; Purpose: enables or disables basic authentication for the restricted use
; of commands that deal with the administration of repositories, certificates
; exports and traces.
; Behaviour: A "401 (Authorization required)" response together with an
; appropriate realm is passed back to the client.
;
;
; AdminSecurityGroup
; ------------------
; Type: TEXT
; Purpose: Restrict the number of users with administrative rights to
; members of this group. AdminSecurityGroup is only evaluated if AdminSecurity
; is enabled. AdminSecurityGroup is a mandatory parameter together with
; AdminSecurity.
;
; AuthService
; -----------
; Type: TEXT
; Range: NIS, Local
; Default: Local
; Purpose: Change password verification from local /etc/passwd to Network
; Information Service (aka Yellow Pages). If turned to NIS, only NIS maps
; will be used to check user authorizations. This requires that a properly
; maintained NIS environment is available. Please read the security notes
; of your NIS provider to avoid security leaks.
;
; TraceLevel
; ----------
; Type: TEXT
; Range: emergency, alert, critical, error, warning, notice, info, debug
; Purpose: Set the trace level from very informative to runtime critical.
; All traces are written into the web server's trace.
; To receive a trace entry the corresponding Web server's trace level must
; be at least the same or higher.
; WARNING: If you set a very high level, the trace file probably grows
; to an extent that consumes all of your free blocks in the file system.
;
; TraceOverride
; -------------
; Type: BOOLEAN
: Purpose: If set all trace messages will appear in the log file regardless
; of the current server log level.
;
; WARNING: THIS SWITCH IS INTENDED FOR SUPPORT REASONS ONLY AND SHOULD
; NEVER BE TURNED ON FOR PRODUCTION. The trace file very likely grows
; to an extend that consumes all of your free blocks in the file system.
;
; REPOSITORY PARAMETERS
; ---------------------
; All repository relevant parameters could also appear in the global section
; as the default for all repository sections.
;
; StorageDriver
; -------------
; Type: Text
; Range: SAPDBStorage, FSStorage
; Purpose: Sets the storage device for this repository. Although the backward
; compatibility "Storage" parameter could be used, it is recommended to define
; the storage type with this parameter.
;
; Storage
; -------
; Type: Text
; Range: ContentStorage.dll, FileSystemStorage.dll
; Purpose: Backward compatibility parameter to keep MS Windows content server
; configurations compatible with Unix configurations.
;
; ContRepRoot
; -----------
; Type: Text
; Range: Any valid system path
; Purpose: Sets the root directory for the repository. This parameter is
; mandatory if StorageDriver=FSStorage is set, otherwise ignored.
; Make sure that the server has full permissions to that directory and that
; the directory exists. The server does not create this directory.
;
; ContentStorageName
; ------------------
; Type: Text
; Range: Any valid SAP DB instance name
; Purpose: Sets the SAP DB instance name to which the server connects, in
; case this repository is being accessed. This parameter is mandatory if
; StorageDriver=SAPDBStorage is set, otherwise ignored.
;
; ContentStorageHost
; ------------------
; Type: Text
; Range: valid hostname, IP-Adress
; Purpose: Sets the hostname on which the SAP DB instance may be found that
; is specified with ContentStorageName. This parameter is mandatory if
; StorageDriver=SAPDBStorage is set, otherwise ignored.
;
; SQLTrace
; --------
; Type: BOOLEAN
; Purpose: Sets or unsets the tracing of all sql traffic to the
; database server.
; This parameter is required only for support reasons by SAP support
; personnel. Setting sqltrace to 1 produces very large trace files.
;
;
; ContRepDescription
; ------------------
; Type: Text
; Purpose: Descriptive repository text
;
; UncompressedMimes
; -----------------
; Type: Text
; Range: all, <empty>
; Purpose: Disables compression of objects. Only all or no objects at all
; could be compressed. Be careful: If set in the global all repositories
; store uncompressed. There is no switch to turn on compression for
; individual repositories again. So this parameter should be used on a
; repository level, unless uncompressed storage for all repositories is
; intended.
;
; Security
; --------
; Type: BOOLEAN
; Purpose: If set, the server checks signatures for all URLs that access
; this repository. All unsigned URLs will be rejected.
; To use repository security, a certificate has to be issued from the SAP system.
;
; DefaultDocProt
; --------------
; Type: TEXT
; Range: c,r,u,d
; Purpose: Restriction of the access rights to this repository.
; The letters may be concatenated (e.g. "c", "cr", "crud").
; See the KPRO HTTP Protocol Definition for further details.
;
;
;----------------------------------------------------------------------------
; Content Server Cache Parameters
;----------------------------------------------------------------------------
;
; CacheThreshold
; --------------
; Type: INTEGER
; Range: 0 - 100
; Default: 70
; Purpose: Maximum storage usage ratio in percent. Cache server starts cache
; reorganisation if this threshold limit is exceeded or storage space is
; insufficient for the next document.
; Setting the ratio to 100% is not a good idea since this increases not
; only the number of reorganization jobs but can also lead to a system lock
; down in case the cache repository is located in a file system.
;
; MaxReorgProcs
; -------------
; Type: INTEGER
; Range: 1-20
; Default: 5
; Purpose: Limit the number of concurrent cache reorganisations. However,
; this parameter works only on file system caches. The number of concurrent
; database cache reorganisations cannot be changed by a parameter. The
; default of 5 concurrent reorganisations should be sufficient even under
; very heavy load conditions.
;
;----------------------------------------------------------------------------
;----------------------------------------------------------------------------
[ContentServer]
TraceLevel=warning
AdminSecurity=1
AdminSecurityGroup=sapsys
ContRepRoot=/usr/sap/sapcs/contrep
ContentStorageHost=yccsraps
ContentStorageName=GCS
StorageDriver=SAPDBStorage
PSEDir=/usr/sap/sapcs/security
[contRep-CS]
ContentStorageHost=172.16.120.121
ContentStorageName=GCS
Storage=ContentStorage.dll
Security=0
DefaultDocProt=rucd
ContRepDescription=SRM content server

[contRep-ZTEST_DMS]
ContentStorageHost=172.16.120.121
ContentStorageName=GCS
Storage=ContentStorage.dll
Security=1
ContRepDescription=ZTEST_DMS

[contRep-ZGCP_CR]
ContentStorageHost=localhost
ContentStorageName=GCS
ContRepDescription=GCP Content Server
Storage=ContentStorage.dll
Security=0
DefaultDocProt=rucd

SAP Content Server
General Architecture

General Architecture

Knowledge Provider is a component of SAP Web Application Server and provides the general infrastructure for storing and administrating documents. The Content Server and the Cache Server are server components that interact with the Knowledge Provider.

SAP Content Server

The SAP Content Server is a stand-alone component in which a large quantity of electronic documents of any format and with any content can be stored.

The documents can be saved either in one or more MaxDB instances or in the file system.

Applications can access Content Server for uploading/downloading documents via Knowledge Provider APIs or directly by providing HTTP URLs

API-RFC

SAP Cache Server

The SAP Cache Server serves the following purposes:

• To provide a seamless and transparent caching facility for existing Content Server landscapes

• To drastically reduce client response times

• To ensure that caching requires as little administration work as possible

Cache servers are used in distributed environments to store documents at a location close to the relevant client, and thus to allow faster access to document content. To do this, the Cache Server creates and stores “working copies” of documents from the Content Server. This also reduces network load, as no remote content server has to be accessed when a client requests read access to a document. Cache servers are similar to content servers. However, with cache servers, little administrative input is required, and access protection is maintained. The central document management functions in the SAP System make sure that out-of-date document versions that are still in the cache are no longer accessed and are eventually deleted.

If the client and the Content Server have the same location, the documents do not (usually) need to be cached. In these cases, the requested URL is sent directly to the Content Server and the content is obtained directly from the Content Server.

The current version of SAP Content Server is 6.40 which will be phased out. The new version of SAP Content Server is 6.50 and this will be made available from May 2014.

Please find more information regarding SAP Content Server 6.50 here.