Configure port settings

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

(iseries) For more information about port numbers that the iSeries system currently uses, enter the NETSTAT *CNN command on the command line. Press F14 to view assigned port numbers.

(iseries) We can also use the port validator tool to find port conflicts between different WebSphere Application Server profiles, products, and servers. See Port validator tool for more information.

Tips:

• Port conflicts might occur if we assign a custom port value within the recommended default dynamic port range. Because port values are assigned dynamically, WAS cannot predetermine the port values that will be assigned to your servers. A way to avoid the possibility of a port conflict among servers is to either accept the default server port values assigned by the Profile Management Tool, or assign custom port values that do not fall within the default dynamic port range. The default dynamic port ranges for pre-2008 operating system is 1025 to 5000 , and the dynamic port ranges for newer operating systems is 49152 to 65535. Because these default ranges are recommended by the Internet Assigned Numbers Authority (IANA), they are common across all operating systems.

• Port conflicts might occur if you install WAS on multiple systems with deployment managers managing servers or clusters on different systems. The configuration-service port-resolution mechanism does not support cross profiles on different host machines.

  • Example 1:

    1. On system A, create a cell profile that includes Dmgr and AppSrv01 (Node1).

    2. On system B, create AppSrv01 and federate AppSrv01 (Node2) to Dmgr on system A.

    3. Create server1 on Node1 and server2 on Node2.

    4. The server1 server and server2 server might contain duplicate server endpoint ports in the serverindex.xml file because Node1 and Node2 are located on different host systems.

  • Example 2:

    1. On system A, create a cell profile that includes Dmgr and AppSrv01 (Node1).

    2. On system B, create AppSrv01 and federate AppSrv01 (Node2) to Dmgr on system A.

    3. On system B, create JobManager.

    4. Create a cluster and add two servers, server1 on Node1 and server2 on Node2.

    5. The server2 server and the JobManager server might contain duplicate server endpoint ports in the serverindex.xml file because server2 and JobManager are in cross profiles. The server2 server is under Dmgr, JobManager is under the JobManager profile. and the Dmgr and JobManager profiles are located on different machines.

1. Review the port number settings, especially when we are planning to coexist.

   (iseries) We can use the dspwasinst command-line tool to display the port information for a profile. See dspwasinst command for more information.

2. Optional: Change the port number settings.

   We can set port numbers when configuring the product after installation.

   • During profile creation using the manageprofiles command, we can accept the default port values or we can specify the port settings. To specify ports, we can do so in any of the following ways:

     • Specify the use of a port file containing the port values.

     • Specify the use of a starting port value.

     • Specify the use of the default port values.

     See manageprofiles command for more information.

   • (dist) During profile creation using the Profile Management tool, we can accept the port settings recommended by the tool or we can specify the port settings.

     See Manage profiles using the GUI for more information.

   • (iseries) We can use the chgwassvr command to change the ports for an application server within a profile.

     See chgwassvr command for more information.

   (zos) We can set port numbers when configuring the product after installation. Start to think about port numbers during the planning phase described in Plan for product configuration.

   (dist) We can perform one of the following actions to change port settings after installation:

   • Use the updatePorts tool to change port settings.

     See Updating ports in existing profiles and Port number settings for more information.

   • Edit the profile_root/config/cells/cell_name/nodes/node/serverindex.xml file to change the port settings, or use scripting to change the values.

Subtopics

• Port number settings
  You should be able to identify the default port numbers used in the various versions of WAS so that we can avoid port conflicts if you plan for an earlier version to coexist or interoperate with v8.5.

• Update ports in existing profiles
  Use the updatePorts.ant script to change ports in an installed profile.

• Host name values
  WebSphere Application Server requires a host name specification during installation, profile creation, and for some configuration activities. This article describes acceptable values for host name fields.

Related tasks

Manage profiles using the GUI

(zos) Planning for product configuration

Update ports in existing profiles

(iseries) dspwasinst command

manageprofiles command

(iseries) chgwassvr command

Port number settings