Label: installing+1-introductory

View: Popular Labels | All Labels

All content with label installing+1-introductory.
Related Labels: location , book-all-dotnet , 42140301---bl , 2-basic , classpath , concepts , gigaspaces , book-admin , common , jvm , infrastructure , helloworld , book-all-java , interfaces , variables , recommended , advanced , 42140851---bl , unit , more » ( - installing , - 1-introductory )

Common Environment Variables (XAP 6.6 Documentation)
Descriptions of the main environment variables set automatically by {{setenv.bat}}. Overview The GigaSpaces environment configuration is maintained by a configuration script file. This script is located in the {{<GigaSpaces Root>\bin}} directory: Windows: {{setenv.bat}} UNIX: {{Setenv.sh}} Below is a list of some of a selected list ...
Installing GigaSpaces (XAP 6.6 Documentation)
Requirements and how to install GigaSpaces with Windows, Linux or Unix. Overview GigaSpaces is 100% pure Java, and therefore can run on any UNIX or Windows machine that supports Java. Prior to Installation Prior to the GigaSpaces installation, make sure: JDK 1.4 ...
License Key (XAP 6.6 Documentation)
Getting a license key and defining it in the space schema. License Key File When you download GigaSpaces XAP from the Internet, you will receive an email message with a valid license key. Edit the {{<GigaSpaces Root>\gslicense.xml}} file and copy ...
Setting Classpath (XAP 6.6 Documentation)
JARs that should be in the classpath of applications accessing a remote or embedded space. Overview GigaSpaces libraries are located under {{<GigaSpaces Root>\lib}}: !ImagesInstallingGigaSpaces6.5RC1.jpg! You can find the space runtime library in the {{<GigaSpaces Root>\lib\JSpaces.jar}} file, and third party ...
Setting JVM Location (XAP 6.6 Documentation)
Setting the {{JAVAHOME}} parameter to tell GigaSpaces where the JDK is installed. Overview GigaSpaces has a dependency on the {{JAVAHOME}} environment variable being set. Make sure you have an environment variable {{JAVAHOME}} defined pointing to your JDK root ...