The table below describes each GemFire resource type; the right column indicates the inventory level for a type in the vRealize Hyperic inventory model.

Table 1. GemFire Resources and the Hyperic Inventory Model

GemFire Resource Hierarchy

Description

Inventory Type

GemFire Distributed System (DS)

GemFire is a distributed caching system. A GemFire Distributed System (DS) is a logical entity --- a set of servers that are configured to communicate with one another. The servers in a DS are referred to as members or nodes. Member types (defined in the rows below) include:

  • JMX Agent

  • Gateway Hub 6.5

  • Cache Server 6.5

  • Application Peer 6.5

platform

JMX Agent

A GemFire JMX Agent is an administrative member of a DS through which the Hyperic Agent obtains GemFire resource and metric data. The JMX Agent returns ModelMBeans attributes that correspond to inventory properties and metric values for members of the DS.

server

Gateway Hub 6.5

A Gateway Hub is present in a DS that is part of a multi-DS deployment. The Gateway Hub for a DS:

  • Creates and manages Gateways for communicating with remote DSs.

  • Receives gateway events from other DSs, and distributes the events to one or all local gateways, in accordance with its distribution policy.

  • Hosts a GemFire cache.

server

Gateway Hub 6.5 Gateway

A Gateway manages a queue of events (where an event is an operation that affects a specific region) to be propagated to a particular remote DS.

service

Cache Server 6.5

A Cache Server is a server for cached objects. (As opposed to a GemFire Application Peer, which is a GemFire cache within an application).

server

Application Peer 6.5

An Application Peer is an application process running a GemFire cache.

server

regions

In GemFire, a region is a set of cached objects that are managed in accordance with the same policies. For example, rules for expiration, data policy, scope, the directories to which region data is written, the Gateway Hub to which region events are distributed, and so on.

A region can have subregions, which in turn can have their own subregions. Regions provide a hierarchical namespace for sets of objects in a cache. A region can exist in any non-admin member of the DS. The name of a region in vRealize Hyperic indicates the resource type of its parent in the managed resource hierarchy:

  • Application Peer 6.5 Region

  • Cache Server 6.5 Region

  • Gateway Hub 6.5 Region

service

Note:

For more information about the managed resource hierarchy, see the vRealize Hyperic Overview guide.