This page describes an older version of the product. The latest stable version is 14.5.

Administration API

The Service Grid Admin API provides a way to administer and monitor all of GigaSpaces services and components, using a simple API. The API provides information and the ability to operate on the currently running Service Grid Agents, Service Grid Managers, Service Grid Containers, Lookup Services, Processing Units and Spaces.

Before diving into the Service Grid Admin API, here are some code examples showing how the API can be used to display information on the currently deployed services/components:

See a fully running example of a Scaling Agent which comes with the product.

Admin Construction

Use ServiceGridAdminBuilder in order to create IServiceGridAdmin instances. Once working with the IServiceGridAdmin is done, its IServiceGridAdmin.Dispose() method should be called.

The admin discovers all the advertised services from the Lookup Services. In order to define which lookup groups are used, the ServiceGridAdminBuilder.Groups.Add can be used. The lookup locators can also be used for a non-multicast-enabled environment, using ServiceGridAdminBuilder.Locators.Add. If the services started are secured, the username and password can be set on the admin as well.

Discovery Process

Once the IServiceGridAdmin is created, it starts to receive discovery events of all the advertised services/components within its lookup groups/lookup locators. Note that the events occur asynchronously, and the data model within the admin gets initialized in the background with services coming and going.

This means that just creating the IServiceGridAdmin, and calling a specific get property for a data structure, might not return what is currently deployed, and one should wait until the structures are filled. Some components have a WaitFor method that allows them to wait for a specific number of services to be up. When navigating the data model, the admin API provides its most up-to-date state of the system that it is monitoring.

Domain Model

The Service Grid Admin Domain Model has representation to the main actors at different GigaSpaces levels. They include:

Name

Description

Main Operations

GridServiceAgent

A process manager that manages Service Grid processes such as GSM, GSC and LUS. More info here.

* Allows you to list all the currently managed processes.- Start processes (GSM, GSC, LUS).

GridServiceAgents

Holds all the currently discovered Grid Service Agents.

* Get all the currently discovered Grid Service Agents.- Wait for X number of Grid Service Agents to be up.- Register for Grid Service Agent addition (discovery) and removals events.

* Deploy Processing Units on a random Grid Service Manager.- Deploy pure Space Processing Units on a random Grid Service Manager.- Get all the currently discovered Grid Service Managers.- Wait for X number of Grid Service Managers to be up.- Register for Grid Service Manager addition (discovery) and removals events.

* Get all the currently discovered Grid Service Containers.- Wait for X number of Grid Service Containers to be up.- Register for Grid Service Container addition (discovery) and removals events.

LookupService

A registry of services (GSM, GSC, Space Instances, Processing Unit Instances) that can be lookup up using it. More info here.

* Get the Lookup Groups and Locator it was started with.

LookupServices

Holds all the currently discovered Lookup Services.

* Get all the currently discovered Lookup Services.- Wait for X number of Lookup Services to be up.- Register for Lookup Service addition (discovery) and removals events.

ProcessingUnit

A deployable processing unit running one or more Processing Unit Instances. Managed by the Grid Service Manager.

* Undeploy the Processing Unit.- Increase the number of Processing Units Instances (if allowed).- Decrease the number of Processing Unit Instances (if allowed).- Get the deployment status of the Processing Unit.- Register for deployment status change events.- Get the managing Grid Service Manager.- Register for Managing Grid Service Manager change events.- Get the list of backup Grid Service Managers.- Register for backup Grid Service Manager change events.- List all the currently running Processing Unit Instances.- Register for Processing Unit Instances additions and removals events.- Wait for X number of Processing Unit Instances to be up.- Get an embedded Space that the Processing Unit has.- Wait for an embedded Space to be correlated (discovered) with the Processing Unit.- Register for Space correlation events.

ProcessingUnitInstance

An actual instance of a Processing Unit running within a Grid Service Container.

* Destroy itself (if SLA is breached, it is instantiated again).- Decrease itself (and destroy itself in the process). It does not attempt to create it again.- Relocate itself to a different Grid Service Container.- List all its inner services (such as event containers).- Get the embedded Space Instance running within it (if there is one).- Get the JEE container details if it is a web processing unit.

ProcessingUnits

Holds all the currently deployed Processing Units.

* Get all the currently deployed Processing Units.- Wait for (and return) a Processing Unit by a specific name.- Register for Processing Unit deployments and undeployment events.- Register for all Processing Unit Instance addition and removal events (across all Processing Units).- Register for Managing Grid Service Manager change events on all Processing Units.- Register for backup Grid Service Manager change events on all Processing Units.

Space

Composed of one or more Space Instances, to form a Space topology (cluster).

* Get all the currently running Space Instances that are part of the Space.- Wait for X number of Space Instances to be up.- Register for Space Instance additions and removals events.- Register for Space Instance change mode events (for all Space Instances that are part of the Space).- Register for Space Instance replication status change events (for all Space Instances that are part of the Space).- Get aggregated Space statistics.- Register for aggregated Space statistics events (if monitoring).- Get a clustered GigaSpace to perform Space operations.

SpaceInstance

An actual instance of a Space that is part of a topology (cluster), usually running within a Processing Unit Instance.

A virtual machine (JVM) that is currently running at least one GigaSpaces component/service.

