Example: Setting Up a Basic Cloud Pod Architecture Configuration

<

This example demonstrates how you can use the Cloud Pod Architecture feature to complete a Cloud Pod Architecture configuration.

In this example, a health insurance company has a mobile sales force that operates across two regions, the Central region and the Eastern region. Sales agents use mobile devices to present insurance policy quotes to customers and customers view and sign digital documents.

Rather than store customer data on their mobile devices, sales agents use standardized floating desktops. Access to customer data is kept secure in the health insurance company's datacenters.

The health insurance company has a data center in each region. Occasional capacity problems cause sales agents to look for available desktops in a non-local data center, and WAN latency problems sometimes occur. If sales agents disconnect from desktops but leave their sessions logged in, they must remember which datacenter hosted their sessions to reconnect to their desktops.

To solve these problems, the health insurance company designs a Cloud Pod Architecture topology, initializes the Cloud Pod Architecture feature, joins its existing pods to the pod federation, creates sites for each of its data centers, entitles its sales agents to all of its desktop pools, and implements a single URL.

The Horizon administrator uses Horizon Administrator to create a single global desktop entitlement that entitles all sales agents to all desktops in the sales agent desktop pools across all pods in the pod federation.

The insurance company uses a single URL and employs a DNS service to resolve sales.example to the nearest pod in the nearest data center. With this arrangement, sales agents do not need to remember different URLs for each pod and are always directed to the nearest data center, regardless of where they are located.