To create an HTTP listener

1. In the tree component, expand the Configurations node.

2. Select the instance to configure:

   • To configure a particular instance, select the instance’s config node. For example, for the default instance, server, select the server-config node.

   • To configure the default settings for future instances that use a copy of default-config, select the default-config node.

3. Expand the HTTP Service node.

4. Select the HTTP Listeners node.

5. On the HTTP Listeners page, click New.

   The Create HTTP Listener page appears.

6. In the Name field, type a name for the listener.

7. In the Listener field, remove the check from the Enabled box if you do not want to enable the listener when the server restarts.

8. In the Network Address field, type 0.0.0.0 if you want the listener to listen on all IP addresses for the server, using a unique port value. Otherwise, type a valid IP address for the server.

9. In the Listener Port field, type a unique port value if the Network Address field is 0.0.0.0, or the desired port value if you are using another IP address.

10. Choose a virtual server from the Default Virtual Server drop-down list.

11. In the Server Name field, type the host name to be used in the URLs the server sends to the client. This name is the alias name if your server uses an alias.

    If your server does not use an alias, leave this field empty.

12. In the Advanced area, perform any of the following tasks:

    • To redirect requests to another port, type a value in the Redirect Port field. The Application Server automatically redirects the request if these two conditions exist:

      • This listener is supporting non-SSL requests.

      • A request is received for which a matching security constraint requires SSL transport.

        By default, the Application Server uses the port number specified in the original request.

    • Change the number of Acceptor Threads.

    • Remove the check from the Powered By box to disable the inclusion of the X-Powered-By: Servlet/2.4 header in servlet-generated HTTP response headers.

      The Java Servlet 2.4 Specification defines this header, which containers may add to servlet-generated responses. Similarly, the JavaServer Pages^TM (JSP^TM) 2.0 Specification defines an X-Powered-By: JSP/2.0 header to be added (on an optional basis) to responses that use JSP technology. The inclusion of the X-Powered-By: JSP/2.0 header is enabled by default for web applications. The goal of these headers is to aid web site administrators in gathering statistical data about the use of Servlet and JSP technology.

      For information on enabling and disabling the X-Powered-By header for JSP pages, see the chapter entitled “Deployment Descriptor Files” in the Application Server Developer’s Guide. See Further Information for a link to this document.

      Production environments might decide to omit the generation of X-Powered-By headers to hide their underlying technology.

13. To create a listener that is not secure, click OK.

14. In the SSL section of this page, you can configure the listener to use SSL, TLS, or both SSL and TLS security.

    To set up a secure listener, do the following:

15. Check the Enabled box in the Security field.

16. To force clients to authenticate themselves to the server when using this listener, check the Enabled box in the Client Authentication field.

17. Enter the name of an existing server key pair and certificate in the Certificate NickName field. See the Security chapter for more information.

18. In the SSL3/TLS section:

    1. Check the security protocol(s) to be enabled on the listener. Check either SSL3 or TLS, or both.

    2. Check the cipher suite used by the protocol(s). To enable all cipher suites, check All Supported Cipher Suites. You can also enable individual cipher suites.

19. The listener is now listed in the HTTP Listeners field for the virtual server that is specified as the Default Virtual Server.

Equivalent asadmin commands

create-http-listener and create-ssl