Requirements

According to the requirement specified in CR 25787, there is a customer-specific contract or ticket store that should act as the source for synchronization to the DirX Identity user store. Synchronization should be started by TOPIC_USER_CHANGE events. For example, if a new contract is added, the workflow should be started via the TOPIC_USER_CHANGE event; the workflow then copies the contract object to the user tree, allowing for a complex mapping scheme to be applied.

This approach has two requirements:

  • The workflow should synchronize objects inside the Identity Store; that is, both the source and the target are the Identity Store. The source objects reside in a source subtree and the target objects reside in target subtree.

  • The workflow should be started via a dxm.event.ebr event.

The following figures illustrate the configuration of the workflow and its join activity.

Real-time Synchronization Workflow Components
Figure 1. Real-time Synchronization Workflow Components
Real-time Synchronization Workflow Join Activity
Figure 2. Real-time Synchronization Workflow Join Activity