Oracle GlassFish Server 3.1 Section 1: asadmin Utility Subcommands
create-connector-connection-pool(1)
create-connector-security-map(1)
create-connector-work-security-map(1)
create-jdbc-connection-pool(1)
create-message-security-provider(1)
create-resource-adapter-config(1)
delete-connector-connection-pool(1)
delete-connector-security-map(1)
delete-connector-work-security-map(1)
delete-jdbc-connection-pool(1)
delete-message-security-provider(1)
delete-resource-adapter-config(1)
disable-http-lb-application(1)
disable-secure-admin-internal-user(1)
disable-secure-admin-principal(1)
enable-secure-admin-internal-user(1)
enable-secure-admin-principal(1)
list-connector-connection-pools(1)
list-connector-security-maps(1)
list-connector-work-security-maps(1)
list-message-security-providers(1)
list-resource-adapter-configs(1)
list-secure-admin-internal-users(1)
list-secure-admin-principals(1)
list-supported-cipher-suites(1)
unfreeze-transaction-service(1)
update-admin-server-coordinates(1)
update-admin-server-local-coordinates(1)
update-connector-security-map(1)
update-connector-work-security-map(1)
Oracle GlassFish Server 3.1 Section 1M: Utility Commands
Oracle GlassFish Server 3.1 Section 5ASC: GlassFish Server Concepts
- deletes a node that is not enabled for remote communication
delete-node-config [--help] node-name
The delete-node-config subcommand deletes a node that is not enabled for remote communication from the domain. This subcommand does not require secure shell (SSH) to be configured.
This subcommand can delete only a node that is not enabled for remote communication. A node that is enabled for communication over SSH must be deleted by using the delete-node-ssh(1) subcommand. To determine whether a node is enabled for communication over SSH, 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.
Displays the help text for the subcommand.
The name of the node to delete. The node must not be enabled for communication over SSH. Otherwise, an error occurs.
Example 1 Deleting a Node That Is Not Enabled for Communication Over SSH
This example deletes the node sj03, which is not enabled for communication over SSH.
asadmin> delete-node-config sj03 Command delete-node-config executed successfully.
command executed successfully
error in executing the command
create-node-config(1), delete-node-ssh(1), delete-instance(1), delete-local-instance(1), install-node(1), list-nodes(1), uninstall-node(1), update-node-config(1), update-node-ssh(1)