Navigation: » No topics above this level«
Bizagi provides a powerful technology for a data-level integration approach known as Data Virtualization and Data Replication.
Using this approach, existing data structures (i.e, tables or views) from an external data source can be seamlessly synchronized with the data model in Bizagi.
This allows you to reuse data structures and information from systems which do not have service-oriented architecture (i.e, legacy systems); it allows you to avoid having islands of information and incurring in administration overhead when keeping information synchronized throughout multiple sources.
You can rely on these benefits while also having Bizagi automatically manage integrity of underlying transactions (i.e, rollbacks when needed).
The following image illustrates the concept of Data Virtualization and Data Replication, while highlighting that the main difference between these two, is that Data Replication works only in one way (synchronizing data periodically and offline, from your external data source into Bizagi), while Data Virtualization happens on-demand, whenever data needs to be updated from the extenal data source into Bizagi, or viceversa.
Consider the following, when planning to use Data Virtualization or Data Replication with Bizagi PaaS:
1. VPN connectivity.
Given that Bizagi PaaS is a cloud service, it supports integration with systems which offer a public endpoint.
When planning to have Bizagi PaaS target your external data sources, you will need to setup a VPN with Bizagi PaaS.
This is because your external data sources are not bound to offer a public endpoint (typically using HTTPS) but offer a TCP connection instead.
To learn more about a VPN and its requirements, refer to Integration using a VPN.
2. Performance assessment.
When having Bizagi PaaS, access an external data source via a VPN over the internet, its communication will inherently depend upon factors such as: A higher latency in data transmission, fluctuations, interference and congestion affecting the speed of the channel, or the quality of the networks used during transmission, among others.
All of these factors are beyond Bizagi PaaS control, and they can affect your overall end user's experience.
Therefore, you will need to mitigate them, consider them during your business applications' design, and gauge them in runtime.
We recommend you to:
•Ensure you choose a Bizagi PaaS data center whose location offers best latency when communicating with your premises.
•Design your user interfaces according to best practices in terms of usability and performance, especially when using this technology (e.g, by using filters, by displaying an adequate number of rows and columns in tables, etc).
For details about best practices when designing forms, please refer to http://help.bizagi.com/bpm-suite/en/index.html?what_to_avoid_in_forms.htm.
•Evaluate beforehand (e.g. test by carrying out a PoC) whether the performance impact of using this technology in a cloud architecture is appropriate for the requirements of your business applications.
To do this, consider variables such as the volume of data being exchanged with your on-premise data source.
In scenarios where you determine that this technology does not fit your needs, then it is best that you offer a service layer on top for your external data sources.
Recall that it is always a best practice and recommended approach to rely on a service-oriented integration, as described at Application integration.
3. Technical requirements.
Your external data source and its tables or views that you plan to integrate through this technology, need to comply to certain requirements.
For complete detail about how to configure this feature or to learn about the requirements needed, refer to http://help.bizagi.com/bpm-suite/en/index.html?integrating_data.htm.