Differences for Bizagi PaaS and on-premises implementations (v 11.1)

<< Click to Display Table of Contents >>

Navigation:  » No topics above this level«

Differences for Bizagi PaaS and on-premises implementations (v 11.1)

Overview

Bizagi PaaS is a Platform as a Service offering that provides all the power of the Bizagi Digital Business platform directly in the cloud.

This means that with Bizagi PaaS, customers get to use Bizagi digital business platform, using its powerful capabilities, plus the system architecture enhancements and optimizations that are precisely built for the cloud.​

 

Within its powerful capabilities, Bizagi PaaS offers that same core principles which trademark and are characteristic in Bizagi; such as: collaborative modeling centered in the business, a build-once-and-execute-anywhere paradigm with a WYSIWYG approach for UI, no need of programming, and re-usability of rules, forms, or the data model components, among others.

In terms of the complete list of features, the same comprehensible set of them are available in Bizagi PaaS, save some exceptions regarding features for integration with other systems.

 

This section presents the differences related to the use of integration features in Bizagi PaaS, when compared to on-premises implementations.

 

CATEGORY

FEATURE

OPTIONS & PARAMETERS

OBSERVATIONS

Identity and access Management and Authentication

Runtime authentication

(refer to Authentication below)

Azure AD

Supported.

Bizagi

Supported.

OAuth

Supported.

Federated

Supported.

LDAP

Supported.

Requires VPN setup.

Windows

Not supported.

Mixed:

Windows + Bizagi

Not supported.

Custom

Not supported.

Mixed:

Custom + Bizagi

Not supported.

Importing users from LDAP

Via LDAP protocol.

Supported.

Requires VPN setup and performance considerations.

Data integration

Replication

(refer to Replication below)

MS SQL Server

Supported

(same on-premises SQL Server versions supported).

Requires VPN setup and performance considerations

Oracle

Not supported.

Custom (other DBs)

Not supported.

Virtualization

(refer to Virtualization below)

MS SQL Server

Supported (same on-premises SQL Server versions supported).

Requires VPN setup and performance considerations.

Oracle

Not supported.

Custom (other DBs)

Not supported.

Application integration

Service-based

WS Connector

Supported.

Bizagi Connectors

Supported (preferred)

ECM integration

 

Supported if cloud-ready.

(same on-premises ECM products supported).

If not cloud-ready requires VPN setup and performance considerations

Point-to-point

SAP Connector

Not currently available.

Component library (view topic below)

Supported, though cloud-inherent restrictions apply.

Custom Jobs

Supported.

Others

Widgets

Supported.

Using Bizagi from external applications

Bizagi SOAP Web services API

Legacy Web services

Supported though it is encouraged to use OData services instead. It is preferable to use WS-Security Web services in case that OData services are not applicable.

WS-Security Web services

Supported though it is encouraged to use OData services instead.

Bizagi Web parts

SharePoint Web parts

Supported for SharePoint online.

SharePoint on premises requires VPN setup and performance considerations.

Web parts for any portal

Supported if cloud-ready

(same on-premises portal products supported).

If not cloud-ready requires VPN setup and performance considerations

Email services

Email server

Via SMTP protocol.

Supported.

Bizagi Cloud includes its own email service. Customers need to adjust settings in Bizagi Studio and Management Console provided by Cloud Operations.

Email integration in forms

Exchange

Supported.

POP3

Bizagi Cloud includes its own email service. Customer needs to adjust settings in Bizagi Studio and Management Console.

IMAP

Bizagi Cloud includes its own email service. Customer needs to adjust settings in Bizagi Studio and Management Console.

Others

Database configuration

ODS

Not applicable due to infrastructure differences.

Columns level encryption

Not available.

Utilities and resource kits

Management Console

Supported via Web UI.

Certain options which handle servers and clusters are not applicable, as well as others regarding configuration of underlying infrastructure.

Automatic Testing

Supported in the Development environment only.

Bizagi Diagnostics

Not available.

Deployment

One-click Deployment

Not applicable due to infrastructure differences.

Advanced Deployment

Deprecated: superseded by the Export bex feature to deploy in cloud environments.

Hidden features

Archiving

Not applicable.

Analytics data store

Deprecated: superseded by Datasets (cloud feature).

Special keys in the web.config file

Deprecated (no longer supported).

CSS or JS overrides

Deprecated (no longer supported).

 

note_pin

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.

 

VPN setup

With Bizagi PaaS, it is entirely optional to use a VPN and it would be needed for integration purposes (i.e. integration with LDAP, DB sources via Replication or Virtualizationn, ECM not cloud ready, or integrations with systems of record), whenever the applications you want to integrate with, do not offer a service-oriented architecture and use different protocols other than HTTP/HTTPS.

