Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:application_configuration:dev:backend [2021/04/29 06:37] tomiskar [Entity events] |
devel:documentation:application_configuration:dev:backend [2021/06/07 18:09] 127.0.0.1 external edit |
||
---|---|---|---|
Line 63: | Line 63: | ||
idm.pub.app.stage= | idm.pub.app.stage= | ||
# Application instance / server id - is used for scheduler etc. | # Application instance / server id - is used for scheduler etc. | ||
- | # Should | + | # 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 | idm.pub.app.instanceId=idm-primary | ||
# global date format on BE. Used in notification templates, logs, etc. FE uses localization key ' | # global date format on BE. Used in notification templates, logs, etc. FE uses localization key ' | ||
Line 77: | Line 77: | ||
# Show role baseCode in frontend application for roles (table, role detail, niceLabel, info components, role select). | # Show role baseCode in frontend application for roles (table, role detail, niceLabel, info components, role select). | ||
idm.pub.app.show.role.baseCode=true | idm.pub.app.show.role.baseCode=true | ||
+ | # Rendered column in role table agenda. Comma is used as separator. Order of rendered columns is preserved as configured. | ||
+ | # Available columns: | ||
+ | # - name - role name info card with link to detail | ||
+ | # - baseCode - role base code (without environment) | ||
+ | # - environment - role environment | ||
+ | # - disabled | ||
+ | # - description | ||
+ | idm.pub.app.show.role.table.columns=name, | ||
+ | # Show role catalogue item code in role catalogue tree | ||
+ | idm.pub.app.show.roleCatalogue.tree.code=false | ||
# Number of items (pagination) in role catalogue tree in root level. Used on role select and agenda. | # Number of items (pagination) in role catalogue tree in root level. Used on role select and agenda. | ||
idm.pub.app.show.roleCatalogue.tree.pagination.root.size=25 | idm.pub.app.show.roleCatalogue.tree.pagination.root.size=25 | ||
Line 128: | Line 138: | ||
idm.sec.core.init.data.enabled=true | idm.sec.core.init.data.enabled=true | ||
</ | </ | ||
+ | |||
+ | === 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 '' | ||
+ | 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 '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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). | ||
+ | |||
+ | Bulk action is available for logged user with required authorities and permissions: | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
==== Jpa === | ==== Jpa === | ||
Line 468: | Line 496: | ||
# Thread priority for threads in event executor pool - 5 by default (normal). | # Thread priority for threads in event executor pool - 5 by default (normal). | ||
scheduler.task.executor.threadPriority= | scheduler.task.executor.threadPriority= | ||
+ | # Asynchronous task processing is stopped. | ||
+ | # Asynchronous task processing is stopped, when instance for processing is switched => prevent to process asynchronous task in the meantime. | ||
+ | # Asynchronous task processing can be stopped for testing or debugging purposes. | ||
+ | # Asynchronous task are still created in queue, but they are not processed automatically - task can be executed manually from ui. | ||
+ | idm.sec.core.scheduler.task.asynchronous.stopProcessing=false | ||
# Event queue processing period (ms). Period to read prepared (~created) asynchronous entity events from queue. | # Event queue processing period (ms). Period to read prepared (~created) asynchronous entity events from queue. | ||
# Events are processed in batch configured by property ' | # Events are processed in batch configured by property ' | ||
Line 606: | Line 639: | ||
idm.sec.core.event.asynchronous.enabled=true | idm.sec.core.event.asynchronous.enabled=true | ||
# Asynchronous event processing is stopped. | # Asynchronous event processing is stopped. | ||
- | # Asynchronous event processing is stopped, when instance for processing is switched => prevent to process | + | # Event processing is stopped, when instance for processing is switched => prevent to process |
- | # Asynchronous event processing can be stopped | + | # Asynchronous event processing can be disabled |
- | # Asynchronous events | + | # Events |
idm.sec.core.event.asynchronous.stopProcessing=false | idm.sec.core.event.asynchronous.stopProcessing=false | ||
# Asynchronous events will be executed on server instance with id. Default is the same as {@link ConfigurationService# | # Asynchronous events will be executed on server instance with id. Default is the same as {@link ConfigurationService# | ||
Line 654: | Line 687: | ||
* '' | * '' | ||
* '' | * '' | ||
+ | * '' | ||
Line 937: | Line 971: | ||
==== Provisioning global break ==== | ==== Provisioning global break ==== | ||
- | <note tip>For enable global provisioning break you must set configurations properties defined below, otherwise global provisioning break will not be active.</ | + | <note tip>For enable global provisioning break you must set configurations properties defined below, otherwise global provisioning break will not be activated.</ |
<code properties> | <code properties> |