| 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
About SSH for Centralized Administration
Determining Whether to Use SSH for Centralized Administration
Requirements for the SSH User's Environment
File Access Permissions on UAC-Enabled Windows Systems
Setting Up Cygwin SSH on Windows
To Download and Install Cygwin
To Set the Path for Windows and for the Cygwin Shell
To Set the Home Directory for the Cygwin SSH User
To Configure and Start the Cygwin SSH Server Daemon sshd
Setting Up the MKS Toolkit on Windows
To Set the Path for Windows and for the MKS Toolkit Shell
To Set the Home Directory for the MKS Toolkit SSH User
To Configure and Start the MKS Toolkit SSH Server Daemon sshd
Setting Up SSH on UNIX and Linux Systems
To Set Up SSH on Oracle Solaris Systems
To Set Up SSH on MacOS Systems
To Set Up SSH on Linux systems
Testing the SSH Setup on a Host
To Test the SSH Setup on a Host
Setting Up SSH User Authentication
To Set Up Public Key Authentication Without Encryption
To Set Up Encrypted Public Key Authentication
To Set Up Password Authentication
Installing and Removing GlassFish Server Software on Multiple Hosts
To Copy a GlassFish Server Installation to Multiple Hosts
To Remove GlassFish Server Software From Multiple Hosts
3. Administering GlassFish Server Nodes
4. Administering GlassFish Server Clusters
5. Administering GlassFish Server Instances
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
GlassFish Server uses secure shell (SSH) to ensure that clusters that span multiple hosts can be administered centrally. To perform administrative operations on GlassFish Server instances that are remote from the domain administration server (DAS), the DAS must be able to communicate with those instances. If an instance is running, the DAS connects to the running instance directly. For example, when you deploy an application to an instance, the DAS connects to the instance and deploys the application to the instance.
However, the DAS cannot connect to an instance to perform operations on an instance that is not running, such as creating or starting the instance. For these operations, the DAS uses SSH to contact a remote host and administer instances there. SSH provides confidentiality and security for data that is exchanged between the DAS and remote hosts.
Note - The use of SSH to enable centralized administration of remote instances is optional. If the use of SSH is not feasible in your environment, you can administer remote instances locally.
The following topics are addressed here:
|