Use the New Network Listener page to create a new network listener.
When you create a network listener, you can simultaneously create a protocol that the network listener will use, or use a protocol that you create first. Typically, there is a one-to-one relationship between a network listener and its associated protocol, but this is not required.
The New Network Listener page contains the following options.
A unique listener name. A network listener name cannot begin with a number.
The protocol associated with the network listener. The following options specify whether to create a protocol or use an existing one.
A new protocol with default settings is created for the network listener. The default name of the protocol is the name of the network listener with -protocol appended, but you can edit this value.
For a new protocol, the virtual server to be associated with the protocol.
The selected protocol is used.
The status of the network listener. The listener can be enabled or disabled. This option is enabled by default. If the listener is disabled, any attempts to connect to the listener result in a socket exception (java.net.ConnectException).
In Enterprise Server versions prior to 9.1, a listener whose enabled attribute was set to false returned a 404 response code for any requests sent to it. To achieve this behavior in the current Enterprise Server version, set the listener's status to enabled, and set every associated virtual server's state to OFF. A virtual server lists its associated listeners in its Network Listeners drop-down list.
If this option is selected, security is enabled for the protocol used by the network listener. This option is disabled by default.
If this option is selected, the listener supports Apache's mod-jk protocol. The mod-jk protocol is a proprietary communication/network protocol between Apache's httpd (web server) and an Enterprise Server back-end instance. If the listener supports this protocol, httpd is supposed to handle all static content, whereas any requests for dynamic resources (i.e., Servlets and JSPs) are routed to the mod-jk enabled network listener of the Enterprise Server, using the mod-jk protocol. This option is disabled by default.
The port number on which the listener will listen. Legal values are 1 through 65535. On a UNIX® system, creating sockets that listen on ports 1 through 1024 requires superuser privileges.
The IP address on which the network listener will listen. The address can be in dotted-pair or IPv6 notation. It can be any (for INADDR_ANY) to listen on all IP addresses. It can be a hostname.
The thread pool associated with the network listener. Normally, you select one of the two thread pools that are configured when you install the Enterprise Server.
The type of transport for the network listener. By default, the only choice is tcp.