Start the IBM® WebSphere® Application Server
Hypervisor Edition for Novell SUSE Linux® Enterprise
Server or Red Hat Enterprise Linux Server virtual image and use the
local graphical user interface to configure the operating system and
the application server product. This article applies to both IBM®
WebSphere® Application Server Hypervisor Edition for Novell SUSE Linux®
Enterprise Server and Red Hat virtual images.
Before you begin
See WebSphere Application Server Hypervisor Edition overview to familiarize
yourself with IBM WebSphere Application Server Hypervisor
Edition.
WebSphere Application
Server Hypervisor Edition for Novell SUSE Linux Enterprise Server is available in three
versions:
- Version 7.0.0.x with Optional Feature Packs
- Version 6.1.0.x
- Version 6.1.0.x with Feature Packs
IBM WebSphere Application Server Hypervisor Edition for
Red Hat Enterprise Linux Server is available in one version:
- Version 7.0.0.x with Optional Feature Packs
Each version (Version 6.1.0.x, Version 6.1.0.x with Feature
Packs, Version 7.0.0.x with Optional Feature Packs) is available in
the following formats:
- ESX .vmx format, which is supported on ESX 3.5.x and ESX 4.0.x
- OVF 1.0 format, which is supported on ESX and ESXi 3.5.x and 4.0.x
About this task
The IBM WebSphere Application Server
Hypervisor Edition virtual image contains the following products:
Table 1. Included products and descriptions
Product |
Description |
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 Server console
|
WebSphere Application
Server Version 7.0.0.x or 6.1.0.x |
- A WebSphere Application
Server environment is provided in the virtual image you have acquired
- Mounted at /opt/IBM/WebSphere/AppServer
- 8 GB SCSI Disk
|
IBM HTTP
Server for WebSphere Application
Server Version 7.0.0.x or 6.1.0.x |
- Mounted at /opt/IBM/HTTPServer
- 2 GB SCSI Disk
|
IBM HTTP
Server Plugin for WebSphere Application
Server Version 7.0.0.x or 6.1.0.x |
/opt/IBM/HTTPServer/Plugins |
Update Installer for WebSphere Application Server Version 7.0.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.0.x
or 6.1.0.x |
- Mounted at /opt/IBM/WebSphere/Profiles
- 2 GB SCSI Disk
|
IBM Installation Manager for WebSphere Application
Server Hypervisor Edition version 7.0.0.11 and above |
/opt/IBM/WebSphere/AppServer/InstallationManager |
The virtual image is set for 1 GB of available RAM,
which you can increase. The virtual image has NAT networking enabled.
You can change to NAT networking to bridged or host only.
Use
the following procedure to provision, configure, and activate WebSphere Application Server
Hypervisor Edition.
Procedure
- Provision the IBM WebSphere Application Server
Hypervisor Edition to the target hypervisor.
- For the image you wish to use, you must download five
files and place them into the same directory. If you are downloading
these files from Passport
Advantage®, then the files are renamed with a part number. Refer
to the Download Document for instructions on obtaining the required
files. The five files consist of:
- Operating system
- WebSphere Application
Server
- WebSphere Application
Server Profiles
- IBM HTTP Server for WebSphere Application Server Hypervisor Edition
- a meta-data package
In the directory containing the five required files, run the tar
-zxvf command against each package.
Best practice: Tar
version 1.20 or higher is required to uncompress the files. If you
need to uncompress the files on a Windows
® operating
system, then use the Cygwin tool with tar.
bprac
Table 2. Virtual image file names. Note: <os>
=
- rhel.x86 (images with RedHat 5.5 guest operating system)
- sles.x86 (images with SUSE 11 guest operating system)
WebSphere Application
Server Hypervisor Edition Version |
VMware Hypervisor |
Files |
7.0.0.x with Optional Feature Packs |
VMware ESX |
was.<version>.nd.linux.vmware.esx. <os>.os.tgz
was.<version>.nd.linux.vmware.esx.binary. <os>.tgz
was.<version>.nd.linux.vmware.esx.profiles. <os>.tgz
was.<version>.nd.linux.vmware.esx.metadata. <os>.tgz
was.<version>.nd.linux.vmware.esx.ihs. <os>.tgz
|
6.1.0.x |
VMware ESX |
was.<version>.nd.linux.vmware.esx. <os>.os.tgz
was.<version>.nd.linux.vmware.esx.binary. <os>.tgz
was.<version>.nd.linux.vmware.esx.profiles. <os>.tgz
was.<version>.nd.linux.vmware.esx.metadata. <os>.tgz
was.<version>.nd.linux.vmware.esx.ihs. <os>.tgz
|
6.1.0.x with Feature Packs |
VMware ESX |
was.<version>.fep.linux.vmware.esx. <os>.os.tgz
was.<version>.fep.linux.vmware.esx.binary. <os>.tgz
was.<version>.fep.linux.vmware.esx.profiles. <os>.tgz
was.<version>.fep.linux.vmware.esx.metadata. <os>.tgz
was.<version>.fep.linux.vmware.esx.ihs. <os>.tgz
|
7.0.0.x with Optional Feature Packs |
VMware ESX/ESXi |
was.<version>.nd.linux.vmware.ovf. <os>.os.tgz
was.<version>.nd.linux.vmware.ovf.binary. <os>.tgz
was.<version>.nd.linux.vmware.ovf.profiles. <os>.tgz
was.<version>.nd.linux.vmware.ovf.metadata. <os>.tgz
was.<version>.nd.linux.vmware.ovf.ihs. <os>.tgz
|
6.1.0.x |
VMware ESX/ESXi |
was.<version>.nd.linux.vmware.ovf.binary. <os>.tgz
was.<version>.nd.linux.vmware.ovf.profiles. <os>.tgz
was.<version>.nd.linux.vmware.ovf.metadata. <os>.tgz
was.<version>.nd.linux.vmware.ovf.ihs. <os>.tgz
was.<version>.nd.linux.vmware.ovf. <os>.os.tgz
|
6.1.0.x with Feature Packs |
VMware ESX/ESXi |
was.<version>.fep.linux.vmware.ovf. <os>.os.tgz
was.<version>.fep.linux.vmware.ovf.binary. <os>.tgz
was.<version>.fep.linux.vmware.ovf.profiles. <os>.tgz
was.<version>.fep.linux.vmware.ovf.metadata. <os>.tgz
was.<version>.fep.linux.vmware.ovf.ihs. <os>.tgz
|
- After you have extracted the packages, you can provision
the virtual image to a hypervisor. Use the following extracted
files and instructions to provision the image:
Table 3. Provisioning
the virtual image. Note: <VMDK_OS> = SLES11-32 or RHEL54-32
WebSphere Application
Server Hypervisor Edition Version |
VMware Hypervisor |
Extracted Files |
Instructions to provision the image |
7.0.0.x with Optional Feature Packs
|
VMware ESX |
<VMDK_OS>.vmdk
<VMDK_OS>-flat.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
|
Transfer the extracted files to the VMware
ESX hypervisor using the VMware Infrastructure Client. Click Configuration
> Storage and double-click a data store. In the Datastore
Browser, you can create directories and upload files to the system.
Place the files inside one of the valid volumes under /vmfs/volumes/XXXX.
Register the virtual image using the VMware Infrastructure Client.
Right-click the WebSphere_V7_activation .vmx file and select Add
to inventory.
|
- 6.1.0.x
- 6.1.0.x with Feature Packs
|
VMware ESX |
<VMDK_OS>.vmdk
<VMDK_OS>-flat.vmdk
WebSphere_Binaries.vmdk
WebSphere_Binaries-flat.vmdk
WebSphere_Profiles.vmdk
WebSphere_Profiles-flat.vmdk
WebSphere_IHS.vmdk
WebSphere_IHS-flat.vmdk
WebSphere_V61.vmx
WebSphere_V61_activation
.vmx
|
Transfer the extracted files to the VMware
ESX hypervisor using the VMware Infrastructure Client. Click Configuration
> Storage and double-click a data store. In the Datastore
Browser, you can create directories and upload files to the system.
Place the files inside one of the valid volumes under /vmfs/volumes/XXXX.
Register the virtual image using the VMware Infrastructure Client.
Right-click the WebSphere_ESX.vmx file and select Add to
inventory.
|
7.0.0.x with Optional Feature Packs |
VMware ESX/ESXi |
WebSphere_V7-disk1.vmdk
WebSphere_V7-disk2.vmdk
WebSphere_V7-disk3.vmdk
WebSphere_V7-disk4.vmdk
WebSphere_V7.ovf
|
Using the VMware Infastructure Client, select
the WebSphere_V7.ovf file and import the Virtual Appliance.
|
|
VMware ESX/ESXi |
WebSphere_V61-disk1.vmdk
WebSphere_V61-disk2.vmdk
WebSphere_V61-disk3.vmdk
WebSphere_V61-disk4.vmdk
WebSphere_V61.ovf
|
Using the VMware Infastructure Client, select
the WebSphere_V61.ovf file and import the Virtual Appliance.
|
- 6.1.0.x with Feature Packs
|
VMware ESX/ESXi |
WebSphere_V61-disk1.vmdk
WebSphere_V61-disk2.vmdk
WebSphere_V61-disk3.vmdk
WebSphere_V61-disk4.vmdk
WebSphere_V61.ovf
|
Using the VMware Infastructure Client, select
the WebSphere_V61.ovf file and import the Virtual Appliance.
|
- For information about changing the default resource settings
on the virtual appliance, see theVMware documentation on the VMware
support Web site.
- Activate WebSphere Application
Server Hypervisor Edition. Click the POWER
ON button on the VMware Infrastructure Client.
- 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
- Use the command line panels to configure WebSphere Application Server Hypervisor
Edition. To navigate within the command line interface,
use the tab, spacebar, enter, up, down, left, and right keys.
- To navigate buttons and selection lists, use the tab key.
- To navigate within a text box, such as a license or log screen,
use the up, down, left, and right keys.
- To select a button or option, use the enter or spacebar keys.
Tip: If you make an error while typing in the command-line
interface, use the Ctrl+h key combination to backspace.
- 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 4. 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 |
- Read and accept all license statements and agreements for
both operating system and WebSphere products.
If you do not accept all licenses, the virtual image installation
halts. Read each agreement, select I understand,
and press Enter to continue.
- 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 required values
for the IP address, Subnet mask, Default
gateway, and DNS server fields.
The DNS server values must be entered as IP addresses. Select Next and
press Enter. 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.
- 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.
Note: Each WebSphere Application
Server installed in the WebSphere Application
Server Hypervisor is owned by virtuser. WebSphere Application Server global security
(Federated Repository) is also enabled with the username of virtuser
and the password entered in this panel.
Note: In Version 7.0.0.13, you can change the username
from the default value "virtuser" to a new username.
- The network and password selections are configured and
the configuration results screen is displayed. Review the
results information and select End and press Enter.
In Version 7.0.0.13, you can change the
default user ID.
- Enter a new password for the root user. Change this password from
the default value. Select Next and press Enter.
- The configuration for virtual image user ID is displayed. You
can change this username from the default value "virtuser".
- The Password configuration screen for the virtual image user is
displayed.
- Enter a new password for the user. This password is for the default
non-root user for the installation.
- Change this password from the default value. Select Next and
press Enter.
Note: Each WebSphere Application Server instance that is installed
in the WebSphere Application Server Hypervisor is owned by virtuser
(or the specified non-root user). WebSphere Application Server global
security (Federated Repository) is also enabled with the username
of virtuser (or the specified non-root user) and the password entered
in this panel.
- After the Linux configuration
is completed, the WebSphere profile
configuration is launched and the environment selection screen is
displayed. Select one of the 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 Application
Server Hypervisor Edition profile types that are described in the
following table:
Table 5. WebSphere Application Server Hypervisor
Edition Version 7.0 profile types
Profile Type |
Description |
Custom profile |
Create a custom profile that belongs to a deployment
manager cell. This profile can make applications available to the
Internet or to an intranet under the management of the deployment
manager. You must federate this node. |
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, administer multiple deployment
managers, and perform asynchronous job submission. |
Administrative agent + n application
server profiles |
Create an administrative agent that provides
a single interface to administer multiple unfederated application
servers. |
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. |
Table 6. WebSphere Application
Server Hypervisor Edition Version 6.1 profile types
Profile Type |
Description |
Custom profile |
Create a custom profile that belongs to a deployment
manager cell. This profile can make applications available to the
Internet or to an intranet under the management of the deployment
manager. You must federate this node. |
Deployment manager |
Create a deployment manager that provides management
capability for multiple federated nodes. The nodes and the deployment
manager make up a cell. |
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.
- 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.
- If you are activating WebSphere Application
Server Hypervisor Edition Version 7.0.0.x, the feature pack menu displays.
If applicable, the profile that you selected in the previous step
will be augmented with the feature packs that you select from this
menu.
- 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.
- After the virtual image activation completes, 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.
- 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
WebSphere Application
Server Hypervisor Edition is now fully provisioned, activated, configured,
and ready to use. 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
After the WebSphere Application Server Hypervisor
Edition has been configured, there are two ways to reset the image
and reconfigure it using the activation panels.
- Resetting the image using the provided reset script.
This method
runs the provided reset script to reset the WebSphere Application
Server profiles, users, passwords, locale, and IP settings created
during the image activation. Any changes to the image outside of
these settings will remain in effect on the system after the reset.
- Stop all Websphere Application Server processes running on the
system. This is crucial to ensure that the script can fully reset
the WebSphere Application Server profile configurations.
- If the non-root user ID has been configured to an ID other than
virtuser, then that user must not be logged into the system, because
the script will reset that userID back to virtuser.
- Log into the system as root and run the following command: +
/var/adm/ibmvmcoc-postinstall/resetvm.sh -notools -resetip
- When the script completes, the image will shut down. Power the
image back on and complete the activation panels according to the
installation instructions.
- Recreating the image from the .tgz files.
This method creates
a fresh image from the original .tgz files, no configuration or data
from the previous image will be saved.
- Stop the image and delete it using the VMWare Infrastructure Client.
- Delete the directory where the .tgz files were extracted. Do
not delete the original .tgz files, they can be re-extracted to set
up the new image.
- 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 user ID and password you configured during image activation.
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.