!--a11y-->
Description of the Content Server Configuration File 
As well as parameters that affect the general behavior of the server, the configuration file contains all the communication parameters necessary for each repository.Usually, the content server keeps the file up to date automatically; in other words, manual editing is not required. The transaction CSADMIN is used for maintaining and administrating the content server.
The
ContentServer.INI file is vital for the smooth operation of the whole SAP
Content Server.
In
particular, you must ensure that besides the regular
Data Backups, the
latest version of this file (as appropriate for the repository backup) is also
always backed up (in line with the Database Backup).
This is because without an up-to-date record of the repository, the content
server cannot access a restored database.
Depending on the operating system the configuration file is called ContentServer.INI (Windows operating systems) or cs.conf (Unix).
Depending on the server variant different parameters or different parameter values are used. For this reason the parameters for the two files are described separately.
The ContentServer.INI file must be stored in the Content Server installation directory. The storage location of file cs.conf is specified in the Web server configuration table CSConfigPath in the Web server configuration profile.When the content server is installed this value is set to <ServerRoot>/conf/cs.conf.
The ContentServer.INI file is subdivided into a number of sections. Each of these sections contains parameter-value pairs that are valid within that section. The first section is an exception, however. All entries in this section represent default values for subsequent sections. You can change these defaults in each individual section.
The sections are as follows:
[ContentServer]
The [ContentServer] section contains all generally valid parameters that influence the runtime of the server.
[contRep-<RepositoryName>]
The section defines a content repository.This means that it contains all the parameters that describe access to the database repository.If the corresponding section does not exist, any repository defined in the database will be inaccessible. A [contRep-<RepositoryName>] section must be created for every repository that you want to be accessible from the SAP system.
All repository parameters can also be defined as global default settings in section [ContentServer]. They are then valid the same for all repositories, they can however by redefined for each repository if required.
One parameter-value pair is allowed per line.
Every parameter-value pair must contain the assignment sign ‘=’.
Parameter-value pairs are case-sensitive.

If you want a particular parameter to be ignored, insert a semicolon ‘;’ at the beginning of the line.
Parameters are only valid within their own sections.
If a number of parameters with the same name but different values exist, the last one is used.
Name: LogRequests
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: log of all client requests in file cs_trace.txt.
Name: ResponseTrace
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: log of all client responses in file cs_trace.txt.
Name: Log404Response
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: log of all NOT FOUND requests in file cs_trace.txt.
Name: FullTrace
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: log of all request/response pairs in their full length in file cs_trace.txt.

This switch should only be used for diagnostic purposes and only in connection with controlled server requests. Do not activate this switch in the productive system.
Name: KeepConnection
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: KeepConnection=0 ends the client connection after the response has been transferred. KeepConnection=1 keeps the connection open, thus allowing the client to send more requests on this connection. This second option enhances performance, as it saves on the resources required to establish a new connection.
Name: MaxTransferBlockSize
Type: Integer
Default setting: 65535
Values: 1..4294967296
Mandatory: no
Description: MaxTransferBlockSize determines the block length of the IIS responses. Zero-byte responses can occur in very busy systems. This is because no send buffer can be allocated on the server. In such cases, we recommend that you reduce the block size (for example, to a minimum of 4096 bytes). The size is specified in bytes.
maxTransferBlockSize is effective from Server Build 161.
Note 328209
Name: Storage
Type: Character
Default setting: ContentStorage.DLL
Values: ContentStorage.DLL
Mandatory: yes
Description: the storage parameter contains the name of the storage layer required for accessing a repository.
Name: ContentStorageHost
Type: Character
Default setting: localhost
Values: qualified host name, IP address, local host
Mandatory: yes, if “Storage“ is set to ContentStorage.DLL.
Description: the ContentStorageHostdetermines the host on which the database containing the repository is located.

The database cannot be run on any machine other than the content server machine.
Name: ContentStorageName
Type: Character
Default setting: SDB
Values: SDB

You
need to change the default value SDB if a different name was used for the
Database
Instance when
the Content Server was installed.
Mandatory: yes, if “Storage“ is set to ContentStorage.DLL.
Description: the parameter ContentStorageNamecontains the name of the database instance.
Name: ContRepRoot
Type: Text
Values: each valid system path
Mandatory: yes, if “storage“ is set to FileSystemStorage.dll.
Description: ContRepRoot specifies the root directory for this repository. A full, absolute path name to a directory that exists (rsp. is mounted) must be specified. This directory must have sufficient authorizations to create subdirectories for the user ID, who started the content server.
Name: ContRepDescription
Type: Character
Default setting: ""
Values: free text
Mandatory: yes
Description: ContRepDescriptioncontains a free text line that explains what the repository is used for.
Name: Security
Type: Boolean
Default setting: 0

