en.help.ref-nodenew.html Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of console-cluster-plugin-help
Online help content for the console-cluster-plugin bundle.
There is a newer version: 3.2-b03

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:


The name must start with a letter, a number, or an underscore.


The name may contain only the following characters:


Lowercase letters


Uppercase letters


Numbers


Hyphen


Period


Underscore



The name must be unique in the domain and must not be the name of another node, a cluster, a named configuration, or a GlassFish Server instance.


The name must not be domain, server, or any other keyword that is reserved by GlassFish Server.



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 and the Installation Directory field is cleared.




Node Host
The name of the host that the node represents. Whether this field is mandatory depends on the type of the node:


If the type of the node is CONFIG, the name of the host may be omitted. The name of the host can be determined when instances that reside on the node are created.


If the type of the node is SSH, 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. If a relative path is specified, the path is relative to the as-install directory.

The default depends on the type of the node:


If the type of the node is CONFIG, no directory for instances is specified for the node in the domain administration server (DAS) configuration. The node directory can be determined when instances that reside on the node are created.


If the type of the node is SSH, the default is as-install/nodes, where as-install is the base installation directory of the GlassFish Server software on the host.



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 depends on the type of the node:


If the type of the node is CONFIG, no installation directory is specified for the node in the DAS configuration. The installation directory can be determined when instances that reside on the node are created.


If the type of the node is SSH, the default is the parent of the default base installation directory of the GlassFish Server software for the 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-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. 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-domain, 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 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:


id_rsa


id_dsa


identity




Related Tasks

To Create a Node


Equivalent asadmin Subcommands

create-node-config(1)


create-node-ssh(1)




Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices