Splicing a session data grid application with the addObjectGridFilter script

Use the addObjectGridFilter command-line script to splice an application with filter declarations and configuration in the form of servlet context initialization parameters.

About this task

For a WebSphere® Application Server deployment, the script is in the following location: was_root/optionalLibraries/ObjectGrid/session/bin/addObjectGridFilter.bat/sh . For a stand-alone deployment, the script is in the following location: wxs_home/ObjectGrid/session/bin/addObjectGridFilter.sh/bat.

Procedure

Run the addObjectGridFilter on your application.

addObjectGridFilter.bat [ear_file] [splicer_properties_file]

addObjectGridFilter.sh [ear_file] [splicer_properties_file]

[ear_file] - Specifies the absolute path to the enterprise archive file to be spliced.
[splicer_properties_file] : Specifies the absolute path to the splicer properties file that contains various configuration properties.

Results

The servlet filter that is spliced maintains defaults for configuration values. You can override these default values with configuration options that you specify in the properties file in the second argument. For a list of the parameters that you can use, see Servlet context initialization parameters.

You can modify and use the sample splicer.properties file that is provided with a eXtreme Scale installation. You can also use the addObjectGridServlets script, which inserts the session manager by extending each servlet. However, the recommended script is the addObjectGridFilter script.

Example

Example using eXtreme Scale installed on WebSphere Application Server on UNIX:

cd wxs_home/optionalLibraries/ObjectGrid/session/bin
addObjectGridFilter.sh /tmp/mySessionTest.ear was_root/optionalLibraries/ObjectGrid/session/samples/splicer.properties

[Unix] Example using eXtreme Scale installed in a stand-alone directory on UNIX:

cd was_root/session/bin
addObjectGridFilter.sh /tmp/mySessionTest.ear was_root/session/samples/splicer.properties