The connection data for clients is stored in this dictionary which
can be found in the instance-specific
config/server.xml file. The
dictionary has the following entries:
cm: Connection Data of the Content Management
database: Dictionary whose
content determines the database configuration Example:
<database filename="sqlite.xml" />
Subelements can be:
adaptor: Name of the
database: Name of the
database (not SQLite).
password: Password of
the database user (not SQLite).
server: Name of the
database server (not SQLite, DB2).
Using this configuration value, you can determine whether
blobs (versions, user settings, etc.) are to be saved in
the database (
true, the default)
or stored in the file
system as files (
false). Never change this
value after the first start of the application unless appropriate
have been taken. Otherwise, your data will be corrupted.
user: Login used for
logging into the database (not SQLite).
blobSizeLimit: Maximum size (in bytes) of data that can be stored in the
blobs table. The default is 1GB (1073741824). Larger amounts of data are already rejected before they are saved in the database (so that, for example, transactions or replication processes with large amounts of data are not impaired). See also
content.maxBlobSize for the database-independent limitation.
httpConnectHost: Other CMS
applications read the value of this entry to determine the name
of the server under which the application can be reached. The
value is obligatory.
httpHost: The server name or
the IP address to which the server binds its HTTP port. If
nothing is specified here, the server can be reached under all
available names of the machine. If
specified here, the server can be accessed from local
httpPort: HTTP port on which
the application can be reached.
httpProxyHost (optional): Name
or IP address of a proxy server via which the application can
httpProxyPort (optional): Proxy
stateHost: Name of the computer
via which the condition of the CMS application can be queried
statePort: State server port.
tclHost: The name of the
machine on which the Tcl server of the CMS applications can be
tclPort: Tcl server port.
<email> <!-- leave 'host' empty to deactive email services--> <host>localhost</host> </email>
log: The subelements of this dictionary define
which type of information is logged in which file. Example:
<configuration> <!-- Valid "info" log levels are 0, 1, 2, 3. Messages will go to the specified log file.--> <logger name="info" level="2" logFile="info.log" /> <logger name="error" logFile="error.log" /> <logger name="alert" logFile="error.log" /> <logger name="warning" logFile="error.log" /> <logger name="debug" logFile="debug.log" /> </configuration>
name attribute determines the log type,
logFile the log file. By means of
individual log file can be specified for each log type. Releative paths
refer to the CMS directory log. The log type
info allows you to determine the amount of information to
log. For this, use the
level attribute (0 = nothing, 3 =
For the GUI, logging is configured in the separate file
ses: Connection data of the Search Engine
cm, however without the
rpcUrlPrefix: Prefix of the URL the Content
Management Server uses to talk to the Java Kernel.
te: Connection data of the Template Engine. The
Template Engine is provided with data from the Content Management
Server via HTTP. This element contains the same elements as