|
Problem(Abstract) |
Can I change the configuration ports (Bootstrap, SOAP,
ORB, Listener, HTTP Transport) that I specified during installation of
WebSphere® Application Server V5.0 by editing the .xml configuration
files? |
|
|
|
Resolving the
problem |
Yes, you can modify the configuration ports by editing the
.xml configuration files following the steps outlined below.
*Important Note:
Before making any changes to the configuration files, run the
backupConfig.sh/bat command from the $WAS_HOME/bin directory to backup
your current configuration
After you have successfully backed up your current configuration, modify
the port values in the following files in the Network Deployment Manager
directory structure to what you want them to be when an application server
has been added to the Network Deployment Manager.
Application Server HTTP Transports:
- Open $WAS_HOME/config/cells/<Cell Name>/nodes/<Node
Name>/servers/<Server Name>/server.xml file
- Find the following lines in the file:
- <transports
xmi:type="applicationserver.webcontainer:HTTPTransport"
xmi:id="HTTPTransport_#" external="false" sslEnabled="false"
sslConfig="somethingManager/DefaultSSLSettings">
- <address xmi:id="EndPoint_#" host="*"
port="xxxx"/>
- </transports>
- Edit the "xxxx" to what you want the http transport to be. (This is an
example, flags can be different)
- Open $WAS_HOME/config/cells/<Cell Name>/virtualhosts.xml
file
- Find the following line in the file where you already have the changed
HTTP transport:
- <aliases xmi:id="HostAlias_#" hostname="*"
port="xxxx"/>
- Edit the "xxxx" to what you modified the application server's HTTP
transport.
- Save all the changes to the files.
- You will have to synchronize so the changes in the file are propagated
to all the nodes.
Node Agent ORB Listener Address:
- Open $WAS_HOME/config/cells/<Cell Name>/nodes/<Node
Name>/serverindex.xml
- First find the following in the file:
- <serverEntries xmi:id="ServerEntry_#"
serverDisplayName="nodeagent" serverName="nodeagent"
serverType="NODE_AGENT">
- Find the following lines below the above entry in the file:
- <specialEndpoints xmi:id="NamedEndPoint_4"
endPointName="ORB_LISTENER_ADDRESS">
- <endPoint xmi:id="EndPoint_5" host="websphere.ibm.com"
port="xxxx"/>
- </specialEndpoints>
- Edit the "xxxx" to what you want the ORB Listener Address to be.
- Save all the changes to the files
- You will have to synchronize so the changes in the file are propagated
to all the nodes.
Application Servers, Node Agents or Network Deployment manager
Bootstrap Port:
- Open $WAS_HOME/config/cells/<Cell Name>/nodes/<Node
Name>/serverindex.xml
- First find the following entry for the JVM you want to change the
bootstrap port for (Note: search for the serverName you want to modify
e.g. "nodeagent")
- <serverEntries xmi:id="ServerEntry_#"
serverDisplayName="nodeagent" serverName="nodeagent"
serverType="NODE_AGENT">
- Find the following lines in the file between <serverEntries ...
> found above and </serverEntries>:
- <specialEndpoints xmi:id="NamedEndPoint_1"
endPointName="BOOTSTRAP_ADDRESS">
- <endPoint xmi:id="EndPoint_1" host="websphere.ibm.com"
port="xxxx"/>
- </specialEndpoints>
- Edit the "xxxx" to what you want the bootstrap port to be.
- Save all the changes to the files
- If you do this to a node agent or an application server you will have
to synchronize so the changes in the file are propagated to all the
nodes.
Application Servers, Node Agents or Network Deployment manager SOAP
port:
- Open $WAS_HOME/config/cells/<Cell Name>/nodes/<Node
Name>/serverindex.xml
- First find the following entry for the JVM you want to change the SOAP
for (Note: search for the serverName you want to modify e.g. "nodeagent")
- <serverEntries xmi:id="ServerEntry_2"
serverDisplayName="nodeagent" serverName="nodeagent"
serverType="NODE_AGENT">
- Find the following lines in the file between <serverEntries ...
> found above and </serverEntries>:
- <specialEndpoints xmi:id="NamedEndPoint_2"
endPointName="SOAP_CONNECTOR_ADDRESS">
- <endPoint xmi:id="EndPoint_2" host="websphere.ibm.com"
port="xxxx"/>
- </specialEndpoints>
- Edit the "xxxx" to what you want the SOAP port to be.
- Save all the changes to the files
- If you do this to a node agent or an application server you will have
to synchronize so the changes in the file are propagated to all the
nodes.
If you modify the bootstrap or the SOAP port and you use wsadmin to
connect to the modified server then you need to do the following:
- Open the Base or ND $WAS_HOME/properties/wsadmin.properties file
- Find the following line that is not commented out:
- com.ibm.ws.scripting.connectionType=AAAA
- Find the following line that is not commented out:
- com.ibm.ws.scripting.port=xxxx
- Edit the "xxxx" to what the SOAP port if "SOAP" is what the
connectionType equals else place the bootstrap port if "RMI" is what the
connectionType equals.
- Save all the changes to the files.
Note:
- You can use the same procedure to modify the port settings
for an application server that is not part of a Network Deployment Manager
cell. Obviously, you won't need to do any synchronization.
Possible Problems:
- If you don't follow the instructions carefully, you can
corrupt the WebSphere configuration files. That is why it is important to
back up the configuration before modifying any files.
- You will not be able to recover if you don't run the
"backupConfig" script.
- Make sure the port/ports you choose is/are free (e.g. do
an netstat -an).
- If you add and remove a node from the Network Deployment
Manager that you modified the application server(s) and/or the node agent
ports manually, they will not be ported over.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|