How to check the port number in websphere application server

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 with Version 6.

When you configure WebSphere Application Server resources or assign port numbers to other applications, avoid conflicts with other assigned ports. In addition, when you configure a firewall, explicitly enable access to particular port numbers.

• For more information about port numbers that your iSeries system currently uses, enter the NETSTAT *CNN command on the OS/400 command line. Press F14 to view assigned port numbers.
• You can also use the port validator tool to find port conflicts between different WebSphere Application Server profiles, products, and servers. For information about the tool, see The port validator tool.

Version 6 port numbers

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 these port assignments by default:

Version 5.x port numbers

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 these port assignments by default:

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