General configuration information
FirstSpirit is configured via configuration files located in the installation directory of the FirstSpirit Server (see Configuration files (FirstSpirit Server)).
This chapter describes the structure of the FirstSpirit configuration files and the respective parameters.
There are various possibilities for editing the configuration files:
- Via FirstSpirit ServerManager: The FirstSpirit ServerManager facilitates editing of the configuration settings for database connection configuration (fs-database.conf) and login configuration (fs-jaas.conf). All changes to these two configuration files carried out via the ServerManager are automatically stored in the respective configuration file and updated on the server.
- Via FirstSpirit ServerMonitoring: Further configuration settings can be carried out via FirstSpirit ServerMonitoring or the JMX Console. Analogue to the ServerManager, all the changes are automatically rewritten and loaded into the respective configuration file.
- Changing the configuration files directly via the file system: Direct changes to the configuration via the configuration files are only possible if access is available via the file system. If access is possible, never execute changes during operation. It is recommended to always change the configuration files via the administration environments provided by FirstSpirit (see the respective Chapters for further details). A server restart might be necessary to implement the changes (see FirstSpirit Server (fs-server.conf) ff.).
- Via JMX Console: The configuration settings from the configuration files can be partially displayed and changed via the JMX Console (see CacheSizeManager for an example).
The following Chapters refer to the respective configuration possibility within the ServerManager, the JMX Console or ServerMonitoring.
The configuration examples in the following Chapters contain expressions, such as
Key _1 = ${Key_2}A placeholder which can accept the value of another parameter is defined via the expression ${ }. In the example, the value Key_2 is allocated to the parameter Key _1 and possibly complemented by additional specifications. Therefore, it is, for example, possible to compose longer paths from individual, previously defined values (see the example under Area: Communication).
 |
When copying configuration examples from the PDF manuals it is necessary to ensure that all line breaks are correctly copied. If the characters are, for example, incorrectly coded on copying, this can result in problems with the configuration. |
|
In general, additions should only be made to the parameters in the actual configuration files that are to be modified. Simply copying configuration examples from the manuals can result in the default values being overwritten, which is not always desirable. |