Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
Ports settings
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.
We can view this admin console page by clicking one of the following paths:
- Servers > Server Types > WebSphere application servers > server_name
> Ports > port_name
- Servers > Server Types > JMS servers > server_name
> Security Port Endpoint
- Servers > Server Types > WebSphere JMS servers > server_name
> Ports > port_name
Port Name
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. We can select either:
Well-known Port
When you select this option , you can select a previously defined port from the drop down list
User-defined Port
When you select this option, create a port with a new name by entering the name of the new port in the text box
Data type. The following table describes the data type for the Port Name setting.
Data type String
Host
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 (IPv4) format for all platforms, and IPv6 (IPv6) format on specific operating systems where the server supports IPv6. 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.
Data type and Default. The following table describes the data type and default for the Host setting.
Data type String Default * (asterisk)
Port
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. Port sharing cannot be created using the admin console. If share a port, use wsadmin commands to define that port. We 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, 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 we 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 and Default. The following table describes the data type and default for the Port setting.
Data type Integer Default None 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.
Server endpoints and their respective port ranges. The following table lists server endpoints and their respective port ranges.
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
Administer application servers