There are two methods for upgrading a server that has been deployed to Apache Tomcat.

For instructions on new installations for Tomcat, see Apache Tomcat Example Deployment.

Recommended Method

If you deployed the SOAtest and Virtualize Server using the method described in Apache Tomcat Deployment Example 1 (Recommended Method), use the following instructions to upgrade the WAR file.

1. Stop Tomcat Server and locate the <SOAVIRT_HOME> directory.
2. Copy config.properties file from <SOAVIRT_HOME>/WEB-INF directory to a temporary location.
3. Delete the following directories from <SOAVIRT_HOME>: 
   • apifiles
   • axis2
   • META-INF
   • WEB-INF 
4. Extract the contents of the new WAR file into <SOAVIRT_HOME>.
5. Replace config.properties file in <SOAVIRT_HOME>/WEB-INF directory with the config.properties file from step 2.
6. Open config.properties file and verify license configuration.
7. Start Tomcat (e.g., from <TOMCAT_HOME>/bin).
8. Browse to http://localhost:8080/ (adjust the port if needed). One of following messages confirms that the application was updated correctly:

Shortcut Method

If you deployed the SOAtest and Virtualize Server using the method described in Apache Tomcat Deployment Example 2 (Shortcut Method), use the following instructions to upgrade the WAR file.

1. Stop Tomcat Server and locate the <TOMCAT_HOME>/webapps/ROOT directory.
2. Save workspace folder to a temporary location.
3. Delete the "ROOT" directory from the webapps directory.
4. Rename the new "soavirt_<version>.war" file to "ROOT.war".
5. Copy "ROOT.war" into the <TOMCAT_HOME>/webapps/ directory.
6. Open config.properties file from <TOMCAT_HOME>/webapps and verify license configuration.
7. Start Tomcat (e.g., from <TOMCAT_HOME>/bin).

8. Browse to http://<host>:<port> and verify that the following message is displayed:

   There are no deployments on this server. Cannot respond to this request: /.

9. Stop Tomcat Server. 
10. Replace workspace folder with the workspace folder saved in step 2.
11. Restart Tomcat Server.
12. Browse to http://<host>:<port> and verify that one of the following messages appears: