InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.48: Administering ports (overview)
6.6.48: Administering ports (overview)
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, edit the bootstrapPort property in the administrative server configuration file
ORB properties
Location Service Daemon (LSD) port
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.
- One for each application server
- Default value is 9080
Secure port for internal HTTP transport
- One for each application server
- Default value is 9443
DrAdmin port
- One for each application server
- Value is 7000
-
This port is assigned dynamically.
Object Level Trace and Debugger port
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.
|
 |
 |
Related topics |
|
| Concept help |
|
|
Overviews |
|
| Administrative procedure |
|
| Administering this object type (overview) |
|
Peer topics |
|
| 6.6.0: About user assistance |
|
| 6.6.1: Administering applications (overview) |
|
| 6.6.2: Administering nodes (overview) |
|
| 6.6.3: Administering application servers (overview) |
|
| 6.6.4: Administering EJB containers (overview) |
|
| 6.6.5: Administering EJB modules (overview) |
|
| 6.6.7: Administering Web containers (overview) |
|
| 6.6.8: Administering Web modules (overview) |
|
| 6.6.11: Administering HTTP session support (overview) |
|
| 6.6.13: Administering transports (overview) |
|
| 6.6.14: Administering database connections (overview) |
|
| 6.6.15: Administering custom services (overview) |
|
| 6.6.16: Administering virtual hosts (overview) |
|
| 6.6.18: Securing applications (overview) |
|
| 6.6.19: Administering the product messages, logs, and traces (overview) |
|
| 6.6.20: Administering transactions (overview) |
|
| 6.6.21: Performing tasks with the Resource Analyzer |
|
| 6.6.22: Administering server groups (overview) |
|
| 6.6.24: Administering application client modules (overview) |
|
| 6.6.26: Administering application server process definitions (overview) |
|
| 6.6.28: Administering Object Level Trace and Distributed Debugger support (overview) |
|
| 6.6.30: Administering Object Request Brokers (overview) |
|
| 6.6.31: Monitoring and tuning performance (overview) |
|
| 6.6.34: Administering environment entries (overview) |
|
| 6.6.35: Administering generation of deployment code |
|
| 6.6.36: Administering Java Virtual Machine settings (overview) |
|
| 6.6.37: Administering mail providers and mail sessions (overview) |
|
| 6.6.38: Administering URL providers and URLs (overview) |
|
| 6.6.39: Administering messaging and JMS providers (overview) |
|
| 6.6.41: Administering WebSphere administrative domains (overview) |
|
| 6.6.42: Administering J2C related administrative resources (overview) |
|
| 6.6.43: Administering references (overview) |
|
| 6.6.44: Administering Web services (overview) |
|
| 6.6.45: Administering WebSphere plug-ins for Web servers (overview) |
|
| 6.6.46: Administering WebSphere administrative servers (overview) |
|
| 6.6.47: Administering generic servers |
|
| 6.6.49: Administering National Language Support (overview) |
|
| 6.6.51: Administering network configurations (overview) |
|
InfoCenter |
|
To launch the full documentation set in a separate browser window, click: |
| Display InfoCenter |
| |
PDF library |
|
To browse the PDF library for this product, containing this article and others, click: |
| PDF versions |
| |
Using this documentation |
|
Become an InfoCenter super user! To find out more about navigation, numbering, search, downloads, and more, click: |
| Using this documentation |
| |
|