Page History

Servoy Application Servers that operate within a servoy Cluster can, for the most part be seen as normal Servoy Application Servers. This chapter describes the differences and the things to look out for.

Servoy Application Server instances that are part of a Servoy Cluster share the same Servoy Repository, databases and databroadcasting mechansism. 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.

...

Except for the useAjax setting on solutions and solutions itself, changes to the configuration of a Servoy Application Server instance are not broadcasted to the other Servoy Application Servers in the cluster. This means that configuration changes need to be applied to all Servoy Application Servers in the cluster manually.

Folder contents
Some The following folders under of the Servoy Application Server install should have the same content for all clustered servers:installation should be synced between all Servoy Application Server instances that are part of the cluster:

• <servoy>/application_server/beans
• <servoy>/application_server/drivers
• <servoy>/application_server/lafs
• <servoy>/application_server/plugins
• <servoy>/application_server/server/webapps/ROOT/servoy-webclient/templates

...

You can use a shared disk or (r)sync program for these folders, since you can modify them via WebDAV or admin page. Or you can keep them synced manually.

...