This section describes how to update In this section:

Upgrading to a New Version

New versions install in their own version subdirectory. Any specific configurations related to usage are handled in the workspace. Run the new installer and update your workspace as necessary.

Updating with a Service Pack

This section describes how to update your existing installation with a service pack.

From the UI

You can install a service pack from a public or internal update site.

Public Site

Choose Help> Check for Updates. Eclipse will check for updates.
If updates are reported, select the available updates and click Next.
Follow the wizard to install the updates.

Internal Site

Choose Window> Preferences and choose Install/Update> Available Software Sites.
Enter the location of the update site in the Update Site Location field. If you’re not sure what site to use, contact your Parasoft representative for details.
If you want to configure Eclipse proxy connections (not related to Parasoft proxy configuration/behavior), set them in the General> Network Connections area of the preferences panel.

Headless

You can install online, offline, and patch headless service pack updates. Headless service pack updates are not applicable to update site installs.

For offline updates, download the p2 zip archive from http://updates.parasoft.com/ to your installation directory.
Ensure that SOAtest and Virtualize are not running.
Run the update.bat or udpate.sh script in the installation directory using the following command (see About the Update Script Options):
update [--debug] [--help] [--patch <arg>| --updatesite <arg>] [–version]The default installation directory for the update script varies by OS:
- MacOS: In the directory parasoft/soatest_virtualize/<version>/Parasoft SOAtest & Virtualize.app/Contents/Eclipse
- Windows: C:\Program Files\Parasoft\SOAtest & Virtualize\<version>
- Linux: In the directory parasoft/soatest_virtualize/<version>
Start SOAtest or Virtualize using soatest.exe -clean or virtualize.exe -clean.

About the Update Script Options

Option	Description
`--debug`	(Optional) Outputs debug logging.
`--patch <arg>`	(For patches, not service packs) updates the current installation with the specified patch .jar file(s) provided as arguments to patch. For example, `--patch patch1.jar patch2.jar` would update two jar files in the installation. Patch files can be specified by file system path; they can reside outside of the update program directory.
`--updatesite <arg>`	Determines where service pack updates are accessed (e.g., which p2 update site or zip archive). To get the latest updates, use: `--updatesite` To use a specific update site, use: `-- updatesite <URL>` where `<URL>` is the remote update site. Example: `--updatesite http://updates.parasoft.com/xtest/archive/virt/<version>/` To use a local P2 zip archive, use `-- updatesite <archive>` where `<archive>` is the P2 archive file with a .zip extension. The file can be specified by file system path. Example 1: `--updatesite com.parasoft.xtest.web.sp_updatesite_<version>.zip` (the zip file is saved in the same directory as the update program). Example 2: `--updatesite C:\mydir\com.parasoft.xtest.web.sp_updatesite_<version>.zip` (the zip file is saved in C:\mydir).
`--version`	(optional) prints the version number of the current installation.