Localizing a new virtual machine instance on Linux

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

        This step is necessary to create a unique node name if you will be federating and clustering this node.

    2. Edit the ./setupCmdLine.sh 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.sh 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.sh 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.sh action-clean-scheduled-tasks -DWasPassword=foo command to clear any scheduled tasks. Existing scheduled tasks might reference the old hostname.

  8. 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 Linux
Virtual environment overview

  Removed the two slashes from in front of $AdminTask because wiki marku... Submitted by Megan Crouch on Nov 22, 2011 8:24:55 AM

Re: Localizing a new virtual machine instance on Linux

Carol, per the developer:

These procedures are specific to the use of VMware virtual machine images, and hence they do not apply to virtualization through the use of z/VM to run multiple Linux images on the same LPAR. It is possible to use cloning procedures to clone and localize WebSphere Portal to run on multiple Linux images in a z/VM environment, but that is a different localization use case and would make use of the WebSphere Portal cloning procedures published on developerWorks. Submitted by Carol McGowan on Nov 17, 2011 3:00:41 PM

Re: Localizing a new virtual machine instance on Linux

Can this also be used for a new virtual linux machine instance on z/vm?


+

Search Tips   |   Advanced Search