A Servoy Application Server installation can be upgraded from the command-line to new maintenance (x.x.x) or minor (x.x.0) version. Command-line upgrades to new major (x.0.0) versions is are not supported, unless explicitly mentioned in the release notes.

In order to perform a command-line upgrade, the Servoy Application Server needs to be able to connect the internet and more explicitly to http://www.servoy.com for downloading the upgrade package.

Upgrading a Servoy Application Server

To upgrade a Servoy Application Server the following steps must be followed:

1. Shutdown the Servoy Application Server
2. Open a command line/terminal window and browse to the {servoyInstall}/application_server directory 

3. Execute one of the commands from the table below

   	Command	Comment
   Default	java -jar servoy_updater.jar	Upgrades to latest final release. Excludes alpha, beta and release candidates
   Include beta versions	java -jar servoy_updater.jar -beta	Upgrades to latest non final release
   Update to specific release (since Servoy 6.1)	java -jar servoy_updater.jar -releaseNumber buildNumber	Upgrades to a release based on the specific build number of the release. The build number for a specific release is mentioned in the announcement of the release on the Servoy Talk forum.

Servoy Repository upgrade

The update process will update only the Servoy Application Server installation. It does NOT update the Servoy Repository structure. When the upgraded Servoy Application Server is launched and it finds an incompatible version of the Servoy Repository, the launch will be aborted with the message that the Servoy Repository needs to be upgraded. See Servoy Repository upgrade for more info on upgrading the Servoy Repository.

Updating and code signing heads-up

When the Servoy Smart Client is used, the topic of signing becomes relevant to:

• make sure that the Smart Client can be deployed without issues
• provide a good user experience when launching the Smart Client

For more on the topic of code signing see ......

Files replaced The code in the files updated by the updater will be properly signed by Servoy. However, if the default Servoy signing has been previously , similar to how all code of the Servoy Application Server is signed when first installed.

If the code signing of the installation has been replaced by custom signing, this means that part of the codebase is now signed using a custom certificate and part of the codebase is signed by Servoy's certificate. while While this is not problematic from a technical perspective (the Smart Client will still work), it does mean that the user will be presented with multiple dialogs that asks if the user trusts the party that signed the code. 

To resign the updated files with a custom certificate, the signing of all files that are part of the Servoy distribution needs to be checked and the files that are now signed using the Servoy certificate need to be resigned using the custom certificate.

For more on the topic of code signing see the Code Signing chapter.

Prevent updating or placement of specific files

...

Some Java environments start with IPv6 Stack. When actually running on IPv4, this might cause issues in the download of the update. Add 'd-Djavajava.net.preferIPv4Stack=true' to  to the end of the update command.

...