Description of ContentServer.INI File
Description of File Structure and Parameters
The ContentServer.INI file describes the structure of the repositories connected to the Content Server. 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 database backups, the latest version of this file is also always backed up (in line with the DB backup). This is because without an up-to-date record of the repository, the Content Server cannot access a restored database.
Storage Location
The ContentServer.INI file must be stored in the Content Server installation directory.
Structure
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 contRep section defines a content repository. In other words, this section contains all 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.General Information on Parameters
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 first one is used.
Parameters for the [ContentServer] Section
Name: LogRequests
Type: Boolean
Default: 0
Values: 0, 1
Mandatory: no
Description: log all client requests in file cs_trace.txt.
Name: ResponseTrace
Type: Boolean
Default: 0
Values: 0, 1
Mandatory: no
Description: log all client responses in file cs_trace.txt.
Name: Log404Response
Type: Boolean
Default: 0
Values: 0, 1
Mandatory: no
Description: log all NOT FOUND requests in file cs_trace.txt.
Name: FullTrace
Type: Boolean
Default: 0
Values: 0, 1
Mandatory: no
Description: log 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: 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: 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).maxTransferBlockSize
is effective from Server Build 161.See also:
Note 328209
If you want to change the password for database access:
See the section
Then make the following entry:
USER=SAPR3
PASSWORD=<new password>
Parameters for the [contRep-<RepositoryName>] Section
Name: Storage
Type: Character
Default: ContentStorage.DLL
Values: ContentStorage.DLL
Mandatory: yes
Description: the
Storage parameter contains the name of the storage layer required for accessing a repository. The default value has to be used.
Name: ContentStorageHost
Name: ContentStorageHost
Type: Character
Default: localhost
Values: Fully qualified hostname, IP address, localhost
Mandatory: yes
Description: the
ContentStorageHost determines 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: 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
Description: the parameter ContentStorageName contains the name of the database instance.
Name: ContRepDescription
Type: Character
Default: ""
Values: Free text
Mandatory: yes
Description:
ContRepDescription contains a free text line that explains what the repository is used for.
Security
Type: Boolean
Default: 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 R/3 Customizing. The transactions involved are
CSADMIN and OAC0.
Name: DefaultDocProt
Type: Character
Default: ""
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: 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: LiveCache
Values: ODBC driver name
Mandatory: no
Description:
driver contains the ODBC driver names required for DB access. The suitable ODBC driver has to be registered under the driver name in the NT ODBC service layer.Only the ODBC drivers of the SAP DB are available for productive operation.