Navigation: » No topics above this level«
Integration and authentication
Bizagi PaaS is a secure, scalable and reliable subscription-based offer, which provides all of the power of the Bizagi Digital Business platform directly in the cloud. When modeling your applications, you can integrate them with different services or connect them to your corporate systems.
Among these different services or corporate systems, you can consider integrating or connecting with:
•Service-oriented systems offering web services.
•Document management systems or Enterprise content managers.
•Other general applications and cloud services.
For more information about using integrated authentication in Bizagi so that you can rely on your own identity providers, refer to Identity managers.
In general, there are two possible approaches to achieve application level integration:
1. Connecting to systems and services which are cloud-ready, while implementing security protocols and standards to protect transmitted data.
These should expose web services which are accessible through the internet (e.g. residing in a DMZ).
oThis alternative is recommended, especially as it follows a service-oriented architecture.
oFor this alternative, there are no specific requirements in Bizagi, but you will need to ensure that services you integrate with Bizagi PaaS follow best security practices. Recall that Bizagi PaaS is available via the HTTPS protocol which encrypts the communication channel; and therefore it would be expected for your service to be available via HTTPS as well.
oConfiguring endpoints of integrated services is done throughout the different Bizagi features, depending on the type of service you are integrating to (e.g. the endpoint for email service is set as an environment parameter of your Bizagi project, whereas endpoints of web services are defined while using Bizagi's Web services connector at each integration point).
2. Connecting to on-premise applications, servers, or systems of record by means of a secure VPN.
Wherever the first alternative is not feasible, you may rely on a VPN to establish a point-to-point integration between Bizagi Engine and your system.
For more information about this alternative, refer to Setting up a VPN.
Consider as cloud-ready, systems and services which are either cloud-native, cloud-enabled or simply published for access through a public channel such as internet.
This means basically a service which has an HTTP/HTTPS (the later preferred) endpoint.
Bizagi provides programmatic access to the processes functionality and to the business information underlying your data model, by providing a powerful service-oriented API which is ready-for-use for every Bizagi project.
You can rely on Bizagi API, whenever there is the need to integrate Bizagi with any of your existing systems or applications (i.e. you can fire new process instances, trigger business events in them, cancel them, get reports, or simply update business information, among other things).
Bizagi API features a SOAP compliant, message-oriented, comprehensive set of web services with convenient and easy-to-use methods, which support WS-Security and other features and standards.
To learn more about this API, refer to the standard functionality described at Bizagi Help documentation.