Change the node host names

After creating a profile or adding a node, the host name of the server or its ports might be incorrect. We can follow the examples to change the server host name using tools and the wsadmin scripting tool, and the host name of the server ports using the console and tools.

Create a profile or add a node to a cell. Verify that the host name of the server and the server ports are correct.

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 tools and the wsadmin scripting tool. The other example task shows how to correct the host name of the server ports using the console and tools.

• Correct the host name for an application server node, a node agent, or a deployment manager node using wsdmin.sh and tools.
  

  1. Launch wsadmin.sh.

     Enter the following command:

     wsadmin -lang jython

  2. List the contents of the server configuration file.

     Enter the following line of code:

     AdminConfig.list('ServerIndex')

  3. In the output, find the ServerIndex object for the application server node, the node agent, or the deployment manager, similar to the following examples:
     
  4. Application server and node agent:
     cells/isthmusCell16/nodes/isthmusNode06|serverindex.xml#ServerIndex_1

     dmgr:

     cells/isthmusCell16/nodes/isthmusCellManager06|serverindex.xml#ServerIndex_1

  5. Modify the host name for the application server node, the node agent, or the deployment manager, similar to the following examples:
     
  6. Application server and node agent:

     Enter the following line of code:

     AdminConfig.modify('(cells/isthmusCell16/nodes/isthmusNode06|serverindex.xml
     #ServerIndex_1)', "[[hostName new_host]]")

     dmgr:

     Enter the following line of code:

     AdminConfig.modify('(cells/isthmusCell16/nodes/isthmusCellManager06|
     serverindex.xml#ServerIndex_1)', "[[hostName new_host]]")

     The commands are split on multiple lines for printing purposes.

  7. Modify the host name for the Daemon instance as it applies to the application server, node agent, and deployment manager.
     

     (zos) Application server and node agent:

     (zos) Enter the following line of code:

     AdminTask.modifyNodeGroupProperty('DefaultNodeGroup', '[ -name was.WAS_DAEMON_protocol_iiop_daemon_listenIPAddress -value newHostname]')

     (zos) Deployment manager:

     (zos) Enter the following line of code:

     AdminTask.modifyNodeGroupProperty('DefaultNodeGroup', '[ -name was.WAS_DAEMON_protocol_iiop_daemon_listenIPAddress -value newHostname]')

  8. Verify that the host names are correct, similar to the following examples:
     
  9. 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]'

     dmgr:

     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.

  10. Save the configuration.

      Enter the following line of code:

      AdminConfig.save()

  11. Type exit to end the wsadmin session.

  12. If we changed the host names for the application server and node agent, update the node with the changes.
      

      1. Stop the node agent.

         Enter the following command:

         stopNode -profileName AppSrv01

      2. Stop the application server.

         Enter the following command:

         stopServer server1 -profileName AppSrv01

      3. Use the syncNode script found in each federated node's /bin directory to synchronize the changes from the master configuration in the node

         dmgr:

         Enter the following command:

         syncNode <DMGR_HOST> <SOAP_PORT>

      4. Restart the node agent.

         Enter the following command:

         startNode -profileName AppSrv01

      5. Restart the application server.

         Enter the following command:

         startServer server1 -profileName AppSrv01

  13. If we changed the host name for the deployment manager, restart the deployment manager to apply the changes.

      1. Stop the deployment manager(from the deployment manager's /bin directory)..

         Enter the following command:

         stopManager -profileName DMgr01

      2. 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 we have to correct the host names of the server ports, then we can make the correction using tools and either the wsadmin scripting tool or the console. We 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 console and tools.

  1. For the application server, select Servers > Server Types > WebSphere application servers > application_server > Ports. For the node agent, select System administration > Node agents > node_agent > Ports. For the deployment manager, select System administration > dmgr > Ports.

  2. Select a port whose host name needs changing.

  3. Change the host name in the Host field; Click OK.

  4. Continue selecting ports and changing host names until you correct each of the host names for the server ports.

  5. Save the changes to the master configuration.

  6. If we changed the host names for the application server and node agent, update the node with the changes.
     

     1. Stop the node agent.

        • Select System administration > Node agents.

        • Select the node agent to stop.

        • Click Stop.

     2. Stop the application server.

        • Select Servers > Server Types > WebSphere application servers.

        • Select the server to stop.

        • Click Stop.

     3. Synchronize the nodes.

        Enter the following command:

        syncNode deployment_manager_host deployment_manager_port

     4. Restart the node agent.

        • Select System administration > Node agents.

        • Select the node agent to restart.

        • Click Restart.

        (zos) Enter the following command:

        startNode -profileName AppSrv01

     5. Restart the application server.

        • Select Servers > Server Types > WebSphere application servers.

        • Select the server to restart.

        • Click Start.

  7. If we changed the host name for the deployment manager, restart the deployment manager to apply the changes.

     1. Stop the deployment manager.

        • Select System administration > dmgr.

        • Click Stop.

     2. 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

We can continue to administer the product by doing such tasks as managing nodes, node agents, and node groups.

Related tasks

Adding, managing, and removing nodes

Create application server profiles

Create cell profiles

Create custom profiles

Create management profiles with deployment managers

manageprofiles command

Introduction: Administrative scripting (wsadmin)

Use command-line tools