Configuring the WebSphere BPM Hypervisor Edition environment

In this article, you'll learn how to use the platform configuration tool to configure the WebSphere® BPM Hypervisor Edition environment for virtual machines without a WebSphere CloudBurst Appliance.


Jie Zhang (, Software Engineer, IBM

Photo of Jie ZhangJie Zhang is a Software Engineer at the IBM China Development Lab in Beijing, China. She has worked as a WebSphere Process Server developer for over three years. She is currently working on WebSphere Business Process Management Hypervisor Editions.

01 June 2011

Also available in Chinese


Hypervisor editions of WebSphere business process management products provide self-contained virtual machine images that contain guest operating systems, as well as WebSphere products like WebSphere Process Server or WebSphere Business Monitor. You can use these to easily create, deploy, and manage WebSphere Process Server or WebSphere Business Monitor environments and applications using hypervisors.

There are two ways to deploy the Hypervisor Edition images:

  • Load the hypervisor editions of WebSphere BPM products onto the WebSphere CloudBurst Appliance to create, deploy, and manage environments and applications in a cloud using IBM® PowerVM ™, IBM z/VM®, or VMware® hypervisors.
  • Construct hypervisor edition virtual images outside of WebSphere CloudBurst Appliance to deploy the virtual image on a VMware ESX or ESXi hypervisor and configure the virtual machine using the platform configuration tool.

This article describes the second method, using the platform configuration tool to configure the WebSphere BPM Hypervisor Edition environment for virtual machines without a WebSphere CloudBurst Appliance.

Before you start

Before using platform configuration tool, you should understand the following terminology:

  • Platform: A platform is comprised of one or more machines. One of those machines will coordinate the configuration of the machines in the platform.
  • Control machine: The machine that coordinates the configuration of the platform is called a control machine.
  • Component machine: The machine that is not the control machine is called a component machine.

Each platform must have one control machine that handles the overall configuration for the platform. The control machine is used to specify a pattern for the platform, assign a part type to each component machine in the platform, and supply all of the required values for part parameters. Each component machine in the platform is configured as a WebSphere Process Server (or WebSphere Business Monitor) Hypervisor Edition part (for example, the Database part or Basic function control node part. (Refer to Resources for more information on parts.) After configuration is complete, the control machine functions as simply another component in the platform.

Process overview

The task flow for using the image without an appliance is as follows:

  1. Download the appropriate image package from Passport Advantage® and extract the contents to a local machine.
  2. Load the image onto the hypervisor or hypervisors you plan to use.
  3. Complete the configuration for each virtual machine. This includes editing virtual system settings and configuring each virtual machine as one of the parts available in the virtual image. This step actually has two parts. First, you need to power on all virtual machines and do the basic configuration, such as specifying the hostname or IP address. Second, use the control machine to do the central configuration.

Configure your machine as a component machine

The platform configuration tool configures both the component machines and the control machine for a platform. It runs on each machine in your platform and is launched automatically after you finish editing the virtual system settings. To make up a platform, you can select one machine as a control machine and others as component machines. To configure the machine as a component machine, do the following:

  1. Start the platform configuration tool. You will see a welcome screen, after which you are prompted to identify the role of the current machine as shown in Figure 1.
    Figure 1. Select the configuration role
    Select the configuration role

    (See a larger version of Figure 1.)

  2. Select Configure this machine to be a component in the platform, then click Next.
  3. On the Confirm Configuration page, shown in Figure 2, you'll see the configuration role you selected, as well as the host name or IP address of this component machine. Please note the host name or IP address; you'll be asked to provide it when you run the platform configuration tool on the control machine to complete the platform configuration. Click Close to complete the configuration of the component machine.
    Figure 2. Confirm configuration page
    Confirm configuration page

    (See a larger version of Figure 2.)

Configure your machine as a control machine

Now you need to select a machine as the control machine and do the configuration on that machine.

  1. On the Select Configuration Role page, select Configure this machine as control machine (see Figure 1), and click Next.
  2. On the Configure Pattern Components page, shown in Figure 3. Do the following:
    • Select a predefined pattern, such as Scalable Environment, in the Pattern name field.
    • The list of parts that make up this pattern will display in the component machine table. For each component machine, you need enter the machine's host name or IP address, and the part type assign to the machine. The Component connection status will display Connected or Not connected based on the network status. If some of the machines can't get connected after you enter the required values, there may be network problems or the machine may not have not been configured yet. You may need to configure the machine,the click Retry connection to update the connection status.
    • When you click any machine, the Component part properties table displays a list of properties in which you need to enter valid values. For information on the values for part properties, refer to the Resources section.
      Figure 3. Configure pattern components
      Configure pattern components

      (See a larger version of Figure 3.)

    • Click Next and confirm the configuration.
  3. Click Configure to configure the entire platform. Depending on the complexity of your platform, this may take some time. When the configuration is complete, you'll see the configuration results page, as shown in Figure 4.
    Figure 4. Configuration results page
    Configuration results page

    (See a larger version of Figure 4.)

Import or export the custom patterns

Platform configuration tool provides three predefined patterns (see Resources for more information about predefined patterns). If the predefined patterns are not suitable for your topology, you can create your own pattern or import an existing pattern.

Create a new pattern

To create a new pattern, on the Configure Pattern Components page (Figure 3), specify a pattern name in Pattern name field and click Add. You can also use the Remove button to remove any patterns you don't want. For each pattern, add an IP address or host name, assign a part type the component and specify the required parameter values. The platform configuration tool provides rules to validate your pattern. You will see error messages if your pattern is invalid.

Export and import a pattern

If you plan to use a pattern in another configuration, you can export it by clicking Export, and saving the pattern to an XML file. This pattern can then be imported using the Import function.

Dealing with configuration errors

Occasionally, you may see an error like that shown in Figure 5.

Figure 5. Configuration failed
Configuration failed

(See a larger version of Figure 5.)

This error shows that one component machine configuration failed. When this happens, select the component machine by IP address or host name to see the detail log and trace files for the failure. If the failure can be corrected by reconfiguration, click the Close and confirm the configuration.

You should see the configuration status for each component machine, as shown in Figure 6. Make any necessary changes, confirm them, and click Configure to retry the configuration.

Figure 6. Verify configuration
Verify configuration

(See a larger version of Figure 6.)


The WebSphere BPM Hypervisor Edition platform configuration tool makes it easy to quickly configure a virtual system, or platform, without a full cloud environment. With this tool, you an configure the virtual machines that comprise your platform using the predefined patterns provided, or create your own patterns or import existing ones.



developerWorks: Sign in

Required fields are indicated with an asterisk (*).

Need an IBM ID?
Forgot your IBM ID?

Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.


All information submitted is secure.

Dig deeper into Business process management on developerWorks

Zone=Business process management, WebSphere
ArticleTitle=Configuring the WebSphere BPM Hypervisor Edition environment