This section covers configuration options related to the server communication and the basic cache configuration.
Connecting to the Content Server
In a CAE application there are a number of properties for setting up the connection to the Content Server, from which the Content Application Engine reads the content to be displayed. Configure the properties shown in the table to define the location of the Content Server and the identity of the user used to log in to the server.
| Property | Description |
|---|---|
|
|
The URL of the Content Server |
|
|
The domain of the Content Server |
|
|
Define the user with which the CAE connects to the Content Server.
Please note that the user must be permitted to use the
|
|
|
The password of the user. |
|
|
Use this property to disable the connection to the Workflow Server, because few content application require access to workflow data. |
Table 3.1. Connection properties
Configuring Cache Sizes
You can configure the size of the Unified API cache and of the disk cache for blobs using the properties defined in the table:
| Property | Description |
|---|---|
|
|
This property indicates the number of bytes used for the main memory cache of the Unified API embedded in the Content Application Engine. For 64 bit JVMs, the actual memory consumption may be up to twice the configured value. For 32 bit JVMs, the byte count is exact. When multiple CAEs run in a single application server, the caches are kept separate and the configured cache sizes add up. |
|
|
This property defines the size of the disk cache for blobs. |
|
|
This property defines the location of the blob cache. Multiple CAEs may share the same directory for the blob cache. Again, the cache sizes add up. Make sure to provide enough disk space for caching. |
Table 3.2. Properties for cache size settings
Purging the Disk Cache after Forced Exits
When an application container is forced to shut down without stopping the web applications first, the CAE might not be able to clear its disk cache in time. This may happen when a Tomcat is shut down, which will invoke a process kill operation at system level, if the Tomcat does not shut down within eight seconds.
In order to avoid a buildup of left over cache files, it makes sense to purge the temporary file directory periodically during a planned downtime or every time at the start of the content application. Make sure not to purge the directory while it is in use by a CAE.
 |  |  |
 |