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-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
- enables administrators to delete a message security provider
delete-message-security-provider [--help] [--target target] --layer message_layer provider_name
The delete-message-security-provider subcommand enables administrators to delete a message security provider.
In terms of what happens when this subcommand is run, the provider-config sub-element for the given message layer (message-security-config element of domain.xml is deleted. The domain.xmlfile specifies parameters and properties to the GlassFish Server). The options specified in the list below apply to attributes within the message-security-config and provider-config sub-elements of the domain.xml file.
If the message-layer (message-security-config attribute) does not exist, it is created, and then the provider-config is created under it.
This command is supported in remote mode only.
If an option has a short option name, then the short option precedes the long option name. Short options have one dash whereas long options have two dashes.
Displays the help text for the subcommand.
Specifies the target from which you are deleting the message security provider. Valid values are
Deletes the message security provider from the default server instance server and is the default value
Deletes the message security provider from the domain.
Deletes the message security provider from every server instance in the cluster.
Deletes the message security provider from a particular sever instance.
The message-layer from which the provider has to be deleted. The default value is HttpServlet.
The name of the provider used to reference the provider-config element.
Example 1 Deleting a message security provider
The following example shows how to delete a message security provider for a client.
asadmin> delete-message-security-provider --layer SOAP mySecurityProvider
command executed successfully
error in executing the command
create-message-security-provider(1), list-message-security-providers(1)