Child pages
  • WAR Deployment

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Servoy Developer (6.1 and later) offers the option to export the Servoy Application Server to a so-called WAR file . This WAR file can then be deployed on any J2EE standards compliant application server, like Glassfish IBM WebSphere Jetty or Apache Tomcat for example.

...

  • Still requires a servoy_repository database connection to operate
  • Can run all the different types of Servoy Client
  • Has the full Servoy Admin page, except for the Library Upload functionality
  • Solutions can be imported through the Servoy Admin page

 

Info
titleDatabase connections and .war deployment

The needed database connections (including the repository server DB connection) have to be operational (so already started) before deploying the .war file. This is not much different from a normal application server where you would also need the repository connection operational before starting the server.

If for some reason the .war deployment failed and you cannot access your solution/admin page as expected please check the J2EE server's log files as well as any relevant log files in (user_home_dir)/.servoy/... For example a repository version in the repository DB that is incompatible with the version of Servoy the .war was built on could generate this problem.

Creating a WAR export

The WAR export functionality is exposed in Servoy Developer through the Export menu (File > Export > Servoy > Export War File). This launches a wizard containing the following steps:

...