Differences from Conventional Workflows
The conventional Java-based real-time workflows operate between the Identity Store and a connected directory that represents the connected system. As a result, an additional connected directory, including channels for accounts, groups, members and passwords exists. This connected directory corresponds to a target system in the Provisioning view.
The following screenshot highlights these elements, which are located under the testLDAP node for this use case, as displayed in the DirX Identity Manager’s Connectivity Expert View.
For the approach described in this use case, we need the following items:
-
An Identity Store with two channel folders: one for the source tree (ContractStore in this use case) and one for the target tree (UserStore in this use case). This configuration corresponds to the requirement that both the source and the target are the Identity.
-
A synchronization workflow that is applicable for dxm.event.ebr instead of dxm.request.provisionToTS.
The following screenshot shows the ContractStore and UserStore subtrees in DirX Identity Manager’s Connectivity view (Expert View).
