Package org.apache.geronimo.clustering

The Geronimo Clustering implementation.

See:
          Description

Interface Summary
DataDeltaListener An interface implemented by components that wish to be notified about changes to Cluster state.
DataListener An interface implemented by components that wish to have their state initialised from the Cluster.
MetaDataListener An interface implemented by components that wish to be notified upon membership of a Cluster changing.
 

Class Summary
Cluster A 'Cluster' is a point of connection between all 'Cluster's with the same name, running in other VMs.
Data An object capable of holding the state of multiple applications and tiers.
DataDelta An object capable of holding a Data change (Delta) and applying it to said Data.
LocalCluster A uniquely identifiable n->n intra-vm event-raising communications channel.
MBeanImpl A base class containing fnality useful to the MBeans of the Clustering module.
NamedMBeanImpl A base class containing fnality useful to Named MBeans of the Clustering module.
Node A Node is an instance of a connection to a Cluster.
Tier Tier abstracts code common to different Tier impls into the same abstract base.
 

Package org.apache.geronimo.clustering Description

The Geronimo Clustering implementation.

Basically it works like this...

  • A Geronimo instance has N Cluster instances.
  • A Cluster instance has N Node instances.
  • A Node instance has N Tier instances (each of a different type - e.g. web/ejb/jndi/etc.).
  • Each Tier instance is responsible for connecting Application state, of a corresponding type, to the Cluster's Data Collection .
  • Clusters, Nodes and Tiers are statically described in a descriptor (clustering-service.xml) that is deployed in the Geronimo instance.

    Other types, more closely bound to the Application arena (e.g. HttpSessionManager) are created dynamically as and when required and hooked to a corresponding Tier Object as described above.

    Messages may travel to and from these types, via their Cluster.

    Clusters map onto backends that are capable of transporting these messages between JVMs, hence this collection of types forms the backbone of Geronimo's distributed architecture.

    All of these types are MBeans, so will register with Geronimo's JMX Agent and export interfaces to it that allow useful information about their internal state to be read and possible written by JMX Clients.



    Copyright © 2003-2005 Apache Software Foundation. All Rights Reserved.