Services Manager

When installing the Service GridClosed A built-in orchestration tool which contains a set of Grid Service Containers (GSCs) managed by a Grid Service Manager. The containers host various deployments of Processing Units and data grids. Each container can be run on a separate physical machine. This orchestration is available for XAP only. on a Microsoft Windows environment, many administrators prefer to setup the Service Grid as A Windows Service, which have several advantages over standard console applications:

  • A service can be configured to start automatically when the machine boots, without any user logging in.
  • A service can be configured to run under predefined credentials, e.g. SYSTEM.
  • A service has no console/GUI which clutters up the desktop (and might be closed accidentally...).
  • Windows provides standard management console, command line and API to manage services, which makes managing services a common task for system administrators.

This page explains how to install a Service Grid as a Windows Service and manage it.


The Windows Services management console lets users start/stop installed services and modify their properties, but does not support installing new services. This task is can be done via a command line, or during installation of an application.

Instead, GigaSpaces XAPClosed GigaSpaces eXtreme Application Platform. Provides a powerful solution for data processing, launching, and running digital services.NET provides a supplementary tool called GigaSpaces Services Manager (located at the bin folder) which simplifies common administration tasks:

  • Install/uninstall Service instances of Grid Service Agent as you please.
  • Perform common operations directly from the tool, no need to switch to the Windows Console (e.g. Start, Stop, change startup type).
  • Side-by-side support for GigaSpaces Installations of different versions on the same machine.
  • Automatically creates a folder for new service instances, with an XML configuration and log files.
  • Create custom templates of different service grid configurations.


Some operations require elevated permissions - make sure you run with appropriate permissions. If you're using Windows Vista or later and UAC is turned on, it is recommended to use "Run As Administrator' (for more info see: http://support.microsoft.com/kb/922708).


Service Properties

To view a service properties, right-click it and select Properties, or simply double-click it. A dialog window with the service properties will appear.


Once the service has been created, the configuration is located in a specific directory. The example below is for version 16.3.0:

New projects should use .NET v6.0 framework which is .NET Core due to the fact that .NET v4.0 is old.  Version .NET v6.0 should work the same way.

The Service Properties window shows the name of the service configuration file. Either Click the configuration label to open the configuration file using your default XML viewer, or click the location label to open the service folder, then edit the configuration file using your favorite XML editor.

The following screen-shot shows where the GigaSpacesServiceHost-gs-agent.exe.config XML needs to be modified in order for the agent to start the components (see line 10). An example using version 16.3.0: C:\GigaSpaces\XAP.NET-16.3.0-patch-p-3-x64\NET v4.0\Services\<Name of service, GigaSpaces suggests: Grid Service Agent 1>\

In order for configuration changes to take effect, the service needs to be stopped and restarted.