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 base WebSphere Application Server, you can view this administrative console page, by clicking Servers > Application Servers > server_name > Ports > port_name
Specifies the name of the port. The name must be unique within the server.
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 Version 4) format for all platforms, and IPv6 (Internet Protocol Version 6) format on specific operating systems where the server supports IPv6.
Data type | String |
Default | * (asterisk) |
Specifies the 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. Specifying the wildcard value is equivalent to specifying the loopback address or 127.0.0.1.
For a base WebSphere Application Server or WebSphere Application Server - Express configuration, protocol channels only accept their own protocol. However, application channels usually accept anything that reaches them. Therefore, for application channels, such as WebContainer, 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 channel must always be last because it accepts everything that is handed to it.
Data type | Integer |
Default | None |
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 Deprecation:: This port is deprecated and is no longer used in the
current version of WebSphere Application Server.
|
1 - 65536 |
ORB_LISTENER_ADDRESS | 0 - 65535 (If 0 is specified, the server starts on any available port.) |
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 |