After creating a profile or adding a node, the host name of the
server or its ports might be incorrect. You can follow the examples to change the server host name
using command line tools and the wsadmin scripting tool, and the host name of the server ports using
the administrative console and command line tools.
Before you begin
Create a profile or add a node to a cell. Verify that the host name of the server and the server ports are
correct.
About this task
If the host name of a server or its ports is incorrect, then you might experience problems
such as errors when you attempt to stop a server. One example task shows how to correct the server
host name through command line tools and the wsadmin scripting tool. The other example task shows
how to correct the host name of the server ports using the administrative console and command line
tools.
Procedure
- Correct the host name for an application server node, a node agent,
or a deployment manager node using the wsadmin scripting tool and command line tools.
- Launch the wsadmin tool.
Enter the following
command:
wsadmin -lang jython
- List the contents of the server configuration file.
Enter the following line of
code:
AdminConfig.list('ServerIndex')
- In the output, find the ServerIndex object for the application
server node, the node agent, or the deployment manager, similar to the following examples:
Application server and node agent:
cells/isthmusCell16/nodes/isthmusNode06|serverindex.xml#ServerIndex_1
Deployment
manager:cells/isthmusCell16/nodes/isthmusCellManager06|serverindex.xml#ServerIndex_1
- Modify the host name for the application server node, the node
agent, or the deployment manager, similar to the following examples:
Application server and node agent:
Enter the following line of
code:
AdminConfig.modify('(cells/isthmusCell16/nodes/isthmusNode06|serverindex.xml
#ServerIndex_1)', "[[hostName new_host_name]]")
Deployment manager:
Enter the following line of
code:
AdminConfig.modify('(cells/isthmusCell16/nodes/isthmusCellManager06|
serverindex.xml#ServerIndex_1)', "[[hostName new_host_name]]")
The commands are split on multiple lines for printing purposes.
- Modify the host name for the Daemon instance as it applies to the
application server, node agent, and deployment manager.
Application server and node agent:
Enter the following line of
code:
AdminTask.modifyNodeGroupProperty('DefaultNodeGroup',
'[ -name was.WAS_DAEMON_protocol_iiop_daemon_listenIPAddress
-value newHostname]')
Deployment manager:
Enter the following line of
code:
AdminTask.modifyNodeGroupProperty('DefaultNodeGroup',
'[ -name was.WAS_DAEMON_protocol_iiop_daemon_listenIPAddress
-value newHostname]')
- Verify that the host names are correct, similar to the following
examples:
Application server and node agent:
Enter the following line of
code:
AdminConfig.show('(cells/isthmusCell07/nodes/isthmusCellManager07|
serverindex.xml#ServerIndex_1)', 'hostName')
The
response is:
'[hostName isthmus]'
Deployment manager:
Enter the following line of
code:
AdminConfig.show('(cells/isthmusCell07/nodes/isthmusNode04|
serverindex.xml#ServerIndex_1)', 'hostName')
The
response is:
'[hostName isthmus]'
The commands are split on multiple lines for printing purposes.
- Save the configuration.
Enter the following line of
code:
AdminConfig.save()
- Type
exit
to end the wsadmin session.
- If you changed the host names for the application server and node agent, update the
node with the changes.
- Stop the node agent.
Enter the following
command:
stopNode -profileName AppSrv01
- Stop the application server.
Enter the following
command:
stopServer server1 -profileName AppSrv01
- Use the syncNode script found in each federated node's /bin directory to
synchronize the changes from the master configuration in the node
Deployment manager:
Enter the following
command:
syncNode <DMGR_HOST> <SOAP_PORT>
- Restart the node agent.
Enter the following
command:
startNode -profileName AppSrv01
- Restart the application server.
Enter the following
command:
startServer server1 -profileName AppSrv01
- If you changed the host name for the deployment manager, restart the
deployment manager to apply the changes.
- Stop the deployment manager(from the deployment manager's /bin directory)..
Enter the
following
command:
stopManager -profileName DMgr01
- Start the deployment manager.
Enter the following
command:
startManager -profileName DMgr01
- Correct the host names for the ports that an application server, node
agent, or deployment manager opens.
If you have to correct the host names of the server ports, then you can make the correction using
command line tools and either the wsadmin scripting tool or the administrative console. You might
have to correct the host names of multiple ports for a particular server. This example shows you how
to correct the host names using the administrative console and command line tools.
- For the application server, select . For the node agent, select
. For the deployment manager, select
.
- Select a port whose host name needs changing.
- Change the host name in the Host field; Click OK.
- Continue selecting ports and changing host names until you correct each of the host
names for the server ports.
- Save the changes to the master configuration.
- If you changed the host names for the application server and node agent, update the
node with the changes.
- Stop the node agent.
- Select .
- Select the node agent that you want to stop.
- Click Stop.
- Stop the application
server.
- Select .
- Select the server that you want to stop.
- Click Stop.
- Synchronize the nodes.
Enter the following
command:
syncNode deployment_manager_host deployment_manager_port
- Restart the node agent.
- Select .
- Select the node agent that you want to restart.
- Click Restart.
Enter the following
command:
startNode -profileName AppSrv01
- Restart the application server.
- Select .
- Select the server that you want to restart.
- Click Start.
- If you changed the host name for the deployment manager, restart the
deployment manager to apply the changes.
- Stop the deployment manager.
- Start the deployment manager.
Enter the following
command:
startManager -profileName DMgr01
Results
You have changed the host name of the server, the host names of the server ports, or both.
What to do next
You can
continue to administer the product by doing such tasks as managing nodes, node agents, and node
groups.