JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide
search filter icon
search icon

Document Information


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

Types of 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 a Cluster

To Stop a Cluster

To Start an Individual Instance Centrally

To Stop an Individual Instance Centrally

To Restart an Individual Instance Centrally

Administering GlassFish Server Instances Locally

To Create an Instance Locally

To Delete an Instance 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

Migrating EJB Timers

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

12.  RMI-IIOP Load Balancing and Failover


Chapter 5

Administering GlassFish Server Instances

A GlassFish Server instance is a single Virtual Machine for the Java platform (Java Virtual Machine or JVM machine) on a single node in which GlassFish Server is running. A node defines the host where the GlassFish Server instance resides. The JVM machine must be compatible with the Java Platform, Enterprise Edition (Java EE).

GlassFish Server instances form the basis of an application deployment. An instance is a building block in the clustering, load balancing, and session persistence features of GlassFish Server. Each instance belongs to a single domain and has its own directory structure, configuration, and deployed applications. Every instance contains a reference to a node that defines the host where the instance resides.

The following topics are addressed here: