| 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
6. Administering Named Configurations
Creating, Listing, and Deleting Named Configurations
To Create a Named Configuration
To List the Named Configurations in a Domain
To List the Targets of a Named Configuration
To Delete a Named Configuration
Modifying Properties for Named Configurations and Instances
Properties for Port Numbers in a Named Configuration
To Modify a Named Configuration's Properties
To Modify Port Numbers of an Instance
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
Configurations exist in a domain. Multiple GlassFish Server instances or clusters in the domain can reference the same configuration, or they can have separate configurations. To ensure that the environment in a cluster’s instances is homogenous, all instances in the cluster inherit the cluster’s configuration.
Each named configuration is one of the following types of configuration:
A standalone configuration is referenced by only one instance or cluster and is not shared with any other instances or clusters.
Note - A configuration that is referenced by only one cluster is a standalone configuration, even if the cluster contains multiple instances.
A shared configuration is referenced by multiple instances or clusters.
The type of an unclustered instance is determined by the type of the configuration that the instance references. For more information, see Types of GlassFish Server Instances.
The default-config configuration is a special configuration that acts as a template for creating named configurations. Clusters and instances cannot refer to the default-config configuration. The default-config configuration can only be copied to create configurations.
When you create a cluster or an instance, you can choose whether to specify an existing configuration that the new cluster or instance will reference. If you choose to create a cluster or an instance without specifying an existing configuration, GlassFish Server automatically creates a configuration for the cluster or instance. For more information, see the following sections:
GlassFish Server automatically creates a configuration by copying the default-config configuration. If you require an instance or cluster to reference a copy of a different configuration, copy the configuration and specify the copy when you create the instance or cluster. For information about how to copy a configuration, see To Create a Named Configuration.
GlassFish Server assigns the name cluster-or-instance-config to an automatically created configuration. cluster-or-instance is the name of the cluster or instance for which the configuration is created. The server-config configuration is automatically created for the domain administration server (DAS) when the domain is created.
When a named configuration is created, GlassFish Server creates a configuration directory on the domain administration server (DAS) at domain-dir/config/config-name.
The directory in which the domain's configuration is stored.
The name that was assigned to the configuration when the configuration was created.
This contents of this directory are synchronized to all instances that inherit or reference the configuration.
|