Skip to main content

Sync Data

Synchronizing data into Fischer is the process through which connected system data is introduced into Fischer so Fischer can take action.


Synchronizing Data

The Sync Data is essential and a pre-requisite to multiple features.  The features that requires Sync Data to be in place inside of Fischer's SYNC_* schema are Compliance Assessments and Re-certification as well as The Load User Feature.  The data imported into Fischer will vary depending on the target systems, however Fischer provides a normalized schema that can be used to ensure that the synchronized data is introduced to Fischer is a standard format.  This abstraction helps maintain a consistent data model inside of Fischer.  Fischer exposes the Provisioning Hub to map attributes from connected systems.  Once the attributes are mapped to the Provisioning Hub schema, various Fischer features can consume the data.  It is important to understand the Provisioning Hub Schema before continuing this guide.


How to Synchronize Data Into Fischer's Provisioning Hub Schema

The process of importing or synchronizing data into Fischer's SYNC_* schema is done via workflows.  The common workflow (SyncImport), which writes all transactions to the SYNC tables of the database, is auto-deployed and available for immediate use to be chained from the export synchronization workflows.  Below is a visual breakdown of how the connected system "Sync Workflows" are constructed and which data elements matter when building and executing the workflows to which will synchronize data into Fischer for further processing.

Before running a compliance assessment process, current data is exported from each target connected system that was used in the IdM Suite (by running synchronization workflows) and populated to the SYNC tables (SYNC_USER_PROFILE, SYNC_USER_ACCOUNT, and SYNC_USER_ENTITLEMENT respectively) in the database. These tables represent the current or actual data.


SynchImport

Note that Fischer will provide the relevant SyncImport workflow out of the box. The version of the workflow will be dependent upon which database was used during the product installation. IGA Administrators would need to write the actual export workflow from the Connected Systems and then chain to the SyncImport workflow to populate the tables required for Fischer's Compliance feature to function. Refer to Configuring Compliance for more details pertaining to the mechanics of the Sync process and how to modify it to meet your specific data requirements.


Each Sync Workflow will be different to some extent depending on the Connected System's schema and the information required to be loaded into Fischer to properly build an account and/or entitlement association with an Identity.


This next section will break down the pre-deployed SyncImport workflow.  This will be the first step to understanding what the Sync data model is required to properly load the SYNC_* schema.  The pre-deployed SyncImport workflow is constructed as follows:

The Studio View Description of Each Tasks Responsibility

*The beginning object for all workflows will be "Start"

Workflow Object Description
System_Logic_PH This provisioning hub is the object that contains the data mapped from the connected-system-specific parent (export) workflow that chained to SyncImport




System Logic Data Mapper This data mapper is responsible for executing any logic required to build the required data model (payload) that will be sent INSERTED into the SYNC_* schema.




SYNC Load_PH This provisioning hub is responsible for receiving the output of the System Logic data mapper and passing the data payload to the final SYNC Load data mapper. At this point, the inbound data from the connected system has been properly formed to be INSERTED




SYNC Load Data Mapper The SYNC Load data mapper is responsible for mapping the final provisioning hub attributes to the SYNC_* table attributes. Once this task executes, Fischer's SYNC_* schema will be populated.




IdMDatabase This is the connected system plug in that integrates with the IdMDatabase. For the SyncImport workflow the INSERT statement is built to INSERT records into Fischer's SYNC_* table schema. This will import the data (that started in the connected system) into the Fischer schema so it can be used to perform Compliance assessments and/or loading Identities into the Fischer product.











Was this article helpful?