AliasSubInstanceConfiguration
This page provides generated reference documentation for the AliasSubInstanceConfiguration data model.
InstanceConfiguration als AliasConfigSub
Overview
| Property | Summary |
|---|---|
| antiBruteforceLoginModuleActive | Actives the anti bruteforce module |
| apiGatewayToken | Specifies the bearer token used to authenticate requests to the api gateway. If empty, no authentication will be performed. |
| automaticUnblockingActive | Determines, if the automatic unblocking is active. If set, blocked users get unblocked after an interval set by automaticUnblockingIntervall. |
| automaticUnblockingIntervall | Sets the time interval after which blocked users get unblocked |
| calendarAlias | Sets the alias on which the calendar should operate. This can be either a database alias or a groupware alias like ExchangeWS. |
| calendarAliasTasks | Sets the alias for the handling of tasks, if those should be handled differently. Typically this will be set to the ADITO system db alias, to handle… |
| calendarCachedRequestInfinityLimitation | Defines a limitation for the search period for cached calender requests when a request against infinity is carried out. |
| calendarCachedRequestLifetime | The maximum time that a request is cached without being requested again by the client. The default is 5 minutes. |
| calendarCachedRequestLimit | Defines the maximum number of requests that the cache can temporarily store. |
| calendarCacheUseOptimizedFullUpdates | Flag that allows the use of the optimized full updates in the CalenderCache. |
| calendarCachingAlias | If calendar caching is used, this property defines the database alias, which is used to cache calendar entries. Typically the ADITO system database alias is… |
| calendarCachingAlwaysUseOwnerCredentials | Always uses credentials of owner for filling cache, even if access is by another user |
| calendarCachingBlacklistEnabled | Activates the calendar caching blacklist. This blacklist contains calendar entries, which provoked an error and are placed on this blacklist to be prevented… |
| calendarCachingFullUpdaterMaxChunkSize | Specifies the maximum amount of requests for a single synchronisation performed by the full updater of the calender cache. Default is 50. |
| calendarCachingFullUpdaterMaxSyncYearsForInfinity | Defines a limit in years for the maximum search period of a request that specifies infinity as start or end time. Default is 0. |
| calendarCachingFullUpdaterSyncPeriodLimit | Defines the limit for the overall time period of a single synchronisation performed by the full updater of the calender cache. |
| calendarCachingMaxPendingRequests | Number of new requests (not already stored) the cache can buffer, before sending them to the actual calender in one request if possible. Default are 10… |
| calendarCachingPendingRequestsExecutionInterval | Interval in which all buffered requests are passed on to the calendar. Default is 1 second. |
| calendarCachingPreload | Enables preloading of the cache at server start |
| calendarCachingUpdateRequestInterval | Interval at which full updates are performed for active cached requests. The default is 30 seconds. |
| calendarCachingUseLegacyCache | If enabled, the server uses the old cache implementation from ADITO 2020 and earlier. |
| calendarEnabled | Enables the calendar module |
| calendarShowErrorOnGetEntries | Previously: -Dadito.calendar.updater.strict=true/false |
| calendarSubscriptionMaxSearchPeriod | Maximum search period of delta queries and Subscriptions in Days. Default is 56 days. |
| calendarSubscriptionsAlwaysUseDelta | Flag which forces the cache to only use delta requests (polling) as subscriptions for calendars, even if it supports other methods. Default is false. |
| calendarSubscriptionsCheckerInterval | Interval at which the cache checks for changes in the subscriptions. Default is 15 seconds |
| calendarSubscriptionsDeltaMaxInterval | Maximum interval to which the execution of the delta queries of a delta subscription (polling) can be increased (throttling) in the event of longer inactivity… |
| calendarSubscriptionsDeltaMinInterval | Smallest interval in which delta queries of an active delta subscription (polling) can be carried out. Default is 3 minutes. |
| calendarSubscriptionsEnabled | When active, the elements of the cache are updated for a limited time via continuous updates. |
| calendarSubscriptionsInitialDuration | The length of time a subscription for a cached request runs when the request is first executed (stored in the cache). Default is 10 minutes. |
| calendarSubscriptionsUpdateDuration | The duration by which a subscription for a cached request is extended if the request is executed again by the client and the remaining duration of the… |
| calendarSyncBlacklistEnabled | Enables the calendar sync blacklist. In this blacklist are all calendar entries, that caused an error on read. These entries wont be loaded again. |
| calendarSyncEnabled | This setting enables or disables calendar synchronization. |
| calendarSyncInterval | Specifies the interval in which the ADITO calendar should be synchronized with the calendar backend. |
| calendarSyncLimit | Time period, starting from the current date into the future, in which the calendar entries are synchronized. If the value is <= 0, the limit is removed and all… |
| calendarSyncRateLimitHandlingEnabled | Whether rate limit handling should be enabled for the calendar sync. |
| calendarSyncScope | Here you can set which calendar items are synchronized. |
| calendarSyncTimespan | Time period, starting from the current date into the past, in which the calendar entries are synchronized. |
| calendarSyncUserEnabledDefault | If the user is not already set to synchronize, this value is used by default. |
| calendarTimeout | Sets the time interval after which a timeout occurs |
| ckeditorConfig | Specifies the config of the CKEditor |
| clientBackground | Background image, specified as an image file. The content is placed as base64-encoded value in the configuration. |
| clientBackgroundFile | Background image, specified by a path to a file on the servers side. |
| clientCustomLogoutThemeEnabled | Enables the clientTheme at the logout screen |
| clientDarkTheme | The name of the dark color theme that should be used. The custom user theme for bright and dark variations are seperate and can be individually selected in the… |
| clientIgnoreWebsocketPushMode | When this property is enabled, the system does not verify whether the client successfully established a WebSocket connection. As a result, the client may fall… |
| clientLogo | Company-Logo, specified as an image file. The content is placed in the configuration as a base64-encoded value. |
| clientLogoFile | Company-Logo, specified by a path to an image on the servers side. |
| clientMaxIdleTime | Specifies how long the maximum time a client cannot report to the server can be. If this period is exceeded without user action, the client sends a small data… |
| clientMaximumSessionThreads | Specifies the maximum number of threads a client session may use exclusively. Shared threads across clients are not subject of this number. Also, there might… |
| clientTheme | The name of the color theme that should be used |
| clientTimeout | Specifies the timeout of a client in milliseconds. |
| clientTitleText | Specifies the user-selectable title of the program title, as can be displayed on the client as a window title, for example. |
| customProperties | Here an administrator / developer can define custom configurations, which can be read via JDito |
| databaseAuditDBTimeout | The time-out for database logging. |
| databaseAuditEnabled | Enables the database audit layer of the ADITO core |
| databaseDBSyncCompleteSyncEnabled | If this is set, all data is synced on the next sync run |
| databaseDBSyncConnectionEncoding | Indicates whether the connection between the master and the slave is encrypted. Possible values are Off and SSL. |
| databaseDBSyncConnectionType | Specifies the connection type between the master and the slave. |
| databaseDBSyncDBFetchSize | Sets the JDBC fetchsize in side the db sync |
| databaseDBSyncDBRequestTimeout | Specifies the time when access to the master server's database will timeout. |
| databaseDBSyncInitialCommitDuration | Determines the amount of time elapsed before a commit is performed. |
| databaseDBSyncInitialCommitSize | Determines the amount of data that is transferred until a commit is performed. |
| databaseDBSyncIntervall | The interval, in milliseconds, during which the synchronization operation is performed. |
| databaseDBSyncMasterAdress | Specifies the address of the master (IP or hostname) for slave systems. This information is required when operating in slave mode. |
| databaseDBSyncMasterPort | The port of the master server. |
| databaseDBSyncStepSize | Normally, the synchronization is performed on a daily basis. If you want to use a different time frame, you can set it here. |
| databaseDBSyncTruncateOnCompleteSync | If activated, the tables of the slave system are emptied before the complete synchronization. |
| databaseDBSyncType | Toggles offline synchronization on or off. |
| databaseDeadlockRetries | Specifies the number of retries in case of a database deadlock |
| databaseMaxValuelistEntries | Specifies the maximum number of entries a value list can have. For example: This restricts the number of values an IN condition can have. "... where FIELD in (… |
| immediateTaskCreationEnabled | Specifies if the tasks can be created immediately (without entering the edit view) via the WunderBar. |
| indexsearchAlias | Sets the alias on which the indexSearch should operate |
| indexsearchEnabled | Enables index lookup for both the client and JDito commands (indexsearch.search()). |
| indexsearchGroupUpdateInterval | Defines the interval in which the indexsearch will check for changes in subGroups of all active index groups. |
| indexsearchGroupUpdateRandomDelay | Defines an additional random factor which will be applied to the group update interval of each server instance. |
| isClientTestlabelsEnabled | This setting enables or disables the Test labels for the client. |
| jditoDebuggerEnabled | Enables the debugger for this system. Only applicable for locally run servers. |
| jditoDebugHost | The host under which the ADITO debugger should be available. |
| jditoDebugObjectsPort | The port under which the JDito debugger exchanges its debug objects between server and designer. |
| jditoDebugPort | The port under which the JDito debugger is to be reachable. |
| jditoWebserviceEnabled | Activates the JDito Web services. |
| jditoWebserviceIdleTimeout | The timeout for REST connections in milliseconds. |
| jditoWebserviceMaxQueued | Maximum number of calls that can be queued if there aren't any worker thread available to service them. |
| jditoWebserviceMaxThreadCount | The maximum threads that will service requests. |
| jloadrConnectionHost | Sets the address of the server from which JLoadr will download the client installation |
| jloadrConnectionPort | Sets the port, to which JLoadr should connect |
| jloadrConnectionUseSSL | Sets wether JLoadr should use SSL encryption or not |
| jloadrSystemProperties | Set the system properties to be used by Jloadr |
| jloadrVmOptions | Set the Java VM option Jloadr should use when starting the client |
| licenseFile | — |
| loggingConsoleEnabled | Specifies whether to use the console logger. |
| loggingConsoleloggerLocale | Specifies the locale settings (language) for the console logger. The messages are then displayed in the set language. |
| loggingConsoleMultiline | — |
| loggingDBThreshold | Time threshold in milliseconds after which the execution time of a database query is logged. |
| loggingDebugLevel | Here you can set the debug level of the logger. Sets the individual debug levels (DB, IO, CALENDAR, ...). |
| loggingFileEnabled | Specifies whether to use the file logger. The file logger wirtes the log messages to a file. |
| loggingFileloggerAppend | Specifies whether the file logger should append the new log data to the existing file when the server is restarted or whether the file should be deleted first.… |
| loggingFileloggerDiscreteModules | Contains the modules that the file logger writes to extra files. |
| loggingFileloggerFile | Specifies the file name for the file logger. If nothing is specified here, but the file logger is activated, it is logged in the directory ‘Adito data’/log. |
| loggingFileloggerFileCount | Specifies the maximum number of log files that can exist. |
| loggingFileloggerMaxSize | Specifies the maximum size, in bytes, of the log file. The value is freely selectable as a positive long value. |
| loggingJavamailEnabled | Enables logging of the Javamail module |
| loggingJDBCEnabled | Enables logging for JDBC messages |
| loggingJDitoThreshold | Time threshold in milliseconds after which the execution time of a process is logged. |
| loggingLog4JLevel | Here you can set the debug level of the log4j logger. This level is applied to all internal libraries, which are using log4j |
| loggingNeonRoundThreshold | Time threshold in milliseconds after which the execution time of a calculation round trip is logged |
| loggingNeonValuesRoundThreshold | Time threshold in milliseconds after which the execution time of a calculation of a value is logged |
| loggingPriority | Specifies the priority for logging the checkpoints. |
| loggingRemoteAddress | The address under which the manager connects to the remote logger. These settings are delivered by the server to the manager through the default server port. |
| loggingRemoteEnabled | Activates the manager's remote logger, which allows the manager to view live output from the server. |
| loggingRemotePort | The port under which the manager connects to the remote logger. These settings are delivered by the server to the manager through the default server port. |
| loggingTelnetAddress | Specifies the address for Telnet access. |
| loggingTelnetEnabled | Sets whether to enable logging via Telnet. |
| loggingTelnetExternalAddress | Specifies the address for Telnet access in cloud systems from external tools, such as the designer |
| loggingTelnetPort | Specifies the port to access via Telnet. This port must be available, otherwise the ADITO server cannot be started. |
| loginList | Configures the login types for the entire system. |
| mailBridgeActiveMailservers | Specifies which active mail bridges are used by this system. This only affects mail bridges that are activated in the project settings. If empty, all active… |
| mailBridgeBlacklistEnabled | Activates the blacklist of the mail bridge. Blacklist means that an email that resulted in an error will not be picked up again. When the server is restarted,… |
| mailBridgeEnabled | Specifies whether to use the mail bridge. The mail bridge can retrieve emails from a mail server, store them in a repository, and create links. Optionally,… |
| mailGlobalEnabled | Specifies whether or not to start the email system. |
| mailGlobalTimeout | Specifies the timeout for access to email backends in milliseconds (a complete timeout for a request to run). The parameter is freely selectable as a positive… |
| maxButtonStripFavoriteItems | Sets the maximum amount of visible favorite items before they get wrapped into a popup button. (default = 4 visible items) |
| maxEntries | The number of entries that can be stored in the history table. if restricted, the number must be positive not zero. If unrestricted the number is -1 (default… |
| maxEntryLifetimeInDatabase | The amount of time that a process remains in the history table. |
| maxInvalidLoginAttempts | Sets the maximum amount of invalid login attempts. After exceeding this amount the user get blocked. |
| maxInvalidLoginAttemptsIntervall | Sets the maximum time interval between invalid login attempts |
| monitoringEnabled | This setting controls whether the monitoring functions are provided on the server side. |
| natsServiceClientConnectionUrl | — |
| natsServiceKeystoreLocation | — |
| natsServiceKeystorePassword | — |
| natsServiceKeystoreProvider | — |
| natsServiceKeystoreType | — |
| natsServiceServerConnectionUrl | — |
| neonClientHeartbeatEnabled | Enables the sending of client side hearbeats. If disabled, hearbeats will only be send from server to client. |
| neonDeactivateUrlShortener | Deactive the URL shortener that is meant to prevent http error coee 431 (header field too long). A change to this property needs a server restart in order to… |
| neonDisableConnectionSecurity | Activates the use of the HTTP protocol instead of HTTPS |
| neonFirebaseEnabled | Activates the firebase push service |
| neonFirebaseGoogleCredentials | Google Credentials File to allow the Server to send Notifications via Firebase Cloud Messaging |
| neonFirebaseGoogleServicesJson | GoogleService Json-File for Firebase on Android |
| neonFirebaseGoogleServicesPlist | GoogleService Plist-File for Firebase on iOS |
| neonHandleCORS | Activates the CORS handling. CORS stands for Cross Origin Resource Sharing. Which enables sharing of resources across more than one origin. |
| neonHeartbeatInterval | The amount of time after which a new heartbeat is sent. After three unsuccessful heartbeats, the session is terminated. |
| neonHttpPort | HTTP port on which the neon modules listen. |
| neonHttpsPort | HTTPS port on which the neon modules listen. |
| neonIdleTimeout | The amount of time the user can be inactive before his or her session is terminated. |
| neonLoginTypeIds | Sets the possible login types for use with the web client |
| neonMaximumJettyThreads | Maximum number of threads for jetty to use. A minimum of 100 is applied. |
| neonNotificationAutoDeleteEnabled | Enables the auto delete mechanism of expired Notifications. This affects expired Notifications (DELETEDATE past). |
| neonNotificationCenterEnabled | Activates the notification center |
| neonNotificationCleanupIntervall | Sets a time interval, which triggers the auto delete mechanism, if enabled. Only notifications with a daysToLive mark will be deleted. A daysToLive mark… |
| neonRemoveIngressCookieOnLogout | Enables deletion of cookie INGRESSCOOKIE on logout. |
| neonSessionTimeout | Timeout for a client session. For example, if the tab is closed without a logout, the session get terminated after the set amount of time |
| neonUpgradeInsecureRequests | Specifies if all Browser requests should be using HTTPS instead of HTTP. If set to "true" following head-tag will be added to all requests: |
| neonUseSelfSignedCertificate | Enables the creation of a self signed certificate |
| neonVaadinClientEnabled | Enables the web client, without this only the legacy system will be started |
| novaCommunicationClientConnectionTimeout | — |
| novaCommunicationClientHeartbeatSubTopic | — |
| novaCommunicationClientMaxReconnectAttempts | — |
| novaCommunicationClientPingInterval | — |
| novaCommunicationClientRequestTimeout | — |
| novaCommunicationClientSendDebugMessages | — |
| novaCommunicationServerConnectionTimeout | — |
| novaCommunicationServerEntityTopicThreadCount | — |
| novaCommunicationServerHeartbeatInterval | — |
| novaCommunicationServerHeartbeatSubTopic | — |
| novaCommunicationServerInitialReconnectWait | — |
| novaCommunicationServerMaxReconnectAttempts | — |
| novaCommunicationServerPingInterval | — |
| novaCommunicationServerReconnectJitter | — |
| novaCommunicationServerRequestTimeout | — |
| processHistoryCollectorAlias | Data alias for the collection of the process execution history. Leave empty to collect no history. If "Internal Cache" is selected, the data will only be… |
| securityConnectionSSLEnabled | Sets wether SSL encryption should be use or not |
| securitySSLDisableCertificateCheck | Disables the verification of hostname and certificates for SSL connections. |
| securitySSOUserTemplate | Here you can specify a template that is used for creating the user name for single-sign-on. |
| serverCommandWebserviceEnabled | This setting controls whether the server command functions are provided on the server side. |
| serverCommandWebserviceLoginTypeIds | Sets the possible login types for use with the server command webservice. The currently supported login type is "internal.default". The authenticated user… |
| serverFarmEnabled | Enables the use of the ADITO server farm functionality |
| serverFarmMaximumPacketSize | Specifies the maximum packet size for connections to the server farm. |
| serverFarmMaximumWorkLoad | Specifies the maximum load for a server instance as a percentage. |
| serverFarmMinimumWorkLoad | Specifies the minimum load for a server instance as a percentage. |
| serverFarmPreferencesAlias | — |
| serverFarmSelfCheckInterval | Specifies the interval at which the server farm self-test should be performed. This is a positive long value. A self-test of the server farm involves checking… |
| serverFarmTimeout | Specifies the time-out for accessing the management table for the server farm in milliseconds. |
| spellcheckerEnabled | Specifies if the spellchecker of the HTML Editor should be enabled by default. |
| systemConnectionType | Specifies the type of connection between the client and the server. Possible values: |
| systemDBLoginTimeout | Specifies the timeout for the login to the system database. |
| systemDBRequestTimeout | After this time a database query is definitely interrupted. The value is specified as a positive long value and should be greater than the… |
| systemDBRequestWarnTimeout | Specifies the query timeout for the system database. This is not a "real" timeout, but after this period of time in the client, the user is asked whether the… |
| systemOrigin | Specifies the external origin of the system. This value can for example be used to generate a link to the system. Note that this Property is set automatically… |
| systemServerAddress | IP address or host name of the server for which the configuration is valid (Note Server License.). If an incorrect address is given here, the server cannot… |
| systemServerPort | Specifies the port on which the server should listen for incoming connections from clients and other servers. The value is specified as an integer between 1… |
| teamsAppId | The appId which is found in the microsoft teams admin center if the ADITO app was installed |
| teamsBotClientId | The BotClientId which is found in the azure portal, under AppRegistration -> {BotName} -> Overview |
| teamsBotSecret | The BotSecret which is found in the azure portal, under AppRegistration -> {BotName} -> Certificates & Secrets -> Secret Client Keys If no secret is stored… |
| teamsClientId | The clientId which can be found in the Azure Portal, under App-Registration -> {AppName} -> Overview |
| teamsClientSecret | The clientSecret which can be found in the Azure Portal, under App-Registration -> {AppName} -> Certificates & Secrets -> Secret Client Keys If no secret is… |
| teamsEmailInvitationMessage | The default invitation message which is send to the recipient's email address if desired |
| teamsEnabled | This setting controls whether the msteams functions are provided to the clients on the server side. The msteams tab in the settings dialog on the client is… |
| teamsImpersoAzureId | The AditoImpersoAzureId which is found in the azure portal, under Users -> {AditoImpersoUsername} -> Profile -> ObjectId |
| teamsImpersoPassword | AditoImpersoPassword is the password that is stored for the AditoImpersoUser |
| teamsImpersoUPN | The AditoImpersoUser which is found in the azure portal, under Users -> {AditoImpersoUsername} -> Profile -> User Principal Name |
| teamsRedirectInvitationUrl | The redirect URL specifies the URL to which the recipient is redirected if he accepts the invitation |
| teamsTenantId | The tenantId which can be found in the Azure Portal, under App-Registration -> {AppName} -> Overview |
| telemetryExternalEnabled | This setting controls whether the monitoring functions are provided on the server side. |
| telemetryExternalLoginTypeIds | Sets the possible login types for use with the telemetry servlet. The currently supported login type is "internal.default". The authenticated user should have… |
| telephonyEnabled | This setting controls whether the telephony functions are provided to the clients on the server side. The telephony tab in the settings dialog on the client is… |
| telephonyProvider | Name of the favourable as a clear string. This can also be set through the client. |
| usageStatisticsEnabled | Enables usage statistics. If enabled, the server will send daily usage statistics to ADITO. Note that the usage statistics don't contain any user identifying… |
| userdirectoryCacheEnabled | Enables user cache on the server. Loads users faster in queries, but increases the memory footprint by loading users into the server's RAM. |
| userdirectoryCachePreloadEnabled | This setting enables all users to be preloaded. Enabling this setting will load users faster but consume more memory. |
| userdirectoryCacheReloadMissingUsers | This setting enables missing users to be immediately reloaded. Disabling this features uses periodically reloading to keep the cache up-to-date. |
| userdirectoryDbIgnoreCase | This setting controls whether user queries for JDito are case-sensitive. |
| userSatisfactionSurveyEnabled | This setting enables or disables the user satisfaction survey. |
| userSatisfactionSurveyUrl | This expert setting allows the configuration of the user satisfaction survey url. The default value should be sufficient, but if something changes this setting… |
| webserverPath | The home directory for the internal seb server. This path is the data of the web server (for example, index.html, client.jnlp). |
| webservicesServerEnabled | Enables webservices for server processes. |
| webservicesServerLoginTypeId | ID of the login type used for webservices servers. This must be present in the loginList (in the security area). |
| whatsnewContentWebservicePassword | Specifies the password that should be used for authorization of the what's new content webservice. |
| whatsnewContentWebserviceUrl | Specifies the URL of the feedback webservice that's called when the user sends feedback. The feedback data that is send to the WS as a JSON e.g. var jsonResult… |
| whatsnewContentWebserviceUsername | Specifies the username that should be used for authorization of the what's new content webservice. |
| whatsnewEnabled | Specifies if the "What's new" feature should be enabled in the client. If set to false then the what's new button in the navigation bar won't be visible. |
| whatsnewFeedbackDisclaimerText | Specifies which disclaimer text should be displayed above the feedback area. If nothing is specified then a default disclaimer text will be displayed. The text… |
| whatsnewFeedbackWebservicePassword | Specifies the password that should be used for authorization of the feedback webservice. |
| whatsnewFeedbackWebserviceUrl | Specifies the URL of the feedback webservice that's called when the user sends feedback. The feedback data that is send to the WS as a JSON e.g. { "user": "Tim… |
| whatsnewFeedbackWebserviceUsername | Specifies the username that should be used for authorization of the feedback webservice. |
| whatsnewTitleText | Specifies which title text should be displayed in the window. The current selected server version is always shown in the title followed by the titleText. |
| workflowEngineAlias | Sets the alias on which the workflow engine should be running. |
| workflowEngineEnabled | Enable the workflow engine |
| workflowEngineLoginTypeIds | Sets the possible login types for use with the workflow service |
| workflowEngineUser | Specifies the user context in which to run a workflow engine servicetask |
| workflowModelerAlias | Sets the alias that holds the location where the modeler exists. |
| workflowTimerEventsEnabled | Enable workflow timer events |
| wunderbarEnabled | Specifies if the WunderBar should be enabled in the client. |
antiBruteforceLoginModuleActive
Type: Boolean
Default: true
Actives the anti bruteforce module
apiGatewayToken
Type: String
Specifies the bearer token used to authenticate requests to the api gateway. If empty, no authentication will be performed.
automaticUnblockingActive
Type: Boolean
Default: true
Requires: antiBruteforceLoginModuleActive = true
Determines, if the automatic unblocking is active. If set, blocked users get unblocked after an interval set by automaticUnblockingIntervall.
automaticUnblockingIntervall
Type: Long
Default: 1 d
Requires: antiBruteforceLoginModuleActive = true
Sets the time interval after which blocked users get unblocked
calendarAlias
Type: String
Requires: calendarEnabled = true
Sets the alias on which the calendar should operate. This can be either a database alias or a groupware alias like ExchangeWS.
calendarAliasTasks
Type: String
Requires: calendarEnabled = true
Sets the alias for the handling of tasks, if those should be handled differently. Typically this will be set to the ADITO system db alias, to handle appointments within a groupware system, but tasks are handled within the ADITO database.
calendarCachedRequestInfinityLimitation
Type: Long
Requires: calendarCachingUseLegacyCache property group
Defines a limitation for the search period for cached calender requests when a request against infinity is carried out.
Default is 8 weeks.
If set to value smaller or equal to 0 the default limitation will be used.
This will not prevent any request against infinity to be executed, only the actual stored request in the cache is limited to this search period.
calendarCachedRequestLifetime
Type: Long
Requires: calendarSubscriptionsEnabled = false
The maximum time that a request is cached without being requested again by the client. The default is 5 minutes.
The lifetime is reset when a similar request is made by the client.
The option is only active if the cache does not use subscriptions.
calendarCachedRequestLimit
Type: Integer
Requires: calendarCachingUseLegacyCache property group
Defines the maximum number of requests that the cache can temporarily store.
With active subscriptions, all elements of the cached requests are automatically kept up-to-date for a limited period of time. Without subscriptions the cache uses scheduled full updates for the stored requests if needed.
If the limit is exceeded, old cached requests are discarded in order to save the current ones.
The limit only applies to requests that are not covered by the preload of the cache.
calendarCacheUseOptimizedFullUpdates
Type: Boolean
Requires: calendarCachingUseLegacyCache property group
Flag that allows the use of the optimized full updates in the CalenderCache.
When true, all differences of the calendar elements are determined via the UID and LAST_MODIFIED_TIME properties.
This means that the elements do not have to be loaded completely from the cache,
which speeds up the synchronization and reduces the data transferred from the cache.
This only works with calendars that support the usage of the LAST_MODIFIED_TIME property.
Default is false.
calendarCachingAlias
Type: String
Requires: calendarEnabled = true
If calendar caching is used, this property defines the database alias, which is used to cache calendar entries. Typically the ADITO system database alias is chosen here. If no value is set, then the value 'defaultDataAlias' (Preferences) is used to determine the alias to use.
calendarCachingAlwaysUseOwnerCredentials
Type: Boolean
Default: false
Requires: calendarCachingAlias property group
Always uses credentials of owner for filling cache, even if access is by another user
calendarCachingBlacklistEnabled
Type: Boolean
Default: true
Requires: calendarCachingAlias property group
Activates the calendar caching blacklist. This blacklist contains calendar entries, which provoked an error and are placed on this blacklist to be prevented from being loaded.
calendarCachingFullUpdaterMaxChunkSize
Type: Integer
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: calendarCachingUseLegacyCache property group
Specifies the maximum amount of requests for a single synchronisation performed by the full updater of the calender cache.
Default is 50.
If set to a value of 0 or smaller the limit is deactivated.
If more requests are sent to the full updater than specified by this limit, they are divided into smaller chunks and executed one after the other.
This limit applies to all requests, regardless of the type.
Be aware that the property calendarCachingFullUpdaterSyncPeriodLimit also limits the chunk size for a single execution
based on the search period of every request.
WARNINGS:
-
The smaller the value, the more requests are carried out, which leads to just as many SQL selects when the database is used as a cache.
-
The higher the value, the higher the memory usage can be during synchronization, since all entries of the cache and the calendar are loaded into memory per chunk for synchronization.
calendarCachingFullUpdaterMaxSyncYearsForInfinity
Type: Integer
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: calendarCachingUseLegacyCache property group
Defines a limit in years for the maximum search period of a request that specifies infinity as start or end time.
Default is 0.
If set to a value of 0 or smaller the limit is deactivated.
This limit only affects the period synchronized by the full updater of the calendar cache.
Examples:
The examples use 100 years as limit and 2021-01-01 as the current day.
-
A requests from
2021-01-01toinfinitywill result in actual request from2021-01-01to2121-1-1 -
A request from
infinityto2021-01-01will result in an actual request from1970-01-01to2020-01-01.The period is limited to
1970-01-01since this is the smallest supported system date (0ms). -
A request form
infinitytoinfinitywill result in an actual request from1971-01-01to2071-01-01.The search period is then calculated from +/- the half of the limit (e.g. +/- 50) depending on the current day.
NOTES:
-
When this option is disabled, infinity requests are not split into multiple smaller requests based on the threshold defined by the
calendarCachingFullUpdaterSyncPeriodLimitproperty, which results in them always being executed one at a time when the threshold is active. -
This property has a direct effect on internal requests made to determine reminders or performed by the
CalenderSyncwhen the calendar cache is used, since they use infinity requests by default.
WARNINGS:
-
Deactivating this limit can result in a large memory consumption when querying towards infinity, since all elements of the cache an the actual calender are loaded into memory for synchronization.
-
Setting this value too high can result in longer synchronization execution times because the request is broken up into several smaller requests that are executed one at a time.
This also results in as many SQL selections when the database is used as a cache.
If the value is set too low, the calendar may not be updated correctly and can therefore quickly become out of date.
calendarCachingFullUpdaterSyncPeriodLimit
Type: Long
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Requires: calendarCachingUseLegacyCache property group
Defines the limit for the overall time period of a single synchronisation performed by the full updater of the calender cache.
The defined value specifies the sync period in days. Default is 8 weeks (56 days).
If set to a value of 0 or smaller the limit is deactivated.
NOTE: This property does only support a plain number as input.
Values like 2W, 2S and 1D are not supported.
This property defines a threshold for paging that limits the overall time span the full updater can synchronize at once, based on the requested period in days.
If the limit is reached or exceed the current chunk is executed even if maximum chunk size has not yet been reached.
The limit is only applied to requests that query a period of more than one day. All requests that query less than a full day, including queries for individual elements, are not affected by this limit. They are only limited by the maximum chunk size.
If a single request queries a longer period than the specified limit, it is divided into several smaller requests that do not exceed the specified maximum query period.
NOTE:
Requests towards infinity are not divided up if the calendarCachingFullUpdaterMaxSyncYearsForInfinity property
is set to 0, but they are still divided into chunks based on their search period and,
if necessary, executed individually and one after the other.
WARNINGS:
-
The smaller the value, the more requests are carried out when synchronizing larger periods of time, which leads to just as many SQL selects when the database is used as a cache.
-
The higher the value, the higher the memory usage when synchronizing large periods of time, since all entries of the cache and the calendar are loaded into memory for the specified period per chunk for synchronization.
calendarCachingMaxPendingRequests
Type: Integer
Requires: calendarCachingUseLegacyCache property group
Number of new requests (not already stored) the cache can buffer, before sending them to the actual calender in one request if possible. Default are 10 requests.
All buffered requests are merged and executed in an interval specified by the property calendarCachingPendingRequestsExecutionInterval
( Default 1 second ).
If the limit is exceeded, old requests in the buffer are executed immediately.
calendarCachingPendingRequestsExecutionInterval
Type: Long
Requires: calendarCachingUseLegacyCache property group
Interval in which all buffered requests are passed on to the calendar. Default is 1 second.
calendarCachingPreload
Type: Boolean
Default: true
Requires: calendarCachingAlias property group
Enables preloading of the cache at server start
All calendar entries that are within a period of +/- 4 weeks are loaded into the cache, based on the date of the user's login.
The period is set when the client logs in and is automatically updated if the client remains logged in for a longer period of time.
Only the entries of the respective user are preloaded.
In the case of active subscriptions, the entries for this period are kept permanently up-to-date, otherwise the preloaded elements are updated if an element or a period that lies within the preload period is requested.
The Preload request is independent of the defined calendarCachedRequestLimit and is never deleted when the limit is reached.
If the legacy cache is used, the entries are only loaded when the client logs in for the first time and are not automatically updated. The entries are updated with every explicit request from the client.
calendarCachingUpdateRequestInterval
Type: Long
Requires: calendarSubscriptionsEnabled = false
Interval at which full updates are performed for active cached requests. The default is 30 seconds.
Cached requests are considered active if the client executes a similar request within the lifetime (default 5 minutes) of the request.
The option is only active if the cache does not use subscriptions.
calendarCachingUseLegacyCache
Type: Boolean
Default: false
Requires: calendarCachingAlias property group
If enabled, the server uses the old cache implementation from ADITO 2020 and earlier.
The legacy cache does not support continuous updates like delta requests and subscriptions for any calendar alias.
The default is false.
This option has the exact same effect as the server command line option -Dadito.calendar.useLegacyCache=true.
calendarEnabled
Type: Boolean
Default: true
Enables the calendar module
calendarShowErrorOnGetEntries
Type: Boolean
Requires: calendarCachingAlias property group
Previously: -Dadito.calendar.updater.strict=true/false
If active, errors that occur when fetching calendar entries are displayed, otherwise those errors will only be logged.
Defaults to true, if no cache or a db backend is used, otherwise false.
Note that only the global configuration is used.
This logic ignores user-specific overrides.
calendarSubscriptionMaxSearchPeriod
Type: Long
Default: 56
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Requires: calendarSubscriptionsEnabled = true
Maximum search period of delta queries and Subscriptions in Days.
Default is 56 days.
Note: All dela request are split in request matching the specified search period.
The minimum is 5 days and the maximum is 365 days (1 year).
calendarSubscriptionsAlwaysUseDelta
Type: Boolean
Default: false
Requires: calendarSubscriptionsEnabled = true
Flag which forces the cache to only use delta requests (polling) as subscriptions for calendars, even if it supports other methods.
Default is false.
The setting has no effect if the cache does not use any subscriptions or the calendar does not offer any other types of subscription.
If a calendar does not have a delta strategy, the setting is also ignored.
calendarSubscriptionsCheckerInterval
Type: Long
Default: 30 s
Requires: calendarSubscriptionsEnabled = true
Interval at which the cache checks for changes in the subscriptions. Default is 15 seconds
Checker tasks:
-
If new requests have been cached, new subscriptions are created for them.
-
If a subscription has expired, the associated request is deleted from the cache.
-
If a cached request was used again by the client, the duration of the subscription will be extended if necessary.
calendarSubscriptionsDeltaMaxInterval
Type: Long
Default: 15 min
Requires: calendarSubscriptionsEnabled = true
Maximum interval to which the execution of the delta queries of a delta subscription (polling) can be increased (throttling) in the event of longer inactivity of the associated request in the cache. Default is 10 minutes.
A request is considered inactive if the client no longer executes a similar request.
The interval is set back to the original minimum if the client sends a similar request before the subscription ends.
calendarSubscriptionsDeltaMinInterval
Type: Long
Default: 5 min
Requires: calendarSubscriptionsEnabled = true
Smallest interval in which delta queries of an active delta subscription (polling) can be carried out. Default is 3 minutes.
calendarSubscriptionsEnabled
Type: Boolean
Default: true
Requires: calendarCachingUseLegacyCache property group
When active, the elements of the cache are updated for a limited time via continuous updates.
The updates are only carried out for elements which are covered by the currently cached requests (including preload).
Subscriptions are only used for calendars that support them. e.g. Exchange. The type of updates used depends on the user's calendar, the request and the implementation of the backend within the server.
WARNING: Use only für testing purposes. System may become unstable due to high cpu usage.
calendarSubscriptionsInitialDuration
Type: Long
Default: 10 min
Requires: calendarSubscriptionsEnabled = true
The length of time a subscription for a cached request runs when the request is first executed (stored in the cache). Default is 10 minutes.
calendarSubscriptionsUpdateDuration
Type: Long
Default: 5 min
Requires: calendarSubscriptionsEnabled = true
The duration by which a subscription for a cached request is extended if the request is executed again by the client and the remaining duration of the subscription is less than the extension. Default is 5 minutes.
calendarSyncBlacklistEnabled
Type: Boolean
Default: true
Requires: calendarSyncEnabled = true
Enables the calendar sync blacklist. In this blacklist are all calendar entries, that caused an error on read. These entries wont be loaded again.
calendarSyncEnabled
Type: Boolean
Default: false
Requires: calendarEnabled = true
This setting enables or disables calendar synchronization.
With calendar synchronization, the ADITO calendar is the primary calendars and entries of an external calendar system are synchronized with this calendar.
calendarSyncInterval
Type: Long
Default: 1 min
Requires: calendarSyncEnabled = true
Specifies the interval in which the ADITO calendar should be synchronized with the calendar backend.
calendarSyncLimit
Type: Long
Default: 0 ms
Requires: calendarSyncEnabled = true
Time period, starting from the current date into the future, in which the calendar entries are synchronized. If the value is <= 0, the limit is removed and all entries will be synchronized.
calendarSyncRateLimitHandlingEnabled
Type: Boolean
Default: false
Requires: calendarSyncEnabled = true
Whether rate limit handling should be enabled for the calendar sync.
calendarSyncScope
Type: String
Requires: calendarSyncEnabled = true
Here you can set which calendar items are synchronized.
Possible settings are appointments, tasks, and both.
calendarSyncTimespan
Type: Long
Default: 28 d
Requires: calendarSyncEnabled = true
Time period, starting from the current date into the past, in which the calendar entries are synchronized.
calendarSyncUserEnabledDefault
Type: Boolean
Default: false
Requires: calendarSyncEnabled = true
If the user is not already set to synchronize, this value is used by default.
calendarTimeout
Type: Long
Default: 30 s
Requires: calendarEnabled = true
Sets the time interval after which a timeout occurs
ckeditorConfig
Type: Map
Specifies the config of the CKEditor
clientBackground
Type: String
Background image, specified as an image file. The content is placed as base64-encoded value in the configuration.
The background image is for example placed at the login and logout screen.
Make sure that the filesize of the image is not too large: This may cause issues within the browser to render it and slow the browser down. (10MB for example are too big.)
When both "clientBackgroundFile" and "clientBackground" are set, the "clientBackgroundFile"-property will take precedence.
clientBackgroundFile
Type: String
Background image, specified by a path to a file on the servers side.
The background image is for example placed at the login and logout screen.
Make sure that the filesize of the image is not too large: This may cause issues within the browser to render it and slow the browser down. (10MB for example are too big.)
The path can be either a URL or a file path. When using a URL, the content from the URL is loaded on the server side. The image is not replaced by reference on the client side.
You may use ADITO-placeholders like $ADITOHOME, $TEMP, etc. - these are resolved when retrieving the logo.
When both "clientBackgroundFile" and "clientBackground" are set, this property will take precedence.
clientCustomLogoutThemeEnabled
Type: Boolean
Default: true
Enables the clientTheme at the logout screen
clientDarkTheme
Type: String
The name of the dark color theme that should be used. The custom user theme for bright and dark variations are seperate and can be individually selected in the client.
clientIgnoreWebsocketPushMode
Type: Boolean
Default: false
When this property is enabled, the system does not verify whether the client successfully established a WebSocket connection. As a result, the client may fall back to LONG_POLLING. This fallback mode can cause multiple issues and is generally not recommended. With LONG_POLLING active, updates to the interface are not immediately sent to the client; instead, they are delivered during the client's next server request.
clientLogo
Type: String
Company-Logo, specified as an image file. The content is placed in the configuration as a base64-encoded value.
The Logo is for example placed at the center of the login and logout screen.
Make sure that the filesize of the image is not too large: This may cause issues within the browser to render it and slow the browser down.
When both "clientLogoFile" and "clientLogo" are set, the "clientLogoFile"-property will take precedence.
clientLogoFile
Type: String
Company-Logo, specified by a path to an image on the servers side.
The Logo is for example placed at the center of the login and logout screen.
Make sure that the filesize of the image is not too large: This may cause issues within the browser to render it and slow the browser down.
The path can be either a URL or a file path. When using a URL, the content from the URL is loaded on the server side. The image is not replaced by reference on the client side.
You may use ADITO-placeholders like $ADITOHOME, $TEMP, etc. - these are resolved when retrieving the logo.
When both "clientLogoFile" and "clientLogo" are set, this property will take precedence.
clientMaxIdleTime
Type: Long
Default: 2 min
Specifies how long the maximum time a client cannot report to the server can be. If this period is exceeded without user action, the client sends a small data packet to the server. If this value is less than or equal to 0, no automatic packets are sent (equivalent to the value "infinity"). If the client is unable to send a data packet to the server for four times this period, it will result in a "client timeout" and the client is disconnected from the server.
The time unit can be specified in minutes (M), seconds (S) or milliseconds, e.g. "1 M" for one minute, or "1" for a millisecond.
clientMaximumSessionThreads
Type: Integer
Constraints: Minimum: 0, Maximum: Integer.MAX_VALUE
Specifies the maximum number of threads a client session may use exclusively. Shared threads across clients are not subject of this number. Also, there might be pools, which do not respect this configuration. Default value is number of available processors.
clientTheme
Type: String
The name of the color theme that should be used
clientTimeout
Type: Long
Default: 1 d
Specifies the timeout of a client in milliseconds.
If a user does not work within this time, the connection is disconnected and the client is terminated.
The value is freely selectable as a positive integer.
clientTitleText
Type: String
Specifies the user-selectable title of the program title, as can be displayed on the client as a window title, for example.
The value can be any text as a string.
customProperties
Type: CustomProperties
Here an administrator / developer can define custom configurations, which can be read via JDito
databaseAuditDBTimeout
Type: Long
Default: 30 s
The time-out for database logging.
If this timeout has elapsed, the ADITO server will no longer attempt to log the change.
databaseAuditEnabled
Type: Boolean
Default: false
Enables the database audit layer of the ADITO core
databaseDBSyncCompleteSyncEnabled
Type: Boolean
Default: true
Requires: databaseDBSyncType property group
If this is set, all data is synced on the next sync run
databaseDBSyncConnectionEncoding
Type: Integer
Requires: databaseDBSyncType property group
Indicates whether the connection between the master and the slave is encrypted. Possible values are Off and SSL.
databaseDBSyncConnectionType
Type: Integer
Default: 5
Requires: databaseDBSyncType property group
Specifies the connection type between the master and the slave.
Possible values: Classic, NIO, stateless, HTTP and NETTY.
Classic: The connections are accepted according to the "old" Java server socket principle and then held in the clients. For each client, a separate thread is needed for communication. The network connection remains in place for the entire duration of the client.
NIO: The connections are accepted with the new "NIO". The connections are then not "blocked", i.e. a single thread observes incoming data packets and then forwards this to the client. However, the network connection will remain in place throughout the client's lifetime.
Stateless: The connections are stateless. This means that in contrast to Classic and NIO, for each command coming from the client, a connection to the server is established, which is separated again after processing the command and sending the response. Internally, connections are used in accordance with the classical principle.
HTTP: The connections are handled via HTTP (also a stateless connection, just via the HTTP protocol).
NETTY: The connections are handled via the NETTY protocol. Here the client can reconnect to the server when the connection is terminated, if necessary.
databaseDBSyncDBFetchSize
Type: Integer
Default: 50
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: databaseDBSyncType property group
Sets the JDBC fetchsize in side the db sync
databaseDBSyncDBRequestTimeout
Type: Long
Default: 15 min
Requires: databaseDBSyncType property group
Specifies the time when access to the master server's database will timeout.
databaseDBSyncInitialCommitDuration
Type: Long
Default: 1 min
Requires: databaseDBSyncType property group
Determines the amount of time elapsed before a commit is performed.
At the end of the databaseDBSyncInitialCommitDuration in the initial synchronization, a "commit" is performed in the database.
databaseDBSyncInitialCommitSize
Type: Integer
Default: 100 MB
Requires: databaseDBSyncType property group
Determines the amount of data that is transferred until a commit is performed.
After exceeding the databaseDBSyncInitialCommitSize in the initial synchronization, a commit is performed in the database.
databaseDBSyncIntervall
Type: Long
Default: 10 min
Requires: databaseDBSyncType property group
The interval, in milliseconds, during which the synchronization operation is performed.
databaseDBSyncMasterAdress
Type: String
Requires: databaseDBSyncType property group
Specifies the address of the master (IP or hostname) for slave systems. This information is required when operating in slave mode.
databaseDBSyncMasterPort
Type: Integer
Constraints: Minimum: 0, Maximum: 65536
Requires: databaseDBSyncType property group
The port of the master server.
This information is required when operating in slave mode. Synchronization takes place through the client port of the master.
databaseDBSyncStepSize
Type: Long
Default: 1 d
Requires: databaseDBSyncType property group
Normally, the synchronization is performed on a daily basis. If you want to use a different time frame, you can set it here.
databaseDBSyncTruncateOnCompleteSync
Type: Boolean
Default: false
Requires: databaseDBSyncType property group
If activated, the tables of the slave system are emptied before the complete synchronization.
databaseDBSyncType
Type: Integer
Default: 0
Toggles offline synchronization on or off.
The synchronization is activated as a master (the current ADITO server is the master server) or slave (the current ADITO server is a slave server). This setting is only stored for the current server. If multiple servers are connected, they must have the same databaseDBSyncConnectionType in the system tab.
For more information on data synchronization, refer to the ADITO Information Document (AID) 056, Datensynchronisation.
databaseDeadlockRetries
Type: Integer
Default: 3
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Specifies the number of retries in case of a database deadlock
databaseMaxValuelistEntries
Type: Integer
Default: -1
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Specifies the maximum number of entries a value list can have. For example: This restricts the number of values an IN condition can have. "... where FIELD in ( ... , ... , ...)"
immediateTaskCreationEnabled
Type: Boolean
Default: false
Specifies if the tasks can be created immediately (without entering the edit view) via the WunderBar.
indexsearchAlias
Type: String
Requires: indexsearchEnabled = true
Sets the alias on which the indexSearch should operate
indexsearchEnabled
Type: Boolean
Default: false
Enables index lookup for both the client and JDito commands (indexsearch.search()).
indexsearchGroupUpdateInterval
Type: Long
Requires: indexsearchEnabled = true
Defines the interval in which the indexsearch will check for changes in subGroups of all active index groups.
The update will trigger a rather expensive call to the search engine in order to load all available subgroups from the underlying index.
Default is one minute (1M), which is also the minimum.
NOTE: For the changes to the property to take effect, either the server or the index search must be restarted.
indexsearchGroupUpdateRandomDelay
Type: Long
Requires: indexsearchEnabled = true
Defines an additional random factor which will be applied to the group update interval of each server instance.
This will cause each server to perform the group updates at different times, which can help increase the stability of underlying search service. The factor defines the maximum mount of seconds that will be subtracted from original update interval.
In order to work propertly the range must be smaller than the update interval and the update interval itself must be set to value grater then the minimum interval. Otherwise, this can cause the update interval to always use the minimum interval of 1 minute.
Default is 0 for no delay.
For example, if the update interval is set to 3 minutes (3M) and this delay to 10 seconds (10S), then it will case each ADITO server of the system to perform the update within in individual interval between 2 minutes and 50 seconds and 3 minutes.
NOTE: For the changes to the property to take effect, either the server or the index search must be restarted.
isClientTestlabelsEnabled
Type: Boolean
This setting enables or disables the Test labels for the client.
jditoDebuggerEnabled
Type: Boolean
Default: false
Enables the debugger for this system. Only applicable for locally run servers.
jditoDebugHost
Type: String
The host under which the ADITO debugger should be available.
jditoDebugObjectsPort
Type: Integer
Default: 1098
Constraints: Minimum: 0, Maximum: 65536
The port under which the JDito debugger exchanges its debug objects between server and designer.
The designer automatically reads the port specified here when the debugger is connected.
jditoDebugPort
Type: Integer
Default: 1099
Constraints: Minimum: 0, Maximum: 65536
The port under which the JDito debugger is to be reachable.
This port is required if you want to use remote debugging because, for example, the default debug port was not released. The designer automatically reads the port specified here when the debugger is connected.
jditoWebserviceEnabled
Type: Boolean
Default: true
Activates the JDito Web services.
jditoWebserviceIdleTimeout
Type: Long
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
The timeout for REST connections in milliseconds.
If this is not set, no timeout is used and the standard timeout of the app server will be used/unchanged.
jditoWebserviceMaxQueued
Type: Integer
Default: 0
Constraints: Minimum: -1, Maximum: Integer.MAX_VALUE
Maximum number of calls that can be queued if there aren't any worker thread available to service them.
If the value is '0', then no queue is used and calls are rejected if no worker thread is immediately available.
If the value is '-1', then an unbounded queue is used and calls are never rejected.
jditoWebserviceMaxThreadCount
Type: Integer
Default: 10
Constraints: Minimum: 1, Maximum: Integer.MAX_VALUE
The maximum threads that will service requests.
jloadrConnectionHost
Type: String
Sets the address of the server from which JLoadr will download the client installation
jloadrConnectionPort
Type: Integer
Constraints: Minimum: 0, Maximum: 65536
Sets the port, to which JLoadr should connect
jloadrConnectionUseSSL
Type: Boolean
Sets wether JLoadr should use SSL encryption or not
jloadrSystemProperties
Type: String[]
Set the system properties to be used by Jloadr
jloadrVmOptions
Type: String[]
Set the Java VM option Jloadr should use when starting the client
licenseFile
Type: String
loggingConsoleEnabled
Type: Boolean
Default: false
Specifies whether to use the console logger.
The console logger writes log output to the console when the server is started using the command (batch or shell script).
loggingConsoleloggerLocale
Type: String
Requires: loggingConsoleEnabled = true
Specifies the locale settings (language) for the console logger. The messages are then displayed in the set language.
loggingConsoleMultiline
Type: Boolean
Default: true
Requires: loggingConsoleEnabled = true
loggingDBThreshold
Type: Long
Default: -1
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Time threshold in milliseconds after which the execution time of a database query is logged.
A value of "-1" disables the logging.
'DB_EXTENDED' must be enabled at 'loggingDebugLevel' for this parameter to take effect.
loggingDebugLevel
Type: String
Here you can set the debug level of the logger. Sets the individual debug levels (DB, IO, CALENDAR, ...).
Further parameters can be found in the operating manual for the debug parameters for the ADITO server.
Note that slow JDITO scripts or slow database statements are only logged when their respective thresholds are enabled (see loggingJDitoThreshold and loggingDBThreshold).
loggingFileEnabled
Type: Boolean
Default: false
Specifies whether to use the file logger. The file logger wirtes the log messages to a file.
loggingFileloggerAppend
Type: Boolean
Default: true
Requires: loggingFileEnabled = true
Specifies whether the file logger should append the new log data to the existing file when the server is restarted or whether the file should be deleted first. Possible values: Yes (append new log data to the existing file) or No (delete log file first).
loggingFileloggerDiscreteModules
Type: String
Requires: loggingFileEnabled = true
Contains the modules that the file logger writes to extra files.
This setting has no effect on the loggingFileloggerFilecount.
loggingFileloggerFile
Type: String
Requires: loggingFileEnabled = true
Specifies the file name for the file logger. If nothing is specified here, but the file logger is activated, it is logged in the directory ‘Adito data’/log.
If the file does not already exist, it is created if necessary. If ‘Adito data’ is not defined, the following directories are used. Linux: Opt/ADITO4Data/log, Mac OS X:/Library/Application support/ADITO/log, Windows: C:\ProgramData\ADITO\log.
loggingFileloggerFileCount
Type: Integer
Default: 10
Constraints: Verification: EVerifier.LOGGING_FILELOGGERFILECOUNT, Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: loggingFileEnabled = true
Specifies the maximum number of log files that can exist.
When the maximum number is reached, the oldest log file is overwritten. The value is freely selectable as a positive integer value.
loggingFileloggerMaxSize
Type: Integer
Default: 10 MB
Requires: loggingFileEnabled = true
Specifies the maximum size, in bytes, of the log file. The value is freely selectable as a positive long value.
loggingJavamailEnabled
Type: Boolean
Default: false
Enables logging of the Javamail module
loggingJDBCEnabled
Type: Boolean
Default: false
Enables logging for JDBC messages
loggingJDitoThreshold
Type: Long
Default: -1
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Time threshold in milliseconds after which the execution time of a process is logged.
A value of "-1" disables the logging.
'JDITO' must be enabled at 'loggingDebugLevel' for this parameter to take effect.
loggingLog4JLevel
Type: ELog4JLoggingLevel
Here you can set the debug level of the log4j logger. This level is applied to all internal libraries, which are using log4j
loggingNeonRoundThreshold
Type: Long
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Time threshold in milliseconds after which the execution time of a calculation round trip is logged
loggingNeonValuesRoundThreshold
Type: Long
Constraints: Minimum: Long.MIN_VALUE, Maximum: Long.MAX_VALUE
Time threshold in milliseconds after which the execution time of a calculation of a value is logged
loggingPriority
Type: String
Specifies the priority for logging the checkpoints.
Possible values are A (low logging) and Z (much logging). In addition, gradations with values between A and Z are possible.
loggingRemoteAddress
Type: String
Requires: loggingRemoteEnabled = true
The address under which the manager connects to the remote logger. These settings are delivered by the server to the manager through the default server port.
This means that the server communicates the connection setting (e.g. 127.0.0.1:7733) directly to the manager. This host does not have to be specified anywhere in the manager.
loggingRemoteEnabled
Type: Boolean
Default: false
Activates the manager's remote logger, which allows the manager to view live output from the server.
loggingRemotePort
Type: Integer
Default: 7733
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: loggingRemoteEnabled = true
The port under which the manager connects to the remote logger. These settings are delivered by the server to the manager through the default server port.
This means that the connection setting (e.g. 127.0.0.1:7733) communicates the server directly to the manager. This port does not have to be specified anywhere in the manager.
loggingTelnetAddress
Type: String
Requires: loggingTelnetEnabled = true
Specifies the address for Telnet access.
loggingTelnetEnabled
Type: Boolean
Default: false
Sets whether to enable logging via Telnet.
If the Telnet logger is enabled even though the specified port (in the standard 7722) is not available, the ADITO server cannot be started.
loggingTelnetExternalAddress
Type: String
Requires: loggingTelnetEnabled = true
Specifies the address for Telnet access in cloud systems from external tools, such as the designer
loggingTelnetPort
Type: Integer
Default: 7722
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: loggingTelnetEnabled = true
Specifies the port to access via Telnet. This port must be available, otherwise the ADITO server cannot be started.
loginList
Type: LogInList
Configures the login types for the entire system.
mailBridgeActiveMailservers
Type: String[]
Requires: mailBridgeEnabled = true
Specifies which active mail bridges are used by this system. This only affects mail bridges that are activated in the project settings. If empty, all active mail bridges are used by default.
mailBridgeBlacklistEnabled
Type: Boolean
Default: true
Requires: mailGlobalEnabled = true
Activates the blacklist of the mail bridge. Blacklist means that an email that resulted in an error will not be picked up again. When the server is restarted, the blacklist is emptied.
mailBridgeEnabled
Type: Boolean
Default: false
Requires: mailGlobalEnabled = true
Specifies whether to use the mail bridge. The mail bridge can retrieve emails from a mail server, store them in a repository, and create links. Optionally, only the processes created with the link can be executed.
mailGlobalEnabled
Type: Boolean
Default: false
Specifies whether or not to start the email system.
As long as this setting is set to No, email functionality cannot be used.
mailGlobalTimeout
Type: Long
Default: 1 min
Requires: mailGlobalEnabled = true
Specifies the timeout for access to email backends in milliseconds (a complete timeout for a request to run). The parameter is freely selectable as a positive long value.
maxButtonStripFavoriteItems
Type: Integer
Default: 4
Sets the maximum amount of visible favorite items before they get wrapped into a popup button. (default = 4 visible items)
maxEntries
Type: Integer
Constraints: Maximum: Integer.MAX_VALUE
The number of entries that can be stored in the history table. if restricted, the number must be positive not zero. If unrestricted the number is -1 (default value)
maxEntryLifetimeInDatabase
Type: Long
The amount of time that a process remains in the history table.
The input is alphanumeric:
1W = one week in ms
1D = one day in ms
1H = one hour in ms
1M = one minute in ms
1S = one second in ms
Example input: 1D 42M
Default value = 90D
maxInvalidLoginAttempts
Type: Integer
Default: 50
Constraints: Minimum: Integer.MIN_VALUE, Maximum: Integer.MAX_VALUE
Requires: antiBruteforceLoginModuleActive = true
Sets the maximum amount of invalid login attempts. After exceeding this amount the user get blocked.
maxInvalidLoginAttemptsIntervall
Type: Long
Default: 15 min
Requires: antiBruteforceLoginModuleActive = true
Sets the maximum time interval between invalid login attempts
monitoringEnabled
Type: Boolean
Default: true
This setting controls whether the monitoring functions are provided on the server side.
natsServiceClientConnectionUrl
Type: String
natsServiceKeystoreLocation
Type: String
natsServiceKeystorePassword
Type: String
natsServiceKeystoreProvider
Type: String
natsServiceKeystoreType
Type: String
natsServiceServerConnectionUrl
Type: String
neonClientHeartbeatEnabled
Type: Boolean
Default: false
Enables the sending of client side hearbeats. If disabled, hearbeats will only be send from server to client.
neonDeactivateUrlShortener
Type: Boolean
Default: false
Deactive the URL shortener that is meant to prevent http error coee 431 (header field too long). A change to this property needs a server restart in order to have an effect.
neonDisableConnectionSecurity
Type: Boolean
Default: true
Activates the use of the HTTP protocol instead of HTTPS
neonFirebaseEnabled
Type: Boolean
Default: false
Activates the firebase push service
neonFirebaseGoogleCredentials
Type: String
Requires: neonFirebaseEnabled = true
Google Credentials File to allow the Server to send Notifications via Firebase Cloud Messaging
neonFirebaseGoogleServicesJson
Type: String
Requires: neonFirebaseEnabled = true
GoogleService Json-File for Firebase on Android
neonFirebaseGoogleServicesPlist
Type: String
Requires: neonFirebaseEnabled = true
GoogleService Plist-File for Firebase on iOS
neonHandleCORS
Type: Boolean
Default: false
Activates the CORS handling. CORS stands for Cross Origin Resource Sharing. Which enables sharing of resources across more than one origin.
neonHeartbeatInterval
Type: Long
Default: 50 s
The amount of time after which a new heartbeat is sent. After three unsuccessful heartbeats, the session is terminated.
neonHttpPort
Type: Integer
Default: 8080
Constraints: Minimum: 0, Maximum: 65536
HTTP port on which the neon modules listen.
neonHttpsPort
Type: Integer
Default: 8443
Constraints: Minimum: 0, Maximum: 65536
HTTPS port on which the neon modules listen.
neonIdleTimeout
Type: Long
Default: 45 min
The amount of time the user can be inactive before his or her session is terminated.
neonLoginTypeIds
Type: String[]
Sets the possible login types for use with the web client
neonMaximumJettyThreads
Type: Integer
Default: 200
Maximum number of threads for jetty to use. A minimum of 100 is applied.
neonNotificationAutoDeleteEnabled
Type: Boolean
Default: true
Requires: neonNotificationCenterEnabled = true
Enables the auto delete mechanism of expired Notifications. This affects expired Notifications (DELETEDATE past).
neonNotificationCenterEnabled
Type: Boolean
Default: true
Activates the notification center
neonNotificationCleanupIntervall
Type: Long
Default: 1 d
Requires: neonNotificationCenterEnabled = true
Sets a time interval, which triggers the auto delete mechanism, if enabled.
Only notifications with a daysToLive mark will be deleted. A daysToLive mark may be set when creating notifications - this is however
optional.
neonRemoveIngressCookieOnLogout
Type: Boolean
Default: false
Enables deletion of cookie INGRESSCOOKIE on logout.
neonSessionTimeout
Type: Long
Timeout for a client session. For example, if the tab is closed without a logout, the session get terminated after the set amount of time
neonUpgradeInsecureRequests
Type: Boolean
Default: false
Specifies if all Browser requests should be using HTTPS instead of HTTP. If set to "true" following head-tag will be added to all requests:
neonUseSelfSignedCertificate
Type: Boolean
Default: false
Enables the creation of a self signed certificate
neonVaadinClientEnabled
Type: Boolean
Default: true
Enables the web client, without this only the legacy system will be started
novaCommunicationClientConnectionTimeout
Type: Long
Default: 5 s
novaCommunicationClientHeartbeatSubTopic
Type: String
novaCommunicationClientMaxReconnectAttempts
Type: Integer
Default: 10
novaCommunicationClientPingInterval
Type: Long
Default: 30 s
novaCommunicationClientRequestTimeout
Type: Long
Default: 10 s
novaCommunicationClientSendDebugMessages
Type: Boolean
Default: false
novaCommunicationServerConnectionTimeout
Type: Long
Default: 5 s
novaCommunicationServerEntityTopicThreadCount
Type: Integer
Default: 1
novaCommunicationServerHeartbeatInterval
Type: Long
Default: 50 s
novaCommunicationServerHeartbeatSubTopic
Type: String
novaCommunicationServerInitialReconnectWait
Type: Long
Default: 2 s
novaCommunicationServerMaxReconnectAttempts
Type: Integer
Default: 5
novaCommunicationServerPingInterval
Type: Long
Default: 50 s
novaCommunicationServerReconnectJitter
Type: Long
Default: 2 s
novaCommunicationServerRequestTimeout
Type: Long
Default: 30 s
processHistoryCollectorAlias
Type: String
Data alias for the collection of the process execution history. Leave empty to collect no history. If "Internal Cache" is selected, the data will only be available until the next server restart.
securityConnectionSSLEnabled
Type: Boolean
Default: false
Sets wether SSL encryption should be use or not
securitySSLDisableCertificateCheck
Type: Boolean
Default: false
Disables the verification of hostname and certificates for SSL connections.
securitySSOUserTemplate
Type: String
Here you can specify a template that is used for creating the user name for single-sign-on.
You can use the variable $USERTITLE in this template, which is resolved according to the user name of the logged-on user.
serverCommandWebserviceEnabled
Type: Boolean
This setting controls whether the server command functions are provided on the server side.
serverCommandWebserviceLoginTypeIds
Type: String[]
Requires: serverCommandWebserviceEnabled = true
Sets the possible login types for use with the server command webservice. The currently supported login type is "internal.default". The authenticated user should have at least the role INTERNAL_TECHNICAL.
serverFarmEnabled
Type: Boolean
Default: false
Enables the use of the ADITO server farm functionality
serverFarmMaximumPacketSize
Type: Integer
Default: 100 MB
Requires: serverFarmEnabled = true
Specifies the maximum packet size for connections to the server farm.
serverFarmMaximumWorkLoad
Type: Integer
Default: 85
Constraints: Verification: EVerifier.SERVERFARM_MAXIMUM_WORKLOAD, Maximum: Integer.MAX_VALUE
Requires: serverFarmEnabled = true
Specifies the maximum load for a server instance as a percentage.
serverFarmMinimumWorkLoad
Type: Integer
Default: 35
Constraints: Verification: EVerifier.SERVERFARM_MINIMUM_WORKLOAD, Maximum: Integer.MAX_VALUE
Requires: serverFarmEnabled = true
Specifies the minimum load for a server instance as a percentage.
serverFarmPreferencesAlias
Type: String
serverFarmSelfCheckInterval
Type: Long
Default: 5 s
Requires: serverFarmEnabled = true
Specifies the interval at which the server farm self-test should be performed. This is a positive long value. A self-test of the server farm involves checking the logged on clients and matching the license information.
serverFarmTimeout
Type: Long
Default: 15 s
Requires: serverFarmEnabled = true
Specifies the time-out for accessing the management table for the server farm in milliseconds.
spellcheckerEnabled
Type: Boolean
Default: false
Specifies if the spellchecker of the HTML Editor should be enabled by default.
systemConnectionType
Type: Integer
Default: 5
Specifies the type of connection between the client and the server. Possible values:
Classic-the connections are accepted according to the "old" Java server Socket principle and then held in the clients. For each client, a separate thread is needed for communication. The network connection remains in place for the entire duration of the client.
NIO-the connections are accepted with the new "NIO". The connections are then not "blocked", i.e. a single thread observes incoming data packets and then forwards them to the client. However, the network connection remains in place throughout the client's lifetime.
Stateless-the connections are stateless. This means that in contrast to classic and NIO, for each command coming from the client, a connection to the server is established, which is separated again after processing the command and sending the response. Internally, connections are used in accordance with the classical principle.
HTTP-the connections are handled via HTTP (also a stateless connection, just via the HTTP protocol).
NETTY-the connections are handled via the NETTY protocol. Here the client can reconnect to the server when the connection is terminated, if necessary.
systemDBLoginTimeout
Type: Long
Default: 30 s
Specifies the timeout for the login to the system database.
systemDBRequestTimeout
Type: Long
Default: 30 s
After this time a database query is definitely interrupted. The value is specified as a positive long value and should be greater than the systemDBRequestWarnTimeout value.
systemDBRequestWarnTimeout
Type: Long
Default: 10 s
Specifies the query timeout for the system database. This is not a "real" timeout, but after this period of time in the client, the user is asked whether the long running database query should be interrupted or continue to run. The value is specified as a positive long value.
systemOrigin
Type: String
Specifies the external origin of the system. This value can for example be used to generate a link to the system. Note that this Property is set automatically for managed systems.
NOTE that this property differs from the "$sys.origin" variable, since the "$sys.origin" variable is determined from the current http request and therefore cannot be used without a client session.
The property includes the scheme (http or https), the hostname (e.g. adito.example.org) and optionally the port if it differs from the default port for the specified scheme.
An example value could be https://adito.example.org.
systemServerAddress
Type: String
IP address or host name of the server for which the configuration is valid (Note Server License.). If an incorrect address is given here, the server cannot start because no bind can be made. To avoid this, you can specify 0.0.0.0 as a wildcard.
systemServerPort
Type: Integer
Constraints: Minimum: 0, Maximum: 65536
Specifies the port on which the server should listen for incoming connections from clients and other servers. The value is specified as an integer between 1 and 65535 and cannot be identical to managerport.
Attention:
Each port on the server can only be used by one service. It is therefore important to ensure that no ports are entered here that are used by another application. If you want to start the server several times, you must specify a different port in each configuration. The default server port for ADITO is Port 7779.
teamsAppId
Type: String
Requires: teamsEnabled = true
The appId which is found in the microsoft teams admin center if the ADITO app was installed
teamsBotClientId
Type: String
Requires: teamsEnabled = true
The BotClientId which is found in the azure portal, under AppRegistration -> {BotName} -> Overview
teamsBotSecret
Type: String
Requires: teamsEnabled = true
The BotSecret which is found in the azure portal, under AppRegistration -> {BotName} -> Certificates & Secrets -> Secret Client Keys If no secret is stored there, create one
teamsClientId
Type: String
Requires: teamsEnabled = true
The clientId which can be found in the Azure Portal, under App-Registration -> {AppName} -> Overview
teamsClientSecret
Type: String
Requires: teamsEnabled = true
The clientSecret which can be found in the Azure Portal, under App-Registration -> {AppName} -> Certificates & Secrets -> Secret Client Keys If no secret is stored there, create one
teamsEmailInvitationMessage
Type: String
Requires: teamsEnabled = true
The default invitation message which is send to the recipient's email address if desired
teamsEnabled
Type: Boolean
This setting controls whether the msteams functions are provided to the clients on the server side. The msteams tab in the settings dialog on the client is normally only visible when the enabled is switched on.
teamsImpersoAzureId
Type: String
Requires: teamsEnabled = true
The AditoImpersoAzureId which is found in the azure portal, under Users -> {AditoImpersoUsername} -> Profile -> ObjectId
teamsImpersoPassword
Type: String
Requires: teamsEnabled = true
AditoImpersoPassword is the password that is stored for the AditoImpersoUser
teamsImpersoUPN
Type: String
Requires: teamsEnabled = true
The AditoImpersoUser which is found in the azure portal, under Users -> {AditoImpersoUsername} -> Profile -> User Principal Name
teamsRedirectInvitationUrl
Type: String
Requires: teamsEnabled = true
The redirect URL specifies the URL to which the recipient is redirected if he accepts the invitation
teamsTenantId
Type: String
Requires: teamsEnabled = true
The tenantId which can be found in the Azure Portal, under App-Registration -> {AppName} -> Overview
telemetryExternalEnabled
Type: Boolean
Default: false
This setting controls whether the monitoring functions are provided on the server side.
telemetryExternalLoginTypeIds
Type: String[]
Sets the possible login types for use with the telemetry servlet. The currently supported login type is "internal.default". The authenticated user should have at least the role INTERNAL_TECHNICAL.
telephonyEnabled
Type: Boolean
Default: false
This setting controls whether the telephony functions are provided to the clients on the server side. The telephony tab in the settings dialog on the client is normally only visible when the telephony is switched on.
telephonyProvider
Type: String
Requires: telephonyEnabled = true
Name of the favourable as a clear string. This can also be set through the client.
usageStatisticsEnabled
Type: Boolean
Default: true
Enables usage statistics. If enabled, the server will send daily usage statistics to ADITO. Note that the usage statistics don't contain any user identifying information.
userdirectoryCacheEnabled
Type: Boolean
Default: true
Enables user cache on the server. Loads users faster in queries, but increases the memory footprint by loading users into the server's RAM.
userdirectoryCachePreloadEnabled
Type: Boolean
Default: true
Requires: userdirectoryCacheEnabled = true
This setting enables all users to be preloaded. Enabling this setting will load users faster but consume more memory.
userdirectoryCacheReloadMissingUsers
Type: Boolean
Default: true
Requires: userdirectoryCacheEnabled = true
This setting enables missing users to be immediately reloaded. Disabling this features uses periodically reloading to keep the cache up-to-date.
userdirectoryDbIgnoreCase
Type: Boolean
Default: true
This setting controls whether user queries for JDito are case-sensitive.
userSatisfactionSurveyEnabled
Type: Boolean
Default: true
This setting enables or disables the user satisfaction survey.
userSatisfactionSurveyUrl
Type: String
Requires: userSatisfactionSurveyEnabled = true
This expert setting allows the configuration of the user satisfaction survey url. The default value should be sufficient, but if something changes this setting can be used.
webserverPath
Type: String
The home directory for the internal seb server. This path is the data of the web server (for example, index.html, client.jnlp).
webservicesServerEnabled
Type: Boolean
Default: true
Enables webservices for server processes.
webservicesServerLoginTypeId
Type: String
ID of the login type used for webservices servers. This must be present in the loginList (in the security area).
whatsnewContentWebservicePassword
Type: String
Default: ``
Specifies the password that should be used for authorization of the what's new content webservice.
whatsnewContentWebserviceUrl
Type: String
Default: ``
Specifies the URL of the feedback webservice that's called when the user sends feedback. The feedback data that is send to the WS as a JSON e.g. var jsonResult = [ { version: "2023.0.2", name: "feature-1", content: "" }, { version: "2023.0.1", name: "feature-2", content: "" }, { version: "2023.0.1", name: "feature-3", content: "" } ];
whatsnewContentWebserviceUsername
Type: String
Default: ``
Specifies the username that should be used for authorization of the what's new content webservice.
whatsnewEnabled
Type: Boolean
Default: false
Specifies if the "What's new" feature should be enabled in the client. If set to false then the what's new button in the navigation bar won't be visible.
whatsnewFeedbackDisclaimerText
Type: String
Default: ``
Specifies which disclaimer text should be displayed above the feedback area. If nothing is specified then a default disclaimer text will be displayed. The text will be translated via translation files.
whatsnewFeedbackWebservicePassword
Type: String
Default: ``
Specifies the password that should be used for authorization of the feedback webservice.
whatsnewFeedbackWebserviceUrl
Type: String
Default: ``
Specifies the URL of the feedback webservice that's called when the user sends feedback. The feedback data that is send to the WS as a JSON e.g. { "user": "Tim Admin", "feedbackIdentifier": "whatsnew-1-dynamicTitlebar", "feedbackContent": "I love this feature", "serverVersion": "2023.0.1", "serverName": "default", "serverUniqueId": "dfcebf87-474f-4c2e-9c4c-138262287374", "licenseId": "_____COMMUNITY" }
whatsnewFeedbackWebserviceUsername
Type: String
Default: ``
Specifies the username that should be used for authorization of the feedback webservice.
whatsnewTitleText
Type: String
Default: ``
Specifies which title text should be displayed in the window. The current selected server version is always shown in the title followed by the titleText.
workflowEngineAlias
Type: String
Requires: workflowEngineEnabled = true
Sets the alias on which the workflow engine should be running.
workflowEngineEnabled
Type: Boolean
Default: false
Enable the workflow engine
workflowEngineLoginTypeIds
Type: String[]
Requires: workflowEngineEnabled = true
Sets the possible login types for use with the workflow service
workflowEngineUser
Type: String
Requires: workflowEngineEnabled = true
Specifies the user context in which to run a workflow engine servicetask
workflowModelerAlias
Type: String
Requires: workflowEngineEnabled = true
Sets the alias that holds the location where the modeler exists.
workflowTimerEventsEnabled
Type: Boolean
Default: false
Requires: workflowEngineEnabled = true
Enable workflow timer events
wunderbarEnabled
Type: Boolean
Default: false
Specifies if the WunderBar should be enabled in the client.