| 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
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
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
After setting up SSH on a host, test the setup to ensure that you can use SSH to contact the host from another host. Testing the SSH setup on a host verifies that the SSH server daemon sshd is running and that the SSH user has a valid user account on the host.
If you cannot use SSH to contact the host, troubleshoot the SSH setup before setting up SSH user authentication.
$ ssh -l user-name host-name
The user name for the SSH user's account on the host.
The host name of the host that you are logging in to.
If this step succeeds, your setup of SSH is complete.
The first time that you connect to a host, you might be warned that the authenticity cannot be established and be asked if you want to continue connection. If you trust the host, answer yes to connect to the host.
Troubleshooting
To obtain diagnostic information, use the -v option of the command-line SSH client and the -d option of the SSH server daemon sshd. How to start the SSH server daemon sshd manually depends on the operating system and SSH provider that you are using.
If the SSH server daemon sshd is set up on a host that has a firewall, ensure that a rule is defined to allow inbound traffic on the SSH port. The default SSH port is port 22.
If your connection is refused, the SSH server daemon sshd is not running and you must start the daemon. For instructions, see the following sections:
If your connection is accepted, but you cannot log in, ensure that the SSH user has a valid user account on the host.
Next Steps
After testing the SSH setup, set up SSH user authentication to enable SSH to authenticate users without prompting for a password. For more information, see Setting Up SSH User Authentication.
|