Applies To:

Show Versions Show Versions

Manual Chapter: Deploying iWorkflow Virtual Edition
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

About VE vCloud Director deployment

To deploy the iWorkflow™ Virtual Edition (VE) system on vCloud Director, you perform these tasks:

  • Verify the host machine requirements.
  • Deploy an iWorkflow™ system as a virtual machine.
  • Deploy a BIG-IP® system.
  • After you have deployed the virtual machines, log in to the iWorkflow VE system and run the Setup utility. Using the Setup utility, you perform basic network configuration tasks, such as assigning VLANs to interfaces.
  • Configure secure communication between the iWorkflow system and the BIG-IP device.

Host machine requirements and recommendations

To successfully deploy and run the iWorkflow™ VE system, the host system must satisfy minimum requirements.

The host system must include these elements:

  • VMware vCloud Director. The Virtual Edition and Supported Hypervisors Matrix, published on the AskF5™ web site, identifies the versions that are supported.
  • VMware ESX or ESXi. The Virtual Edition and Supported Hypervisors Matrix, published on the AskF5™ web site, identifies the versions that are supported.
  • VMware vSphere™ client
  • Connection to a common NTP source (this is especially important for each host in a redundant system configuration)
Important: The hypervisor CPU must meet the following requirements:
  • Use a 64-bit architecture.
  • Have support for virtualization (AMD-V or Intel VT-x) enabled.
  • Support a one-to-one thread-to-defined virtual CPU ratio, or (on single-threading architectures) support at least one core per defined virtual CPU.
  • Intel processors must be from the Core (or newer) workstation or server family of CPUs.

Deploying the iWorkflow VE virtual machine

The first step in deploying iWorkflow™ Virtual Edition (VE) is to download the compressed OVF file to your local system. Next, you can run the Deploy OVF Template wizard from within the vCloud Director vSphere client. Follow the steps in this procedure to create an instance of the iWorkflow system that runs as a virtual machine on the host system.

Important: Do not modify the configuration of the vCloud Director guest environment with settings less powerful than the ones recommended in this document. This includes the settings for the CPU, RAM, and network adapters. Doing so might produce unexpected results.
Note: The following procedures are a suggested guideline. F5 Networks® recommends that you consult vCloud Director documentation for template creation as the steps might differ with your organization's vCloud Director deployment.
  1. In a browser, open the F5 Downloads page (
  2. Download the iWorkflow v2.x/Virtual Edition file package. The file name ends in
    The file package creates a 95GB disk footprint at installation.
  3. Extract the file from the Zip archive.
  4. Start the vCloud Director vSphere web-based client and log in.
  5. Click Catalogs > My Organization's Catalogs and on the vApp Templates tab, click Upload.
  6. Browse for and select the extracted .ovf file, type a name for the template, and click Upload.
  7. Type a name and optional description for the vApp template.
  8. Select a virtual data center and catalog.
  9. Click Upload.
    If you want to track the progress, you can click Launch Uploads and Downloads Progress Window.
  10. Click My Cloud > vApps .
  11. Click Add vApp from Catalog.
    The add vApp from Catalog window opens.
  12. Select My organization's catalogs or Public catalogs from the list, select a vApp template, and click Next.
    You can also enter an optional description for the vApp.
  13. Read and accept the license agreement, and click Next.
    The Name and Location pane opens.
  14. Under Configure Virtual Machines, specify the full name and computer name for the vApp, and configure the network settings.
    1. Select the network for NIC0 from the list of networks.
      This network is used to manage the VE system. The Select IP Assignment – Static settings have no effect, so you should configure IP address for management interface through the console after the VM starts. When using DHCP, you should have a DHCP server on that network.
    2. Select the networks for NIC1, NIC2, and NIC3 if you want additional network interfaces.
      Note: iWorkflow does not require multiple network interfaces.
    3. Click Next.
  15. Configure organizational settings, such as Fence vApp and IP persistence for example, and click Next.
  16. Verify the settings and click Finish to start deployment.

Power on the iWorkflow VE virtual machine

Power on the virtual machine so that you can begin assigning IP addresses.
  1. In the vCloud Director web interface, click My Cloud > vApps .
  2. Select the vApp to power on.
  3. Click Start.
    The virtual machine starts.

There are two default accounts used for initial configuration and setup:

  • The root account provides access locally, or using SSH, or using the F5 Configuration utility. The root account password is default.
  • The admin account provides access through the web interface. The admin account password is admin.

You should change passwords for both accounts before bringing a system into production.

Accessing the iWorkflow VE management user interface

If your network has DHCP, an IP address is automatically assigned to iWorkflow™VE during deployment. You can use this address to access the iWorkflowVE user interface or tmsh command-line utility.

If no IP address was assigned, you can assign one by using the iWorkflowConfiguration utility.

Important: Do not use VMware tools to configure the IP address; the iWorkflow system will not use these changes.
  1. In the vSphere client, click Launch Virtual Machine Console.
    The console screen opens. After a few seconds, a login prompt appears.
  2. At the password prompt, type default.
  3. Type config and press Enter.
    The F5 Management Port Setup screen opens.
  4. Click OK.
  5. If you want DHCP to automatically assign an address for the management port, select Yes. Otherwise, select No and follow the instructions for manually assigning an IP address and netmask for the management port.

You can use a hypervisor generic statement, such as tmsh list sys management-ip to confirm that the management IP address has been properly assigned.

You can now log into the iWorkflow VE user interface, and license and provision iWorkflow VE.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Additional Comments (optional)