Edit Node

Use the Edit Node page to update the configuration data of a GlassFish Server node. You can also use this page to change the type of a node from CONFIG to DCOM or SSH to enable remote communication for the node.

If you change the type of the node from CONFIG to DCOM, default values are applied if any of the following fields is left empty:

If you change the type of the node from CONFIG to SSH, default values are applied if any of the following fields is left empty:

The options that the Edit Node page contains depend on the type of the node.

Options for All Types of Nodes

The following options are available for all types of nodes:

Name

The name that was assigned to the node when the node was created. This field is read only.

Type

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

CONFIG

The node does not support remote communication. If CONFIG, is selected, no options for DCOM or SSH configuration are displayed. If the current type of the node is SSH and you select CONFIG, DCOM or SSH configuration data is removed from the node's configuration when you save your changes.

DCOM

The node supports communication over the Distributed Component Object Model (DCOM) remote protocol. The DCOM protocol is available only on Windows systems.

SSH

The node supports communication over secure shell (SSH).

Node Host

The name of the host that the node is to represent after the node is updated. Whether this field is mandatory depends on the type of the node:

Node Directory

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

If this field is left empty, the configuration of the node is updated as follows:

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/.

If this field is left empty, the configuration of the node is updated as follows:

Additional Options for DCOM Nodes

The following options are available only if the Type field is set to DCOM:

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 DCOM.

Validate DCOM

If the Enabled option is selected, GlassFish Server tests the connection over DCOM to the node host before updating the node. As part of the test, GlassFish Server copies a script that is named delete_me.bat to the host.

If you select this option, the Remote Test Directory field is activated to enable you to provide the directory to which GlassFish Server should copy the script.

Remote Test Directory

The folder on the remote host in which GlassFish Server should create the delete_me.bat file. The user that the Windows User Name option specifies must have write access to this folder. Otherwise, an error occurs. The default is C:\.

Windows Domain

The name of the Windows domain that contains the user that the Windows User Name option specifies. The default is the name of the host on which the Administration Console is running.

Windows User Name

The user on this node's host that is to run the process for connecting to the host through DCOM. The default is the user that is running the DAS process. If the Node Host option is set to localhost-domain, the Windows User Name option is ignored.

Windows User Authentication

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

Password

The Windows 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 Windows User Password field and the Confirm Password field are activated to enable you to provide the password.

Password Alias

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

Windows User Password

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

Confirm Password

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

Password Alias

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

Additional Options for SSH Nodes

The following options are available only if the Type field is set to SSH:

Force

If the Enabled option is selected, the node is updated in the domain administration server (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.

If you change the type of the node from CONFIG to SSH and leave this field empty, the SSH Port option is set to 22.

If the Node Host option is set to localhost-domain, the SSH Port option is ignored.

SSH User Name

The user on this node's host that is to run the process for connecting to the host through SSH.

If you change the type of the node from CONFIG to SSH and leave this field empty, the User Name option is set to the user that is running the DAS process.

If the Node Host option is set to localhost-domain, the SSH User 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 User Password field and the Confirm 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.

Setup SSH

If the Enabled option is selected, GlassFish Server sets up an SSH key on the node host. GlassFish Server sets up the SSH key by copying existing key files from the DAS host or, if required, by generating the files before copying the files. This option is available only if the SSH User Authentication option is set to Key File.

Generate Key

If the Enabled option is selected, GlassFish Server generates the SSH key files before copying the files to the node host.

SSH User Password

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

Confirm 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 User Password field.

Password Alias

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

Public Key File

The absolute path to the SSH public key file for user that the SSH User Name option specifies. The content of the public key file is appended to the user's .ssh/authorized_keys file on the node host. If the .ssh/authorized_keys file does not exist on the host, GlassFish Server creates the file.

The path to the key file must be reachable by the DAS and the key file must be readable by the DAS.

The default is a key file in the user's .ssh directory. If multiple key files are found, GlassFish Server uses the following order of preference:

  1. id_rsa

  2. id_dsa

  3. identity

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(1) 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 default depends on whether you change the type of the node from CONFIG to SSH to enable SSH communication for the node:

If you change the type of the node from CONFIG to SSH and leave this field empty, the Key File option is set to a key file in the user's .ssh directory. If multiple key files are found, GlassFish Server uses the following order of preference:

  1. id_rsa

  2. id_dsa

  3. identity

Related Tasks

To Edit a Node

Equivalent asadmin Subcommands
Copyright © 2005, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices