Use this to view and change the configuration for a communication port used by run-time components running within a process. A communication port provides host and port specifications for a server. For WebSphere Application Server for Network Deployment, you can view this administrative console page by clicking one of the following paths:
Specifies the name of the port. The name must be unique within the server. Note that this field displays only when you are defining a port for an application server. You can select either:
Data type | String |
Specifies the IP address, domain name server (DNS) host name with domain name suffix, or just the DNS host name, used by a client to request a resource (such as the naming service, administrative service, or JMS broker).
For example, if the host name is myhost, the fully qualified DNS name can be myhost.myco.com and the IP address can be 155.123.88.201.
Host names on the ports can be resolvable names or IP addresses. The server will bind to the specific host name or IP address that is supplied. That port will only be accessible through the IP address that is resolved from the given host name or IP address. The IP address may be of the IPv4 (Internet Protocol V4) format for all platforms, and IPv6 (Internet Protocol V6) format on specific operating systems where the server supports IPv6.
Data type | String |
Default | * (asterisk) |
Port for which the service is configured to accept client requests. The port value is used in conjunction with the host name.
Port numbers in the server can be reused among multiple ports as long as they have host names that resolve to unique IP addresses and there is not a port with the same port number and a wildcard ( * ) host name. A port number is valid in the range of 0 and 65535. 0 specifies that the server should bind to any ephemeral port available.
Port sharing cannot be created using the administrative console. If you need to share a port, use wsadmin commands to define that port. You must also make sure that the same discrimination weights are defined for all of the transport channels associated with that port.
For a WebSphere Application Server Network Deployment configuration, protocol channels only accept their own protocol. However, application channels usually accept anything that reaches them. Therefore, for application channels, such as WebContainer, or Proxy, you should specify larger discrimination weights when sharing levels with protocol channels, such as HTTP or SSL. The one exception to this rule is if you have application channels that perform discrimination tests faster than the protocol channels. For example, a JFAP channel is faster at deciding on a request than the SSL protocol channel, and should go first for performance reasons. However, the WebContainer and Proxy channels must always be last because they accept everything that is handed to them.
Data type | Integer |
Default | None |
The following table lists server endpoints and their respective port ranges. In contrast to the z/OS platform, on a distributed platform or on the i5/OS platform, the ORB_LISTENER_ADDRESS and the BOOTSTRAP_ADDRESS endpoints must not specify the same port.
Endpoint (port) | Acceptable values for the port field |
---|---|
BOOTSTRAP_ADDRESS | 1 - 65536 |
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESSÂ | 1 - 65535 |
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS | 1 - 65535 |
DCS_UNICAST_ADDRESS | 1 - 65536 |
DRS_CLIENT_ADDRESS | 1 - 65536 |
ORB_LISTENER_ADDRESSÂ | 0 - 65535 (If 0 is specified, the server starts on any available port and does not use the location service daemon) |
SAS_SSL_SERVERAUTH_LISTENER_ADDRESSÂ | 1 - 65535 |
SIB_ENDPOINT_ADDRESSÂ | 1 - 65536 |
SIB_ENDPOINT_SECURE_ADDRESSÂ | 1 - 65536 |
SIB_MQ_ENDPOINT_ADDRESSÂ | 1 - 65536 |
SIB_MQ_ENDPOINT_SECURE_ ADDRESSÂ | 1 - 65536 |
SOAP_CONNECTOR_ ADDRESSÂ | 1 - 65536 |
WC_adminhost | 1 - 65536 |
WC_adminhost_secure | 1 - 65536 |
WC_defaulthost | 1 - 65536 |
WC_defaulthost_secure | 1 - 65536 |
ORB_SSL_LISTENER_ADDRESS | Not supported on the distributed and iSeries platforms |