Rather than redeploy the VM Access Proxy, you can replace several files to upgrade it. You may find this more convenient than redeploying the appliance if you are using an SSL certificate issued by a certificate authority, or have applied other security updates to the base OS, for example.


Note: The VM Access Proxy 2.11 uses updated versions of Linux, Java and other underlying technologies. As such, there is no upgrade available between earlier versions and 2.11.


Preparing the VM Access Proxy


Make sure to take a snapshot before attempting these instructions. Many of the commands used can be typed incorrectly without an error message being thrown.


  1. Login to the VM Access Proxy using a console connection.

    username
    : vcommander
    password: gRHrB211

  2. Issue the command, enter the password again when prompted:

    sudo -s

  3. Issue the commands:

    /etc/init.d/tomcat7 stop
    rm -rf /var/lib/tomcat7/webapps/RemoteAccess*

    rm -rf /etc/tomcat7/config.properties
    rm -rf /etc/tomcat7/server.xml

    service ssh start

These commands delete the files you will be replacing, and turns on SSH so clients can connect and copy over the replacement files. Leave the conole connection open as you will use it to finalize your changes in a moment.


Preparing the Upgrade Files


  1. Download the appropriate update package offered in the Files section at the end of this article. 
  2. Extract the zip file to the computer from which you'll connect to the VM Access Proxy using one of the client methods described below. There will be three files:
    • RemoteAccess.war
    • server.xml
    • config.properties
  3. Upload the files to the VM Access Proxy using either Filezilla or WinSCP as described below.


Uploading with Filezilla


Filezilla is a free, open source FTP client that also supports secure copy. Download and install Filezilla and complete the steps below.


  1. Under the File menu, choose Site Manager.
  2. Click New Site and name it VM Access Proxy.
  3. Enter the hostname or IP address of the VM Access Proxy in the Host field.
  4. Choose SFTP - SSH File Transfer Protocol from the Protocol menu.
  5. Choose Normal as the Logon Type.
  6. Enter the Username (vcommander) and Password (gRHrB211).
  7. Click Connect.
  8. If you are using the VM Access Proxy's self-signed certificate, you will receive a warning that the connection is untrusted. Check Always trust this host, add this key to the cache and click OK.

  9. Enter /home/vcommander/ in the Remote Site pane.
  10. Copy the replacement files from the upgrade package to the VM Access Proxy.


Uploading with WinSCP


WinSCP is a free, open source secure copy client for Windows. Download and install WinSCP and complete the steps below.


  1. Choose SFTP as the File protocol.
  2. Enter the hostname or IP address of the VM Access Proxy in the Hostname field.
  3. Enter the Username (vcommander) and Password (gRHrB211).
  4. Click Login.
  5. When presented with the authentication banner, click Continue.



  6. Browse to /home/vcommander/.
  7. Copy the replacement files from the upgrade package to the VM Access Proxy.


Finalizing the Upgrade


  1. Return to the console connect and issue the following commands:

    cp /home/vcommander/RemoteAccess.war /var/lib/tomcat7/webapps/RemoteAccess.war
    cp /home/vcommander/server.xml /etc/tomcat7/server.xml
    cp /home/vcommander/config.properties /etc/tomcat7/config.properties


  2. Restart the VM Access Proxy appliance. The changes will take effect upon restart, and the SSH service will be stopped as before.
  3. Login to vCommander and browse to Configuration > System Configuration > Integrations.
  4. Click Edit on the VM Access Proxy section.
  5. Click Test and confirm the version information returns correctly
  6. Click OK.


You can confirm the operational status of the VM Access Proxy by browsing https://your.proxy.address:8443/RemoteAccess/details. The version, status, and capabilities are all displayed, as below.


Files