Differences

This shows you the differences between two versions of the page.

--- devel:documentation:application_configuration:dev:backend [2019/02/05 09:44]
svandav [Workflow]
+++ devel:documentation:application_configuration:dev:backend [2019/04/26 10:00]
tomiskar
@@ Line 205: / Line 205: @@
 # older temporary files will be purged, default 14 days
 idm.sec.core.attachment.tempTtl=1209600000
+#
+# Max file size of uploaded file. Values can use the suffixed "MB" or "KB" to indicate a Megabyte or Kilobyte size.
+multipart.max-file-size=1Mb
+</code>
+In the application profile (application.properties).
+<code properties>
+#
+# Max file size of uploaded file. Values can use the suffixed "MB" or "KB" to indicate a Megabyte or Kilobyte size.
+multipart.max-file-size=1Mb
 </code>
@@ Line 389: / Line 402: @@
 # Thread priority for threads in event executor pool - 5 by default (normal).
 scheduler.task.executor.threadPriority=
-# Event queue processing period (ms). Default 1000ms.
+# Event queue processing period (ms). Period to read prepared (~created) asynchronous entity events from queue.
-scheduler.event.queue.process=1000
+# Events are processed in batch configured by property 'idm.sec.core.event.asynchronous.batchSize'. If you events are processed quickly (~provisioning on your environment is quick), then batch size can be higher or this property can be lower.
+# Default 500ms.
+scheduler.event.queue.process=500
 # Event executor core pool size. Uses CPU count + 1 as default.
 scheduler.event.executor.corePoolSize=
@@ Line 399: / Line 414: @@
 # Waiting events to be processed. Uses 1000 as default - prevent to prepare events repetitively and use additional threads till maxPoolSize. {@link LinkedBlockingQueue} is used for queue => capacity is initialized dynamically.
 # {@link AbotrPolicy} is set for rejected tasks.
-scheduler.event.executor.queueCapacity=1000
+scheduler.event.executor.queueCapacity=50
 # Thread priority for threads in event executor pool - 6 by default (a little higher priority than normal 5).
 scheduler.event.executor.threadPriority=6
@@ Line 419: / Line 434: @@
 idm.pub.core.identity.passwordChange=ALL_ONLY
 #
-# required old password for change password. Needed on FE (=> public)
+# required old password for change password.
+# Needed on FE (=> public)
 idm.pub.core.identity.passwordChange.requireOldPassword=true
 #
@@ Line 425: / Line 441: @@
 # true - change to IdM and all system
 # false - change to all system except IdM
+# Needed on FE (=> public)
 idm.pub.core.identity.passwordChange.public.idm.enabled=true
 #
@@ Line 430: / Line 447: @@
 # skipped in synchronizations - contract synchronization should be provided.
 idm.pub.core.identity.create.defaultContract.enabled=true
+#
+# Skip identity dashboard content - show full detail directly (link from table or from info component)
+# Needed on FE (=> public)
+idm.pub.core.identity.dashboard.skip=
 #
 # supports authorization policies for extended form definitions and their values for identities
@@ Line 497: / Line 518: @@
 # Asynchronous events will be executed on server instance with id. Default is the same as {@link ConfigurationService#getInstanceId()} (current server instance).
 idm.sec.core.event.asynchronous.instanceId=
+# Asynchronous events will be executed in batch - batch will be split for event with HIGH / NORMAL priority in 70% HIGH / 30% NORMAL.
+# If you events are processed quickly (~provisioning on your environment is quick), then batch size can be higher (in combination with higher 'scheduler.event.queue.process' property).
+idm.sec.core.event.asynchronous.batchSize=15
 </code>