# Overview

# WebLogic Server Virtual Edition Overview

BEA WebLogic Server Virtual Edition™ (WLS-VE) is a Java application server that is optimized for running in virtualized computing environments. The following sections describe the features of WLS-VE:

- Using WLS-VE to Leverage Your Virtualized Environment
- Comparison of WebLogic Server with WLS-VE
- Environment Requirements
- Recommended Topology
- Licensing WLS-VE
- Downloading an Evaluation Copy

## Using WLS-VE to Leverage Your Virtualized Environment

WLS-VE combines BEA WebLogic Server® with BEA LiquidVM™, a Java Virtual Machine (JVM) that works with hypervisor software and provides only the set of operating system (OS) features that WebLogic Server needs to offer its full range of services. Because hypervisor software recognizes LiquidVM as a guest OS, WLS-VE offers life-cycle control and monitoring features that are unavailable with other application servers.

In addition, WLS-VE removes layers of the software stack (see Figure 1), which reduces the number of software installations to license, patch, and monitor, and makes it possible to avoid some of the performance degradation that is common in virtualized data centers.

Figure 1 WLS-VE Removes Layers of the Software Stack

### How LiquidVM Provides Operating System Features

While application servers can consume large amounts of computing resources, even full-featured Java Platform, Enterprise Edition (Java EE) application servers such as WebLogic Server use only a subset of the services that a standard operating system provides.

For example, while operating systems typically provide a user interface (either a graphical user interface or a command-line interface), Java EE application servers do not need such services. Instead, application servers rely on the operating system mostly for networking and file-system services, and they rely on the JVM for most other services, such as translating Java code into hardware-specific instructions, managing memory, and scheduling threads.

In a virtualized software stack, the responsibilities of the JVM and operating system are unchanged, but an additional layer of software—the hypervisor—resides between the operating system and the hardware. The hypervisor coordinates low-level calls from multiple operating systems that are running on a single physical machine. To fill its coordinating role, the hypervisor provides hardware-specific device drivers and other hardware-specific services.

LiquidVM provides the JVM services and operating-system services that WebLogic Server needs to offer its full set of services, and it relies on hypervisor software to provide hardware-specific device drivers and other hardware-specific services (see Figure 2).

Figure 2 LiquidVM Provides Operating System Features

### Benefits of WLS-VE

WLS-VE offers the following advantages over running WebLogic Server in a Windows or UNIX guest OS within a virtualized environment:

- Less disk space.

Because LiquidVM contains only a fraction of the services and programs of a standard OS, WLS-VE requires significantly less disk space than a stack of WebLogic Server, JVM, and a standard OS.

- Less memory.

Because LiquidVM provides basic operating-system services, WLS-VE instances consume only as much memory as required for basic operations. A virtual machine that runs WLS-VE does not need to reserve memory for the hundreds of programs that are in a standard OS but are unused by WebLogic Server.

- Greater efficiency.

Because WLS-VE uses less disk space and less memory, you can operate more virtual servers on the same physical server without noticeably affecting the performance of any of the individual servers.

- Faster hibernate and resume cycles.

Hypervisor software can take a snapshot of a virtual machine's state, write the state to disk, and then use the state data to restart the machine exactly as it was at the time of the snapshot.

Because LiquidVM instructs the hypervisor to store only the JVM data that is needed to restore WLS-VE's state, the snapshot of a machine that runs WLS-VE is significantly smaller than snapshots of machines with other JVMs. This smaller snapshot requires less time to write and read from disk.

- Less potential for security incursions.

Because LiquidVM provides only required low-level services, WLS-VE has fewer opportunities for security incursions than with standard operating systems.

#### Manage Your Applications as Software Appliances

In a virtualized environment, a software appliance is a pre-configured software stack that the hypervisor can start, stop, hibernate, and resume. Some software vendors package software appliances as a single file. WLS-VE includes utilities that enable you to manage a WLS-VE application stack as a software appliance, even though your application and WLS-VE are packaged as a collection of files (see Figure 3).

To configure your WLS-VE-hosted application to run as a software appliance, you create a WebLogic Server domain and deploy your applications onto the WebLogic managed servers in the domain. Then you use WLS-VE utilities to configure a VM that will run one of the managed servers in your domain. You create one such pre-configured virtual machine for each managed server in the domain.

Figure 3 WLS-VE Applications as Software Appliances

#### Application Versioning and Patching Model for WLS-VE Appliances

