Date: Thu, 28 Mar 2024 23:33:57 +0000 (UTC) Message-ID: <857229301.10815.1711668837276@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10814_1264531639.1711668837276" ------=_Part_10814_1264531639.1711668837276 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Servoy Application Server is the heart of the deployment con= figuration in most deployment scenarios. In case of stand alone deployment = using the Servoy Runtime Cl= ient and in case of WAR D= eployment, Servoy Application Server installation with the embedde= d tomcat is not utilized .
WAR deployment must be used for NGClient deployment and requires a = J2EE standards compliant application server to be= installed (for example Tomcat). From Servoy 8 on this is the more preferre= d way of deployment.
When deploying on premises or as a service, either on dedicated hardware= or in the cloud, the Servoy Application Server is the core of the deployme= nt configuration.
So Servoy Applicaton Server that you can install from the installer is a= the Servoy Server Runtime with an embedded tomcat build in, a War deployme= nt is the Servoy Server Runtime but then without the embedded tomcat.
This chapter discusses all aspects of the Servoy Application Server as a= standalone deployment or as the Servoy Server Runtime deployed as a WAR on= a J2EE Application server.