Servoy 2020 Documentation
Child pages
  • Operating Servoy Application Servers in a Cluster

Versions Compared

Old Version 12

changes.mady.by.user Paul Bakker

Saved on

compared with

New Version 13

changes.mady.by.user Paul Bakker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

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.

Client Licenses

  • Client licenses: the same Client License key needs to be installed on every Servoy Application Server. It will work as if the cluster uses this license, allowing a number of clients to be connected per cluster, not per Servoy Application Server.
  • CPU licenses: each Servoy Application Server requires it's own CPU License key

Folder contents
The following folders of the Servoy Application Server 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
Tip

To identify individual Servoy Application Servers when loggin onto the Servoy Admin page, an an INSTANCE system property can be set in the wrapper.conf or servoy_server.sh/.bat of each server, to provide a unique identifier to each server. The value set for the INSTANCE system property shows up on the main page of the Servoy Admin page.

For example in servoy_server.sh/.bat add "-DINSTANCE=serverX" to the java command. the text "serverX" will appear on the Servoy Admin page.