XAP

Service Grid License Setup

License Validation on Start-Up

The license is validated whenever the service grid is started. If the license is invalid for some reason (for example, if it is expired), the system will report a problem with the license and terminate. If the license expires while the system is up and running, it will continue to run. However, if a system components fails and tries to restart, it will fail because the license is not valid. Example:

If you're using Docker images for evaluation, add the -e GS_LICENSE=... option to the Docker run command, using the license key you got.

License Lookup Order

The system looks for the license key in the following 5 locations, in the following order:

The 5 options below are in sequential order. That is, option 1 will override option 2. Option 2 will override option 3.  And so on.

Option Description Example
1 The com.gs.licensekey system property.
  1. Upload the license directly into the system properties.

  2. Use either the command line, startup script, batch file or update the setenv-overrides bat/sh file:

set GS_OPTIONS_EXT=-Dcom.gs.licensekey=12345:

2 The GS_LICENSE environment variable.
  1. Add the GS_LICENSE environment variable which is located in the setenv-overrides bat/sh file.

  2. For the GS_LICENSE you will need to set the value GS_LICENSE=licensekeyvalue.

Following are the ways to verify if the license in the system properties is valid:

  1. The XAP services are running.

  2. From the log folder, open one of the recent log files:

  3. From the Java monitoring and management console, review the license:

3 A gs-license.txt file in the Classpath.  
4 A gs-license.txt file in the GigaSpaces installation folder (can be explicitly set using com.gs.home system property).

This is the simplest option:

  1. Open the gs-license text file:

  2. Paste the license key inside:

  3. Save and restart XAP services.

5 A gs-license.txt file in the current directory.