Differences

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

Link to this comparison view

Both sides previous revision Previous revision
tutorial:adm:systems [2019/05/13 06:57]
tomiskar
tutorial:adm:systems [2019/05/16 11:09] (current)
tomiskar
Line 17: Line 17:
   * **Virtual** - some systems can be managed via user tasks instead of direct communication. See the chapter about [[.:​modules:​virtual_systems|virtual systems]].   * **Virtual** - some systems can be managed via user tasks instead of direct communication. See the chapter about [[.:​modules:​virtual_systems|virtual systems]].
   * **Asynchronous provisioning** - if the provisioning is asynchronous for the system, all the data is stored in the queue and managed by appropriate scheduled task. [[devel:​adm:​scheduled_tasks|Long running task]] ProvisioningQueueTaskExecutor operates above the queue periodically and starts CREATED provisioning operation processing. Make sure you have **ProvisioningQueueTaskExecutor** configured, if you have some target system switched to use asynchronous provisioning. This is recommended option, since it significantly improves responsiveness of the application.   * **Asynchronous provisioning** - if the provisioning is asynchronous for the system, all the data is stored in the queue and managed by appropriate scheduled task. [[devel:​adm:​scheduled_tasks|Long running task]] ProvisioningQueueTaskExecutor operates above the queue periodically and starts CREATED provisioning operation processing. Make sure you have **ProvisioningQueueTaskExecutor** configured, if you have some target system switched to use asynchronous provisioning. This is recommended option, since it significantly improves responsiveness of the application.
-  * **Readonly** – Systems marked in this way allow data reading only and are either source systems in CzechIdM or systems which are controlled but provisioning of data to them is intentionally prohibited for some time. In the latter case, all provisioned data is sent to the provisioning queue. The provisioning queue and history is displayed by: Systems -> system detail (magnifying glass) -> Provisioning. See the chapter [[.:​audit|Audit]]. +  ​* **State** –  system states other than active: 
-  * **Inactive** – Inactive systems do not allow even reading ​operationsSystem can be disabled two ways: +    ​* **Readonly** ​- **with** provisioning queue – Systems marked in this way allow data reading only and are either source systems in CzechIdM or systems which are controlled but provisioning of data to them is intentionally prohibited for some time. In the latter case, all provisioned data is sent to the provisioning queue. The provisioning queue and history is displayed by: Systems -> system detail (magnifying glass) -> Provisioning. See the chapter [[.:​audit|Audit]]. 
-    * **with** provisioning queue - If provisioning to such a system is to take place, then the operations end up in a queue as in the case of Readonly systems. +    ​* ​ **Readonly** **without** provisioning queue – Systems marked in this way allow data reading ​onlyProvisioning operations are not saved into queue, cannot ​be executed again. IdM account is created only (uid attribute only). 
-    * **without** provisioning queue - Provisioning operations are not saved into queue, cannot be executed again. IdM account is created only (uid attribute only).+    * **Inactive** - **with** provisioning queue - Inactive systems do not allow even reading operations. ​If provisioning to such a system is to take place, then the operations end up in a queue as in the case of Readonly systems. 
 +    * **Inactive** - **without** provisioning queue - Inactive systems do not allow even reading operations. ​Provisioning operations are not saved into queue, cannot be executed again. IdM account is created only (uid attribute only).
 <note important>​ Attribute values of Inactive systems with provisioning queue is available **are** calculated in the provisioning log.</​note>​ <note important>​ Attribute values of Inactive systems with provisioning queue is available **are** calculated in the provisioning log.</​note>​
 ===== Configuration ===== ===== Configuration =====