Skip to content

Home > DIY > Proving Ground Guides

TestDrive, Cloud Provisioning, and Omnissa Connect Architecture

A Proving Ground (PG) is like any other production Omnissa-hosted environment. This guide provides a high-level architectural view of how TestDrive, cloud provisioning, Omnissa Connect, and the services related to each other.

Summary

  • TestDrive is an external broker. It does not host or operate services. It authorizes access to the PG request and initiates provisioning (and decommissioning) of PG tenants by calling Omnissa's proprietary cloud provisioning platform.
  • Omnissa Connect is the access platform and account manager for every Omnissa Connect organization: production, trial, or Proving Ground.
  • Hosted services are the production Omnissa services, e.g., Omnissa platform, all of the Workspace ONE services, and Horizon Cloud that users access through an Omnissa Connect organization.

Architecture Diagram

flowchart TB
    TD["TestDrive<br/>(External Broker)"]
    CPP{{"Cloud provisioning<br/>platform"}}

    subgraph Cloud["Hosted services"]
        Intelligence["Intelligence"]
        UEM["UEM"]
        Access["Access"]
        Hub["Hub Services"]
        Horizon["Horizon Cloud"]
        Intelligence ~~~ UEM ~~~ Access ~~~ Hub ~~~ Horizon
    end

    subgraph OC["Omnissa Connect — Access Platform & Org Manager"]
        Org1["Org 1"]
        Org2["Org 2"]
        Org3["PG Org"]
    end

    TD -- "authorizes PG access & initiates PG services' provisioning" --> CPP
    CPP -- "provisions services" --> Cloud
    CPP -- "triggers OC org creation" --> OC
    OC -- "onboards orgs & manages user access" --> Cloud

    style Org3 stroke-dasharray: 5 5

How to Read the Diagram

  • TestDrive → cloud provisioning platform: TestDrive never touches any hosted Omnissa services. When a Proving Ground is requested (or expires), TestDrive calls the proprietary cloud provisioning platform API to create (or decommission) the underlying Omnissa services.
  • Cloud provisioning platform → hosted services: The cloud provisioning platform is the provisioning API behind all hosted Omnissa services. It's how new tenants come into existence and how entitlements are set. Provisioning the services also triggers the Omnissa Connect organization creation process.
  • Omnissa Connect → hosted services: Once an organization exists, Omnissa Connect is the single access platform and account manager for it—handling sign-in, organization user manamgement, and SSO to all of the Omnissa services attached to an organization.

Why This Matters

TestDrive is a broker, not an operator. After tenants are provisioned by TestDrive, and Omnissa Connect organization onboarding is completed by the user, account management, access, and support for that organization's services all flow through Omnissa Connect or the owning product teams. This is the same boundary described in the Proving Ground Support guide.

Reference