Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
tutorial:adm:server_os_updates [2019/12/16 10:04] fiserp [Things to consider] |
tutorial:adm:server_os_updates [2019/12/16 10:17] fiserp [Things to consider] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * Impact on users | * Impact on users | ||
| * IdM is often deployed as a self-service portal for users. You should plan the downtime such that minimal number of users is affected. | * IdM is often deployed as a self-service portal for users. You should plan the downtime such that minimal number of users is affected. | ||
| - | * Users may make changes in the IdM that start some long running tasks (e.g. automatic roles changes). Those tasks are executed asynchronously and may be running even if the user, who started the task, already logged off. TODO | + | * Users may make changes in the IdM that start some long running tasks (e.g. automatic roles changes). Those tasks are executed asynchronously and may be running even if the user who started the task has already logged off. TODO |
| - | * Impact on IdM batch jobs | + | * Impact on IdM batch jobs (long running tasks - LRT) |
| + | * IdM has internal cron that schedules batch jobs. To make things safe, no job should be running when you are doing the update. The safest way to achieve this is to stop the IdM service before applying updates. | ||
| + | * Batch jobs run usually at night so it is not entirely necessary to stop the IdM, but you have to make sure you have enough time to perform the patching (and possible rollback) before the batch jobs start to execute. | ||
| + | * Restarting IdM cancels the LRT that was currently running, LRT **will not pick up automatically** after IdM goes up again. | ||