Installing the Module for AppServers

This topic describes how to install the AppServer module.

Installing the Module in Your Application Server

Most of the time it will be sufficient for all of the necessary jar files to be bundled within the war or ear file you wish to deploy. However, there may be situations where the core GemFire and Module jars need to be shared across web application deployments. The following instructions provide guidelines on how to do this.
  1. Download and unpack the HTTP Session Management for AppServers Module into a directory on the application server.
  2. From the directory where you unpacked the files, copy the following files from /lib to an appropriate location on your application server (see table below) in order to make them available to all applications.
    • gemfire-<version>.jar
    • gemfire-modules-<version>.jar
    • gemfire-modules-session-<version>.jar
    • slf4j-api-<version>.jar
    • slf4j-jdk14-<version>.jar*
Application Server Version Location
WebLogic 11g (10.3.x) <domain>/lib
WebSphere 7 <websphere install dir>/lib/ext
WebSphere 8 Consult your application server's documentation
JBoss AS 5 <jboss install dir>/lib
JBoss AS 6 <jboss install dir>/common/lib
JBoss AS 7 Consult your application server's documentation

* For WebLogic you should substitute gemfire-modules-slf4j-weblogic-<version>.jar for slf4j-jdk14-<version>.jar.

This table lists all application server versions that have been tested with the GemFire HTTP Session Management modules. However, the generic HTTP Session Management Module for AppServers is implemented as a servlet filter and should work on any application server platform that supports the Java Servlet 2.4 specification.

Note: The GemFire evaluation license allows you to create up to three GemFire processes. To use GemFire with additional processes, refer to How GemFire Manages Licenses.