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.
Before you begin
For more information about port numbers
that your iSeries® system currently uses, enter the NETSTAT
*CNN command on the 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. See Port validator tool for more
information.
Tips: - Port conflicts might occur if you assign a custom port value within
the recommended default dynamic port range. Because port values are
assigned dynamically, WebSphere Application Server
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 WebSphere Application
Server 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:
- On system A, create a cell profile that includes Dmgr and AppSrv01
(Node1).
- On system B, create AppSrv01 and federate AppSrv01 (Node2) to
Dmgr on system A.
- Create server1 on Node1 and server2 on Node2.
- 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:
- On system A, create a cell profile that includes Dmgr and AppSrv01
(Node1).
- On system B, create AppSrv01 and federate AppSrv01 (Node2) to
Dmgr on system A.
- On system B, create JobManager.
- Create a cluster and add two servers, server1 on Node1 and server2
on Node2.
- 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.
Procedure
- Review the port number settings, especially when you are
planning to coexist.
You can use
the dspwasinst command-line tool to display the
port information for a profile. See dspwasinst command for
more information.
- Optional: Change the port number settings.
![[IBM i]](../images/iseries.gif)
You can set port numbers when configuring
the product after installation.