InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.48: Administering ports

6.6.48: Administering ports

The product uses the following ports. See below for port assignment guidelines, particularly notes about the effects of port changes on other WebSphere components. For example, changing the bootstrap port from the product default requires a new parameter when you start the Java administrative console.

Bootstrap port

  • One for each administrative server
  • Default value is 900
  • To change it, modify the administrative server configuration file
Location Service Daemon (LSD) port

  • One for each administrative server
  • Default value is 9000
  • To change it, modify the administrative server configuration file
ORB listener port for RMI/IIOP

  • One for each application server and one for each administrative server
  • Value is assigned randomly
  • To make the value static, add -Dcom.ibm.CORBA.ListenerPort=xxxx where xxxx is a valid TCP port (see guidelines below).
    • For application servers, add the argument to the Command Line Arguments setting of the application server properties.
    • For administrative servers, add the argument to the com.ibm.ejs.sm.util.process.Nanny.adminServerJvmArgs parameter in the administrative server configuration file.
DrAdmin port

  • One for each application server
  • Value is 7000
  • This port is assigned dynamically.
Object Level Trace and Debugger port

  • One for each application server
  • Value is 2012
  • To change it, use the administrative console to modify OLT and Debugger-related settings in the WebSphere Application Server administrative console

Guidelines for assigning ports

Though WebSphere Application Server provides default values, the above port numbers can be modified by the system or network administrator. Here are some guidelines:

  • Ports can range from 1024 to 64000. Choose a port that does not conflict with existing ports in use. To check ports in use:
    • Use the netstat command (netstat -a)
    • View the /etc/services file on UNIX
    • View the drive\winnt\system32\drivers\etc\services file on Windows NT
  • Ports must be unique in the scope of each physical host. That is, two servers on the same machine cannot have the same port values.
  • The same port numbers can be used for servers running on different physical hosts. That is, the administrative server on Machine A can have bootstrap port 900, while administrative servers on other machines have this same number.
  • For administrative servers, pick port numbers above 1024 if not using the default port and running as non-root.
  • Changing the bootstrap port from its default affects the administrative clients. When starting the Java administrative console, you must specify the new port number:

    On UNIX-based operating systems:

    adminclient.sh hostname port
    

    On Windows-based operating systems:

    adminclient hostname port
    
  • Remember to configure firewalls to allow traffic to pass for each assigned port. For security, try to minimize ports.
Go to previous article: Adding generic servers with the Java administrative console Go to next article: Administering National Language Support

 

 
Go to previous article: Adding generic servers with the Java administrative console Go to next article: Administering National Language Support