This page describes an older version of the product. The latest stable version is 12.3.

Upgrading from a Previous Version


If you are currently using a previous version of XAP or InsightEdge, contact support@gigaspaces.com for assistance in upgrading 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 XAP version 11.0 (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 XAP 12.1, 12.0, and 11.0.

Windows Environments

If you are upgrading to version 12.2 or later in a Windows environment and using XAP as a Windows service, you must add the following environment variables to the wrapper.conf file:

  • wrapper.java.additional.27 = -DXAP_GSA_OPTIONS=${xap_gsa_options}
  • wrapper.java.additional.28 = -DXAP_GSC_OPTIONS=${xap_gsc_options}
  • wrapper.java.additional.29 = -DXAP_GSM_OPTIONS=${xap_gsm_options}
  • wrapper.java.additional.30 = -DXAP_LUS_OPTIONS=${xap_lus_options}

For more information about the wrapper.conf file, refer to the XAP as a Windows Service topic in the Administration section.

New Location for xap-datagrid.jar File

As of version 12.2, the xap-datagrid.jar file was moved to /lib/required. When upgrading from an earlier version, verify that there isn’t an additional copy of this file in the old location /lib/optional/pu-common. Having multiple copies of this file will result in a failure to instantiate data when the data grid is started, and an exception will be thrown.

Maven Artifacts

If you are upgrading from an earlier version to any 12.x version, review the page on Maven artifacts in the Getting Started section to ensure that the client application will continue to behave as expected.

Using the Administration API with XAP.NET

The Administration API code was extracted to a separate JAR file, but the configuration file was not updated accordingly. To use this administration tool, modify the DefaultApp.config file to include the xap-admin jars.

For example, C:\GigaSpaces\XAP.NET-12.1.1-x64\NET v4.0\Config\DefaultApp.config. Add the following: <add Path="$(XapNet.Runtime.Path)\lib\platform\service-grid\*.jar"/>.