[z/OS]

Port number settings on z/OS

Learn about the default server values for WebSphere® Application Server for z/OS®.

z/OS port assignments

Table 1. Port definitions for WebSphere Application Server for z/OS. The table lists port names and the default values of the port numbers.
Port Name Default Value
Standalone Application Server Federated Application Server Deployment Manager Administrative Agent Job Manager Secure Proxy Server Secure Proxy Server Administrative Agent Administrative Subsystem
Administrative Console Port (WC_ adminhost) 9060 ---- 9060 9060 9960 ---- ---- ----
Administrative Console Secure Port (WC_ adminhost_ secure) 9043 ---- 9043 9043 9943 ---- ---- ----
HTTP Transport Port (WC_ defaulthost) 9080 9080 ---- ---- ---- 80 ---- ----
HTTPS Transport Secure Port (WC_ defaulthost_ secure) 9443 9443 ---- ---- ---- 443 ---- ----
ORB Listener Port (BOOTSTRAP_ ADDRESS and ORB_ LISTENER_ ADDRESS) 2809 2809 9809 9807 9808 ---- 9807 ----
Cell Discovery Port (CELL_ DISCOVERY_ ADDRESS) ---- ---- 7277 ---- ---- ---- ---- ----
High Availability Manager Communication Port (DCS_ UNICAST_ ADDRESS) 9353 9353 9352 ---- ---- ---- ---- ----
Internal JMS Server Port (JMSSERVER_ SECURITY_ PORT) 5557 ---- ---- ---- ---- ---- ---- ----
Administrative Interprocess Communication Port (IPC_ CONNECTOR_ ADDRESS) 9633 9633 9632 9630 9631 9633 9630 9634
MQ Transport Port (SIB_ MQ_ ENDPOINT_ ADDRESS) 5558 5558 ---- ---- ---- ---- ---- ----
MQ Transport Secure Port (SIB_ MQ_ ENDPOINT_ SECURE_ ADDRESS) 5578 5578 ---- ---- ---- ---- ---- ----
ORB SSL Listener Port (ORB_ SSL_ LISTENER_ ADDRESS) 0 0 0 0 0 ---- ---- ----
RMI Connector Port (RMI_ CONNECTOR_ ADDRESS) ---- ---- ---- ---- ---- ---- ---- 9810
JSR 160 RMI Connector Port (JSR160RMI_ CONNECTOR_ ADDRESS) ---- ---- ---- ---- ---- ---- ---- 9811
Service Integration Port (SIB_ ENDPOINT_ ADDRESS) 7276 7276 ---- ---- ---- ---- ---- ----
Service Integration Secure Port (SIB_ ENDPOINT_ SECURE_ ADDRESS) 7286 7286 ---- ---- ---- ---- ---- ----
SIP Container Port (SIP_ DEFAULTHOST) 5060 5060 ---- ---- ---- 5060 ---- ----
SIP Container Secure Port (SIP_ DEFAULTHOST_ SECURE) 5061 5061 ---- ---- ---- 5061 ---- ----
JMX SOAP Connector Port (SOAP_ CONNECTOR_ ADDRESS) 8880 8880 8879 8877 8876 ---- 8877 8881
DataPower® Appliance Manager Secure Inbound Port (DataPowerMgr_ inbound_ secure) ---- ---- 5555 ---- ---- ---- ---- ----
Middleware Agent RPC Port (XDAGENT_ PORT) ---- ---- 7060 ---- ---- ---- ---- ----
Administration Overlay UDP Port (OVERLAY_ UDP_ LISTENER_ ADDRESS) 11003 11003 11005 ---- ---- ---- ---- ----
Administration Overlay TCP Port (OVERLAY_ TCP_ LISTENER_ ADDRESS) 11004 11004 11006 ---- ---- ---- ---- ----
Status Update Listener Port (STATUS_ LISTENER_ ADDRESS) ---- ---- 9420 ---- 9425 ---- ---- ----
IBM® HTTP Server Port 80 ---- ---- ---- ---- ---- ---- ----
IBM HTTPS Server Administration Port 8008 ---- ---- ---- ---- ---- ---- ----
When you federate an application server node into a deployment-manager cell, the deployment manager instantiates the node agent server process on the application server node. The node agent server uses these port assignments by default.
Table 2. Port definitions for the node agent server process. The table lists port names and the default values of the port numbers.
Port Name Default Value
Cell Node Agent
JMX SOAP Connector Port (SOAP_ CONNECTOR_ ADDRESS) 8878
ORB Listener Port (BOOTSTRAP_ ADDRESS and ORB_ LISTENER_ ADDRESS) 2810
High Availability Manager Communication Port (DCS_ UNICAST_ ADDRESS) 9354
ORB SSL Listener Port (ORB_ SSL_ LISTENER_ ADDRESS) 0
Node Discovery Port (NODE_ DISCOVERY_ ADDRESS) 7272
Node Multicast Discovery Port (NODE_ MULTICAST_ DISCOVERY_ ADDRESS) 5000
Node IPV6 Discovery Port (NODE_ IPV6_ MULTICAST_ DISCOVERY_ ADDRESS) 5001
Node Agent Interprocess Communication Port (IPC_ CONNECTOR_ ADDRESS) 9626
Node Middleware Agent RPC Port (NODE_ XDAGENT_ PORT) 7061
Node Administration Overlay UDP Port (NODE_ OVERLAY_ UDP_ LISTENER_ ADDRESS) 11001
Node Administration Overlay TCP Port (NODE_ OVERLAY_ TCP_ LISTENER_ ADDRESS) 11002

Location service daemon ports

Standalone application server node location service daemons are considered temporary. The ports assigned to a standalone application server node's location service daemon are used only until that node is federated. It is advisable to set aside a couple of ports to serve as interim ports for the standalone application server node location service daemon. The permanent location service daemon ports are the ones assigned to the deployment manager. Those same ports are copied to location service daemons created when a standalone application server node on another MVS™ image is federated into the deployment manager cell.

Node agent ports

There is a node agent per MVS image on which the cell spans. One design option calls for all node agents to have the exact same ports so the Sysplex Distributor is able to balance the traffic between the two. The node agent is created when the BBOWADDN customized job is run.

Server clusters

A server cluster is a grouping of two or more servers into a one logical server. A cluster is created through the administrative console. Servers within a cluster are called cluster members. Servers (members) within a cluster start out being clones of one another. When it comes to the TCP ports for the members in a cluster, the administrative console allows you during the creation of the cluster to specify if you want the HTTP ports to be unique or the same. The other ports -- bootstrap, ORB, ORB SSL and SOAP -- will be made unique by the application server.

For complex configurations with multiple members in a cluster it is advisable to make the members be as nearly identical to one another as possible, including the TCP ports. Therefore, when planning it is recommended a range of ports be allocated for a cluster with the intention to make certain all members of that cluster were given the same set of ports. Because WebSphere will automatically generate unique ORB, ORB SSL and SOAP ports for the second cluster member, it is necessary to go back in and remap the ports back to the ports set aside for the server cluster
Note: When a vertical cluster, two members on the same MVS image, is the potential configuration, you will need to consider port sharing by two members of the same cluster on the same MVS image.
Reference topic    

Terms and conditions for information centers | Feedback

Last updated: April 20, 2014 09:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-zos&topic=rrun_portszos
File name: rrun_portszos.html