[AIX HP-UX Linux Solaris Windows]

Installing virtual images for VMware ESX

Start the IBM® WebSphere® Application Server Hypervisor Edition virtual image and use the local graphical user interface to configure the operating system and the application server product.

Before you begin

See WebSphere Application Server Hypervisor Edition Beta overview to familiarize yourself with IBM WebSphere Application Server Hypervisor Edition.

You must have VMware ESX 3.0.x or 3.5.x to run the WebSphere Application Server Hypervisor Edition with SLES 10 for VMware ESX Server virtual image.

About this task

The IBM WebSphere Application Server Hypervisor Edition virtual image contains the following products:
Table 1. Included products and descriptions
Product Description
Novell SLES 10 for x86 Operating System
  • Mounted at /
  • 12 GB SCSI Disk
  • Root user and virtuser operating system IDs
  • No additional drives (For example CD-ROM or DVD) are configured, but they can be added through the VMware ESX Server console.
WebSphere Application Server Version 7.0.x
  • A WebSphere Application Server Network Deployment environment is provided in the virtual image you have acquired.
  • Mounted at /opt/IBM/WebSphere/AppServer
  • 2 GB SCSI Disk
IBM HTTP Server for WebSphere Application Server Version 7.0.x Mounted at /opt/IBM/HTTPServer
IBM HTTP Server plug-in for WebSphere Application Server Version 7.0.x /opt/IBM/HTTPServer/Plugins
Update Installer for WebSphere Application Server Version 7.0.x /opt/IBM/WebSphere/AppServer/UpdateInstaller
IBM Support Assistant Lite /opt/IBM/WebSphere/AppServer/ISA/ISALite
Pre-created profiles for WebSphere Application Server Version 7.0.x Mounted at /opt/IBM/WebSphere/Profiles

The virtual image is set for 1 GB of available RAM, which you can increase. The virtual image has NAT networking enabled, which you can change to bridged or host only.

Use the following procedure to install the virtual image product, configure the operating system, and configure the application server product.

