Resource wizard: Object type activation
|
Since 4.9
This functionality is available since version 4.9.
|
This part of object type wizard allows you to define behavior for Activation. This extends far beyond a simple definition of account being enabled or disabled.
Starting with version 4.8, midPoint contains GUI support for activation mappings. We can use predefined mappings (rules) for many interesting situations.
See also the following pages for more information:
Inbound activation mappings
The table contains the list of inbound activation mappings.
Figure 1. Empty inbound table for activation
Click Add inbound to add a new inbound activation mapping.
In the popup, specify the activation rule (predefine behavior), e.g. "Administrative status". Then configure details for mapping as appropriate for the activation scenario.
Figure 2. Popup for adding of new inbound activation mapping
|
Figure 3. Activation table with inbound mapping for administrative status
|
Each mapping also allows setting Lifecycle state.
This can be used during Simulations, e.g. specifying lifecycle state as Proposed will be used only to simulate the activation mapping, Draft disables the activation mapping etc.
Click Save mappings when done to return to the previous page from which you started the activation editor.
Outbound activation mappings
The table contains the list of outbound activation mappings.
Figure 4. Empty outbound table for activation
Click Add outbound to add a new outbound activation mapping.
In the popup, specify the activation rule (predefine behavior), e.g. "Administrative status" or "Disable instead of delete". Then configure details for mapping as appropriate for the activation scenario.
Figure 5. Popup for adding of new outbound activation mapping
|
Figure 6. Activation table with outbound mapping for administrative status and predefined mappings for 'Disable instead of delete' and 'Delayed delete' configuration
|
Predefined mapping configurations contain only one configuration step.
Figure 7. Predefined details configuration for 'Delayed delete'
Each mapping also allows setting Lifecycle state.
This can be used during Simulations, e.g. specifying lifecycle state as Proposed will be used only to simulate the activation mapping, Draft disables the activation mapping etc.
Click Save settings when done to return to the previous page from which you started the activation editor.
Configuration of resource wizard panels
Some wizard panels are configurable, for more information see Wizard panels.
How to Use Lifecycle States
You can use different lifecycle states for resources, object types, attributes, mappings, synchronization situations, and other aspects of resource configuration. You can use the lifecycle state property for simulations. Resources are created in the Proposed lifecycle state by default, and don’t work in normal deployment before switching the state to Active.
You can use the Proposed lifecycle state to test (simulate) the configuration without causing any damage to your target system data. When the simulation results are satisfactory, you can switch the lifecycle state to Active.
You can set different lifecycle states for various configuration items, which lets you put specific parts of configuration to production incrementally.
For example, after you switch your resource to the Active lifecycle state, you can add new mappings in Proposed lifecycle state first. You can simulate the new mapping safely and switch it to Active when it’s ready.
See also:
Limitations
Resource wizard has several limitations as of midPoint 4.8, such as:
-
expression editor supports
As is,Script,LiteralandGenerateexpressions only -
mapping ranges are not supported
-
mapping domains are not supported
-
correlation configuration currently supports only The
itemsCorrelator
midPoint resource wizard won’t be able to show or allow editing of these features but should tolerate them and keep them in the configuration.
Was this page helpful?
YES
NO
Thanks for your feedback