Content with label cluster in Coherence 3.4 User Guide (See content from all spaces)
Related Labels: heap , failover , best-practices , coherence-web , proxy , session-management , servletcontext , production-environment , listeners , reliability , availability , backing-map , c-w-archive , core-concept , service , network , failback , sessions , scalability , performance , serviceability , testing , optimistic , httpsessioncontext , death-detection , invocation , example , faq-coherence-web , faq-config , multicast , federation , glossary , member , operating-system , session-cache-config , mbeans , replication , mutext , local , hardware , distributed , update-after-forums-move , manageability , singleton , faq-code-examples , security , events , load-balancing more »

Advanced Session Scoping Sometimes you may want to explicitly prevent HTTP session data from being shared by different Java EE applications that participate in the same Coherence cluster. For example, say you have two applications {{HRPortal}} and {{InWeb}} that share cached ...

Automatically manage dynamic cluster membership Coherence manages cluster membership, automatically adding new servers to the cluster when they start up and automatically detecting their departure when they are shut down or fail. Applications have full access to this information, and can sign up to receive event notifications ...

Clustering Coherence is built on a fully clustered architecture. Since "clustered" is an overused term in the industry, it is worth stating exactly what it means to say that Coherence is clustered. Coherence is based on a peertopeer clustering protocol, using a conference room model, in which servers ...

Cluster Services Overview Coherence functionality is based on the concept of cluster services. Each cluster node can participate in (which implies both the ability to provide and to consume) any number of named services. These named services may already exist, which is to say that they may already ...

Cluster your objects and your data Coherence is an essential ingredient for building reliable, highscale clustered applications. The term clustering refers to the use of more than one server to run an application, usually for reliability and scalability purposes. Coherence provides all of the necessary capabilities for applications ...

Coherence Caching Terminology several terms which are used to describe the ability of multiple servers to work together to handle additional load or to survive the failure of a particular server. Basic terms Failover Failover refers to the ability of a server to assume the responsibilities of a failed server. For example, "When ...

How to Manage Custom MBeans Within the Coherence Cluster addition to How to Manage Coherence Using JMX, Coherence http://www.tangosol.com/coherence.jsp provides the ability to manage and monitor "custom MBeans" (i.e. applicationlevel MBeans) within the Coherence JMX Management and Monitoring framework. This allows you to manage and/or monitor any ...

Production Checklist Deploying Coherence in a production environment is very different from using Coherence in a development environment. Development environments do not reflect the challenges of a production environment. Coherence tends to be so simple to use in development that developers do not take the necessary planning steps ...

Session Management for Clustered Applications CoherenceWeb content has been moved and consolidated under the CoherenceWeb Session Management Module page