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 GlassFish Server instance
delete-instance [--help] instance-name
The delete-instance subcommand deletes a GlassFish Server instance. This subcommand requires secure shell (SSH) to be configured on the host where the domain administration server (DAS) is running and on the host that is represented by the node where the instance resides.
Note - SSH is not required if the instance resides on a node of type CONFIG that represents the local host. A node of type CONFIG is not enabled for communication over SSH.
You may run this subcommand from any host that can contact the DAS.
The subcommand can delete any GlassFish Server instance, regardless of how the instance was created. For example, this subcommand can delete an instance that was created by using the create-local-instance(1) subcommand.
The instance that is being deleted must not be running. Otherwise, an error occurs.
The subcommand deletes an instance by performing the following actions:
Removing the instance from the configuration of the domain administration server (DAS)
Deleting the instance's files from file system
If the instance that is being deleted is the only instance that is using the node directory, that directory is also removed.
If a standalone instance is deleted, the instance's standalone configuration is also deleted. A standalone instance refers to a configuration that is named instance-name-config to which no other clusters or unclustered instances refer.
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
The name of the instance to delete.
Example 1 Deleting a GlassFish Server Instance
This example deletes the GlassFish Server instance pmdsainst.
asadmin> delete-instance pmdsainst Command delete-instance executed successfully.
command executed successfully
error in executing the command
create-instance(1), create-local-instance(1), delete-local-instance(1), setup-ssh(1), start-instance(1), start-local-instance(1), stop-instance(1), stop-local-instance(1)