Sodium Sync enables data synchronization between directory servers and other data sources such as files and databases.
On this page you can read about Sodium Sync's workflow capabilites. On other pages you can read about sync configuration and scheduling, Data Transformation Mapping and Merging, additional Sodium Sync features and Sodium Sync Conformance.
Simple syncs occur as independent events but more complex scenarios exist where it makes sense for syncs to have relationships to each other and to external events, for example:
- To sync data inwards from an external source before sending a sync outwards to multiple targets.
- Running a database report generation program to generate a file, prior to loading via a sync.
- Load in data, check its validity, and publish automatically via another sync if the checks succeed. It the checks fail, publication will not happen. This will ensure operator checking, and that the published data has always been checked.
This type of capability is referred to as 'Directory Replication Workflow'. The first feature to support this is Group Syncs. A sequence of syncs and checks can be grouped together, so that they are run in order and subsequent syncs will only run if the previous ones succeed. This can help with situations where data is brought in from multiple sources and then sent onwards. It can also bring in remote data, perform processes, and then only transmit onwards if a series of checks succeed. Configuration is shown below:
Sync Profile Group Configuration (click to show/hide)
This enables the definition of a new group and defines error handling proceedures. Groups are shown on the management screen and syncs in a group can be run independently or as a group.
The 'Hooks' tab in the Sync Profile Editor (below) enables the specification of commands to be run before and after a sync, allowing external processes to be integrated with the directory replication workflow.
Sync Profile Hooks (click to show/hide)