Pivotal GemFire Native Client Supported Configurations

The Pivotal GemFire native client provides access for C++ and Microsoft® .NET™ clients to the GemFire distributed system. It operates on platforms running Microsoft Windows, Linux (Intel), and Sun Solaris.

Operating system requirements are listed in the chart below:

Note: GemFire 8.2 deprecates all 32-bit platforms and other platforms as indicated below and in the Pivotal GemFire Native Client 8.2 Release Notes. Support for deprecated platforms may be removed in a future release of the product.

Operating System	Processor and Architecture	RAM	Swap Space	32-bit Disk Space Required	64-Bit Disk Space Required
Solaris 10	x86 (64-bit) (Deprecated in v8.2.1)	2GB	256MB		120MB
Solaris 11	x86 (64-bit)	2GB	256MB		120MB
RHEL 5 (Deprecated in v8.2)	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	105MB	120MB
RHEL 6	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	105MB	120MB
RHEL 7	x86 (64-bit)	2GB	256MB	105MB	120MB
SLES 10**	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	105MB	120MB
Windows 2008 R2 (Deprecated in v8.2)	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	104MB	125MB
Windows 2012 Server** (Deprecated in v8.2)	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	104MB	125MB
Windows 2012 Server R2**	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	104MB	125MB
Windows 8** (Deprecated in v8.2)	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	104MB	125MB
Windows 8.1**	x86 (64-bit) x86 (32-bit) (Deprecated in v8.2)	2GB	256MB	104MB	125MB

**Indicates operating systems that have not been fully tested but are still supported.

Windows Support Details

The Pivotal GemFire native client is built and tested on Windows 2008 R2 .

The native client is not supported on Windows NT 4.0.

Runtime Library Requirements

The GemFire native client also requires the Microsoft Visual C++ 2010 Redistributable Package. This package is installed for you when you use the native client .msi installer. If you do not use the .msi installer, you will need to install this package for your platform architecture manually (x86 or x64) on all machines that will run the GemFire native client. This package contains runtime libraries needed by the native client.

.NET Framework Version Support

The Pivotal GemFire native client is supported with Microsoft .NET Framework 3.0, and 3.5 and 4.0.

Microsoft .NET Framework 2.0 is no longer supported.

A Microsoft .NET Framework must be installed to support the C++/CLI (Common Language Infrastructure) library for the native client.

Note: You can download the .NET Framework Redistributable Package (x86 for 32-bit or x64 for 64-bit) for the version you wish to use from http://www.microsoft.com/downloads. If it isn’t listed on the Download Center page, use the Search tool to search for ".NET Framework".

The Pivotal GemFire native client 8.2 supports .NET 4.0 and Visual Studio 2010 (for compiling C++ applications on Windows). For advantages and more information on the features of .NET 4.0 and Visual Studio 2010 SP1, see http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx and http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx.

Linux

The Pivotal GemFire native client is built on Red Hat Enterprise ES 5 kernel version 2.6.18-8.el5.

The native client is tested on the following Linux versions:

Red Hat Enterprise 5 release 5 (Tikanga), kernel version 2.6.18-8.EL5
Red Hat Enterprise 6, kernel version 2.6.32-220.el6.x86_64

If you are not sure of the kernel version on your system, use this command to list it:

prompt> uname -r

The following table lists the RPM package dependencies for several Linux distributions. The i386 or i686 after the package name indicates that you must install the package for that particular architecture regardless of the native operating system architecture. All of the packages listed are available with the default media for each distribution.

Table 1. GemFire Dependencies on Linux RPM Packages
Linux Version	glibc	libgcc
Red Hat Enterprise Linux Server release 5 (i686)	glibc	libgcc
Red Hat Enterprise Linux Server release 5 (x86_64)	glibc (i686)	libgcc (i386)
Red Hat Enterprise Linux Server release 6 (i686)	glibc	glibc
Red Hat Enterprise Linux Server release 6 (x86_64)	glibc (i686)	ibgcc (i386)

For versions of Linux not listed in the table, you can verify that you meet the native client dependencies at the library level by using the ldd tool and entering this command:

prompt> ldd $GFCPP/lib/libgfcppcache.so

This step assumes you have already installed the native client and have set the GFCPP environment variable to productDir, where productDir represents the location of the NativeClient_xxxx_bnnnnn directory (xxxx is the four-digit product version and bnnnnn is the product build number).

The following libraries are external dependencies of the native library, libgfcppcache.so. Verify that the ldd tool output includes all of these:

libdl.so.2
libm.so.6
libpthread.so.0
libc.so.6
libz.so.1

For details on the ldd tool, see its Linux online man page.

Solaris

The Pivotal GemFire native client is supported on the following Solaris versions:

Solaris 9 kernel update 118558-38
Solaris 10 kernel update 118833-24

Running Pivotal GemFire Native Client on vSphere

Without tuning, the Pivotal GemFire native client can suffer a performance drop in virtual environments, including the VMware vSphere virtual platform. Without correct tuning, you can expect to see significant performance degradation when running the GemFire native client on vSphere versus running GemFire on dedicated hardware.

We recommend that you tune your GemFire native client on vSphere deployments using the same guidelines published for Pivotal GemFire.

See Improving GemFire Performance on vSphere for a list of guidelines and recommendations.

Software Requirements for Using SSL

If you plan on using SSL in your GemFire native client and server deployment, you will need to download and install OpenSSL.

The GemFire native client requires OpenSSL 1.0.1s or later. For Windows platforms, you can use either the regular or OpenSSL "Light" version.

In addition, make sure that your system environment variables have been configured to include OpenSSL.

See SSL Client/Server Communication for instructions.