| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
1. High Availability in GlassFish Server
2. Setting Up SSH for Centralized Administration
3. Administering GlassFish Server Nodes
4. Administering GlassFish Server Clusters
5. Administering GlassFish Server Instances
Administering GlassFish Server Instances Centrally
To Create an Instance Centrally
To List All Instances in a Domain
To Delete an Instance Centrally
To Start an Individual Instance Centrally
To Stop an Individual Instance Centrally
To Restart an Individual Instance Centrally
Administering GlassFish Server Instances Locally
To Start an Individual Instance Locally
To Stop an Individual Instance Locally
To Restart an Individual Instance Locally
Resynchronizing GlassFish Server Instances and the DAS
Default Synchronization for Files and Directories
To Resynchronize an Instance and the DAS Online
To Resynchronize Library Files
To Resynchronize Custom Configuration Files for an Instance
To Resynchronize Users' Changes to Files
To Resynchronize Additional Configuration Files
To Prevent Deletion of Application-Generated Files
To Resynchronize an Instance and the DAS Offline
To Enable Automatic EJB Timer Migration for Failed Clustered Instances
To Migrate EJB Timers Manually
6. Administering Named Configurations
7. Configuring Web Servers for HTTP Load Balancing
8. Configuring HTTP Load Balancing
9. Upgrading Applications Without Loss of Availability
10. Configuring High Availability Session Persistence and Failover
11. Configuring Java Message Service High Availability
Each GlassFish Server instance is one of the following types of instance:
A standalone instance does not share its configuration with any other instances or clusters. A standalone instance is created if either of the following conditions is met:
No configuration or cluster is specified in the command to create the instance.
A configuration that is not referenced by any other instances or clusters is specified in the command to create the instance.
When no configuration or cluster is specified, a copy of the default-config configuration is created for the instance. The name of this configuration is instance-name-config, where instance-name represents the name of an unclustered server instance.
A shared instance shares its configuration with other instances or clusters. A shared instance is created if a configuration that is referenced by other instances or clusters is specified in the command to create the instance.
A clustered instance inherits its configuration from the cluster to which the instance belongs and shares its configuration with other instances in the cluster. A clustered instance is created if a cluster is specified in the command to create the instance.
Any instance that is not part of a cluster is considered an unclustered server instance. Therefore, standalone instances and shared instances are unclustered server instances.
|