If you are running a desktop firewall that blocks access to your
systems ports, you may receive warnings when starting servers, or the servers
may simply fail to start. To work around the problem, you must give TCP/IP
port access to the server process.
This is usually done by adding a rule which allows a particular process
access to a number or range of ports.
- For WebSphere® Application
Server, the Java™ process used to start the server can be found at:x:/runtimes/server_name/java/jre/bin/javaw.exe, where x is the installation
directory of WebSphere Application
Server.
- For the TCP/IP Monitor, the monitor is started within the development
environment process.
- If you are debugging on the server, a dynamic port number is used
by default. If you want to restrict the debugger to use a particular port,
you must edit the server and specify a debug port. To do this, open up the
server with a text editor and set the following property:
Option |
Description |
WebSphere v6.0 server |
This is
done using the WebSphere administrative
console by changing the address parameter of the Debug Argument under the Java virtual
machine settings. For further details, visit the WebSphere InfoCenter a search for the topic
"Java virtual
machine settings". |
WebSphere v5.x server (.server) |
INSTANCE_DEBUG_PORT_NUM_ID="####" |
For Tomcat server (.server) |
debug-port="####" |
where #### is the port you want to use for debugging.