Most of the Content Server configuration is done in
contenserver.properties.
In addition, the following setting in contentserver.properties should be in sync with the
corresponding setting in server.xml:
cap.server.http.port
See the description of the properties for more details. The corresponding settings in the server.xml file of the
servlet container are shown in XPath syntax.
| Property | Value | Default | Description |
|---|---|---|---|
cap.server.http.port
| Port | This property defines the HTTP(S) port of the application container containing the
Content Server.
The entry
/Server/Service/Connector@port in server.xml
has to have the same value as this property. | |
cap.server.ORBServerHost
| String | The host of the ORB which the Content Server instantiates. This property is deprecated and is ignored when using the application server's ORB. | |
cap.server.ORBServerPort
| Int | The port of the ORB which the Content Server instantiates. This property is deprecated and is ignored when using the application server's ORB. | |
cap.server.ORBServerSSLPort
| Int | 0 | The port of the ORB which the Content Server instantiates for SSL encrypted communication. Set to 0 or leave empty if you do not want an SSL server socket. This property is ignored when using the application server's ORB. |
cap.server.repository.home
| Path | /Home
| Using this property, you can define the folder which will be used to store the
home folders of the users. The whole folder hierarchy of the home folders is only
visible to the administrator. Other user will only see one home
folder with the path defined in cap.server.repository.home containing his
personal files, such as the preferences. The default folder is /Home which
will be automatically created by the system. If you define another folder, you need to
create this folder by your own. |
cap.server.repository.system
| Path | /System
| Using this property, you can define the system folder. It contains for example
the public dictionary of the spell checker. The default folder is /System
which will be automatically created by the system. If you define another folder, you
need to create this folder by your own. |
cap.server.multipleLiveServers
| true/false | false | This property defines whether the server publishes to multiple live servers. Note that this flag cannot be easily changed after the first start of the Content Management Server. |
cap.server.documentTypes
| URL/Path |
This property defines where the server finds the XML file(s) containing the content type definitions. You can specify multiple files as a comma separated list or use Ant-style patterns with wildcards like '*', '?' and '**'. Example:
| |
cap.server.resourcecache.size
| Int | 60000 | This property defines the resource cache size, that is, the number of resources the server holds in memory. This value should sometimes be adapted to the increasing number of resources in the actual working set. If the value is too small, the server does not perform well. One resource needs about 2kB of heap space. |
cap.server.license
| URL/Path | properties/corem/license.zip
| This property defines where the server finds the license file. |
cap.server.login.bouncers
| URL/Path | This property points to the optional login bouncer configuration. A login bouncer can grant or deny access to the Content Server based on the characteristics of the user and the set of currently logged in users. | |
cap.server.useStrictWorkflow
| true/false | false | This property enforces the strict workflow mode. That is, the approver of a resource must be different from the editor. This is checked independently of the workflow engine, and should only be used in cases where a custom workflow definition is not an option. |
cap.server.checkUniqueDbAccess
| true/false | false | This property determines whether to check for another server that is running concurrently on the same database on server startup. For compatibility, this property defaults to false, but it is recommended to set it to true in order to prevent data corruption. |
cap.server.uniqueDbAccessWriteInterval
| Int | 0 | If unique DB access is checked and if this property is positive, this property determines the number of seconds between two writes of the current timestamp to the database to indicate the liveliness of the server; if 0 or negative the server neither writes a timestamp regularly nor expects a timestamp to be written; this value defaults to 0. |
cap.server.usercache.size
| Int | 500 | This property defines the size of the user cache. It limits the maximum number of users which can be found in one search for users in the user window of the Site Manager. Set the property to the size of the largest user search you want to perform, or the number of concurrently working users, whichever is greater. |
cap.server.groupcache.size
| Int | 500 | This property defines the size of the group cache. It limits the maximum number of groups which can be found in one search for groups in the user window of the Site Manager. Set the property so that all groups connected to rights can be cached in memory. |
cap.server.rightscache.size
| Int | 3000 | This property defines the size of the rights cache. This cache stores the
results of right calculations per resource, content type and member. If you have lots
of different resources, content types and users you might need to adapt the value of
the property. Check the proper size of the cache by examining the cache misses and
faults in the log. To activate the log output of the rights cache set the
cap.server.rightscache.status.interval property to a value larger than
zero. |
cap.server.memberfolderrightscache.size
| Int | 1000 | This property defines the size of the folder-specific rights cache.
This cache stores the results of right calculations per folder and member,
aggregating the results for all content types. This cache might help custom
code using APIs other than the Unified API,
but mainly it affects the performance of the
Site Manager in rare cases. Change this setting
only if you observe the method getRights(MemberKey) in thread dumps of
a slow Content Server. |
cap.server.allowSyntheticReplay
| true/false | true | Whether it is allowed for clients to request a synthetic replay
of the content repository,
for example using the constant Timestamp.SYNTHETIC_REPLAY of the
Unified API.
This is a very expensive operation that is rarely used
except when setting up a Replication Live Server from scratch.
|
cap.server.rightscache.status.interval
| Int | 0 | This property defines the interval (in seconds) at which log output of the rights cache is written. "0" means, that no log output is written. |
cap.server.blob.channel.timeout
| Int | 60 | This property sets the timeout for streaming blobs to and from the database in
seconds. In general, you don't have to change the default value. It is provided for
exceptional cases, when the connection to the database is unreliable. If you deploy the
Content Server as a web application, you have to use the
connection timeout setting of the servlet container. In XPath notation this is
/Server/Service/Connector@connectionTimeout in server
.xml.
|
cap.server.init.runlevel
| String | online | The initial runlevel that the server will try to reach on startup. Possible runlevels are: online, administration, maintenance. This property does not override the default behavior of the Replication Live Server for the initial replication as described in Section 3.10.1, “Installing the First Replication Live Server”. The property is effective only in the case of web application deployment. |
cap.server.maximumStartupDelay
| int | 60 | The maximum time after which the Content Server is treated as initialized. Dependent web applications will be started when the Content Server has reached its initial runlevel or after this time. Note that large values may delay the startup of the container by that time. |
cap.server.encryptpasswords.keyfile
| String |
The location of the key generated by cm encryptpasswords. If empty, defaults to
etc/keys/<databasename>.<dbuser>.rijndael
| |
cap.server.initialPassword.<user>
| String | The initial password to set for the default user with the indicated name, taken from the list in Section 3.16.1.1, “Standard Groups and Users”. This password is set when the server is started for the first time. You can change the passwords later on at any time. |
Table 5.1. contentserver.properties
Properties for SSL connection:
| Property | Value | Default | Description |
|---|---|---|---|
cap.server.https.keystore
| Path | The path to the KeyStore file which contains the certificate for the connection.
The entry
/Server/Service/Connector@keystoreFile in server.xml
(for a separate SSL connector)has to have the same value as this property.
| |
cap.server.https.password
| String | The password of the KeyStore.
The entry
/Server/Service/Connector@keystorepass in server.xml
(for a separate SSL connector)has to have the same value as this property.
| |
cap.server.https.keypassword
| String | The key to the certificate.
The entry
/Server/Service/Connector@keyPass in server.xml
(for a separate SSL connector)has to have the same value as this property. |
Table 5.2. contentserver.properties
Properties to enable/disable the search service:
| Property | Value | Default | Description |
|---|---|---|---|
cap.server.search.enable
| true or false
| false
| if true full text search is enabled. |
Table 5.3. contentserver.properties
![[Caution]](../common/images/caution.png) | Caution |
|---|---|
Use the home folder as it is defined above only for your personal files (queries, preferences etc.). Don't use it for content that will be published. |
 |  |  |
 |