| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server Message Queue 4.5 Administration Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server Message Queue 4.5 Administration Guide |
Part I Introduction to Message Queue Administration
1. Administrative Tasks and Tools
3. Starting Brokers and Clients
6. Configuring and Managing Connection Services
8. Configuring Persistence Services
9. Configuring and Managing Security Services
The Cluster Configuration File
Cluster Configuration Properties
Cluster Connection Service Properties
Conventional Broker Cluster Properties
Enhanced Broker Cluster Properties
Displaying a Cluster Configuration
Managing Conventional Clusters
Connecting Brokers into a Conventional Cluster
Adding Brokers to a Conventional Cluster
Removing Brokers From a Conventional Cluster
Changing the Master Broker in a Conventional Cluster with Master Broker
Managing a Conventional Cluster's Configuration Change Record
Converting Between Types of Conventional Clusters
Connecting Brokers into an Enhanced Cluster
Adding and Removing Brokers in an Enhanced Cluster
Preventing or Forcing Broker Failover
Backing up a Shared Data Store
Converting a Conventional Cluster to an Enhanced Cluster
Cluster Conversion : File-Based Data Store
Cluster Conversion: JDBC-Based Data Store
11. Managing Administered Objects
12. Configuring and Managing Bridge Services
13. Monitoring Broker Operations
14. Analyzing and Tuning a Message Service
17. Broker Properties Reference
18. Physical Destination Property Reference
19. Administered Object Attribute Reference
20. JMS Resource Adapter Property Reference
21. Metrics Information Reference
22. JES Monitoring Framework Reference
A. Distribution-Specific Locations of Message Queue Data
B. Stability of Message Queue Interfaces
Message Queue supports the use of broker clusters: groups of brokers working together to loprovide message delivery services to clients. Clusters enable a message service to scale its operations to meet an increasing volume of message traffic by distributing client connections among multiple brokers.
In addition, clusters provide for message service availability. In the case of a conventional cluster, if a broker fails, clients connected to that broker can reconnect to another broker in the cluster and continue producing and consuming messages. In the case of an enhanced cluster, if a broker fails, clients connected to that broker reconnect to a failover broker that takes over the pending work of the failed broker, delivering messages without interruption of service.
See the Chapter 4, Broker Clusters, in Oracle GlassFish Server Message Queue 4.5 Technical Overview for a description of conventional and enhanced broker clusters and how they operate.
This chapter describes how to configure and manage both conventional and enhanced broker clusters:
|