Configuring the Environment Variables
This topic explains how the GigaSpaces and GigaSpaces environments are configured, and how to customize them to suit your specific application needs.
GigaSpaces
The GigaSpaces environment configuration is maintained by a configuration script file called setenv, located in the GS/bin directory. Each GigaSpaces script invokes this script to load the GigaSpaces configuration. If you are developing a standalone GigaSpaces client, it is recommended to use the setenv utility to derive the commonly used GigaSpaces libraries and setup environment.
To use this utility, you can simply call it from within your script file.
GigaSpaces
The GigaSpaces environment configuration is maintained by a configuration script file called setenv-overrides, located in the /bin directory. Each GigaSpaces script invokes this script to load the GigaSpaces configuration. Additionally, isetenv-overrides starts by invoking the GigaSpaces setenv configuration script, so all of the GigaSpaces environment configuration is also applied.
Customizing the Environment Variables
During the initial development stages, it is usually unnecessary to change any of the default GigaSpaces environment values. However, at some point the environment will need customization to suit your specific requirements (such as the Grid Service Container heap size).
Do not make changes to the original setenv script, as it complicates upgrading GigaSpaces later on. Instead, use the setenv-overrides script, which is automatically called by setenv and is intended for specifying custom overrides in a safe manner.
GigaSpaces Environment Variables
The following list describes GigaSpaces-related environment variables:
When running in ./gs-agent --manager configuration, this environment variable is ignored.
In-Memory Data Grid - achieve unparalleled speed, persistence, and accuracy.