GlassFish Server Documentation Set
Related Documentation
Typographic Conventions
Symbol Conventions
Default Paths and File Names
Documentation, Support, and Training
Documentation Accessibility
Java EE Platform Overview
Java EE Applications
Containers
Java EE Services
Web Services
Client Access
External Systems and Resources
GlassFish Server Components
Server Instances
Administrative Domains
Domain Administration Server (DAS)
Clusters
Named Configurations
HTTP Load Balancer Plug-in
Session Persistence
IIOP Load Balancing in a Cluster
Message Queue and JMS Resources
Configuration Roadmap for High Availability of GlassFish Server
To Configure GlassFish Server for High Availability
Establishing Performance Goals
Estimating Throughput
Estimating Load on GlassFish Server Instances
Maximum Number of Concurrent Users
Think Time
Average Response Time
Requests Per Minute
Planning the Network Configuration
Setting Up Traffic Separation
Estimating Bandwidth Requirements
Calculating Bandwidth Required
Estimating Peak Load
Choosing Network Cards
Planning for Availability
Rightsizing Availability
Using Clusters to Improve Availability
Adding Redundancy to the System
Identifying Failure Classes
Planning Failover Capacity
Design Decisions
Designing for Peak or Steady State Load
System Sizing
Sizing the Administration Thread Pool
Planning Message Queue Broker Deployment
Multi-Broker Clusters
Master Broker and Client Synchronization for Conventional Clusters
Configuring GlassFish Server to Use Message Queue Brokers
Java Message Service Type
Managing JMS with the Administration Console
Managing JMS with asadmin
Default JMS Host
Example Deployment Scenarios
Default Deployment
Using a Message Queue Broker Cluster with a GlassFish Server Cluster
Specifying an Application-Specific Message Queue Broker Cluster
Application Clients
Checklist