deletes a node that is not enabled for remote communication
delete-node-config [--help] node-name
delete-node-config subcommand deletes a node that is not enabled for remote communication from the domain. This subcommand does not require the Distributed Component Object Model (DCOM) remote protocol or 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 DCOM must be deleted by using the delete-node-dcom(1) subcommand.
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.
The predefined node
localhost-domain cannot be deleted.
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
The name of the node to delete. The node must not be enabled for communication over DCOM or SSH. Otherwise, an error occurs.
This example deletes the node
sj03, which is not enabled for remote communication.
asadmin> delete-node-config sj03 Command delete-node-config executed successfully.
command executed successfully
error in executing the command
create-node-config(1), create-node-dcom(1), delete-node-ssh(1), delete-instance(1), delete-local-instance(1), install-node(1), install-node-dcom(1), install-node-ssh(1), list-nodes(1), uninstall-node(1), uninstall-node-dcom(1), uninstall-node-ssh(1), update-node-config(1), update-node-dcom(1), update-node-ssh(1)