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
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
Set up the MKS Toolkit on the DAS host and on all hosts where instances in your cluster will reside.
The following topics are addressed here:
For centralized GlassFish Server administration, the default installation of the MKS Toolkit is sufficient.
See Also
For detailed information about installing MKS Toolkit, seeInstalling MKS Toolkit in MKS Toolkit v9.4 Release Notes.
To enable GlassFish Server tools to find commands for SSH, each user's path for Windows and for the MKS Toolkit shell must contain the following directories:
The MKS Toolkit bin directory, for example C:\Program Files\MKS Toolkit\mksnt
The bin directory of the JDK software
The MKS Toolkit installer automatically adds the MKS Toolkit bin directory to the path. However, you must add the bin directory of the JDK software to the path yourself.
Logging in as a user with Administrator privileges ensures that the change applies to all users.
The SSH Server Daemon sshd locates a user's home directory from the configuration in the user database, not from environment variables such as HOME. To ensure that all GlassFish Server commands can run without errors, each SSH user must be configured to have a home directory.
Each user on a Windows host where SSH is set up potentially has two home directories:
Windows home directory. GlassFish Server commands, which are run in a Windows command window, use the Windows home directory.
SSH home directory. SSH commands, which are run in a shell such as bash or ksh, use the SSH home directory.
If these home directories are different, GlassFish Server and SSH each locate a user's .ssh directory in different directories. To simplify the set up of SSH, configure each user's home directory for SSH and Windows to be the same directory. A disadvantage of this approach is that the SSH home directory has spaces in its path name. Spaces in path names are cumbersome in the UNIX environment.
|
HOMEPATH
HOMEDRIVE
Home Directory
Home Directory Drive
$ userinfo user-name
The user name for the user whose home directory you are setting, for example Administrator.
If the settings match, no further action is required.
To update the settings, run the following command in an MKS Toolkit shell:
$ userinfo -u -fHomeDirDrive:"drive" -fHomeDir:"path" user-name
The drive identifier of the disk drive on which the user's Windows home directory resides, for example, C:.
The path to the user's Windows home directory, for example, \Documents and Settings\Administrator.
The user name for the user whose home directory you are setting, for example Administrator.
$ userinfo user-name
The user name for the user whose home directory you are setting, for example Administrator.
Example 2-1 Setting the Home Directory for the MKS Toolkit User
This example sets the home directory for the MKS Toolkit user Administrator to C:\Documents and Settings\Administrator.
$ userinfo -u -fHomeDirDrive:"C:" -fHomeDir:"\Documents and Settings\Administrator" Administrator
Note - Do not set the command shell to cmd.exe. The use of SSH for centralized GlassFish Server administration requires a shell in the style of a UNIX shell.
$ service query MKSSecureSH Name: MKS Secure Shell Service Service Type: WIN32_OWN_PROCESS Current State: RUNNING Controls Accepted: ACCEPT_STOP Check Point: 0 Wait Hint: 0 Start Type: AUTO_START Error Control: IGNORE Path: "C:\Program Files\MKS Toolkit\bin\secshd.exe" Dependency: NuTCRACKERService Dependency: tcpip Service Start Name: LocalSystem
Next Steps
After you have completed the setup of SSH on a host, test the setup on the host as explained in Testing the SSH Setup on a Host.