Before you begin
For more information about port numbers
that your IBM i® 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. Read the "port validator tool"
article in the information center for more information.
Tip: 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.