XAP8 == "XAP9NET" || XAP8 == "XAP9" || XAP8 == "XAP9NET")

Running GigaSpaces as a Windows Service


Search XAP 8.0
Searching XAP 8.0 Documentation
Browse XAP 8.0
Offline Documentation

Download latest offline documentation
in HTML format:

xap-8.0-documentation.zip (15MB)

                                                              

Summary: Running GigaSpaces as a Windows Service

Common Scenarios

GigaSpaces infrastructure can be started using a GigaSpaces Grid Service Agent as explained in GSA page. When using Windows based OS for running GigaSpaces infrastructure, users want to convert GSA into a windows service for following common reasons,

  1. GSA process should survive a user logoff.
  2. GSA command windows should be hidden so that they are not closed accidentally by users.
  3. GSA process should restart automatically after a machine restart and all GigaSpaces infrastructure should be available without user/administrator intervention.

psexec

If your requirement is only item 1 and/or 2 above, you can use psexec (SysInternals/Microsoft tool, http://technet.microsoft.com/en-us/sysinternals/bb897553). When you start the GSA using psexec from a remote machine in the network the process does not open command windows and does not get terminated on a logoff of the user.

Windows Service

If you need to fulfill all 3 reasons above, then you have to create a windows service for GSA.

Easiest way to convert GSA into service is to use the .Net version of the product and create windows service using the instructions that are documented on our .Net wiki.

Some users are not comfortable using the .Net version of the product and want to use only Java version of the product. In such cases, there are many software that can help in converting a Java Application (like GigaSpaces) to a Windows Service.

Following are some popular software that can help:

Example

An example GSA windows service configuration created using Java Service Wrapper can be downloaded from here. It was created using the instructions on Tanuki software website.

  • Modify the wrapper.config file per your environment.
  • Set the values for all the environment variables (look for set.xxx) per your environment.
  • This example starts 2 GSC's, GSM and a LUS. Modify these settings as needed.
  • Also modify Additional Java parameters (look for wrapper.java.additional.xxx) defined in the wrapper.config file.
  • Install the service using the included InstallGSAService-NT.bat script.
  • After the install you should be able to see the service in the Windows Services applet.
  • Service is installed with Startup Type of "Manual". Change it to "Automatic" to start the service automatically after every restart.
  • Use the UninstallGSAService-NT.bat script to uninstall the service.

Other Information

  • It is recommended that the deploy command be run manually instead of defining this as a windows service.
  • Typically, GigaSpaces cluster spans multiple machines and redundant instances of GSM's and LUS's run on different machines. If a machine is restarted, deployment will still be intact and be managed by available redundant GSM that is running on other machine. Once the machine and GSC's are restarted missing PU instances are deployed by GSM into these newly started GSC's as needed.
  • To convert other individual components (GSC, GSM or LUS) into windows service, same instructions can be used with simple modifications.
IMPORTANT: This is an old version of GigaSpaces XAP. Click here for the latest version.

Additional resources: XAP Application Server | XAP Data Grid | XAP for Cloud Computing | XAP J2EE Support

Labels

 
(None)