Upgrading from a Previous Version

If you are currently using a previous version of GigaSpaces or InsightEdge, contact support@gigaspaces.com for information on how to upgrade to the most recent version.

As a best practice, when upgrading to the latest version, unzip the downloaded software package and port the necessary changes from your previous environment into your new environment. It is recommended to use the new distribution as-is.

Backwards Compatibility

This version of the InsightEdge Platform is backwards compatible to GigaSpaces version 12.x (APIs and client-server). For more information about GigaSpaces' backwards compatibility policy, refer to the Product Life Cycle and End-of-Life Policy page.

For information about product changes that may affect your upgrade process, refer to the sections on Upgrading from a Previous Version for the following releases: 12.3, 12.2, 12.1, and 12.0.

Default GSC Service Limit

The default GSC service limit has been changed to 1. If this causes problems in your system, you can change this value via either the GS_GSC_SERVICE_LIMIT environment vairable, or the com.gigaspaces.grid.gsc.serviceLimit system property.

GigaSpaces Command Line Interface (CLI)

The scripts that run the command line interface (new and legacy) have been unified, and are now in a single script called "gs". This script starts the latest CLI by default (version 2). For more information, refer to Upgrading the CLI.

Maven Integration

Up to and including release 14.2, a dedicated script was used to install GigaSpaces Maven artifacts to a local Maven repository (installmavenrep), along with an additional script for InsightEdge. These scripts have been removed as of release 14.5, and the functionality is now provided by the new gs install maven command in the CLI. For more information, refer to Maven Artifacts.

Changes to XAP.NET Package

Due to changes in the available Java distributions, Java is no longer packaged with XAP.NETT. By default, if you have Java already installed on the host machine then XAP.NET will use it (via the JAVA_HOME environment variable). For more information, see the JVM Configuration topic of the XAP.NET section.