Localizing a new virtual machine instance on Windows

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

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 virtual machine instance.

To localize a new virtual machine instance:

  1. Stop the WebSphere_Portal server running on the virtual machine.

  2. Verify that the server1 server is running on the virtual machine. If it is not running, start the server.

  3. Update the host name for the virtual machine instance per the instructions of the OS.

  4. Run the wsadmin -c "$AdminTask changeHostName {-nodeName node_name -hostName new_host_name}" command from the WP_PROFILE/bin directory to update the WebSphere Portal host name in the IBM WAS 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.

  5. Optional. To update the node name in the IBM WAS configuration:

    1. Run the wsadmin -c "$AdminTask renameNode {-nodeName old_node_name -newNodeName new_node_name}" command to update the node name in the IBM WAS configuration.

        old_node_name is the original node name of the current configuration and new_node_name is the new node name you will use for this instance. Remember: This step is necessary to create a unique node name if you will be federating and clustering this node.

    2. Edit the setupCmdLine.bat file, located in the WP_PROFILE/bin directory and modify the SET WAS_NODE=node_name entry to specify the updated node name.

    3. Run the ConfigEngine.bat rename-node-in-cell-registry -DWasPassword=foo -DpreviousNodeName=oldNodeName, from the WP_PROFILE/ConfigEngine, where oldNodeName is the prior value of the node name.

  6. Run the ConfigEngine.bat localize-clone -DWasPassword=foo command from the WP_PROFILE/ConfigEngine to update WebSphere Portal with the information from the IBM WAS configuration.

  7. Run the ConfigEngine.bat action-clean-scheduled-tasks -DWasPassword=foo command to clear any scheduled tasks. Existing scheduled tasks might reference the old hostname.

  8. Optional. If you had an existing Windows™ Service set up for the WebSphere_Portal server, it will still reference the old host name and node name. To continue using the Windows Service to start and stop servers, re-create the services using the WASService command. See the 'WASService Command' link for information.

  9. Restart the server1 server and start the WebSphere_Portal server on the virtual machine.

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


Parent

Install on Windows
Virtual environment overview


Related tasks

WASService command

  Removed the slash from in front of $AdminTask because wiki markup adde... Submitted by Megan Crouch on Jun 14, 2011 7:56:51 AM

Re: Localizing a new virtual machine instance on Windows: wp7

After speaking with the developer, the above steps are tested. Although it may be possible to rename the host name before starting server1, it has not been tested. Submitted by Marc w Smith on Jun 2, 2011 2:31:09 AM

Re: Localizing a new virtual machine instance on Windows: wp7

Is it possible to rename hostname and then start server1? I'm currently getting the same error in portal starting and server1. I'm thinking it's because I didn't have server1 starting before I changed the host name in the OS. Can anyone verify to me that it has to be done the order above? Thx


+

Search Tips   |   Advanced Search