Reference of application-wide parameters
Parameter | Description | Mandatory | Allowed Values | Default | Comments |
|---|---|---|---|---|---|
| Directory path to the file for repository configuration. For more information see Location of the repository.cfg file . | yes |
|
| starting with version 2.1.0 |
| Name of the config file. For more information see Location of the repository.cfg file . | yes |
|
| starting with version 2.1.0 |
| Enables multitenancy support. For more information see Multitenancy . Note: There exist | no |
|
| starting with version 2.5.0 |
| Description of the running instance. Is displayed in the status webapp. | no |
|
| starting with version 3.4.0 |
| Directory path to the license file For more information see Location of the license file | no |
|
| starting with version 2.5.0 |
| Interval for checking for updates in license file. | no |
|
| starting with version 2.6.0 |
| Defines the endpoint for CMIS-Infos requests urls. Pattern is | no |
|
| starting with version 3.13.3 |
| value for the module field in the protocol | no |
|
| |
| Specifies the factor of the size of the working memory at which a file to be uploaded is written to the temp directory | no | Decimal number between 0 and 1 (e.g |
| starting with version 3.17.0 |
| Log Level for all logging. If log level for package is configured, package configuration will overrule. Recommended for production systems is | no |
|
|
|
| Log level for the package. Recommended for production systems is setting parameter | no |
|
| starting with version 2.1.0 |
| Location of the configuration file for the logging framework. | no | <path> | before tia® Content Server core 3.0:
| starting with version 2.1.0 Recommended configuration for cloud-deployment:
|
| Listener port of the Content Server | yes | <port number> |
| starting with version 2.1.0 |
| Web context of the Content Server | no | <web context> |
| starting with version 2.1.0 |
| Maximum file size in Bytes allowed for upload. | no | <Numeric> |
| starting with version 2.1.0 |
| Maximum size for multipart bodies in Bytes allowed. | no | <Numeric> |
| starting with version 2.1.0 |
| Allow loading of additional jars when using the container deployment, e.g. for custom jdbc driver. | no | <path or jar file> typical values: |
| starting with version 2.7.0
|
| Maximum individual header length. Applicable for CMIS, ILM, and SAPHTTP. Before 2.7.0: This parameter can ONLY be set as Java-startup parameter. Since 2.7.0: The parameter can be set also as environmental variable or in For more information about the variants to apply application-wide parameters, please refer to Application wide settings . | no | <Numeric> | before 2.7.0:
starting with 2.7.0:
|
|
| Key store format. Supported are PKCS12 and JKS supported. PKCS12 is preferred. | no |
|
| |
| Location of the keystore file | no |
|
| |
| Password for the keystore | no |
|
| |
| Alias for the certificate in the pkcs12 store | no |
|
| |
|
| no |
|
| |
| volume counter sender (to VCRS) connection timeout |
|
| 3000 |
|
| enables volume counter sender (to VCRS) |
|
| false |
|
| set how much last days will be sent by volume counter sender to VCRS |
|
| 90 |
|
| volume counter sender (to VCRS) max retries |
|
| 6 |
|
| volume counter sender (to VCRS) proxy password |
|
|
|
|
| volume counter sender (to VCRS) proxy uri. |
|
|
|
|
| volume counter sender (to VCRS) proxy user |
|
|
|
|
| volume counter sender (to VCRS) request timeout |
|
| 3000 |
|
| volume counter sender (to VCRS) response timeout |
|
| 3000 |
|
| volume counter sender (to VCRS) retry interval in ms |
|
| 3000 |
|
| volume counter sender VCRS uri. |
|
|
|
|
| Configuration of tia web application authentication type For more information, please read tia® Status UI Authentication | no |
|
|
|
| Setting the user name for basic authentication. Only available, when | no | <user name> |
|
|
| Setting the password hash for basic authentication. Only available, when For information how to generate a password hash, please refer to Creating a bcrypt-hash value . | no | <password hash> | If parameter is not set, a password is autogenerated every web application start. |
|
| OAuth2 Authentication endpoint URL Only available, when | no | <OAuth2 endpoint URL> |
|
|
| OAuth2 Application Client ID Only available, when | no | <OAuth2 client id> |
|
|
| OAuth2 Redirect URL (URL-encoded). Only available, when | no | <local URL to /info/login-callback> |
|
|
Deployment specific proxy settings
Besides specifying proxy settings for individual services, proxy settings can also be defined for the wholes deployment, either for parts that have no individual setting (e.g. OAuth for CMIS) or to simplify the specification. The proxy definition is done for http and https, the parameters below exist for both. They can be used e.g. -Dhttp.proxyHost=10.16.23.12 -Dhttps.proxyHost=10.22.51.1
Parameter | Description | Example |
|---|---|---|
proxyHost | the hostname of the proxy | 10.11.12.13 |
proxyPort | the port to use on the proxy host | 3254 |
nonProxyHosts | define exempts from the proxy, either hostname or ip, each separated by | | localhost|127.0.0.1 |
proxyUser | Username for basic auth at the proxy | johndoe |
proxyPassword | Password for basic auth at the proxy | johndoespassword |