GXflow license scheme

The GXflow licensing scheme is very versatile, it adapts to the requirements of different companies and the production lifecycle of your inbox driven applications.

This document contains two sections. The first details the license types you may use and where to store them depending on your needs. The second is specific for users that are updating systems to GeneXus 15 Upgrade 8 or higher.

Licenses can be handled with two different methods or mechanisms, each storing licenses in different locations, depending on your needs. Two options are available: Native (default) and Protection Server.

The Native protection method is recommended when the application is installed on a Platform as a Service environment (PaaS) or on an environment that needs horizontal scalability; more than that, in most of those cases it is the only one that is suitable for those scenarios. Because of infrastructure and networking issues, this is also the one that is more easy to install and set up, especially in non-Windows servers (Linux, AIX, iSeries, etc).

The Protection Server protection method is recommended for development and testing stages, where licenses are shared for different prototypes and databases are temporary.

So, generally speaking, the Native is the one that is recommended for production environments and the Protection Server for prototyping.

GeneXus 15 Upgrade 8 features scalability, stability and usability improvements related to GXflow, specifically to GXflow license management. Licenses can now be stored in the database to improve scalability and ability to run in Platform as a Service (PaaS) environments and a new license manager has been introduced to easily handle the licenses no matter on what environment, operating system or DBMS you are running.