Administering View Cloud Pod Architecture

2 Connect to any View Connection Server instance in the pod federation by using the credentials of a user
in one of your new global entitlements.
After you connect to the View Connection Server instance, the global entitlement name appears in the
list of available desktops and applications.
3 Select the global entitlement and connect to a desktop or application.
The desktop or application starts successfully. Which desktop or application starts depends on the
individual configuration of the global entitlement, pods, and desktop and application pools. The Cloud Pod
Architecture feature attempts to allocate a desktop or application from the pod to which you are connected.
What to do next
If the global entitlement does not appear when you connect to the View Connection Server instance, use
View Administrator to verify that the entitlement is configured correctly. If the global entitlement appears
but a desktop or application does not start, all desktop or application pools might be fully assigned to other
users.
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 View 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 View
URL.
1 Designing the Example Topology on page 23
The insurance company designs a Cloud Pod Architecture topology that includes a site for each
region.
2 Initializing the Example Configuration on page 23
To initialize the Cloud Pod Architecture feature, the View administrator logs in to the View
Administrator user interface for a View Connection Server instance in East Pod 1, selects View
Configuration > Cloud Pod Architecture, and clicks Initialize the Cloud Pod Architecture feature.
3 Joining Pods in the Example Configuration on page 24
The View administrator uses View Administrator to join Central Pod 1 and Central Pod 2 to the pod
federation.
4 Creating Sites in the Example Configuration on page 24
The View administrator uses View Administrator to create a site for the Eastern and Central
datacenters and adds pods to those sites.
Administering View Cloud Pod Architecture
22 VMware, Inc.