Table Of Contents Prev << Ch. 4: GridGain Basics Next >> Ch. 4.1.5: Troubleshooting

GETTING AND INSTALLING

In this chapter:

• 4.1.1 Download
  • 4.1.1.1 Maven
  • 4.1.1.2 Versions
  • 4.1.1.3 Supported Operating Systems
  • 4.1.1.4 Java and Scala
• 4.1.2 Installation
  • 4.1.2.1 Installing On Shared Location
• 4.1.3 Uninstallation
• 4.1.4 Upgrading

4.1.1 Download

There are two way how you can get GridGain:

• you can download it from http://www.gridgain.com,
• or you can use Maven2 repository to get it

We highly recommend to use the first method and simply download ZIP file from www.gridgain.com website. To do so - simply open http://www.gridgain.com in your favorite browser and locate the download link that usually on the right side:

Once you clicked on the download link you'll be on download page and you'll need to enter your name and email:

Keep in mind several things:

• There are two editions available for the download - enterprise and community
• There is a link on top of the page for past downloads that contains all previous releases of GridGain
• In the download table (see above) you can see date of the build, its version, and the link to Release Notes

There are four downloads (as of version 3.0.2):

• Enterprise and Community for Windows
• Enterprise and Community for Linux/Unix/Mac OS.

All downloads are simple ZIP files. ZIP files are versioned and clearly named to indicate for what OS they intended to.

^Top

4.1.1.1 Maven

Maven repository available only for version 3.0.0c-RC1 and up.

If you decide to use Maven please keep in mind:

• Only Maven2 repository currently available (as of version 3.0.2)
  • Maven3 is not supported yet.
• Only community edition is available in our public repository
  • Enterprise edition can only be downloaded directly from http://www.gridgain.com website
• Only the main GridGain JAR file is available in Maven repository
  • Depending on your usage of GridGain you may need configuration files, working directly, etc. that won't be created when using Maven to get GridGain.

To utilize our Maven repository you'll need to make the following changes. In your POM file you need to add dependency for GridGain:

<dependencies>
    .
    .
    .
    <dependency>
        <groupId>org.gridgain</groupId>
         <artifactId>gridgain</artifactId>
         <version>3.0.0c-rc1</version> <!-- CHANGE IT! -->
    </dependency>
<dependencies>

Make sure to properly change the version of the GridGain.

You will need to add GridGain repository to your POM file as well:

<repositories>
    .
    .
    .
    <repository>
        <id>gridgain</id>
        <url>http://www.gridgainsystems.com/maven2/</url>
    </repository>
</repositories>

Once you have it done - you are ready for Maven-based usage of GridGain.

Internal Repository We recommend to use internal Maven repositories for your projects if Maven is something you like to use. You can download GridGain as usual through www.gridgain.com website and deploy necessary files to your local repository for the rest of the team to use. This way you have full control on how GridGain is available via Maven for your particular project.

^Top

4.1.1.2 Versions

GridGain follows traditional rules on versioning and what specific version number means:

In general, we target one major release every 12 months and mid-point release every 6 months. Point releases are being cut as we see need to patch issues or provide hot bug fixes.

^Top

4.1.1.3 Supported Operating Systems

GridGain is actively developed and tested on three major operating systems:

• Mac OS X
• Linux (Ubuntu, Fedora)
• Windows

Being Java-based software GridGain has minimal dependency on particular operating system (as long as Java is available for it). Most of the dependencies are in scripts. With every release of GridGain we thoroughly testing the software against the following version of operating systems:

• Mac OS X 10.x
• Linux Ubuntu (current active release)
• Linux Fedora (current active release)
• Windows XP/Vista/2007 (as of 3.0.2 version)

Note that we do not actively test against the following operating system but verified independently that GridGain 3.0 works stable and correct on them:

• Solaris (current release)
• HP-UX (current release)
• Window 2003, Windows 2000

In general, with extremely rare exceptions, GridGain will work out-of-the-box on any Windows or Linux/Unix-based system as long as Java 6 is available on it.

^Top

4.1.1.4 Java and Scala

As of version 3.0 GridGain requires Java 6. Note that GridGain 3.0 has not been tested with upcoming Java 7.

Starting with version 3.0.1 GridGain requires Scala 2.8 or later. Note that original release of GridGain 3.0.0 came before Scala 2.8 GA was released and was compatible only with Scala 2.7.

Keep in mind that you can develop with either Java, Scala or both. Specifically, Scala is not required to develop with GridGain but some of the tools, like GridGain Visor - monitoring tool in enterprise edition, use Scala REPL and therefore Scala is required for its usage. Note also that as of GridGain 3.0.2 - none of the functionality in community edition explicitly require Scala.

As of November 2010 you can download both Java and Scala from:

• http://www.oracle.com/technetwork/java/javase/downloads/index.html for latest Java
• http://www.scala-lang.org/node/165 for latest Scala

Java for Mac OSX Note that Java download for Mac OSX may change its location as its development is shifting from Apple to Oracle as of November 2010.

^Top

4.1.2 Installation

Once you download whatever ZIP file your have selected - the installation process is rather trivial:

1. Unzip it to any location you prefer.
2. Set up GRIDGAIN_HOME environment variable pointing to installation folder

Note that installation does not perform any new-line translations and text files may have wrong new-lines depending on what OS installation is performed.

Unix/Linux/Mac OSX ZIP file has all Shell scripts with executable flag set so that they can be called directly.

GRIDGAIN_HOME Note that strictly speaking GRIDGAIN_HOME is not required for GridGain operation - and if you know that your setup won't require it (explained later in the book) - you can skip it. If you are new to GridGain - it's very advisable to set GRIDGAIN_HOME right after the unzipping the downloaded file.

Note: make sure there is no trailing '\' in GRIDGAIN_HOME path.

^Top

4.1.2.1 Installing On Shared Location

One good practice for testing, staging or production setups is to install GridGain into shared location like a network share or shared hard drive. This way multiple grid nodes can share single configuration, libraries and working directory. This significantly simplifies management of GridGain installation in a distributed environment.

^Top

4.1.3 Uninstallation

Uninstalling GridGain is even simple than installing - you simply remove the GRIDGAIN_HOME folder where GridGain was installed. If it was configured to use paths outside of GRIDGAIN_HOME you will need to delete them too (if necessary).

^Top

4.1.4 Upgrading

Due to complexity of GridGain (mostly due to its distributed nature) we have decided not to provide incremental upgrade (or patching) capabilities. We recommend upgrading GridGain by cleanly uninstalling and installing a new upgrade version.

^Top

		Table Of Contents Prev << Ch. 4: GridGain Basics Next >> Ch. 4.1.5: Troubleshooting