How GemFire Manages Licenses

Before you install vFabric GemFire licenses, understand how GemFire manages your license information.

How GemFire Finds and Verifies Your License

GemFire has a default license that it uses if it cannot locate any other valid licensing.

Non-default licensing is verified using a combination of the product gemfire.jar file and the serial numbers you provide, or a license may be acquired dynamically from the vFabric License Server.

GemFire uses the first valid licensing it finds in this list:
  1. Serial number specified by one of the license properties in gemfire.properties.
  2. Dynamic licensing provided from a serial number file stored in the local VMware vFabric serial number directory, configured by specifying dynamic for one of the license properties in gemfire.properties.
  3. Dynamic licensing provided by the vFabric License Server, configured by specifying dynamic for one or both of the license properties in gemfire.properties.

If GemFire cannot validate any of the specified licensing in the above list, the application or cache server process will not start and will throw an exception.

If no licensing is specified, GemFire uses the default evaluation licensing shipped with the product.

License Working Directory

GemFire stores licensing information in a directory on your system.

GemFire writes to the first writable directory it finds in this list:
  1. The value of the property license-working-dir if specified in the member's gemfire.properties.
  2. The member process's current working directory as determined by System.getProperty("user.dir") at startup.
These are the files GemFire writes:
  1. License state files with names ending with -license.cfg. Example: vf.gf.dmn-license.cfg.
  2. License events files with names ending with -events.txt. Example: vf.gf.dmn-events.txt.

Leave these files alone. Do not edit or delete these files and do not alter the permissions on the files or the directory where these files are located. These files are created using the default permissions of the user who is starting up the GemFire process. Any user needing to stop or start the GemFire process will need write permissions for this directory and the files in it. Make sure that the permissions for each user are sufficient otherwise GemFire may throw an exception during stop or start.

Local VMware vFabric Directories

Note: Directory path names are case sensitive. Please use the directory path names as specified in the tables below.

Local VMware vFabric home directory

For most vFabric Suite components, the local VMware vFabric home directory is used as a license working directory by the vFabric License Manager. By default, however, vFabric GemFire uses the current working directory as the license working directory as described in License Working Directory. The default location of the local VMware vFabric home directory, if it exists, varies by operating system:

Windows %ALLUSERSPROFILE%\VMware\vFabric
Linux (or other OS) /opt/vmware/vFabric

Local VMware vFabric serial numbers directory

The location of the local VMware vFabric serial numbers directory, if it exists, varies by operating system:

Windows %ALLUSERSPROFILE%\VMware\vFabric
Linux (or other OS) /etc/opt/vmware/vfabric

If the serial numbers directory does not already exist, you must first create the directory in order to use serial number license files for vFabric GemFire licensing. The directory should maintain read/write permissions for all users who will be starting and stopping GemFire processes.