Steps to change the WebSphere Portal v7.0.x or v8.0.x host name or node name

Technote (FAQ)


Question

What steps can be taken to change the host name or node name of the server IBM® WebSphere® Portal v7.0.x resides on?

Answer

IMPORTANT: These steps do NOT apply to Portal Express.
To change the host name or node name of your WebSphere Portal server, please follow these steps:


Standalone WebSphere Portal server instructions:

1. To change the hostname, execute this wsadmin command from the <profile root>/bin directory:

    Windows: wsadmin.bat -user your_admin_id -password your_password -c "$AdminTask changeHostName {-nodeName  node_name -hostName  new_host_name}"

    UNIX: ./wsadmin.sh -user your_admin_id -password your_password -c "\$AdminTask changeHostName {-nodeName node_name -hostName new_host_name}"

2. To change the node name, follow these steps:
    a. Execute the following wsadmin command from the <profile root>/bin directory.
      Windows: wsadmin.bat -user your_admin_id -password your_password-c "$AdminTask renameNode {-nodeName  old_node_name -newNodeName  new_node_name}"

      UNIX: ./wsadmin.sh -user your_admin_id -password your_password-c "\$AdminTask renameNode {-nodeName old_node_name -newNodeName new_node_name}"
    b. Edit the setupCmdLine.sh/bat file, located in the <profile root>/bin directory and modify the SET WAS_NODE= node_name entry to specify the updated node name.

    c. Portal v7.0.x only. Execute the following ConfigEngine script to update the Node Name in ConfigEngine's registry:
      Windows: ConfigEngine.bat rename-node-in-cell-registry -DWasPassword=<password> -DpreviousNodeName= old_node_name
      UNIX:
      ./ConfigEngine .sh rename-node-in-cell-registry -DWasPassword=<password> -DpreviousNodeName= old_node_name


3. Execute the following ConfigEngine script from the <wp_profile root>/ConfigEngine directory:
    Windows: ConfigEngine.bat localize-clone -DWasPassword=<password>
    UNIX:
    ./ConfigEngine .sh localize-clone -DWasPassword=<password>

4. Verify that the <profile>/ConfigEngine/properties/wkplc.properties has been updated with the new hostname and node name.
    WpsHostName=<new host name>
    NodeName=<new node name>

5. Execute the following ConfigEngine script from the <wp_profile root>/ConfigEngine directory to clear any potential references to the hostname from the scheduled tasks in the database:
    Windows: ConfigEngine.bat action-clean-scheduled-tasks -DWasPassword=<password>
    UNIX:
    ./ConfigEngine .sh action-clean-scheduled-tasks -DWasPassword=<password>



Cluster WebSphere Portal instructions:

Note: The 'localize-clone' ConfigEngine script is not supported in a cluster.

1. T o change the hostname, execute this wsadmin command from the <profile root>/bin directory:

Windows: wsadmin.bat -user your_admin_id -password your_password -c "$AdminTask changeHostName {-nodeName  node_name -hostName  new_host_name}"

UNIX: ./wsadmin.sh -user your_admin_id -password your_password -c "\$AdminTask changeHostName {-nodeName node_name -hostName new_host_name}"

2. To change the node name, follow these steps.
    a. Execute the following wsadmin command from the <profile root>/bin directory.
      Windows: wsadmin.bat -user your_admin_id -password your_password-c "$AdminTask renameNode {-nodeName  old_node_name -newNodeName  new_node_name}"

      UNIX: ./wsadmin.sh -user your_admin_id -password your_password-c "\$AdminTask renameNode {-nodeName old_node_name -newNodeName new_node_name}"
    b. Edit the setupCmdLine.sh/bat file, located in the <profile root>/bin directory and modify the SET WAS_NODE= node_name entry to specify the updated node name.

    c. Portal v7.0.x only. Execute the following ConfigEngine script to update the Node Name in ConfigEngine's registry:
      Windows: ConfigEngine.bat rename-node-in-cell-registry -DWasPassword=<password> -DpreviousNodeName= old_node_name
      UNIX:
      ./ConfigEngine .sh rename-node-in-cell-registry -DWasPassword=<password> -DpreviousNodeName= old_node_name

3. Login to your DMGR

4. Navigate to Environment -> WebSphere Variables

5. Set scope to the WebSphere_Portal server on your first node

6. Edit the WCM_HOST variable to be the new hostname of your first node.

7. Repeat steps 6-7 for each Portal server in your cluster that has a new hostname.

8. Set scope to the Node for your first node.

9. Edit the WAS_NODE_NAME variable and set it to the new node name.

10. Repeat steps 9-10 for each node name that has been changed.

11. Save changes and log out of the DMGR.

12. On node 1, edit the wkplc.properties file and set WpsHostName to the new hostname and NodeName to the new node name.

13. Repeat step 13 for each node in your cluster.

14. Execute the following ConfigEngine script from the <wp_profile root>/ConfigEngine directory on your primary node to clear any potential references to the hostname from the scheduled tasks in the database. This only needs to be executed on the primary node:
    Windows: ConfigEngine.bat action-clean-scheduled-tasks -DWasPassword=<password>
    UNIX:
    ./ConfigEngine .sh action-clean-scheduled-tasks -DWasPassword=<password>


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal
Installation & Configuration

Software version:

7.0, 8.0

Operating system(s):

AIX, Linux, Solaris, Windows

Software edition:

Enable, Extend, Server

Reference #:

1569040

Modified date:

2013-04-19

Translate my page

Machine Translation

Content navigation