This topic describes VMware Tanzu GemFire’s federated MBean architecture.
Tanzu GemFire uses MBeans to manage and monitor different parts of Tanzu GemFire. Tanzu GemFire’s federated MBean architecture is scalable and allows you to have a single-agent view of a Tanzu GemFire cluster.
Federation of Tanzu GemFire MBeans and MBeanServers
Federation of the MBeanServers means that one member, the JMX Manager Node, can provide a proxied view of all the MBeans that the MBeanServer hosts. Federation also means that operations and notifications are spread across the cluster.
Tanzu GemFire federation takes care of the following functionality:
- MBean proxy creation
- MBean state propagation
- Notifications propagation
- Operation invocation
MBean Proxy Naming Conventions
Each Tanzu GemFire MBean follows a particular naming convention for easier grouping. For example:
GemFire:type=Member,service=LockService,name=<dlsName>,memberName=<memberName>
At the JMX Manager node, this MBean will be registered with GemFire/<memberId> as domain.
The following are some sample MBean names:
MemberMBean:
GemFire:type=Member,member=<Node1>
Use of MXBeans
In its Management API, Tanzu GemFire provides MXBeans to ensure that any MBeans that are created are usable by any client, including remote clients, without requiring the client to access specific classes in order to access contents of the MBean.
MBean Proxy Creation
Tanzu GemFire proxies are inherently local MBeans. Every Tanzu GemFire JMX manager member hosts proxies pointing to the local MBeans of every managed node. Proxy MBeans will also emit any notification emitted by local MBeans in managed nodes when an event occurs in that managed node.
Note: Aggregate MBeans on the JMX Manager node are not proxied.
