BEA Says No OS Necessary With WebLogic Server Virtual Edition
It aims to make SOA more flexible, running in a Java VM directly on top of a VMware hypervisor, without an operating system.
BEA WebLogic Server Virtual Edition aims to make SOA applications more flexible. How? By eliminating the operating system and instead using LiquidVM, a modified JRockit Java virtual machine that runs directly on a hypervisor. This approach promises to simplify VM management while reducing system resource consumption by 25% to 50% compared with running Windows or Linux.
Java competitors IBM and Sun have also heavily embraced virtualization, but they have strong roots in the world of operating systems that they won't abandon. By competing with operating systems, BEA is also going up against Linux vendors, including its partner Red Hat. Microsoft likewise is a big competitor, though BEA plans to support its upcoming hypervisor
LiquidVM will give BEA an important boost--if it can meet its performance claims, especially once extended beyond WebLogic. However, the real benefits will stem from easier VM management, and users will have to wait longer for that. The server is available now, but the management tools aren't due until near the end of the year.
If you think operating systems are becoming entirely too bloated, BEA Systems has a radical solution: ditch them entirely. Its WebLogic Server Virtual Edition, intended for virtualized servers that are part of a service-oriented architecture infrastructure, runs directly on top of VMware, no Windows or Linux necessary.
Losing the operating system has several benefits. Many OS services are already duplicated by Java or the hypervisor, and BEA estimates that cutting the OS can reduce consumption of system resources such as memory and CPU cycles by 25% to 50%. It also simplifies management, as WLS-VE knows it's being virtualized and so can more easily map software processes to the hardware it's running on. Performance can improve, as a complete OS doesn't have to be loaded whenever a virtual machine is started.
Still, though WLS-VE shipped in July, its Liquid Operations Control management system won't be available until December. Performance claims haven't yet been proved and will depend on using hardware with virtualization support baked in--without it, VMware simply takes the place of the OS.
Moreover, WLS-VE supports only 32-bit x86 applications: Though it can run on 64-bit hardware, each VM behaves like a 32-bit machine. And some customers will miss OS features that BEA has cut in the name of efficiency, especially support for local disk drives.
BEA is taking a unique path here. Java VM competitors IBM, Microsoft, and Sun are all retaining their operating systems. Even SOA platform vendors such as SAP that don't make operating systems see little reason to scrap this layer. However, all aim to simplify management of VMs in an SOA. Service-oriented architecture and virtualization belong together, as both aim to increase IT's flexibility: SOA by building apps out of reusable services that can be mashed together in new ways, virtualization by making services less dependent on an underlying computing platform. If a service is reused in an SOA, virtualization should let IT managers quickly, or even automatically, allocate hardware as needed.
BEA's approach to SOA virtualization is aided by the dominance of Java. Because Java apps are designed to be portable across different platforms, they run inside a VM that isolates them from the underlying environment. The server-side Java applications in SOA don't care whether they're on Windows, Solaris, or Linux.
Because a Java VM is concerned entirely with running Java code, it duplicates some higher-level OS functions, such as memory allocation as each Java app runs in its own memory space, but not device drivers or anything that affects hardware. Hypervisors like those from VMware approach virtualization from the opposite direction: They operate underneath the OS, appearing to it as hardware (see diagram, below). To achieve this, a hypervisor must perform many of the same tasks as an OS, duplicating lower-level functions so multiple operating systems can run concurrently.
The result: The OS in a virtualized Java server is squeezed from both sides, using an increasing share of system resources but with relatively little to do.
Though the OS has a reduced role, it's still responsible for several critical functions, including networking, I/O, and file storage. BEA has added these to its JRockit Java VM, producing a Java implementation that can run directly on a hypervisor. BEA also dropped some OS features that it thinks aren't really needed in modern enterprise servers, including the GUI and support for some local devices. The one that users are most likely to miss is storage: Instead of its own hard drive, the server must use network-attached storage; SAN support is planned.
BEA's souped-up version of Java, LiquidVM, can run most JRockit software unmodified. The main exception is anything that uses Java Native Interface, a method for calling functions within the underlying OS, usually Linux. JNI can't be implemented because there's no underlying OS. At present, LiquidVM is available only as part of WLS-VE, but BEA plans to use it as the basis of other products, including its AquaLogic service bus, and may license the technology to other vendors.
LiquidVM is still very much a first-generation product, meaning initial applications likely will be limited. While servers are moving to 64 bits, it currently supports only 32-bit applications, limiting each VM to 3.8 Gbytes of addressable memory space. And because it's designed to take advantage of hardware-assisted virtualization technology in x86 chips, it doesn't support other hardware platforms that JRockit is compatible with, including Itanium.
The only hypervisor that LiquidVM runs on is VMware ESX, though others are planned in response to customer demand. A new version, due in late 2007, will add support for XenSource's implementation of Xen, while the revision after that will support Microsoft's Viridian hypervisor. Running on new hypervisors is simply a matter of testing and support, as all are emulating the same underlying hardware.
LiquidVM's most direct competitor is Linux, increasingly promoted by BEA competitors IBM and Sun as a platform for Java. Neither plans to abandon the OS, though both are developing management tools that aim to simplify virtualization in an SOA.
Microsoft is following much the same strategy, though based on .Net and Windows. If BEA enters the virtual appliance market, it will face more competition from Linux, whose open source nature means vendors can already discard components they don't need.
5 Top Federal Initiatives For 2015As InformationWeek Government readers were busy firming up their fiscal year 2015 budgets, we asked them to rate more than 30 IT initiatives in terms of importance and current leadership focus. No surprise, among more than 30 options, security is No. 1. After that, things get less predictable.