We encourage you to expose all your systems in a demilitarized zone, where Bizagi could integrate without the need of a VPN.

 

A VPN setup adds an additional cost to the subscription costs.

 

For more information about VPN setup, refer to Cloud VPN.

 

 

Authentication: Bizagi PaaS supports integrating with Identity Management services such as the Open ID Connect protocol. The following authentication methods are supported:

oAzure Active Directory (Azure AD)

oLDAP (this integration requires VPN setup)

oBizagi.

If you have any other authentication method, it must be analyzed. For more information refer to Identity managers.

 

Virtualization and Replication

Data Virtualization and Replications entails some aspects you will need to consider. When integrating an on-premise data source via data Virtualization, Bizagi PaaS will connect to it through its assigned TCP service port, and therefore, you will need a VPN to allow such communication and to implement it with due hardened security measures.  

Access to an external data source over the internet, inherently depends upon different factors which are beyond Bizagi PaaS' control, such as: a higher latency in data transmission, fluctuations, interference and congestion affecting the speed of the channel, the quality of the networks used during transmission, etc. All of these factors may affect the overall user experience, and therefore, you will need to mitigate them. Refer to Data virtualization.

 

Component library

Supported, through consider that you are solely responsible of the code developed in custom components added through this feature.

This entails: watching after an adequate performance while ensuring that locks or issues are not generated, being accountable for uploading secure code, and ensuring that such code is thoroughly tested throughout the different environments, among others.

 

Consider that components must be self-contained (i.e, all libraries needed by a component must be uploaded via the component library). This means that a component may not rely on driver, DLL, file in general, or connectivity setup that needs to be installed separately into the local machine.

 

Recall that Bizagi PaaS, as a cloud-centric architecture, is built for scalability among other pillars.

A high scalability in Bizagi PaaS considers that computing power, storage services and other capabilities, are made available on-demand as elastic resources which operate behind a load balancer, and therefore, point-to-point integrations which demand the installation of a component in a specific location is not a best practice.

For this reason, it is important that when integrating your systems and services you can follow modern and service-oriented principles such as using Connectors when applicable.

For more info refer to Bizagi Connectors.

 

Deployments

Deployments in cloud environments are performed differently than in on premises projects. Neither one-click-deployment nor Advanced deployment are used.

Please ensure that Customers are familiarized with the cloud-based deployment process described in this article: Export to Cloud.

This understanding is vital to guarantee  the continuous improvement in migrated projects.

 

New URLs

One lingering question is how the transition to Bizagi PaaS will affect an organization’s URLs. Once your application is running in Bizagi PaaS, each environment will have separate resources which translate into an independent URL, as described below.

Test environment: http://test-projectname-company.bizagi.com

Production environment: http://projectname-company.bizagi.com

 

If the customer uses the mobile application the project's URL should be updated as well, using the same URLs for desktop access.

 

It is necessary to inform this change to the customer's organization with due time.

 

Case links

Your SMTP configuration needs to be changed to adapt to Bizagi PaaS setup. The Cloud Operations team will send you instructions to adjust the SMTP server information in all your environments.

 

Users and access rights

Moving to Bizagi PaaS will require the creation and delegation of users to be administrators of the subscription. These users will be able to monitor resources, and make the actual deployments to the Testing and Production environments.

All end users should have their own unique email. Email duplicates are not supported in Bizagi PaaS.

Users and groups will be exactly the same as in on premise application. No additional configuration is required.

It is highly recommended that customer's administrators take the cloud administration training course, prior to the migration to Bizagi PaaS.

 

About performance considerations

For those features where there are performance considerations, you will need to take into account certain aspects relevant to your network communications, application design, testing and tuning overall. This applies when connecting to on-premises systems via a VPN.

Given the nature of a cloud-based service where the communication from your premises to the cloud inherently depends upon factors which are beyond Bizagi PaaS' control (such as a higher latency in data transmission, fluctuations, interference and congestion affecting the speed of the channel, the quality of the networks used during transmission, etc), you will need to make sure that the use you give to certain features is appropriate for the specific requirements of your applications.

 

About service-based integration

Recall that it is strongly recommended to rely on a service-oriented architecture in order to make the most of your Bizagi PaaS implementation.

The VPN alternative is strictly optional and furthermore, it is not the recommended option.

Through a best practice such as a service-based integration, you achieve greater maintainability and scalability among others, and also promote a better system architecture over the one entailed in point-to-point communications.