Before setting up SSH, decide which SSH user GlassFish Server will use when connecting to remote hosts. For the following reasons, administration is simplest if the SSH user is the user that starts the DAS:
For public key authentication, the user that starts the DAS must be able to read the SSH user's private key file.
Remote instances are started as the SSH user.
By default, the DAS assumes that the SSH user is the user that is running the DAS.
The environment of the SSH user on any remote host to which the user will connect must meet the requirements that are stated in Paths and Environment Settings for the JDK Software in Oracle GlassFish Server 3.1-3.1.1 Release Notes.
The SSH user's environment on a host is set by the environment set-up files that are run when the user uses SSH to run a command on the host. You must ensure that these files set up the SSH user's environment correctly.
The files that are run when the user uses SSH to run a command are different than the files that are run when the user logs in to a host. For example, in the bash shell, .profile and .bashrc are run when the user logs in, but only .bashrc is run when the user runs a command. Therefore, in the bash shell, you must ensure that .bashrc contains the required environment settings for the SSH user.
Note - The User Account Control (UAC) feature is available only on some versions of the Windows operating system, for example, Windows 7, Windows Vista, and Windows 2008.
You might be using a UAC-enabled Windows system and choose to store files for GlassFish Server instances in a directory other than the SSH user's home directory. In this situation, the SSH user must have native (that is, nonvirtual) read and write access to the file system where the instances are to be stored. The OS-level administrator has such access by default. You can also configure the system to grant such access to other users. For more information, see the documentation for the Windows operating system.