Page History

...

Servoy Application Server instances that are part of a Servoy Cluster share the same Servoy Repository, databases and databroadcasting mechanism. The Servoy Application server is also aware of the clients connected to the other servoy Application servers in the cluster. This means the following:

Solution imports
Import of solutions into a Servoy Application Server connected to the Servoy Cluster will broadcast to all connected Servoy Application Servers. When using the pre- and post import hooks ic.w. the Maintenance plugin, all operations performed by the Maintenance plugin will operate on the entire cluster.

...

The following things need to be taken into account when operating Servoy Application servers within a Servoy Cluster:

Server plugins
Server plugins live on the server side. Each Servoy Application Server in the cluster will create and use an instance of the plugin. Unless specifically build to operate within a Servoy Cluster , each Servoy Application Server will instantiate an instance of the plugin(cluster-aware), the plugin will simply interact with it's Servoy Application server. Depending on what the plugin does this might be ok or not. All plugins that are shipped by default with Servoy will be instantiated on each individual Servoy Application server.

The RestfulWS plugin for example, which operates partly serverside, has a serverside setting, detailing the maximum number of licenses used for handling concurrent requests. As the plugin gets instantiated on each Server Application Server, this value is the maximum number per Servoy Application Server.

...