Date: Fri, 29 Mar 2024 11:17:44 +0000 (UTC) Message-ID: <1461859980.11027.1711711064171@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11026_584971841.1711711064171" ------=_Part_11026_584971841.1711711064171 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Servoy Application Servers that operate within a Servoy Cluster = can, for the most part be seen as normal Servoy Application Servers. This c= hapter describes the differences and the things to look out for.
Servoy Application Server instances that are part of a Servoy Cluster sh= are the same Servoy Repository, databases and databroadcasting mechanism. T= he Servoy Application server is also aware of the clients connected to the = other servoy Application servers in the cluster. This means the following:<= /p>
Import of solutions into a Servoy Application Server connected to the Se= rvoy Cluster will broadcast to all connected Servoy Application Servers. Wh= en using the pre- and post import hooks ic.w. the Maintenance plugin, all o= perations performed by the Maintenance plugin will operate on the entire cl= uster.
All the Servoy Application Servers in the cluster need to connect to the= same set of databases. Although the connection settings might differ, the = physical database to which a Database Server connects needs to be the same,= otherwise the databroadcasting mechanism will work incorrectly.
Servoy Admin page Clients overview
The Clients overview page on the =
Servoy Admin page will show all clients connected to the cluster, not just =
the clients connected to the specific Servoy Application Server instance. T=
he Clients overview provides a link to toggle between grouping by Servoy Ap=
plication Server first, then solution or vise versa. Flushing clients, send=
ing messages and killing clients can be done on individual client level, pe=
r solution, per server or per solution per server.
The following things need to be taken into account when operating Servoy= Application servers within a Servoy Cluster:
Server plugins live on the server side. Each Servoy Application Server i= n the cluster will create and use an instance of the plugin. Unless specifi= cally build to operate within a Servoy Cluster (cluster-aware), the plugin = will only interact with it's Servoy Application server. Depending on what t= he plugin does this might be ok or not.
The RestfulWS plugin for example, which operates partly serverside, has = a serverside setting, detailing the maximum number of licenses used for han= dling concurrent requests. As the plugin gets instantiated on each Server A= pplication Server, this value is the maximum number per Servoy Application = Server.
When using 3rd party plugins, check with the vendor if the plugins suppo= rt operating in a Servoy Cluster.
A Servoy Application Server stores all of it's settings in the serrvoy.p= roperties file in <servoy>/application_server. When running inside a = Servoy Cluster, each Servoy Application Server instance still has it's own = servoy.properties file.
Many of the properties will have to have the same value, to provide the = enduser with a consistent behavior, regardless of which Servoy Application = Server they connect to.
Except for the useAjax setting on solutions and solutions itself, change= s to the configuration of a Servoy Application Server instance are not broa= dcasted to the other Servoy Application Servers in the cluster. This means = that configuration changes need to be applied to all Servoy Application Ser= vers in the cluster manually.
The following folders of the Servoy Application Server installation shou= ld be synced between all Servoy Application Server instances that are part = of the cluster:
To identify individual Servoy Application Servers when loggin onto the S= ervoy 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 identifie= r to each server. The value set for the INSTANCE system property shows up o= n the main page of the Servoy Admin page.
For example in servoy_server.sh/.bat add '-DINSTANCE=3DserverX' to the j= ava command. the text 'serverX' will appear on the Servoy Admin page.