Skip to main content
Jump to: navigation, search

Scout/Tutorial/3.7/Deploy to Tomcat

< Scout‎ | Tutorial‎ | 3.7

Wiki Home

Deploy a Scout Application to Tomcat

This page shows how to export and deploy your Scout application to a Tomcat webserver using the Scout SDK.

Install Tomcat

If you have not yet installed Tomcat please go to the Tomcat homepage. Then download and install Tomcat version 6 or 7 using the proposed default settings. Once you started the webserver you verify that its running by starting your browser with the address http://localhost:8080. Your browser should display some page similar as shown below.

Tomcat running.png

Export Scout Application to WAR File

In the Scout SDK perspective use the context menu 'Export to WAR file ...' on the server node as shown below.

Export to war contextmenu.png

This opens the WAR export wizard dialog

Export to war dialog.png

  • Product file: Server product to be deployed. This will usually be the production product (not the development product)
  • WAR file: Path to the webapps directory of your Tomcat installation followed by the WAR file name
  • Checkbox Overwrite existing WAR file: Replaces an existing WAR file (path, and file name as specified above)

  • Checkbox Include client application: Exports and packs the client application into the WAR file (see selection dialog below)
  • Client product to include: Client product to be included in the WAR file

Export to war client.png

In the screenshot above we've selected the SWT client (production product) to be included in the WAR

Restart Tomcat, View Application Home Page, Download Client

With autodeploy or restart of the Tomcat server we can access the application homepage under http://localhost:8080/documentApp/

Scout app homepage.png

By clicking on Download or the Scout client can be downloaded from the webserver. To start the client follow the steps described on the application home page.

Deploy to remote host

If your tomcat server is not at localhost, change the value server.url in the config.ini of the desired client e.g. ui.swt.production, like below:



Back to the top