JATOS Configuration
JATOS' properties can be configured in three different ways:
- via a config file (named jatos.conf or production.conf)
- via command-line arguments
- via environment variables (possible for only a few of the properties)
The config file is located in the JATOS folder under ./conf and is named jatos.conf for versions >= 3.8.3 and production.conf for versions < 3.8.3. It uses the HOCON format. Remember to always restart JATOS after making any changes to a config file.
Command-line argument names are usually the same as the names in the config file except that they are prefixed with -D
(except JVM arguments that have a -J
), e.g. jatos.urlBasePath
and -Djatos.urlBasePath
.
Command-line arguments can be appended to JATOS' loader.sh start
command. E.g., here is the command with the two arguments -Djatos.urlBasePath
and -Djatos.tmpPath
:
./loader.sh start -Djatos.urlBasePath="/mybasepath/" -Djatos.tmpPath="/my/tmp/dir"
JVM arguments
JVM arguments (arguments for the Java Virtual Machine) are special since they are not directly intended for JATOS but for the JVM running JATOS. They can only be specified via command line arguments and have to be prefixed with -J
.
One commonly used JVM argument is -Xmx
. It limits JATOS's memory usage (JVM's maximum heap memory usage to be precise). It has to be written as -J-Xmx
, e.g. to allow 4GB memory -J-Xmx4G
.
HTTP config
Address and port
By default JATOS binds to all locally available IP addresses including 127.0.0.1 on port 9000. Usually JATOS is installed together with a reverse proxy (e.g Nginx or Apache) but if you don't want to use a proxy, you have to set up the hostname or IP address and the port in one of the ways.
Via config file properties
- For v3.8.1 and lower)
play.server.http.address
andplay.server.http.port
- For v3.8.2 and higher)
jatos.http.address
andjatos.http.port
Example:
jatos.http.address = 1.2.3.4
jatos.http.port = 80- For v3.8.1 and lower)
Via command-line arguments
- For v3.8.1 and lower)
-Dplay.server.http.address
and-Dplay.server.http.port
- For v3.8.2 and higher)
-Djatos.http.address
and-Djatos.http.port
Example:
-Djatos.http.address=1.2.3.4 -Djatos.http.port=80
- For v3.8.1 and lower)
Server idle timeout
The idle timeout for an open connection after which it will be closed. Set to null
or infinite
to disable the timeout, but notice that this is not encouraged since timeouts are important mechanisms to protect your servers from malicious attacks or programming mistakes. Default is 75 seconds.
Via config file property
play.server.http.idleTimeout
Example:
play.server.http.idleTimeout = 100s
Via command-line argument
-Dplay.server.http.idleTimeout
Example:
-Dplay.server.http.idleTimeout=100s
Request timeout
How long can a request take until it times out. Set to null
or infinite
to disable the timeout. Default is infinite
.
Via config file property
play.server.akka.requestTimeout
Example:
play.server.akka.requestTimeout = 100s
Via command-line argument
-Dplay.server.akka.requestTimeout
Example:
-Dplay.server.akka.requestTimeout=100s
URL base path
JATOS can be configured to use an base path. E.g we have the host www.example.org and let JATOS run under mybasepath so that all URLs start with www.example.org/mybasepath/.
The path always has to start and end with a "/". And keep in mind that if you add a base path to JATOS' URL you have to adjust all absolute paths to the study assets (in HTML and JavaScript files) too - or use relative paths (which is recommended anyway).
Via config file properties
- For v3.8.1 and lower)
play.http.context
- For v3.8.2 and higher)
jatos.urlBasePath
Example:
jatos.urlBasePath = "/mybasepath/"
- For v3.8.1 and lower)
Via command-line arguments
- For v3.8.1 and lower)
-Dplay.http.context
- For v3.8.2 and higher)
-Djatos.urlBasePath
-Djatos.urlBasePath="/mybasepath/"
- For v3.8.1 and lower)
Via environment variable
JATOS_URL_BASE_PATH
JATOS_URL_BASE_PATH="/mybasepath/"
X-Frame-Options header
The X-Frame-Options header can be used to allow or disallow embedding a JATOS study in an iframe (or similar embedding techniques). Possible values are DENY
(completely disallow iframes), SAMEORIGIN
(embedding page has the same origin as the iframe), or null
(allow iframes everywhere). By default it set to SAMEORIGIN
.
Via config file property
play.filters.headers.frameOptions
Example:
play.filters.headers.frameOptions = null
Via command-line argument
-Dplay.filters.headers.frameOptions
Example:
-Dplay.filters.headers.frameOptions=null
Trusted certificates
It's possible to add multiple certificates, e.g. for for encrypted LDAP. type can be PKCS12
, JKS
or PEM
.
Only via config file property
play.ws.ssl.trustManager.stores
play.ws.ssl.trustManager.stores = [ { type = "PEM", path = "conf/certs/ca.pem" } ]
Study assets root path
The study assets root folder is the location where all study's HTML, JavaScript files etc. are stored. By default it is located in the JATOS folder and has the default name study_assets_root, except when JATOS runs in a Docker container, where it is under /opt/jatos_data/study_assets_root"
Via config file property
jatos.studyAssetsRootPath
jatos.studyAssetsRootPath = "/path/to/my/assets/root/folder"
Via command-line argument
-Djatos.studyAssetsRootPath
-Djatos.studyAssetsRootPath="/path/to/my/assets/root/folder"
Via environment variable
JATOS_STUDY_ASSETS_ROOT_PATH
JATOS_STUDY_ASSETS_ROOT_PATH="/path/to/my/assets/root/folder"
Temporary directory path
(Only in version >= 3.8.3)
JATOS uses a directory to temporarily store files, e.g. during study import. By default the system's temporary directory is used (on Linux/Unix /tmp or on Windows c:\temp), except when JATOS runs in a Docker container, when it is under /opt/jatos_data/tmp.
Via config file property
jatos.tmpPath
jatos.tmpPath = "/my/tmp/dir"
Via command-line argument
-Djatos.tmpPath
-Djatos.tmpPath="/my/tmp/dir"
Via environment variable
JATOS_TMP_PATH
JATOS_TMP_PATH="/my/tmp/dir"
Application logs
The application log records messages from the JATOS application. The application logs use a daily log rotation with a history of maximal 30 days.
Don't confuse the application logs with the study logs.
Application logs path
The application logs are by default in the JATOS folder under ./logs.
Via config file property
jatos.logs.path
jatos.logs.path = "/my/dir/logs"
Via command-line argument
-Djatos.logs.path
-Djatos.logs.path="/my/dir/logs"
Via environment variable
JATOS_LOGS_PATH
JATOS_LOGS_PATH="/my/dir/logs"
Application logs filename
By default the logs filename is application (without suffix).
Via config file property
jatos.logs.filename
jatos.logs.filename = "myFilename"
Via command-line argument
-Djatos.logs.filename
-Djatos.logs.filename="myFilename"
Via environment variable
JATOS_LOGS_FILENAME
JATOS_LOGS_FILENAME="myFilename"
Application logs appender
The logs appender can be either ASYNCSTDOUT
or ASYNCFILE
. Default is ASYNCFILE
. If you don't want to record the logs to a file but to stdout, change the value to ASYNCSTDOUT
.
Via config file property
jatos.logs.appender
jatos.logs.appender = ASYNCSTDOUT
Via command-line argument
-Djatos.logs.appender
-Djatos.logs.appender=ASYNCSTDOUT
Via environment variable
JATOS_LOGS_APPENDER
JATOS_LOGS_APPENDER=ASYNCSTDOUT
Study logs
Every study stored in JATOS has its own study log (more info). Among other things, it calculates hashes of result data, which can be CPU-intensive, and on smaller machines it can be better to disable it.
Don't confuse the study logs with the application logs. .
Enable/disable study logging
By default study logging is enabled.
Via config file property
jatos.studyLogs.enabled
jatos.studyLogs.enabled = false
Via command-line argument
-Djatos.studyLogs.enabled
-Djatos.studyLogs.enabled=false
Path to study logs
By default the study logs are stored in the JATOS folder under ./study_logs.
Via config file property
jatos.studyLogs.path
jatos.studyLogs.path = "/path/to/my/jatos_study_logs"
Via command-line argument
-Djatos.studyLogs.path
-Djatos.studyLogs.path="/path/to/my/jatos_study_logs"
Via environment variable
JATOS_STUDY_LOGS_PATH
JATOS_STUDY_LOGS_PATH="/path/to/my/jatos_study_logs"
Study members
Allow all users that exist on a JATOS to be added at once as members of a study. Can be useful in small setups, e.g. for a lab installation. Default is false
.
Via config file property
jatos.studyMembers.allowAddAllUsers
jatos.studyMembers.allowAddAllUsers = true
Via command-line argument
-Djatos.studyMembers.allowAddAllUsers
-Djatos.studyMembers.allowAddAllUsers=true
Results pagination
Maximal number of results to be fetched from the DB at once. Default is 10.
Via config file property
jatos.maxResultsDbQuerySize
jatos.maxResultsDbQuerySize = 5
Via command-line argument
-Djatos.maxResultsDbQuerySize
-Djatos.maxResultsDbQuerySize=5
Result data
Maximum size of the result data of one component run. Default is 5MB.
Via config file property
jatos.resultData.maxSize
jatos.resultData.maxSize = 10MB
Via command-line argument
-Djatos.resultData.maxSize
-Djatos.resultData.maxSize=10MB
Result file uploading
During study runs it is possible to upload files to JATOS usually with results. This is an alternative to result data that are stored in the database. It is also possible to download previously uploaded files during a study run.
Enable/disable result file uploading
Default is true
(enabled).
Via config file property
jatos.resultUploads.enabled
jatos.resultUploads.enabled = false
Via command-line argument
-Djatos.resultUploads.enabled
-Djatos.resultUploads.enabled=false
Path to result files
The path where JATOS stores the uploaded result files from study runs. By default they are stored in the JATOS folder under ./result_uploads.
Via config file property
jatos.resultUploads.path
jatos.resultUploads.path = "/path/to/my/jatos_result_uploads"
Via command-line argument
-Djatos.resultUploads.path
-Djatos.resultUploads.path="/path/to/my/jatos_result_uploads"
Via environment variable
JATOS_RESULT_UPLOADS_PATH
JATOS_RESULT_UPLOADS_PATH="/path/to/my/jatos_result_uploads"
Max file size
Specifies the maximum file size per uploaded file. Default is 30MB.
Via config file property
jatos.resultUploads.maxFileSize
jatos.resultUploads.maxFileSize = 100MB
Via command-line argument
-Djatos.resultUploads.maxFileSize
-Djatos.resultUploads.maxFileSize=100MB
Via environment variable
JATOS_RESULT_UPLOADS_MAX_FILE_SIZE
JATOS_RESULT_UPLOADS_MAX_FILE_SIZE=100MB
All files size limit per study run
Specifies the maximum file size of all files together that are uploaded during one study run. Default is 50MB.
Via config file property
jatos.resultUploads.limitPerStudyRun
jatos.resultUploads.limitPerStudyRun = 100MB
Via command-line argument
-Djatos.resultUploads.limitPerStudyRun
-Djatos.resultUploads.limitPerStudyRun=100MB
Via environment variable
JATOS_RESULT_UPLOADS_LIMIT_PER_STUDY_RUN
JATOS_RESULT_UPLOADS_LIMIT_PER_STUDY_RUN=100MB
Superuser
The Superuser role can be granted to a user and it allows this user to access ANY study on this JATOS as if they were a member of this study. This includes accessing the result data and even deleting the study itself. This can be useful in small setups, e.g. for a lab installation or if there is a dedicated person responsible for running online studies. Default is false
.
If set to true
an user with the Admin role can grant the role Superuser to any user.
Via config file property
jatos.user.role.allowSuperuser
jatos.user.role.allowSuperuser = true
Via command-line argument
-Djatos.user.role.allowSuperuser
-Djatos.user.role.allowSuperuser=true
LDAP authentication
At the moment LDAP users still have to be added manually in JATOS' User manager (with the switch LDAP turned on). Only the authentication is done via LDAP.
If your LDAP server uses encryption, you have to add your certificate to JATOS' trusted certificates defined with play.ws.ssl.trustManager.stores
(only possible in a config file). E.g., if your certificate's location is in /jatos/conf/certs/ca.pem
, then use the following to add it:
play.ws.ssl.trustManager.stores = [
{ type = "PEM", path = "/jatos/conf/certs/ca.pem" }
{ path: ${java.home}/lib/security/cacerts, password = "changeit" }
]
The first line adds your certificate (type can be PKCS12
, JKS
or PEM
). The second line adds Java's default key store. Its default password is "changeit" (don't change it).
LDAP URL
Specifies URL of the LDAP server. Not set or an empty string disables authentication via LDAP. Default is empty (""
).
Via config file property
jatos.user.authentication.ldap.url
jatos.user.authentication.ldap.url = "ldap://my.ldap.org:389"
Via command-line argument
-Djatos.user.authentication.ldap.url
-Djatos.user.authentication.ldap.url="ldap://my.ldap.org:389"
LDAP base DN
Specifies the base DN (distinguished name). It can be one DN with a single string (e.g. "ou=students,dc=example,dc=com"
) or a list of DNs in squared brackets (e.g. ["ou=students,dc=example,dc=com", "ou=scientists,dc=example,dc=com"]
). Not set or an empty string disables authentication via LDAP. Default is empty (""
).
Via config file property
jatos.user.authentication.ldap.basedn
jatos.user.authentication.ldap.basedn = "dc=example,dc=com"
Via command-line argument
-Djatos.user.authentication.ldap.basedn
-Djatos.user.authentication.ldap.basedn="dc=example,dc=com"
LDAP admin DN and password
Specifies an DN (distinguished name) and password of an (optional) admin user that has the right to search for other users. Some LDAP servers need this, if it is impossible to bind directly to an uid. Not set or an empty string means no admin user is needed. Default is empty (""
).
Via config file properties
jatos.user.authentication.ldap.admin.dn
andjatos.user.authentication.ldap.admin.password
jatos.user.authentication.ldap.admin.dn = "cn=read-only-admin,dc=example,dc=com"
jatos.user.authentication.ldap.admin.password = "mypassword"Via command-line arguments
-Djatos.user.authentication.ldap.admin.dn
and-Djatos.user.authentication.ldap.admin.password
-Djatos.user.authentication.ldap.admin.dn="cn=read-only-admin,dc=example,dc=com"
-Djatos.user.authentication.ldap.admin.password="mypassword"
LDAP timeout
Time in milliseconds JATOS waits for a response from your LDAP server. Default is 5000 ms.
Via config file property
jatos.user.authentication.ldap.timeout
jatos.user.authentication.ldap.timeout = 10000
Via command-line argument
-Djatos.user.authentication.ldap.timeout
-Djatos.user.authentication.ldap.timeout=10000
Google Sign-In
JATOS users can be authenticated by Google Sign-in. Not set or an empty string disables authentication via Google Sign-In. Default is empty (""
).
Specifies the Google API client ID.
Via config file property
jatos.user.authentication.oauth.googleClientId
jatos.user.authentication.oauth.googleClientId = "1234567890-abc123abc123.apps.googleusercontent.com"
Via command-line argument
-Djatos.user.authentication.oauth.googleClientId
-Djatos.user.authentication.oauth.googleClientId="1234567890-abc123abc123.apps.googleusercontent.com"
OpenID Connect (OIDC) authentication
(Only in version >= 3.8.5)
JATOS users can be authenticated by OIDC sign-in.
OIDC discovery URL
Specifies the OIDC provider's discovery URL. It usually ends in .well-known/openid-configuration.
Via config file property
jatos.user.authentication.oidc.discoveryUrl
jatos.user.authentication.oidc.discoveryUrl = "http://myOidcProvider/.well-known/openid-configuration"
Via command-line argument
-Djatos.user.authentication.oidc.discoveryUrl
-Djatos.user.authentication.oidc.discoveryUrl="http://myOidcProvider/.well-known/openid-configuration"
OIDC client ID
Specifies the OIDC client ID. Not set or an empty string disables authentication via OIDC Sign-In. Default is empty (""
).
Via config file property
jatos.user.authentication.oidc.clientId
jatos.user.authentication.oidc.clientId = "myClientId"
Via command-line argument
-Djatos.user.authentication.oidc.clientId
-Djatos.user.authentication.oidc.clientId="myClientId"
OIDC client secret
Specifies the OIDC client secret. This is optional and can be left empty (""
).
Via config file property
jatos.user.authentication.oidc.clientSecret
jatos.user.authentication.oidc.clientSecret = "myClientSecret"
Via command-line argument
-Djatos.user.authentication.oidc.clientSecret
-Djatos.user.authentication.oidc.clientSecret="myClientSecret"
OIDC ID token signing algorithm
Specifies the OIDC ID token signing algorithm. Default is RS256
.
Via config file property
jatos.user.authentication.oidc.idTokenSigningAlgorithm
jatos.user.authentication.oidc.idTokenSigningAlgorithm = "ES512"
Via command-line argument
-Djatos.user.authentication.oidc.idTokenSigningAlgorithm
-Djatos.user.authentication.oidc.idTokenSigningAlgorithm="ES512"
OIDC sign-in button text
Specifies the text of the OIDC sign-in button on the login page. Default is Sign in with OIDC
.
Via config file property
jatos.user.authentication.oidc.signInButtonText
jatos.user.authentication.oidc.signInButtonText = "Sign in with ABC university"
Via command-line argument
-Djatos.user.authentication.oidc.signInButtonText
-Djatos.user.authentication.oidc.signInButtonText="Sign in with ABC university"
OIDC sign-in button logo
Specifies the URL of a logo that can be used instead of the standard OIDC logo, e.g. a university logo. Default is the OIDC logo.
Via config file property
jatos.user.authentication.oidc.signInButtonLogoUrl
jatos.user.authentication.oidc.signInButtonLogoUrl = "http://somedomain/logo.svg"
Via command-line argument
-Djatos.user.authentication.oidc.signInButtonLogoUrl
-Djatos.user.authentication.oidc.signInButtonLogoUrl="http://somedomain/logo.svg"
OIDC success feedback
Specifies the text of a message that is shown after a successful sign-in. If left empty (""
) no message is shown. Default is ""
.
Via config file property
jatos.user.authentication.oidc.successFeedback
jatos.user.authentication.oidc.successFeedback = "You successfully signed in with ABC university"
Via command-line argument
-Djatos.user.authentication.oidc.successFeedback
-Djatos.user.authentication.oidc.successFeedback="You successfully signed in with ABC university"
ORCID (orcid.org) authentication
(Only in version >= 3.8.5)
JATOS users can be authenticated by ORCID sign-in. Internally ORCID uses OpenId Connect.
ORCID client ID
Specifies your ORCID client ID.
Via config file property
jatos.user.authentication.orcid.clientId
jatos.user.authentication.orcid.clientId = "APP-ABCDEFGHIJKLMNOP"
Via command-line argument
-Djatos.user.authentication.orcid.clientId
-Djatos.user.authentication.orcid.clientId="APP-ABCDEFGHIJKLMNOP"
ORCID client secret
Specifies your ORCID client secret.
Via config file property
jatos.user.authentication.orcid.clientSecret
jatos.user.authentication.orcid.clientSecret = "1234abcd-12ab-12ab-12ab-123456abcdef"
Via command-line argument
-Djatos.user.authentication.orcid.clientSecret
-Djatos.user.authentication.orcid.clientSecret="1234abcd-12ab-12ab-12ab-123456abcdef"
User password restrictions
By default JATOS' keeps it simple and relies on the users to choose save passwords: it just enforces a length of at least 7 characters. But this can be changed with the following two properties.
Password length
Via config file property
jatos.user.password.length
jatos.user.password.length = 8
Via command-line argument
-Djatos.user.password.length
-Djatos.user.password.length=8
Password strength
Can be one of the following. Default is 0.
- 0 - No restrictions on characters
- 1 - At least one Latin letter and one number
- 2 - At least one Latin letter, one number and one special character (out of
#?!@$%^&*-
) - 3 - At least one uppercase Latin letter, one lowercase Latin letter, one number and one special character (out of
#?!@$%^&*-
)
Via config file property
jatos.user.password.strength
jatos.user.password.strength = 3
Via command-line argument
-Djatos.user.password.strength
-Djatos.user.password.strength=3
Database
See JATOS with MySQL.
Old style database properties beginning with db.default are deprecated and the new properties beginning with jatos.db should be used instead.
Database URL
Via config file property
jatos.db.url
jatos.db.url = "jdbc:mysql://127.0.0.1:3306/jatos?characterEncoding=UTF-8&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC"
Via command-line argument
-Djatos.db.url
-Djatos.db.url="jdbc:mysql://127.0.0.1:3306/jatos?characterEncoding=UTF-8&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC"
Via environment variable
JATOS_DB_URL
JATOS_DB_URL="jdbc:mysql://127.0.0.1:3306/jatos?characterEncoding=UTF-8&useJDBCCompliantTimezoneShift=true&useLegacyDatetimeCode=false&serverTimezone=UTC"
Username and password
Via config file properties
jatos.db.username
andjatos.db.password
jatos.db.username = "myusername"
jatos.db.password = "mypassword"Via command-line argument
-Djatos.db.username
and-Djatos.db.password
-Djatos.db.username = "myusername" -Djatos.db.password = "mypassword"
Via environment variable
JATOS_DB_USERNAME
andJATOS_DB_PASSWORD
JATOS_DB_USERNAME="myusername"
JATOS_DB_PASSWORD="mypassword"
Database driver
For modern MySQL or MariaDB databases this property needs to be set to com.mysql.cj.jdbc.Driver
.
Via config file property
jatos.db.driver
jatos.db.driver = "com.mysql.cj.jdbc.Driver"
Via command-line argument
-Djatos.db.driver
-Djatos.db.driver="com.mysql.cj.jdbc.Driver"
Via environment variable
JATOS_DB_DRIVER
JATOS_DB_DRIVER="com.mysql.cj.jdbc.Driver"
Multi-node mode
If you intend to run JATOS on multiple machines in parallel in a cluster you have to set this property to true
. Default is false
.
Via config file property
jatos.multiNode
jatos.multiNode = true
Via command-line argument
-Djatos.multiNode
-Djatos.multiNode = true
User session configuration
Timeout
User session timeout in minutes. Default is 1440 minutes (1 day).
Via config file property
jatos.userSession.timeout
jatos.userSession.timeout = 180
Via command-line argument
-Djatos.userSession.timeout
-Djatos.userSession.timeout = 180
Inactivity timeout
User session timeout after inactivity in minutes. Default is 60 minutes.
Via config file property
jatos.userSession.inactivity
jatos.userSession.inactivity = 120
Via command-line argument
-Djatos.userSession.inactivity
-Djatos.userSession.inactivity=120
Secure session
This property can be used to restrict user access to HTTPS. Default is false
.
Via config file property
play.http.session.secure
play.http.session.secure = true
Via command-line argument
-Dplay.http.session.secure
-Dplay.http.session.secure=true
ID cookies
Secure ID cookies
This property can be used to restrict participant access to HTTPS. Sets the ID cookie's secure attribute. Default is false
.
Via config file property
jatos.idCookies.secure
jatos.idCookies.secure = true
Via command-line argument
-Djatos.idCookies.secure
-Djatos.idCookies.secure=true
SameSite attribute
Defines the IDCookies' SameSite attribute. Possible values are None
, Lax
, or Strict
. Setting to Strict
makes the usage of external recruiting tools, like MTurk, impossible. Default is None
.
Via config file property
jatos.idCookies.sameSite
jatos.idCookies.sameSite = "Lax"
Via command-line argument
-Djatos.idCookies.sameSite
-Djatos.idCookies.sameSite = "Lax"
PID file location
Defines the location of the PID file in the file system.
Via config file property
play.pidfile.path
play.pidfile.path = "/var/run/jatos.pid"
Via command-line argument
-Dplay.pidfile.path
-Dplay.pidfile.path = "/var/run/jatos.pid"
Home page
Welcome message
Specifies a URL that can be used by JATOS to fetch some static HTML. This HTML will then be shown on the home page instead of the default welcome message (more info). If left empty (""
) the default welcome message is shown. Default is empty.
Via config file property
jatos.brandingUrl
jatos.brandingUrl = "https://mydomain.com/foobar-university-welcome-page.html"
Via command-line argument
-Djatos.brandingUrl
-Djatos.brandingUrl = "https://mydomain.com/foobar-university-welcome-page.html"
'Terms of use' info box
Specifies a URL link to the 'terms of use' that will be shown in an info box on the home page. If left empty (""
) the info box is not shown. Default is empty.
Via config file property
jatos.termsOfUseUrl
jatos.termsOfUseUrl = "https://mydomain.com/my-terms-of-use.html"
Via command-line argument
-Djatos.termsOfUseUrl
-Djatos.termsOfUseUrl = "https://mydomain.com/my-terms-of-use.html"
Study manager page
Enable/disable some columns in the study manager table. Sometimes the calculation of those columns takes too much time due to a slow database or file system.
Via config file properties
jatos.studyAdmin.showStudyAssetsSize
,jatos.studyAdmin.showResultDataSize
, andjatos.studyAdmin.showResultFileSize
jatos.studyAdmin.showStudyAssetsSize = false # Default is true
jatos.studyAdmin.showResultDataSize = true # Default is false
jatos.studyAdmin.showResultFileSize = true # Default is falseVia command-line arguments
-Djatos.studyAdmin.showStudyAssetsSize
,-Djatos.studyAdmin.showResultDataSize
, and-Djatos.studyAdmin.showResultFileSize
-Djatos.studyAdmin.showStudyAssetsSize = false # Default is true
-Djatos.studyAdmin.showResultDataSize = true # Default is false
-Djatos.studyAdmin.showResultFileSize = true # Default is false
JATOS API
Enable/disable the JATOS API. By default it is enabled (true
).
Via config file property
jatos.api.allowed
jatos.api.allowed = false
Via command-line argument
-Djatos.api.allowed
-Djatos.api.allowed = false