Configuration parameters
OpenKM is preconfigured with several parameters. However, if you plan to use it in production, you should look at Recommended configuration parameters. To access Configuration parameters, go to Administration > Configuration parameters.
Configuration parameters are shown in a table with three columns:
Property Key Type Value
The property key is the unique identifier for each configuration property.
There are several configuration types:
- String.
- Integer (only numeric values are allowed).
- Boolean (only true or false values are allowed).
- List (each broken line is considered a new list element).
- Text.
- HTML ( HTML tags allowed ).
- File.
To create your parameters, read Creating your own parameters.
Edit a parameter
Section titled “Edit a parameter”- Click the edit icon.
- View and modify the value.
- Click the Edit button to confirm the change.
Delete a parameter
Section titled “Delete a parameter”- Click remove icon
. - In Delete confirmation view, click the Delete button.
Backup configuration parameters
Section titled “Backup configuration parameters”- Click at the top right of the Configuration parameters export icon
. - The browser will download an SQL file with the configuration.
New configuration parameter
Section titled “New configuration parameter”- Go to the top-right corner to see the action buttons in the table.
- Click the New configuration parameter button.
Check Configuration
Section titled “Check Configuration”This action will check whether some conflicting parameters are correctly configured (pdf2swf, convert tool, OCR engine, or LibreOffice path).
- Click at the top right on the Check icon
. - It will show the Configuration check view. If some parameters are misconfigured or wrong, they will be shown in red.
Multitenant configuration
Section titled “Multitenant configuration”- Click on the top menu
Configuration button and then click on the submenu Tenant Configuration link. - In tenant configuration, you can create your configuration parameters. These will have preference over the default values. For example, have another application.url value for each tenant.