You can modify listeners by using either the administration console or the CLI.
Note:
When you modify a listener, you are, in effect, modifying a configuration. So for the new settings of a listener to take effect in the Oracle Traffic Director instances, you should redeploy the configuration as described in Section 4.3, "Deploying a Configuration."
The CLI examples in this section are shown in shell mode (tadm>). For information about invoking the CLI shell, see Section 2.3.1, "Accessing the Command-Line Interface."
Modifying a Listener Using the Administration Console
To modify an HTTP or TCP listener by using the administration console, do the following:
Log in to the administration console, as described in Section 2.3.2, "Accessing the Administration Console."
Click the Configurations button that is situated at the upper left corner of the page.
A list of the available configurations is displayed.
Select the configuration for which you want to modify listeners.
In the navigation pane, click Listeners.
The Listeners page is displayed. It shows a list of the HTTP/TCP listeners defined for the configuration.
Click the name of the listener that you want to modify.
The Listener Settings page is displayed. On this page, you can do the following:
Enable and disable the listener.
Change the listener port number and IP address.
For HTTP listeners: Change the server name and the default virtual server.
For TCP listeners: Change the TCP proxy.
If server certificates have been created for the configuration, you can enable SSL/TLS and configure SSL/TLS settings for the listener. For more information, see Section 11.2.2, "Configuring SSL/TLS for a Listener."
Change the protocol family—IPv4, IPv6, or SDP—for which the listener should accept requests.
For HTTP listeners: Configure parameters to tune the performance of the virtual server—the number of acceptor threads, the listen queue size, receive buffer size, and so on. For more information, see Section 15.2.2, "Tuning HTTP Listener Settings."
Specify the parameters that you want to change.
On-screen help and prompts are provided for all of the parameters.
When you change the value in a field or tab out of a text field that you changed, the Save button near the upper right corner of the page is enabled.
At any time, you can discard the changes by clicking the Reset button.
After making the required changes, click Save.
A message, confirming that the updated listener was saved, is displayed in the Console Messages pane.
In addition, the Deployment Pending message is displayed at the top of the main pane. You can either deploy the updated configuration immediately by clicking Deploy Changes, or you can do so later after making further changes as described in Section 4.3, "Deploying a Configuration."
Modifying a Listener Using the CLI
To change the properties of an HTTP listener, run the set-http-listener-prop command. For example, the following command changes the port number of the listener ls1 in the configuration soa to 1911.
tadm> set-http-listener-prop --config=soa --http-listener=ls1 port=1911 OTD-70201 Command 'set-http-listener-prop' ran successfully.
To change the SSL/TLS settings of an HTTP listener, run the set-ssl-prop command. For example, the following command enables SSL 3.0 support for the listener ls1 in the configuration soa.
tadm> set-ssl-prop --config=soa --http-listener=ls1 ssl3=true OTD-70201 Command 'set-ssl-prop' ran successfully.
To change the properties of a TCP listener, run the set-tcp-listener-prop command. For example, the following command changes the port number of the listener tcp_ls1 in the configuration soa to 1911.
tadm> set-tcp-listener-prop --config=soa --tcp-listener=tcp_ls1 listen-queue-size=238 OTD-70201 Command 'set-tcp-listener-prop' ran successfully.
To change the SSL/TLS settings of an TCP listener, run the set-ssl-prop command. For example, the following command enables SSL 3.0 support for the listener tcp_ls1 in the configuration soa.
tadm> set-ssl-prop --config=soa --tcp-listener=ls1 ssl3=true OTD-70201 Command 'set-ssl-prop' ran successfully.
For the updated configuration to take effect, you should deploy it to the Oracle Traffic Director instances by using the deploy-config command.
For a list of the properties that you can set or change by using the set-tcp-listener-prop and set-ssl-prop commands, see the Oracle Traffic Director Command-Line Reference or run the commands with the --help option.