Port number settings in WebSphere Application Server versions

This topic provides reference information about identifying port numbers in versions of WebSphere Application Server, as a means of determining port conflicts that might occur when you intend for an earlier version to coexist or interoperate.

Version 3.5.x port numbers

Resolve port conflicts by inspecting the configuration of the Version 3.5.x product, either WebSphere Application Server Advanced Edition or WebSphere Application Server Standard Edition. When the administrative server is running, use this command to examine current node and port settings:

xmlConfig -export config.xml -nodeName theNodeName
Look for the OSE Remote port assignments.


WebSphere Application Server Version 3.5.x default port definitions in the admin.config file

Port name Standard Edition Advanced Edition
Value
lsdport (Location Service Daemon) 9000 9000
bootstrapPort 900 900
LSDSSL (With security on) 9001 9001



Version 4.0.x port numbers

For WebSphere Application Server Advanced Single Server Edition, Version 4.0.x: Inspect the server-cfg.xml file to find the Web container HTTP transports port values for the configuration.

For WebSphere Application Server Advanced Edition, Version 4.0.x: When the administrative server is running, use this command to extract the configuration from the database:

xmlConfig -export config.xml -nodeName theNodeName
Look for the Web container HTTP transports port assignments.


Port definitions for WebSphere Application Server V4.0.x

Port name Value Advanced Edition EnterpriseEdition Advanced Single Server Edition
File
bootstrapPort 900 admin.config admin.config server-cfg.xml
lsdPort 9000
LSDSSLPort 9001
HTTP transport port 9080 database database
HTTPS transport port 9443
Admin Console HTTP transport port 9090
ObjectLevelTrace 2102
diagThreadPort 7000



Version 5.x port numbers

You can use the administrative console to configure the Version 5.x application server to resolve conflicting ports.


Port definitions for WebSphere Application Server Version 5.x

Port name WebSphere Application Server Network Deployment File
Value
HTTP_TRANSPORT 9080 Not applicable server.xml and virtualhosts.xml
HTTPS Transport Port (HTTPS_TRANSPORT) 9443 Not applicable
HTTP Admin Console Port (HTTP_TRANSPORT_ADMIN) 9090 9090
HTTPS Admin Console Secure Port (HTTPS_TRANSPORT_ADMIN) 9043 9043
Internal JMS Server (JMSSERVER_SECURITY_PORT) 5557 Not applicable server.xml
JMSSERVER_QUEUED_ADDRESS 5558 Not applicable serverindex.xml
JMSSERVER_DIRECT_ADDRESS 5559 Not applicable
BOOTSTRAP_ADDRESS 2809 9809 serverindex.xml
SOAP_CONNECTOR-ADDRESS 8880 8879 serverindex.xml
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 0 9401 serverindex.xml
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 0 9403 serverindex.xml
CSIV2_SSL_MULTIAUTH_LISTENER_ADDRESS 0 9402
IBM HTTP Server Port 80 Not applicable virtualhosts.xml, plugin-cfg.xml, and IHSinstall_root/conf/ httpd.conf
IBM HTTPS Server Admin Port 8008 Not applicable IHSinstall_root/conf/ admin.conf
CELL_DISCOVERY_ADDRESS Not applicable 7277 serverindex.xml
ORB_LISTENER_ADDRESS 9100 9100 serverindex.xml
CELL_MULTICAST_DISCOVERY_ADDRESS Not applicable 7272 serverindex.xml



When you federate an Application Server node into a deployment manager cell, the deployment manager instantiates the nodeagent server process on the Application Server node. The nodeagent server uses the following port assignments by default:


Port definitions for the V5.x nodeagent server process

Port name Value File
BOOTSTRAP_ADDRESS 2809 serverindex.xml
ORB_LISTENER_ADDRESS 9900
SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9901
CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9101
CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9201
NODE_DISCOVERY_ADDRESS 7272
NODE_MULTICAST_DISCOVERY_ADDRESS 5000
DRS_CLIENT_ADDRESS 7888
SOAP_CONNECTOR_ADDRESS 8878



Note: Do not remove the predefined end points from serverindex.xml. If required, you may edit the end points to modify the host and port values.

When you federate an Application Server node with the embedded messaging server feature into a deployment manager cell, the deployment manager instantiates a JMS server process, jmsserver, on the Application Server node. The JMS server uses the following port assignments by default:


Port definitions for V5.x jmsserver process

Port name Value File
JMSSERVER_DIRECT_ADDRESS 5559 serverindex.xml
JMSSERVER_QUEUED_ADDRESS 5558
SOAP_CONNECTOR_ADDRESS 8876
JMSSERVER SECURITY PORT 5557 server.xml




Related tasks
Creating multiple Version 5 configuration instances
Setting up Version 3.5.x and Version 5 coexistence
Setting up Version 4.0.x and Version 5.x coexistence
Setting up Version 5 coexistence
Changing HTTP transport ports
Related reference
Example: Modifying port numbers in the serverindex file



Searchable topic ID:   rins_portnumber
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rins_portnumber.html

Library | Support | Terms of Use | Feedback