Default port assignments

This article lists the default server values for WebSphere® Application Server for z/OS®.

WebSphere Application Server for z/OS port assignments

Table 1. Default port assignments.

This table lists the default port values for WebSphere Application Server for z/OS.

Port Name Default Value
Standalone Application Server Deployment Manager ND Node Agent ND Managed Node Administrative Agent Job Manager
HTTP Transport Port (WC_ defaulthost) 9080     9080    
HTTPS Transport Secure Port (WC_ defaulthost_ secure) 9443     9443    
Administrative Console Port (WC_ adminhost)   9060   9060 9060 9960
Administrative Console Secure Port (WC_ adminhost_ secure)   9043   9043 9043 9943
Administrative Interprocess Communication Connector Port(IPC_ CONNECTOR_ ADDRESS) 9633 9632     9630 9631
Bootstrap Port (BOOTSTRAP_ ADDRESS) 2809 9809 2809 9810    
ORB 2809 9809 2809 9810 9807 9808
ORB SSL 0 0 0 0 0 0
SOAP/JMX (SOAP_ CONNECTOR_ ADDRESS) 8880 8879 9360 8880 8877 8876
Node Discovery Address (NODE_ DISCOVERY_ ADDRESS)     7272      
Node Multicast Discovery Address (NODE_ MULTICAST_ DISCOVERY_ ADDRESS)     5000      
Cell Discovery Address (CELL_ DISCOVERY_ ADDRESS)   7277        
Service Integration Port (SIB_ ENDPOINT_ ADDRESS) 7276          
Service Integration Secure Port (SIB_ ENDPOINT_ SECURE_ ADDRESS) 7286          
Service Integration MQ Interoperability Port (SIB_ MQ_ ENDPOINT_ ADDRESS) 5558          
Service Integration MQ Interoperability Secure Port (SIB_ MQ_ ENDPOINT_ SECURE_ ADDRESS) 5578          
Session Initiation Protocol Port (SIP_ DEFAULTHOST) 5060          
Session Initiation Protocol Secure Port (SIP_ DEFAULTHOST_ SECURE) 5061          
High Availability Manager Communications (DCS_ UNICAST_ ADDRESS) 9353 9352 9354      
DataPower® Application Manager   5555        
Daemon Port 5655 5755        
Daemon SSL Port 5656 5756        

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, 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 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 Reference topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 20, 2011 12:20:53 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=rrun_ports
File name: rrun_ports.html