|
Problem |
Steps to assign a static "Dr Admin" port for the
Administrative Server, Application Servers, and clones on all releases of
WebSphere® Application Server V4.0. |
|
Solution |
By default, the WebSphere Application Server Dr
Admin port is assigned randomly to the Administrative Server,
Application Servers and clones at startup.
Determining what ports are being used by Dr Admin
- Administrative Server
Each Administrative Server in your node will have a port to Dr Admin.
$WAS_HOME\logs\tracefile
DrAdminServer I WSVR0053I: DrAdmin available on port 3752
- Application Servers and clones
$WAS_HOME\logs\stdout
DrAdminServer I WSVR0053I: DrAdmin available on port 3514
Assigning a static Dr Admin port to the Administrative Server
- Edit $WAS_HOME/bin/admin.config file to reflect following:
# Administrative Server DrAdmin port
com.ibm.ejs.sm.adminServer.diagThreadPort=port#
where port# is the port you are defining.
Example:
# Node 1 Administrative Server DrAdmin static port
com.ibm.ejs.sm.adminServer.diagThreadPort=6789
- Exit and Save.
- Recycle the node for the port assignment to take effect.
Assigning a static Dr Admin port to the Application Servers and
clones
For V4.0.3 and V4.0.4 only, you must install PQ63146 for this
option to work.
- Open the Administrative Console and edit the following setting for the
Application Server or clone for which you are configuring a static Dr
Admin port.
- Select the Application Server or clone.
- Select JVM™ Settings tab on the right side panel.
- Click Add in the System Properties section, then type
the following:
Name:diagThreadPort (this is case sensitive)
Value: port# (where port# is the port you are defining)
- Click Apply.
- Confirm that this setting has been added, go to the Generated
Command Line Arguments. It should now show:
-DdiagThreadPort=<port#>
- Recycle the Application Server for the port assignment to take
effect.
|
|
|