Installing GigaSpaces

  Search Here
Searching XAP 6.0 Documentation

                                               

Summary: 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, 1.5, or 1.6 is installed (see warning below):
    • JDK 1.4
    • JDK 1.5 – download JDK 5.0 Update 12 as seen below:


    • JDK 1.6 – download JDK 6 Update 2 as seen below:


  • The JAVA_HOME environment variable points to the correct JDK (not JRE) directory before running GigaSpaces. For example, D:\Java\jdk1.5.
  • The JAVA_HOME environment variable should be added to the beginning of the Path environment variable. For example, %JAVA_HOME%;SystemRoot%\system32;%SystemRoot%;%SystemRoot%
  • Your network and machines running GigaSpaces are configured to have multicast enabled. See the Multicast Configuration section for details on how to enable multicast.

Installation

Installing on Windows

  1. Unzip the ZIP file (using your favorite unzip tool, for example, WinZip) to the location of your choice. Unzipping the file creates a <GigaSpaces Root> directory with several sub-directories. An example for the name of the ZIP file: GigaSpacesXAP6.0_1.5_build_BUILD_NUMBER.zip (where GigaSpacesXAP is replaced with GigaSpacesXAPCommunity/GigaSpacesEDG for the Community/EDG editions). (Don't install GigaSpaces in a path with spaces, see below.)

  2. After unzipping the ZIP file, you should have the following files and folders under the GigaSpaces root folder:


  3. You are ready to enter the GigaSpaces world!

What's Next?

Installing on Linux

  1. Go to the directory into which you want to install, e.g. opt, and issue the unzip following command, supplying the path to the name of the ZIP file – GigaSpacesEdition_build_BuildNumber. For example:

    unzip GigaSpacesXAP6.0_1.5_build_1814
    

    where GigaSpacesXAP is replaced with GigaSpacesXAPCommunity/GigaSpacesEDG for the Community/EDG editions.

  2. Make sure all sh file(s) in the /bin and the /examples directory are in executable mode, meaning you can run them from your machine. To check this, use the ls -al command for the relevant directory, and make sure that x is included in the file permissions.

  3. Once all files extracted – you are ready to enter the GigaSpaces world!

What's Next?

Mixing Versions

Mixing GigaSpaces versions/builds

Supported:
Applications built using GigaSpaces 6.0 (these run without any code changes on a clean 6.0.x installation).

Not supported:
Mixing clients/servers from different GigaSpaces releases/builds – 6.0 clients can not run against 6.0.x servers. 6.0.x clients can not run against 6.0 servers. 6.0.x servers do not communicate well with 6.0 servers.

Mixing JDK 1.4 and JDK 1.5/1.6 Environments

GigaSpaces running with JDK 1.5/1.6 can run with GigaSpaces 1.4 JARs, but GigaSpaces running with JDK 1.4 can't run with GigaSpaces 1.5/1.6 JARs:

If you have GigaSpaces running with JDK 1.4 and another installation of GigaSpaces running with JDK 1.5/1.6, use the GigaSpaces JAR files from the earliest version – copy the JSpaces.jar and JSpaces-ui.jar files from the <GigaSpaces Root>\lib directory of your GigaSpaces 1.4 installation to the <GigaSpaces Root>\lib directory of your GigaSpaces 1.5/1.6 installation.

GigaSpaces .NET does not support JDK 1.4.

Mixing Different GigaSpaces JARs in Same Deployment Environment

GigaSpaces components (space, cluster of spaces, Processing Unit, GSM, GSC, LUS, Mahalo, GUI, CLI) can run only with the same GigaSpaces JARs (i.e., the same version and same build number).

Important Tips

Do not have spaces in the GigaSpaces Installation Path

Make sure the path under which GigaSpaces is installed doesn't include spaces. For example, here is an incorrect path, with spaces:

C:\Program Files\GigaSpaces XAP 6.0

Here is a correct path, without spaces:

C:\GigaSpacesXAP6.0

Running GSCs with 64-bit JVMs

GSC configuration is 32-bit compliant, but can be overridden to support a 64-bit platform. For more details, see Running Services - GSC and GSM.

Use JDK and not JRE

It is recommended to use a JDK (Java Development Kit), and not a JRE (Java Runtime Environment), which can be used for runtime only and not for development. However, if you do decide to use a JRE, make sure the JAVA_HOME environment variable points to the correct JRE directory.

You should also remove specific JDK command-line arguments, like -server, which do not exist in JRE.

Use JDK and not JRE

It is recommended to use a JDK (Java Development Kit), and not a JRE (Java Runtime Environment), which can be used for runtime only and not for development. However, if you do decide to use a JRE, make sure the JAVA_HOME environment variable points to the correct JRE directory.

You should also remove specific JDK command-line arguments, like -server, which do not exist in JRE.

Performance Tips

Before you begin working with GigaSpaces, it is recommended to review the performance tips section and apply some of the required changes. For example, you must update the max file descriptors limit before you begin.


GigaSpaces 6.0 Documentation Contents (Current Page in Bold)

    Java

    C++

    .NET

    Middleware Capabilities

    Configuration and Management

Add GigaSpaces wiki search to your browser search engines!
(works on Firefox 2 and Internet Explorer 7)

Labels

 
(None)