All Downloads are FREE. Search and download functionalities are using the official Maven repository.

com.sun.enterprise.v3.admin.cluster.delete-node-config.1 Maven / Gradle / Ivy

delete-node-config(1)     asadmin Utility Subcommands    delete-node-config(1)

NAME
       delete-node-config - deletes a node that is not enabled for remote
       communication

SYNOPSIS
           delete-node-config [--help] node-name

DESCRIPTION
       The delete-node-config subcommand deletes a node that is not enabled
       for remote communication from the domain. This subcommand does not
       require the secure shell (SSH) to be configured.

       This subcommand can delete only a node that is not enabled for remote
       communication. The subcommand for deleting other types of nodes depends
       on the type of the node:

       *   A node that is enabled for remote communication over SSH must be
           deleted by using the delete-node-ssh(1) subcommand.

       To determine whether a node is enabled for remote communication, use
       the list-nodes(1) subcommand.

       No GlassFish Server instances must reside on the node that is being
       deleted. Otherwise, the subcommand fails. Before running this
       subcommand, delete any instances that reside on the node by using, for
       example, the delete-instance(1) subcommand or the
       delete-local-instance(1) subcommand.

           Note
           +--------------------------------------+
           |           The predefined node        |
           |           localhost-domain cannot be |
           |           deleted.                   |
           +--------------------------------------+

       This subcommand is supported in remote mode only.

OPTIONS
       --help, -?
           Displays the help text for the subcommand.

OPERANDS
       node-name
           The name of the node to delete. The node must not be enabled for
           communication over SSH. Otherwise, an error occurs.

EXAMPLES
       Example 1, Deleting a Node That Is Not Enabled for Remote Communication
           This example deletes the node sj03, which is not enabled for remote
           communication.

               asadmin> delete-node-config sj03

               Command delete-node-config executed successfully.

EXIT STATUS
       0
           command executed successfully

       1
           error in executing the command

SEE ALSO
       create-node-config(1), delete-node-ssh(1),
       delete-instance(1), delete-local-instance(1), install-node(1),
       install-node-ssh(1), list-nodes(1),
       uninstall-node(1), uninstall-node-ssh(1),
       update-node-config(1), update-node-ssh(1)

       asadmin(1M)

Jakarta EE 10                         8 Dec 2011             delete-node-config(1)




© 2015 - 2025 Weber Informatics LLC | Privacy Policy