...

NOTE: You should not use the Servoy application server (the tomcat we ship) as your target for your WAR. This can result in errors and weird behavior because then 2 application servers are running at the same time in the same space that is not separated from each other. Two war deployements on the same server should be fine (they are separated by tomcat) you only have to make sure that the rmi ports are then different if you enabled rmi/smartclients.

NOTE: NGClient needs the support of websockets and then the java implementation that is based on: JSR-356. For example Tomcat supports this from 7.0.43 and higher and Jetty from 9.1

Benefits

The benefits of the WAR export option are:

...

When upgrading an existing WAR deployment, make sure to use the exact same context, otherwise when the WAR file gets deployed, it doesn't update the existing deployment, but instead deploys the WAR as a new application under the new context.

Application server support

The Servoy Application Server can be deployed as a WAR file on any J2EE standards compliant application server. These include for example JBoss, IBM WebSphere, Apache Tomcat and Glassfish.

The WAR deployment of the Servoy Application Server is actively tested by Servoy on:

• Apache Tomcat
• IBM WebSphere
• GlassFish
• Jetty

NGClient needs the support of websockets and then the java implementation that is based on: JSR-356. For example Tomcat supports this from 7.0.43 and higher and Jetty from 9.1
NOTE: You should not use the Servoy application server (the tomcat we ship) as your target for your WAR. This can result in errors and weird behavior because then 2 application servers are running at the same time in the same space that is not separated from each other. Two war deployements on the same server should be fine (they are separated by tomcat) you only have to make sure that the rmi ports are then different if you enabled rmi/smartclients.

Trouble Shooting

Admin page not accessible

...