Upgrade Kaazing WebSocket Gateway

The upgrade procedure migrates the existing Kaazing WebSocket Gateway (including any associated applications) into Kaazing WebSocket Gateway release 4.0. The following checklist provides the steps necessary to upgrade Kaazing WebSocket Gateway to the next release.

Step Topic or Reference
Understand Gateway release number strategy and the upgrade process. About Kaazing WebSocket Gateway Releases and Upgrades
Find out what's new and changed in this release. Release Notes

If you are performing a major release upgrade, then obtain a new license file (for example, from release 3.5 (or later) to release 4.0).

If you are performing a minor release upgrade or a patch release upgrade, then skip to the next step.

To upgrade your license, contact your Customer Support Representative.

Full enterprise licenses for versions of Kaazing WebSocket Gateway prior to 4.0 (including Kaazing WebSocket Gateway 9.06) will not work if you are upgrading from release 3.x to 4.x. Note that you can use the developer license, in the meantime, to get started. See Kaazing Developer License Agreement for more information about licenses.

Upgrade to the new Gateway release using one of the following:

  • Using the Windows or Linux installer to install the Gateway into conventional (default) operating system locations.
  • Unpacking the .zip for Windows or .tar.gz for Linux, UNIX, or Mac) into any directory location.
Setting Up Kaazing WebSocket Gateway

See Upgrade Options for help choosing an upgrade methodology.

Migrate your existing Gateway configuration file and other files to the new Gateway installation. Migrate the Gateway Configuration
If you are using a Gateway in a cluster, then you need to perform additional steps to migrate the cluster members. Clustering and Load Balancing Migration

Note: Upgrade all members of the Gateway cluster before you migrate any clients.

Verify the Gateway is upgraded. View the release number via Command Center, the Gateway start-up output, or the log file.
If you are using JMX MBeans to monitor the Gateway, update the MBean paths. In 3.x, the MBeans path is com.kaazing.gateway.server.management > services. In 4.x, the MBeans path is com.kaazing.gateway.server.management > gateways > process_id@hostname > services. See Monitor with JMX for more information. Note that some service names may have changed or been deprecated.
Learn how clients that are built using Kaazing WebSocket Gateway can take advantage of the Kaazing WebSocket Gateway client libraries. General Client Information
(Recommended) Migrate Kaazing JavaScript and Java clients that use the ByteSocket API on releases 3.3 (and later releases) to the WebSocket API in release 4.x.

See Also

TOP