Localizing a new virtual machine instance on Linux

If you are using VMware ESX, you can create a virtual environment that allows you to create virtual instance. When a new virtual instance is created, you must update IBM® WebSphere® Portal with the machine-specific information, such as the host and node names of the instance.

Before you begin

You must install and configure VMware ESX to create a virtual machine environment. You must also have WebSphere Portal installed and if appropriate configured before localizing your virtual machine instance.

About this task

Complete the following steps to localize a new virtual machine instance:

Procedure

  1. Stop the WebSphere_Portal server running on the virtual machine.
  2. Update the host name for the virtual machine instance per the instructions of the operating system.
  3. Run the ./wsadmin.sh -c "\$AdminTask changeHostName {-nodeName node_name -hostName new_host_name}" -conntype NONE command from the wp_profile_root\bin directory to update the WebSphere Portal host name in the IBM WebSphere Application Server configuration.

    node_name is the node name of the current configuration and new_host_name is the TCP/IP host name of the new virtual machine instance.

  4. Optional: Complete the following steps to update the node name in the IBM WebSphere Application Server configuration:
    1. Run the ./wsadmin.sh -c "\$AdminTask renameNode {-nodeName old_node_name -newNodeName new_node_name}" -conntype NONE command to update the node name in the IBM WebSphere Application Server configuration.

      old_node_name is the original node name of the current configuration and new_node_name is the new node name you use for this instance.

      Remember: This step is necessary to create a unique node name if you are federating and clustering this node.
    2. Edit the ./setupCmdLine.sh file, located in the wp_profile_root\bin directory and modify the SET WAS_NODE=node_name entry to specify the updated node name.
  5. Run the ./ConfigEngine.sh localize-clone -DWasPassword=password command from the wp_profile_root/ConfigEngine directory to update WebSphere Portal with the information from the IBM WebSphere Application Server configuration.
  6. Run the ./ConfigEngine.sh action-clean-scheduled-tasks -DWasPassword=password command to clear any scheduled tasks. Existing scheduled tasks might reference the old hostname.
  7. Start the WebSphere_Portal server on the virtual machine.

Results

WebSphere Portal is now ready to be used in this virtual machine instance.