Procedure

  1. Transfer the ESX virtual system disks to your ESX hypervisor. You need to transfer the IBM WebSphere Application Server Hypervisor Edition virtual system disks to the target hypervisor.
    1. Extract the contents of the compressed packages to the ESX hypervisor. Run the tar command against each package:
      Table 2. Virtual image file names
      Product Files
      VMware ESX
      • was.7003.nd.linux.vmware.esx.sles.os.tgz
      • was.7003.nd.linux.vmware.esx.binary.tgz
      • was.7003.nd.linux.vmware.esx.profiles.tgz
      • was.7003.nd.linux.vmware.esx.metadata.tgz
      • was.7003.nd.linux.vmware.esx.ihs.tgz
    2. Upload the files to the ESX hypervisor. Transfer the extracted files to the VMware ESX hypervisor using the VMware Infrastructure Client. Click Configuration > Storage and double- click a data store. This accesses the Datastore Browser where you can create directories and upload files to the system. Place the files inside one of the valid volumes under /vmfs/volumes/XXXX. After the packages are extracted, the following files are available for transfer:
      SLES10SP2-32.vmdk
      WebSphere_Binaries.vmdk
      WebSphere_Binaries-flat.vmdk
      WebSphere_Profiles.vmdk
      WebSphere_Profiles-flat.vmdk
      WebSphere_IHS.vmdk
      WebSphere_IHS-flat.vmdk
      WebSphere_V7.vmx
      WebSphere_V7_activation.vmx
      
    3. Register the virtual image. You can register the virtual image using the VMware Infrastructure Client. Right click the WebSphere_V7_activation.vmx file and select Add to inventory.
  2. Read the additional notes for the VMware image for more information.
  3. Click the POWER ON button to launch the virtual image on the VMware Infrastructure Client or web based client. The VMware image starts with a command-line login entry display.
  4. The virtual machine starts and a command-line interface is displayed. Log in to the operating system using the default root credentials.
    • wasvmx login: root
    • Password: password
    Tip: If you make an error while typing in the command-line interface, use the Ctrl+h key combination to backspace.
  5. Read and accept all license statements and agreements for both Novell and WebSphere products. If you do not accept all licenses, the virtual image installation halts. Read each agreement and select I understand and press Enter to continue.
  6. After the license statements are accepted, the language and keyboard selection panel is displayed. Specify your values, select Accept, and press Enter. Although the operating system supports additional languages, the installation panels are only available in the languages supported by WebSphere Application Server Hypervisor Edition. The following table lists the supported languages:
    Table 3. WebSphere Application Server Hypervisor Edition Supported Languages
    Locale Country Language (UTF-8)
    en_US United States English
    de_DE Germany German
    ja_JP Japan Japanese
    ko_KR Korea Korean
    zh_CN China Simplified Chinese
    zh_TW China Traditional Chinese
    fr_FR France French
    it_IT Italy Italian
    es_ES Spain Spanish
    pt_BR Brazil Portuguese
    cs_CZ Czech Republic Czech
    hu_HU Hungary Hungarian
    pl_PL Poland Polish
    ru_RU Russia Russian
  7. The Network Configuration screen is displayed. Specify a static or Dynamic Host Configuration Protocol (DHCP) network protocol by entering an x next to your selection.

    If you specify DHCP, then enter the values for the Host name and Domain fields.

    If you specify static addressing, then enter values for the IP address, Subnet mask, Default gateway (Optional), and DNS server (Optional) fields. The DNS server values must be entered as IP addresses.

    Select Next and press Enter.

  8. The Password configuration screen for the root user is displayed. Enter a new password for the root user. Change this password from the default value. Select Next and press Enter.
  9. The Password configuration screen for the virtuser user is displayed. Enter a new password for the virtuser user, which is the default non-root user for the installation.Change this password from the default value. Select Next and press Enter.
  10. The network and password selections are configured and the configuration results screen is displayed. Review the results information and select End and press Enter.
  11. After the Linux® configuration is completed, the WebSphere profile configuration is launched and the environment selection screen is displayed. Select one of the six pre-configured WebSphere Application Server profiles, or select None if you prefer to create a profile using the Profile Management Tool or the manageprofiles command after you start up the virtual image. Select one of the pre-configured WebSphere profile types that are described in the following table:
    Table 4. WebSphere environment types
    Profile Type Description
    Application server Create a stand-alone application server profile.
    Custom profile Create a custom profile which belongs to a deployment manager cell, to make applications available to the Internet or to an intranet under the management of the deployment manager. You must federate this node to use it.
    Deployment manager Create a deployment manager that provides management capability for multiple federated nodes. The nodes and the deployment manager make up a cell.
    Job manager Create a job manager that provides a single console to administer multiple base servers, multiple deployment managers, and do asynchronous job submission.
    Administrative agent + n application server profiles Create an administrative agent that provides a single interface to administer multiple unfederated application servers.
    Cell Create a cell with two profiles: a deployment manager and an application server node that is already federated into the deployment manager cell. This is useful for development environments.
    IBM HTTP Server Create an IBM HTTP Server profile. When the IBM HTTP Server profile is selected on the blue screens, SLES init.d services is created and started by default for the IBM HTTP Server and adminserver.
    None Do not create a profile. However, if you do not create a profile at this time, then you must create a profile after installation to have an operational product.

    Select Next and press Enter.

  12. The Profile configuration screen is displayed. You can change the cell name and node name of the selected profile. If the chosen profile is an application server profile, custom profile or IBM HTTP Server profile, then you can choose to federate the profile to a deployment manager. If the selected profile is an admin agent, then you can choose the number of base profiles you want and you can optionally register the profile with a job manager.

    You can also select the option to automatically start the servers you have created when the configuration is completed.

  13. The configuration process runs to completion and the configuration progress screen is displayed. The location of the configuration log is indicated on the results screen. Select End and press Enter.
  14. The virtual image completes loading, and the desktop for virtuser is displayed. The desktop is pre-configured with icons for WebSphere Application Server administration console, First Steps, and the Profile Management Tool. Additionally, depending on the profile you selected, the desktop has icons to start the pre-configured deployment manager or application servers.
  15. Configure a Network Time Protocol (NTP) Server or manually set the current date, time, and time zone on the virtual image. The virtual system times must be synchronized to ensure proper federation. Setting up an NTP server is preferable, but manually synchronizing the system times is an alternative solution.

Results

You have installed and configured the WebSphere virtual image. Start your profile environment with the available desktop icons if the environment has not been started already. If any problems are experienced during activation, the activation logs can be reviewed at /opt/IBM/AE/AR/ConfigWAS.traceout and /opt/IBM/WebSphere/Profiles/.ibm/ConfigWAS.summary.

Resetting the image

To reset the image after WebSphere Application Server Hypervisor Edition has been configured, complete the following operation:
  • su - root
    /var/adm/ibmvmcoc-postinstall/resetvm.sh -notools –resetip
  • Stop the image and delete the directory where you extracted the .tgz files. Do not delete the original .tgz files. Start again by following the installation instructions at the beginning of this document.

What to do next

Start your profile environment with the available desktop icons if the environment has not been started already. Click the Websphere Administrative Console icon to open the administrative console. Log in with the virtuser user ID and password you configured earlier.

Apply maintenance to the application server using the Update Installer for WebSphere Software or through updated virtual images from IBM. For more information on application server maintenance, see the topic Installing maintenance packages, interim fixes, fix packs, and refresh packs in the information center. Apply operating system maintenance to the virtual image through downloadable packages or through updated virtual images from IBM.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 20, 2011 1:27:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v800hyperv&product=was-nd-mp&topic=tins_virt_install_vmware_esx
File name: tins_virt_install_vmware_esx.html