Ports when creating a new profile
When creating a new WebSphere application server profile, the profile will contain one application server, named server1 by default. If using the manageprofiles.sh (Linux) or manageprofiles.bat (Windows) scripts to create the profile and you do not use the -portsFile or -startingPort or -defaultPorts options, the application server will be assigned a predefined collection of port values, such as 9080 for HTTP and 9443 for HTTPS.
The -portsFile option can be used to use a file to define the port values. The portdef.props file can be used. Following are the locations of the portdef.props files.
Typically, the portdef.props file is used. Or, the -startingPort option can be used to define the starting port number, such as 12345.
Ports when creating a new application server
After federating a node into a WebSphere network deployment manager (dmgr), you can then use the WebSphere admin console to create a new WebSphere application server. This could either be a stand alone application server that is not part of a static cluster or dynamic cluster. Or, you could create a new application server that is part of a static cluster or dynamic cluster. Regardless of whether the application server is stand alone or part of a cluster, the creation of the application server will cause the application server to have a certain collection of unique port values.
Additionally, there will be a virtual host aliases for each port.
Additionally, some of the application server ports will also be defined in the web container transport chains. Changes made to the application server ports will also update the web container transport chain port.
Refer to our article on how to change WebSphere application server ports.