Signature checking should always be switched on in a productive system. This is because signature checking is the only method of preventing unauthorized access to documents.
However, it may be necessary to temporarily switch off signature checking if you are analyzing problems or carrying out an installation.
Values: 0, 1
Mandatory: yes
Description: switches signature checking on and off.
If there are inconsistencies between the content server and the SAP system, documents cannot be accessed. In this case, you should remove all certificates from the content server and in Customizing. The transactions involved are CSADMIN and OAC0.
Name: DefaultDocProt
Type: Character
Default setting: ""
Values: {r c u d} r - Read, c - Create, u - Update, d - Delete
Mandatory: no
Description: DefaultDocProt determines document access protection for this repository. The default value for the security level can be overwritten when this document is stored. As the default value is usually used, however, this parameter is relatively unimportant. This parameter mainly influences whether or not a signature is required for creating a document.
Name: sqltrace
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: if sqltrace==true, an SQL trace is written to the directory c:\winntsystem32. This trace should be activated for diagnostic purposes only, and is switched off in a productive system.
Name: driver
Type: Character
Default setting: LiveCache
Values: ODBC driver name
Mandatory: no
Description: drivercontains the ODBC driver names required for DB access. The suitable ODBC driver has to be registered under the driver name in the ODBC service layer.
Only the ODBC drivers of the database instance are available for productive operation.
Name: AdminSecurity
Type: Boolean
Default setting: 0
Values: 0, 1
Mandatory: no
Description: switches administrative authentication on and off. If AdminSecurity is activated, the server for security-relevant administration URLs sends return code “401 (authorization required)“ back to the client. Only when a valid user and password for an administration request is sent by the client, does the content server process this command.
Name: AdminSecurityGroup
Type: Text
Default setting: none
Mandatory: yes, if “AdminSecurity” is set to 1.
Description: The content server checks whether the operating system user specified in the request is a member of the user group specified in AdminSecurityGroup. When the content server is installed this group is interrogated and assigned the default value “sapsys”.
Name: AuthService
Type: Text
Default setting: local
Values: NIS, Local
Mandatory: no
Description: AuthServicespecifies the password or group file against which the transferred user is to be checked. If AuthService is not specified the check is always made against /etc/passwd. If AuthService=NIS is set, the check is made against the “Network Information System (NIS)“. The check against /etc/password can also be set explicitly by using AuthService=Local.
Name: TraceLevel
Type: Text
Default setting: error
Values: emergency, alert, critical, error, warning, notice, info, debug
Mandatory: no
Description: TraceLevelspecifies, how detailed the actions in content server are to be recorded. The lower the trace level, the quicker the server log file grows. Trace level debug is only relevant for maintenance and diagnosis. Generally the content server cannot issue messages that exceed the trace level set for the Web server. So, if the trace level of the Web server is set to Warning and the trace level of the content server to debug, no messages of type notice, info or debug will be issued.
If you change the trace level of the Web server, you must restart it.
Name: TraceOverride
Type: Boolean
Values: 0
Mandatory: no
Description: You can use this parameter to override the trace level of the Web server for diagnostic purposes. All content server actions are logged with at least the trace level of the Web server. This parameter is intended for diagnostic and support purposes, as it enables the debug trace to be activated without having to restart the server.
Name: StorageDriver
Type: Text
Values: SAPDBStorage, FSStorage
Mandatory: yes
Description: StorageDriverspecifies the storage medium the repository is created on.
Name: Storage
Type: Text
Values: ContentStorage.dll, FileSystemStorage.dll
Manadatory: yes, but deprecated
Description: Parameter Storage is included for compatability reasons and at present it has the same meaning as the parameter StorageDriver.
Name: ContRepRoot
Type: Text
Values: each valid system path
Mandatory: yes, if “StorageDriver“ is set to FSStorage.
Description: ContRepRootspecifies the root directory for this repository. A full, absolute path name to a directory that exists (rsp. is mounted) must be specified. This directory must have sufficient authorizations to create subdirectories for the user ID, who started the content server.
Name: ContentStorageName
Type: Text
Values: each valid SAPDB instance name
Mandatory: yes, if “StorageDriver“ is set to SAPDBStorage.
Description: ContentStorageName is the name of the SAPDB instance, in which the current repository is stored.
Name: ContentStorageHost
Type: Text
Values: each valid host name, IP address
Mandatory: yes, if “StorageDriver“ is set to SAPDBStorage.
Description: ContentStorageHost is the name of the host, on which the SAPDB instance is running.
Name: SQLTrace
Type: Boolean
Mandatory: no
Description: If SQLTrace is activated, all database operations are recorded. The resulting log is used by SAP for support and diagnosis purposes.In normal operation this trace should always be deactivated, since the resulting traces become very large and affect the performance of the server.
Name: ContRepDescription
Type: Text
Mandatory: no
Description: Free text description of the repository logged in transaction CSADMIN.
Name: UncompressedMimes
Type: Text
Values: all
Mandatory: no
Description: This parameter deactivates the compression for all new objects you want to create.
Name: Security
Type: Boolean
Default setting: 0
Mandatory: no
Description: Securityactivates and deactivates the signature check for URLs directed to this repository. To check signatures an appropriate certificate must have already been sent to the content server and activated
Name: DefaultDocProt
Type: Text
Values: c, r, u, d
Mandatory: no
Description: Specifies the security level for checking signatures of documents.