Differences

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

--- devel:documentation:application_configuration:dev:backend [2021/05/05 08:54]
tomiskar [Bulk actions]
+++ devel:documentation:application_configuration:dev:backend [2021/05/05 09:08]
tomiskar [Application/ Server]
@@ Line 63: / Line 63: @@
 idm.pub.app.stage=
 # Application instance / server id - is used for scheduler etc.
-# Should be defined in property file only
+# Can be defined in property file only! Overidding via ConfigurationService is not possible for application instance (~ more instanceos on the same database)
 idm.pub.app.instanceId=idm-primary
 # global date format on BE. Used in notification templates, logs, etc. FE uses localization key 'core:format.date'.
@@ Line 128: / Line 128: @@
 idm.sec.core.init.data.enabled=true
 </code>
+=== Change server for asynchronous processing (switch application instance) ==
+@since 11.1.0
+Application instance (server) is used for asynchronus processing - for scheduled tasks, asynchronous long running tasks and events.
+Instance identifier can be defined in the application profile (application.properties) by property ''idm.pub.app.instanceId''.
+When we want to schedule and process asynchronous tasks and event on other instace (or when one instance shutdown), then we can switch processing by provided bulk action ''Change server for asynchronous processing'' in configuration agenda:
+{{ :devel:documentation:application_configuration:dev:switch-instance-bulk-action.png |}}
+Previous and new instance identifier is required as input parameters. All scheduled tasks and all created (~ not processed) asynchronous long running tasks and events will be moved from previous to new instance and will be processed on new instance (server).
 ==== Jpa ===
@@ Line 610: / Line 623: @@
 # disable / enable asynchronous event processing. Events will be executed synchronously, if it's disabled. Enabled by default.
 idm.sec.core.event.asynchronous.enabled=true
+# Asynchronous event processing is stopped.
+# Event processing is stopped, when instance for processing is switched => prevent to process instances in the meantime.
+# Asynchronous event processing can be disabled for testing or debugging purposes.
+# Events are still created in queue, but they are not processed.
+idm.sec.core.event.asynchronous.stopProcessing=false
 # 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=