You can install the virtual image product, configure the
operating system, and configure the application server product.
Before you begin
To familiarize yourself with IBM® WebSphere® Application Server
Hypervisor Edition, see the IBM WebSphere Application Server
Hypervisor Edition overview.
You must have the appropriate version
of VMware ESX or VMware ESXi to run the WebSphere Application Server
Hypervisor Edition image.
About this task
The IBM WebSphere Application Server
Hypervisor Edition virtual image contains the following products:
Table 1. Included products and descriptionsProduct |
Description |
Novell SLES or RedHat Enterprise Linux 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.
|
IBM Binary Disk |
- Mounted at /opt/IBM
- 13GB SCSI disk
|
WebSphere Application Server Version 8.5.x |
Installed in /opt/IBM/WebSphere/AppServer |
IBM HTTP Server for WebSphere Application Server
Version 8.5.x |
Installed in /opt/IBM/HTTPServer |
IBM HTTP Server plug-in for WebSphere Application
Server Version 8.5.x |
Installed in /opt/IBM/Plugins |
IBM Installation Manager |
Installed in /opt/IBM/InstallationManager |
Pre-created profiles for WebSphere Application
Server Version 8.5.x |
Installed in /opt/IBM/WebSphere/Profiles |
IBM WebSphere Application Server Web 2.0 and
Mobile Toolkit |
Installed in /opt/IBM/WebSphere/Web20Mobile |
WebSphere eXtreme Scale Version 8.5.x client |
Installed in /opt/IBM/WebSphere/AppServer |
The virtual image is set for 1.5 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
- Upload the .ovf image to your hypervisor. You
need to transfer the IBM WebSphere Application Server
Hypervisor Edition virtual system disks to the target hypervisor.
- Extract the contents of the compressed packages to your
local system. Run the tar -xzf command
against each package:
Table 2. Virtual image file namesProduct |
Files |
VMware ESX |
- was.85xx.nd.linux.vmware.ovf.binary.sles.x86.tgz
- was.85xx.nd.linux.vmware.ovf.metadata.sles.x86.tgz
- was.85xx.nd.linux.vmware.ovf.sles.x86.os.tgz
|
- Upload the files to the ESX hypervisor. Transfer
the extracted files to the VMware ESX hypervisor using the VMware
Infrastructure Client. Click File > Deploy OVF template.
In the first panel of the wizard, click browse and
locate the WebSphere_V8.ovf file extracted in the previous step. Name
your image, select the appropriate datastore, and select the network
to use. At the conclusion of the wizard your disks transfer to the
hypervisor and the VM is registered.
- Read the additional notes for the VMware image for more
information.
- 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.
- 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.
- 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.
- 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 LanguagesLocale |
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 |
- You can create a pattern from the IBM Workload Deployer
or PureApplication System console. Select Patterns
>Virtual Systems.
- Select the plus icon to create a new pattern. Enter
a name for the pattern. Click OK.
- To edit the pattern, select edit. The panel displays the parts from your WebSphere Application
Server imported image. You can select and drag parts. To complete
the pattern, select Done editing. For more
details on Advanced Options, see the IBM Workload Deployer Information
Center.
- 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 profile
types that are described in the following table:
Table 4. WebSphere environment
typesProfile 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. |
Liberty profile server |
Create a Liberty profile server. |
ODR |
Create a demand router. |
- To deploy the pattern, select Deploy.
Enter a Virtual System Name and select the check
box.
- You have the option to choose an environment from the cloud
group. Select .
- Enter and confirm your root password and virtuser password. Click OK.
- Deploy the virtual application pattern. Click OK.
Results
You have installed and configured the WebSphere virtual image. Start your profile
environment with the available desktop icons if the environment has
not started. If there are problems during activation, you can view
the activation logs 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:
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.
For information about applying maintenance
and service, see WebSphere Application Server Hypervisor Edition overview.