Each HTTP listener has an HTTP transport, which is created either by using the create-transport subcommand or by using the built-in transports that are applied when you follow the instructions in To Create an HTTP Network Listener.
The following topics are addressed here:
Use the create-transport subcommand in remote mode to create a transport for a network listener,
Ensure that the server is running.
Remote subcommands require a running server.
Create a transport by using the create-transport(1) subcommand.
Information about options and properties for the subcommand are included in this help page.
This example creates a transport named http1-trans that uses a non-default number of acceptor threads.
asadmin> create-transport --acceptorthreads 100 http1-trans Command create-transport executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help create-transport at the command line.
Use the list-transports subcommand in remote mode to list the existing HTTP transports.
Ensure that the server is running.
Remote subcommands require a running server.
List the existing transports by using the list-transports(1) subcommand.
This example lists the existing transports.
asadmin> list-transports http1-trans tcp Command list-transports executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help list-transports at the command line.
Use the delete-transport subcommand in remote mode to remove a transport.
Ensure that the server is running.
Remote subcommands require a running server.
Delete a transport by using the delete-transport(1) subcommand.
This example deletes he transport named http1-trans.
asadmin> delete-transport http1-trans Command delete-transport executed successfully. |
You can also view the full syntax and options of the subcommand by typing asadmin help delete-transport at the command line.