Parameter | Description | mandatory | allowed values | default value | 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 Multi-Tenant-Supportmultitenancy support. For more information see Multi-Tenant-Support (tC) Multitenancy .
| 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 | ||||||
| enable the headers like x-frame-options, X-Content-Type-Options and moreThis parameter enables Content-Security-Policy Headers in Web environments. Enabling this increases the security level, while it is possible that functionality not prepared for this may fail. For more information about Content Security Policy, refer to external link: https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP . | no |
|
| starting with version 2.6.0 | |||||
| Log level for the package. | no |
| starting with version 2.1.0 | ||||||
| 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 | |||||
| Location of the configuration file for the logging framework. | no | <path> | before tia Core tia® Content Server core 3.0:
| starting with version 2.1.0 Recommended configuration for cloud-deployment:
| |||||
| Allow loading of additional jars when using the container deployment, e.g. for custom jdbc driver. | no | <path or jar file> typicall typical values: | starting with version 2.7.0 |
| Endpoint were service is reachable. Applicable for CMIS, ILM, and SAPHTTP. | yes | <endpoint> | for CMIS: / for ILM: /ilm/ for SAPHTTP: /contentserver/ | |
| 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> |
Page Comparison
General
Content
Integrations