Purpose
The following table lists the default server values for WebSphere Application Server for z/OS V5.
z/OS port assignments
The following table lists the z/OS port assignments.
Port | Base location service daemon | Base Application Server | ND location service daemon | ND Application Server | node agent | JMS Server | Deploy. Manager |
---|---|---|---|---|---|---|---|
HTTP | 9080 | 9080 | 9090 | ||||
HTTP/S | 9443 | 9443 | 9043 | ||||
Bootstrap | 2809 | 9810 | 2809 | 2810 | 9809 | ||
ORB | 5655 | 2809 | 5755 | 9810 | 2809 | 2810 | 9809 |
ORB SSL | 5656 | 0 | 5756 | 0 | 0 | 0 | 0 |
SOAP/JMX | 8880 | 8880 | 8878 | 8876 | 8879 | ||
DRS | 7873 | 7873 | 7888 | 7989 | |||
JMS Queued | 5558 | 5558 | |||||
JMS Direct | 5559 | 5559 | |||||
Node Discovery | 7272 | ||||||
Node Multi-cast Discovery | 5000 | ||||||
Cell Discovery | 7277 |
Daemon ports
Base Application Server node location service daemons are considered temporary. The ports assigned to a base 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 base 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 base 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, DRS, 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 DRS, ORB, ORB SSL and SOAP ports for the second cluster member, it is necessary to go back in and re-map 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.