Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
devel:documentation:application_configuration:dev:backend [2021/05/05 08:55]
tomiskar [Entity events] 		devel:documentation:application_configuration:dev:backend [2021/05/17 20:45]
tomiskar [Application/ Server]
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 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 idm.pub.app.instanceId=idm-primary
 # global date format on BE. Used in notification templates, logs, etc. FE uses localization key 'core:format.date'. # global date format on BE. Used in notification templates, logs, etc. FE uses localization key 'core:format.date'.
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, baseCode, environment, disabled, description
 # 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 136:
 idm.sec.core.init.data.enabled=true idm.sec.core.init.data.enabled=true
 </code> </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).
 +
 +Bulk action is available for logged user with required authorities and permissions:
 +  * ''CONFIGURATION\_UPDATE'' - configuration property contains instance for asynchronous processing will be changed => authority and ''UPDATE'' base permission for property ''idm.sec.core.event.asynchronous.instanceId'' is reguired.
 +  * ''SCHEDULER\_UPDATE'' - scheduled tasks and created (~ not processed) asynchronous long running tasks will be changed.
 +  * ''ENTITYEVENT\_UPDATE'' - created (~ not processed) asynchronous events will be changed.
 +
  
 ==== Jpa === ==== Jpa ===
  • by chalupat