Overview

The command-line utilities provide life-cycle management both for the container and the spaces it manages. You can start and shutdown containers, and create, ping, clean, stop, start, and destroy spaces. You may discover the spaces running over the network and perform some network diagnosis tasks.

The general format of most of the utilities is:

Utility <container name> <space name> | [ -l <lookup host> | -r <RMIregistry host> ] <utility specific options>

The default container name is the name of the host running the container. You can use also "." as the container name – this will count as:

<Space name>_container

The space name is the same name given when the space was created. All the utilities provide two basic methods of locating a space in the environment:

• Using the Jini Lookup Service – This option enables both a Unicast and Multicast lookup. Multicast is the default option. Use Unicast if you specify the lookup host with the -l option.
• Using the RMI Registry – Every container has an embedded RMI Registry. The default port for it is 10098. This mode allows the space to be located independently of the Jini services. It also enables more control of the space by providing direct access to the container, thus avoiding the possibility of conflict, if and when spaces with the same name and containers run across the network.

Service Grid CLI See also Service Grid CLI Reference.

More in this Section

• Starting GigaSpaces Server
• Starting GigaSpaces Instance
• Pinging the space
• Creating a space
• Cleaning a space
• Stopping a space
• Starting a space
• Restarting a space container
• Destroying a space
• Shutting down the container
• User Administrator
• MulticastTest Utility
• Starting Jini Lookup Service
• Starting the Jini Transaction Manager
• Locating Running Spaces
• Platform Version
• Platform Info
• Benchmark
• generateGsXml