Because WLS-VE, domains, and applications are packaged as separate files, you can deploy a new version of your application without stopping your appliances and without interrupting your application's clients. (See Deploying Applications to WebLogic Server in Deploying Applications to WebLogic Server.)

In addition, as with WebLogic Server, you can use BEA's rolling upgrade process to install BEA patches for your WLS-VE appliances without shutting down the entire domain or cluster (see WebLogic Server Rolling Upgrade in Upgrading WebLogic Application Environments).

#### Which Application Types Benefit from WLS-VE?

Applications that never or only occasionally experience performance barriers due to lack of CPU, memory, or networking resources are good candidates for running in a virtual environment and are therefore good candidates for WLS-VE. For these applications, deploying and serving from WLS-VE is indistinguishable from WebLogic Server.

Note: | Applications that frequently experience performance barriers due to lack of CPU, memory, or networking resources usually require dedicated hardware resources and are not good candidates for running in a virtual environment or on WLS-VE.

#### Use WLS-VE in Production or Testing Environments

WLS-VE delivers the same high-availability, security, and deployment features of WebLogic Server that are required for production environments, and its support for virtual environments enables you to maximize the use of the computing resources in your data center.

In a testing (QA) environment, WLS-VE simplifies the process of configuring machines or entire collections of machines for running tests. Using a single script, QA engineers can instantiate an entire WebLogic Server domain running on machines with pre-configured amounts of memory, CPU, and network resources. When the tests have completed, another script can reconfigure the same physical machines for additional tests that use different amounts of computing resources.

### Limitations of WLS-VE

Note the following limitations when using WLS-VE:

- WLS-VE is a platform for production and testing environments, not for development environments.

The WLS-VE installation package does not include WebLogic Workshop or the WebLogic Server samples.

- WLS-VE is the only process that can run in a VM that runs LiquidVM as a guest OS. For example:

- You cannot run Microsoft Windows in the VM that hosts WLS-VE, so your applications cannot use DCOM/ActiveX to access Microsoft Office applications.
- You cannot use BEA Node Manager.
- You cannot use startup scripts or classes that attempt to start additional processes on the same machine but outside the JVM (such as a database, a Perl script, or monitoring software). For example, you cannot start a Perl script by invoking `System.exec` from your WebLogic Server.
- You cannot use Type 2 JDBC drivers. Instead, use Type 4 drivers.

- Because BEA Node Manager is not available:

- You cannot start/suspend/resume managed servers from the admin console. But you can still stop servers from the admin console.
- You cannot perform server migration from WLS-VE. You can, however, use VMware Vmotion functionality for virtual machine migration.
- You cannot perform service migration in WLS-VE.

- WLS-VE and applications that run in WLS-VE cannot execute non-Java (native) code.
- WLS-VE uses a Network File System (NFS) file server to read and write files (such as domain and application configuration files, log files, and files in a file store).

Applications that use file stores extensively (or that frequently write files directly to the file system) could experience some performance degradation when served from WLS-VE.

Caution: | Ensure that unauthorized users cannot snoop network traffic, mount the WLS-VE directories, or access the directories on the NFS server's local disk. Any attacker with read access to a WLS-VE domain directory can use the data in the directory to decrypt the WLS-VE boot password, gain administrative privileges, and compromise the entire domain. For more information, see Setting Up System Security in WebLogic Server VE Installation and Configuration Guide.

## Comparison of WebLogic Server with WLS-VE

Table 1 compares how managed servers are distributed on hardware with WebLogic Server and WLS-VE.

Table 1 Distribution of Managed Servers
WebLogic Server in Non-Virtualized Environment | WebLogic Server in Virtualized Environment | WLS-VE
--- | --- | ---
On a single machine, you can run multiple managed servers and you can run multiple additional processes. | On a single machine, the hypervisor layer enables you to run multiple VMs. Each VM runs a full operating system (guest OS), which can host multiple managed servers and additional processes. | On a single machine, the hypervisor layer enables you to run multiple VMs. Each VM runs only WLS-VE, which includes its own guest OS, a WebLogic Server instance, and one or more Java applications.

Table 2 compares the location of file storage for WebLogic Server and WLS-VE.

Table 2 Location of File Storage
WebLogic Server in Non-Virtualized Environment | WebLogic Server in Virtualized Environment | WLS-VE
--- | --- | ---
All artifacts related to WebLogic Server (BEA classes, domain configuration documents and runtime caches, application classes, descriptors, file stores, and log files) can reside on local disk or network-attached storage (NAS). | All artifacts related to WebLogic Server can reside on the virtual machine's virtual disk, which can be implemented as a local disk, SAN, or NAS. | WLS-VE classes are packaged in a file that conforms to the ISO standard for CD-ROM images (ISO 9660). This ISO image file can reside on the local disk of the hypervisor's host machine, SAN, or NAS. All other artifacts must reside on an NFS file server.

