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.
![[AIX Solaris HP-UX Linux Windows]](../dist.gif)
You can view
this administrative console page, by clicking server_nameport_name
![[AIX Solaris HP-UX Linux Windows]](../dist.gif)
You
can view this administrative console page by clicking one of the following
paths:
If you are running on z/OS®,
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.
| Information | Value |
|---|---|
| Data type | String |
The following ports apply to the z/OS platform
only. | End point | Description |
|---|---|
| JMSSERVER Queued Address | Specifies the host and port number
used to configure the WebSphere® JMS Provider topic
connection factory. The JMS Server Queued Address port is the listener
port used for full-function JMS-compliant, publish/subscribe support.
The default Queued Address port number is 5558. Since the queue manager and queue broker for the WebSphere JMS Provider are configured outside the administrative console, changes to this port require corresponding configuration changes to the queue manager and queue broker. |
| JMSSERVER Direct Address | Specifies the host and port number
used to configure the WebSphere JMS Provider topic
connection factory. The JMS Server Direct Address port is the listener
port used for direct TCP/IP connection (non-transactional, nonpersistent,
and nondurable subscriptions only) for publish/subscribe support.
The default Direct Address port number is 5559. Since the queue manager and queue broker for the WebSphere JMS Provider are configured outside the administrative console, changes to this port require corresponding configuration changes to the queue manager and queue broker. |
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.
Avoid trouble: If your TCP/IP network is set
up to use distributed dynamic virtual IP addresses (DVIPAs), and if
the node agent is in the process of starting the application server,
TCP/IP waits until the JVM TCP/IP timeout period expires before notifying
the node agent that the target application server is not responsive. gotcha| Information | Value |
|---|---|
| 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.
Avoid trouble: Port sharing cannot be created
using the administrative console. If you need to share a port, you
must 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. 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.
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.
gotcha| Information | Value |
|---|---|
| Data type | Integer |
| Default | None |
Avoid trouble: The following
table lists server endpoints and their respective port ranges. In
contrast to an IBM® i or distributed platform environment, for
a z/OS environment, the ORB_LISTENER_ADDRESS and
the BOOTSTRAP_ADDRESS must specify the same port.gotcha
| Endpoint (port) | Acceptable values for the port field |
|---|---|
| BOOTSTRAP_ADDRESS | 0 - 65535 |
| DATAPOWERMGR_INBOUND_SECURE | 1 - 65536 |
| DCS_UNICAST_ADDRESS | 1 - 65536 |
| ORB_LISTENER_ADDRESS | 1 - 65535 (If 0 is specified, the server starts on any available port and does not use the location service daemon) |
| 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 | 0 - 65535 (0 specifies that the server should bind to any ephemeral port that is available.) |
![[AIX Solaris HP-UX Linux Windows]](../dist.gif)
Important: The following table
lists server endpoints and their respective port ranges. In contrast
to the z/OS environment, for a distributed platform
or the IBM i environment, the ORB_LISTENER_ADDRESS and
the BOOTSTRAP_ADDRESS endpoints must not specify the same port.![[AIX Solaris HP-UX Linux Windows]](../dist.gif)
| 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 |
| DATAPOWERMGR_INBOUND_SECURE | 1 - 65536 |
| 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.) |
| 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 for the distributed and iSeries® environments |