Each HTTP listener has an HTTP protocol, which is created either by using the create-protocol subcommand or by using the built-in protocols that are applied when you follow the instructions in To Create an HTTP Network Listener.
The following topics are addressed here:
Use the create-protocol subcommand in remote mode to create a protocol.
Ensure that the server is running.
Remote subcommands require a running server.
Create a protocol by using the create-protocol(1)
Information about options and properties for the subcommand are included in this help page.
This example creates a protocol named http-1 with security enabled.
asadmin> create-protocol --securityenabled=true http-1 Command create-protocol executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help create-protocol at the command line.
Use the list-protocols subcommand in remote mode to list the existing HTTP protocols.
Ensure that the server is running.
Remote subcommands require a running server.
List the existing protocols by using the list-protocols(1) subcommand.
This example lists the existing protocols.
asadmin> list-protocols admin-listener http-1 http-listener-1 http-listener-2 Command list-protocols executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-protocols at the command line.
Use the delete-protocol subcommand in remote mode to remove a protocol.
Ensure that the server is running.
Remote subcommands require a running server.
Delete a protocol by using the delete-protocol(1) subcommand
This example deletes the protocol named http-1.
asadmin> delete-protocol http-1 Command delete-protocol executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help delete-protocol at the command line.