The import of metadata and the installation procedure described in the previous chapter is used to generate configuration files. These are stored as XML files in the directory
"[installation directory of rendering services] / conf / esmain".
It may be necessary to edit these files manually (e.g. when a domain changes) or a Web server configuration requires special adaptations.
For each application, even for the rendering service itself, a configuration file must exist. Furthermore, there is a file "ccapp-registry.properties.xml" where configuration files are referenced. Here is an example of a file:
The values of "application files" are the configuration files "homeApplication.properties.xml" for the rendering service and "app-repository.properties.xml" for a repository as comma separated values.
Configuration of the rendering services
The configuration file "homeApplication.properties.xml" consists primarily of values for the authentication of a rendering service with an edu-sharing repository. An example might look like this:
Explanation of keys / values:
appid: must match the value in the configuration file of the rendering service in the repository
appcaption: freely selectable
host: IP of the server on which the rendering service has been installed
port: port via which the service rendering can be reached
public_key: Public SSL key
private_key: SSL Private Key
homerepid: application ID of the home repository
In the file
"/config/system.conf.php" important system constants are defined. Under certain circumstances, these must be edited if changes have been made on the server or if the rendering service is run behind a proxy.
$MC_URL: URL of the Rendering Service
$MC_DOCROOT: Path of the document root, e.g. "/ var / www".
$CC_RENDER_PATH. Directory in which the objects are cached, e.g. "/ var / cache / esrender /"
Should changes in the database configuration be necessary, for example, because the database is moved to another server or another user is to be used, the necessary adjustments can be made in "/conf/db.conf.php".
If the rendering service is operated behind a proxy server, some constants must be defined in "/conf/proxy.conf.php". This is necessary in order to enable the reachability of the Web services:
USE_HTTP_PROXY: "true" or "false"
HTTP_PROXY_HOST: Domain name of the proxy
HTTP_PROXY_PORT: Proxy Port
HTTP_PROXY_USER: username (optional)
HTTP_PROXY_PASS: password (optional)
HTTP_PROXY_SNI: Sets SOAP Parameters "SNI_enabled" to "TRUE"
Configuration of the repository
In addition to the configuration file for the rendering service itself at least one configuration file for the repository housing the content to be rendered must be present. In this example it is the file "app-repository.properties.xml". The name of this file must be composed as follows: "app- [appid] .properties.xml". The appid is defined within the configuration file itself and must be the same appid as the one of the repository the rendering service was registered with. A sample configuration for a repository might look like this:
Explination of keys / values:
appid: must match appid of the repository in its own homeApplication.properties.xml. Is crucial for the naming of this configuration file (see above).
appcaption: freely selectable
trusted client: "true"
host: IP of the server on which the repository is installed
port: port through which the repository can be reached
authenticationwebservice: address where the authentication service of the repository can be found
authenticationwebservice_wsdl: address where the WSDL of the authentication service can be found
usagewebservice: address where the web service of the usage service of the repository can be reached
usagewebservice_wsdl: address of the WSDL file of the usage service
alfresco_webservice_url: Address of the Alfresco Web Services
renderinfoservice_wsdl: address of the WSDL file of the rendering service
domain: domain name of the repository