Overview

The GigaSpaces Manager (GSM), is a special infrastructure service, responsible for managing The GigaSpaces Containers. The GSM accepts user deployment and undeployment requests of Processing Units, and provisions them to the Service Grid Cloud accordingly.

The GSM monitors SLA breach events throughout the life-cycle of the application, and is responsible for taking corrective actions, once SLAs are breached.

It is common to start two instances of GSM services within each Service Grid cloud, for high-availability reasons.

Starting the GSM

The preferable way to start a GSM is using The GigaSpaces Agent. A GSM can be started on its own using the [GSHOME]/bin/gsm.(bat/sh) script (starts a GSM with embedded Lookup Service), or using the [GSHOME]/bin/gsm_nolus.(bat/sh) script (starts a GSM without embedded Lookup Service).

Configuring the GSM

Configuring the GSM (and possibly system level settings for other services, such as the communication layer) can be done using system properties.

System properties are best set using the EXT_JAVA_OPTIONS environment variable. It can be added within the GSM script, or in a wrapper script.

GSM specific configuration used to be done using the services.config configuration file. In this version, the services.config no longer exists, and its settings can be set using system properties (follows the [component name].[\property name] notation). If the services.config is still needed to be used, the installation comes with services.config.template file, which can be renamed back to services.config. By renaming it, it will be taken into account.