Message-ID: <1884016894.86003.1711630853815.JavaMail.wiki@ip-172-26-1-188> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_86002_399471106.1711630853813" ------=_Part_86002_399471106.1711630853813 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
DBSync is a proven integration platform. It facilitates integration - be= tween various legacy systems, services, processes, business partners and da= ta - to provide value and improve performance. DBSync manages communication= , data translation and process interactions among various connected applica= tions.
Businesses and organizations define business processes and use DBSync's = platform to synchronize their data between two or more databases and/or app= lications.
Processes use Connectors to connect to different databases and applicati= ons through "Extract, Transform, and Load" - ETL.
The typical architecture of the DBSync's platform is as shown in the ima= ge below:
The following table lists core components or ingredients of the DBSync's= platform. These components are related to the ETL concepts, as shown in th= e aforementioned image, to help readers attain an in-depth understanding of= how the whole platform works.
Component |
Description |
---|---|
Project |
A Project is a set of Connectors, Processes, = Workflows and Mappings, which collectively solves a business integration re= quirement. |
Process |
A Process is a combination of Control flow an= d data flow that is required to build a complete integration logic. A Proje= ct can have more than one process. |
Workflow |
A Workflow is a combination of Trigger, Rule,= and one or more map. By default, any workflow will have a start-stat= e and an end-state. |
Connectors |
Connectors are modules that encapsulate all t= he necessary protocols and logic to effectively communicate with the endpoi= nts. |
Trigger (Extract) |
The process of extracting information from on= e Database/Application to be used in another is known as the "Extract" proc= ess. |
Map (Transform) |
The process of transforming data, after it ha= s been extracted, so that it can be read from one database/application (Eg:= Salesforce) and understood by another database/application (Eg: QuickBooks= ), is known as "Transform". |
Rule (Load) |
The process of loading the transformed data s= o that it can be read in the new Database/Application is known as the "Load= ". |
Update Source |
Update Source provides a feedback loop from t= he Rule and are used to notify Source Applications. |
Template Library |
Contains pre-defined Projects with default ma= ppings for integrating applications such as Salesforce and QuickBooks etc.<= /p> |
Scheduler |
Allows user to schedule the processes in Proj= ects to run at scheduled intervals. |