WebSphere® Message Broker Hypervisor Edition is a self-contained virtual machine image that contains a guest operating system and WebSphere Message Broker. Use Hypervisor Edition to create, deploy, and manage WebSphere Message Broker environments and applications by using a computer, which is known as a hypervisor, that hosts a virtual system.
You can use hypervisors to divide the physical resources of a server between multiple instances of an operating system, so that each can run securely on the same computer, increasing the utilization of the server. A hypervisor manages the state of virtual machines; including processors, memory, and other resources, as well as allocating these resources among the virtual machines. Two hypervisors are supported for use with WebSphere Message Broker; VMware ESXi for RHEL Linux on x86-64 and PowerVM® for AIX® on POWER® systems.
Clouds are composed of one or more virtual systems. Virtual systems are composed of one or more virtual machine images that each contains an operating system and any number of applications.
Clouds contain one or more pieces of hardware (physical servers). A hypervisor controls each piece of hardware or a collection of hardware. The following diagram shows a cloud that contains several physical servers. Each server has a hypervisor that manages multiple virtual machines. The cloud in the diagram also contains a virtual system that consists of three virtual machines. In the diagram, all of the virtual machines are running on the same physical server, but it is possible for a virtual system to have virtual machines running on different physical servers in the cloud.
IBM® Workload Deployer and IBM PureApplication® System are hardware appliances that provide access to IBM middleware virtual images and patterns to easily, quickly and repeatedly create application environments that can be securely deployed and managed in a private cloud.
Before you use WebSphere Message Broker Hypervisor Edition, ensure that you understand the terminology and concepts it shares with your IBM Hardware Appliances. For more information, see IBM Workload Deployer Information Center and IBM PureApplication System Information Center.
If you are using a hypervisor virtual machine image with IBM Hardware Appliances, the virtual systems are deployments of patterns; each hypervisor virtual machine image is configured as one part of a pattern, with a part representing a single virtual machine.
If you are using the hypervisor virtual machine image without the IBM Hardware Appliances, you must configure and deploy the hypervisor virtual machine image manually, by means of VMware ESXi for Linux on x86-64, or mksysb image for AIX on POWER systems.
The following table lists the supported combinations of operating systems and virtual machine images:
Operating System | Virtual Machine Image | Information |
---|---|---|
RHEL Linux on x86-64 | IBM Workload Deployer | See Using WebSphere Message Broker Hypervisor Edition with IBM Workload Deployer for Linux on x86-64 |
IBM PureApplication System | See Using WebSphere Message Broker Hypervisor Edition with IBM PureApplication System for Linux on x86-64 | |
VMware ESXi | See Using WebSphere Message Broker Hypervisor Edition with VMware for Linux on x86-64 | |
AIX on POWER systems | IBM Workload Deployer | See Using WebSphere Message Broker Hypervisor Edition with IBM Workload Deployer for AIX on POWER |
IBM PureApplication System | See Using WebSphere Message Broker Hypervisor Edition with IBM PureApplication System for AIX on POWER | |
mksysb image | See Using WebSphere Message Broker Hypervisor Edition mksysb image for AIX on POWER systems |