* Get the Grid Service Agent (if it exists).- Get the Grid Service Manager (if it exists).- Get the Grid Service Container (if it exists).- Get all the Processing Unit Instances that are running within the Virtual Machine.- Register for Processing Unit Instance additions and removals events.- Get all the Space Instances that are running within the Virtual Machine.- Register for Space Instance additions and removals events.- Get the details of the Virtual Machine (min/max memory, and so on).- Get the statistics of the Virtual Machine (heap used, and so on).- Register for statistics change events (if monitoring).

An actual Machine (identified by its host address) running one or more GigaSpaces components/services in one or more Virtual Machines. Associated with one Operating System.

* Get all the Grid Service Agents running on the Machine.- Get all the Grid Service Containers running on the Machine.- Get all the Grid Service Managers running on the Machine.- Get all the Virtual Machines running on the Machine.- Get all the Processing Unit Instances running on the Machine.- Register for Processing Unit Instance additions and removals events from the Machine.- Get all the Space Instances running on the Machine.- Register for Space Instances additions and removals events from the Machine.- Get the Operating System the Machine is running on.

Machines

Holds all the currently discovered Machines.

* Get all the currently running Machines.- Wait for X number of Machines to be up.- Register for Machine additions and removals events.

OperatingSystem

The Operating System GigaSpaces components/services are running on. Associated with one Machine.

* Get the details of the Operating System.- Get the Operating System statistics.- Register for statistics change events (if monitoring).

OperatingSystems

Holds all the currently discovered Operating Systems.

* Get all the current Operating Systems.- Get the aggregated Operating Systems details.- Get the aggregated Operating Systems statistics.- Register for aggregated Operating Systems statistics change events (if monitoring).- Register for Operating System level statistics change events (across all Operating Systems, if monitoring).

* Get all the current Transports.- Get the aggregated Transports details.- Get the aggregated Transports statistics.- Register for aggregated Transports statistics change events (if monitoring).- Register for Transport level statistics change events (across all Transports, if monitoring).

Accessing the Domain Model

There are two ways the Service Grid Admin API can be used to access information the Admin API can provide:

Call specific properties for the data, and enumerate over them (as shown in the example at the top of the page).

Register for specific events using the Service Grid Admin API. Events are handled by different components of the Admin API in similar manner. We will take one of them and use it as a reference example.

If we want to register, for example, for Grid Service Container additions, we can use the following code (note, removing the event listener is not shown here for clarity):

All other data structures use a similar API to register for events. Some might have specific events that go beyond just additions and removals, but they still use the same model. For example, here is how we can register for Space Mode change events across all currently running Space topologies and Space Instances:

Of course, we can register the same event listener on a specific ISpace topology, or event on a specific ISpaceInstance.

Details and Statistics

Some components in the Admin API can provide statistics. For example, an ISpaceInstance can provide statistics on how many times the read API was called on it. Statistics change over time, and in order to get them, either the property for the statistics can be used, or a statistics listener can be registered for statistics change events.

Details of a specific component provide information that does not change over time, but can be used to provide more information regarding the component, or to compute statistics. For example, the IVirtualMachine provides in its details, the minimum and maximum heap memory size, from which the IVirtualMachine statistics provide the currently used heap memory size. The detailed information is used to provide the percentage used in the Virtual Machine statistics.

The Admin API also provides aggregated details and statistics. For example, ISpace provides ISpaceStatistics, allowing you to get the aggregated statistics of all the different Space Instances that belong to it.

Each component in the Admin API that can provide statistics (either direct or aggregated statistics) implements the IStatisticsMonitor interface. The statistics monitor allows you to start or stop monitoring statistics. Monitoring for statistics is required if one wishes to register for statistics change events. The interval at which statistics are polled, is controlled using the statistics interval.

The statistics interval is an important event when the Admin API is not actively polling for statistics. Each call to a property of statistics only performs a remote call to the component, if the last statistics fetch happened before the statistics interval. This behavior means that users of the Admin API do not have to worry about “hammering” different components for statistics, since the Admin makes sure that statistics calls are cached internally for the statistics interval period.

An ISpaceInstance implements the IStatisticsMonitor interface. Calling StartMonitor and StopMonitor on it, causes monitoring of statistics to be enabled or disabled on it.

ISpace also implements the IStatisticsMonitor interface. Calling StartMonitor on it, causes it to start monitoring all its ISpaceInstance s. If an ISpaceInstance is discovered after the the call to startMonitor occurred, it starts monitoring itself automatically. This means that if the SpaceInstanceStatistics event was registered on the ISpace, it automatically starts to get Space Instance statistics change events for the newly discovered ISpaceInstance.

ISpaces also implements the IStatisticsMonitor interface. Calling StartMonitor on it, causes it to start monitoring all the ISpace s it has (and as a result, also ISpaceInstance s, - see the paragraph above). A SpaceInstanceStatistics can also be registered on the ISpaces level as well.

The above Space level statistics behavior works in much the same way with other components. For example, IVirutalMachine and IVirtualMachines, ITransport and ITransports, IOperatingSystem and OperatingSystems.

The IServiceGridAdmin interface also implements the IStatisticsMonitor interface. Calling StartMonitor on it, causes all holders to start monitoring. These include: ISpaces, IVirtualMachines, ITransports, and IOperatingSystems.