Difference between revisions of "Appliance Proxy Server Upgrade"

From Swivel Knowledgebase
Jump to: navigation, search
m (1 revision imported)
(No difference)

Latest revision as of 12:52, 11 May 2017


This document covers the upgrade of the Swivel Proxy. for further information on the Appliance Proxy see the How To Guide Proxy Server.

When you upgrade to Swivel 3.8, you also need to upgrade the proxy of the Swivel appliance so that it is compatible with the new Swivlet/iPhone/Android provisioning process.

This article outlines the steps required to upgrade the proxy to the latest Swivel 3.8 compatible version.

Note: All Swivel appliances up to an including appliance build 2.0.12 have the old proxy and will need to be upgraded.


  • Command Line access to the Swivel appliance (Read the PuTTY_How_To_Guide);
  • WinSCP (Read the WinSCP_How_To_Guide for more information on how to use this with the Swivel appliance);
  • Scheduled downtime as the proxy will be replaced, thus causing connectivity issues for users attempting to connect via the proxy.

Obtain the latest proxy.war

Download the latest version of the proxy.war file from PINsafe software. You will need to extract it from the zip file before deploying.

Remove the current proxy

During this process you must ensure that Tomcat is running at all times. It must be running in order for the new proxy.war file to deploy successfully.

The first step is to remove the proxy that is currently installed upon the appliance. This can be performed in two ways:

1. Using PuTTY: Login to the command line of the appliance. Remove the current proxy.war file located in /usr/local/tomcat/webapps2/ using the following command:

[admin@primary ~]# rm /usr/local/tomcat/webapps2/proxy.war

2. Using WinSCP: Login to the appliance using WinSCP. Remove the current proxy.war file located in /usr/local/tomcat/webapps2/ . Navigate to the directory and right click on the proxy.war file. Select the delete option.

Check that the old proxy was removed successfully

The next step is to ensure that the proxy was removed successfully. Again, this can be performed in two ways:

1. Using PuTTY: Run the following command to ensure that the proxy/ folder has been automatically removed:

[admin@primary ~]# ls -l /usr/local/tomcat/webapps2/proxy/

If, after 20 seconds, the file has not been removed, you can run the following command to remove the directory manually:

[admin@primary ~]# rm -f /usr/local/tomcat/webapps2/proxy/

2. Using WinSCP: Refresh the directory /usr/local/tomcat/webapps2/ to see if the proxy/ directory has disappeared. If not the right click the proxy/ directory and select Delete.

Deploy the new war file

  • Copy the new proxy.war file to the appliance using WinSCP. Place it into the /usr/local/tomcat/webapps2/ directory. You should notice after refreshing the webapps2 directory that after 10 seconds or so, the new proxy/ directory will exist.


You should now be able to use the new proxy and you will find that it is compatible with the new features provided by Swivel 3.8.

Remember to perform this on both nodes of a HA pair.