Table 3 compares life-cycle control options for WebLogic Server and WLS-VE.

Table 3 Life Cycle Control
WebLogic Server in Non-Virtualized Environment | WebLogic Server in Virtualized Environment | WLS-VE
--- | --- | ---
To start WebLogic Server instances, you can do any of the following: Log on to the host machine and run a startup script. Configure the OS to run WebLogic Server as a Windows service or daemon. Use Node Manager. You can also configure Node Manager to restart a server when the server's health has failed. | To start WebLogic Server instances, you can do any of the following: Log on to the VM's guest OS and run a startup script. Configure the guest OS to run WebLogic Server as a Windows service or daemon. Use Node Manager. You can also configure Node Manager to restart a server when the server's health has failed. | To start a WLS-VE appliance, you can use either of the following: A WLS-VE startup script. The hypervisor's management console. You cannot use Node Manager or the WebLogic Server Administration Console to start or manage WLS-VE appliances.
To stop servers, you can: Use the WebLogic Server Administration Console. Use Node Manager. | To stop servers, you can: Use the WebLogic Server Administration Console. Use Node Manager. Note that the VM and its guest OS continue to consume resources until you use the hypervisor to stop the VM. | To stop a WLS-VE appliance, you can: Use the WebLogic Server Administration Console.
| The hypervisor software makes it possible to suspend (hibernate) and resume an entire VM. | The hypervisor software makes it possible to suspend (hibernate) and resume an entire VM. LiquidVM facilitates this process by instructing the hypervisor to store only the JVM data that is needed to restore WLS-VE's state.

## Environment Requirements

WLS-VE requires the following software and computing components to be in your environment:

- VMWare® ESX Server 3.0 or higher must be installed directly on all machines on which you want to run WLS-VE.

BEA supports WLS-VE on any platform that runs VMWare ESX Server 3.0 or higher. For information about the platforms that ESX Server supports, see the VMWare Compatibility Guides for VMWare ESX Server 3.0.

- VMWare ESX Server requires you to install at least one instance of VMware Virtual Center. Because VMware Virtual Center is supported only on Microsoft Windows, your environment must include at least one Windows machine.
- WLS-VE requires network attached storage that uses the NFS file system.

For more information about environment requirements, see Verifying That Your Environment Supports WLS-VE in the WLS-VE Installation and Configuration Guide.

## Recommended Topology

While the combinations of hardware and software in data center environments can vary widely to support different business needs, BEA recommends the following general principles for the network topology of your production environments:

- Install the BEA Home directory and WLS-VE product directory on an NFS server. These directories contain the BEA license file along with software that you need to run the BEA configuration wizard and start-up utilities. These are also the directories into which you install WLS-VE maintenance packs as they become available.
- Install the WLS-VE ISO image on the local disk of each hypervisor's host machine.
- Create a WebLogic Server cluster of managed servers.
- To maximize use of computing power on available machinery, run multiple managed servers on a single machine.
- To ensure high availability, run at least one managed server on a separate physical machine.
- The Administration Server can run on any machine.
Figure 4 Recommended Topology

Configuring web servers and load balancers for WLS-VE is no different from WebLogic Server—when you configure a virtual machine, you assign it an IP address. Then you configure the web server and load balancer to listen for the IP addresses that you have assigned to the VMs in your cluster.

## Licensing WLS-VE

BEA licenses the number of WLS-VE instances that you can run concurrently in your organization. Unlike WebLogic Server licensing, WLS-VE licensing neither restricts the IP address nor limits the number of CPUs of the host machine. For example, if you purchase a license for a single instance of WLS-VE, you can run a WLS Administration Server and deploy your applications onto the Administration Server. You can run this WLS-VE instance on a machine with any IP address and with any number of CPUs. You can shut down this instance and restart it on another machine with a different IP address and a different number of CPUs. If you purchase a license for 10 instances, you can run a WLS Administration Server and up to nine managed servers concurrently.

When you first install WLS-VE, the installation includes an evaluation license that grants the ability to run up to five instances of WLS-VE concurrently for up to 60 days.

## Downloading an Evaluation Copy

You can download WLS-VE from the BEA web site at http://commerce.bea.com.

If you prefer to install from a DVD, contact a BEA sales representative.