New Node

Use the New Node page to create a GlassFish Server node. A node represents a host on which the GlassFish Server software is installed. A node must exist for every host on which GlassFish Server instances reside.

The New Node page contains the following options:

Name

The name of the node.

The name must meet the following requirements:

Type

Drop-down list to specify the type of the node, which is one of the following types:

SSH

The node supports communication over secure shell (SSH).

CONFIG

The node does not support remote communication. If CONFIG, is selected, no options for SSH configuration are displayed.

Node Host

The name of the host that the node represents. The name of the host must be specified. Otherwise, an error occurs.

Node Directory

The path to the directory that is to contain GlassFish Server instances that are created on the node. The default is as-install/nodes, where as-install is the base installation directory of the GlassFish Server software on the host. If a relative path is specified, the path is relative to the as-install directory.

Installation Directory

The full path to the parent of the base installation directory of the GlassFish Server software on the host, for example, /export/glassfish3/. The default is the parent of the default base installation directory of the GlassFish Server software for the domain administration server (DAS). This default is useful only if GlassFish Server is installed in the same location on all hosts.

Force

If the Enabled option is selected, the node is created in the DAS configuration even if validation of the node's parameters fails. To validate a node's parameters, the DAS must be able to contact the node's host through SSH.

SSH Port

The port to use for SSH connections to this node's host. The default is 22. If the Node Host option is set to localhost, the SSH port option is ignored.

SSH User Name

The user that is to run the process for connecting to this node's host through SSH. The default is the user that is running the DAS process. To ensure that the DAS can read this user's SSH private key file, specify the user that is running the DAS process. If the Node Host option is set to localhost, the User Name option is ignored.

SSH User Authentication

Drop-down list to specify how the SSH user is authenticated when logging in to this node's host. The possible methods for authentication are as follows:

Key File

The SSH user is authenticated through an SSH private key file. If you select this option, specify the absolute path to the file in the Key File field.

Password

The SSH user is authenticated through a password that is stored in the DAS configuration.


Caution - This password is stored in clear text in the DAS configuration. For enhanced security, use a key file or a password alias


If you select this option, the SSH Password field and the Confirm SSH Password field are activated to enable you to provide the password.

Password Alias

The SSH user is authenticated through a password alias. If you select this option, select the password alias from the Password Alias drop-down list.

SSH Password

The password that the SSH user will use when logging in to this node's host.

Confirm SSH Password

Confirmation of the password that the SSH user will use when logging in to this node's host. The content of this field must match exactly the content of the SSH Password field.

Password Alias

Drop-down list of password aliases that are defined for this domain.

Key File

The absolute path to the SSH private key file for user that the User Name option specifies. This file is used for authentication to the sshd daemon on the node's host.


Note - GlassFish Server also supports password authentication through the AS_ADMIN_SSHPASSWORD entry in the password file. The password file is specified in the --paswordfile option of the asadmin(1M) utility.


If the SSH private key file is protected by a passphrase, the password file must contain the AS_ADMIN_SSHKEYPASSPHRASE entry.

The path to the key file must be reachable by the DAS and the key file must be readable by the DAS. The path may contain Java properties of the form ${prop.name}.

The default is the a platform-dependent key file in the user's .ssh directory, for example:

Related Tasks
Equivalent asadmin Subcommands
Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices