6.0

Sharing Key Data in the Global Data Layer
View Connection Server instances in a pod federation use the Global Data Layer to share key data. Shared
data includes information about the pod federation topology, user and group entitlements, policies, and
other Cloud Pod Architecture configuration information.
In a Cloud Pod Architecture environment, shared data is replicated on every View Connection Server
instance in a pod federation. Entitlement and topology configuration information stored in the Global Data
Layer determines where and how desktops are allocated across the pod federation.
View sets up the Global Data Layer on each View Connection Server instance in a pod federation when you
initialize the Cloud Pod Architecture feature.
Sending Messages Between Pods
View Connection Server instances communicate in a Cloud Pod Architecture environment by using an
interpod communication protocol called the View InterPod API (VIPA).
View Connection Server instances use the VIPA interpod communication channel to launch new desktops,
find existing desktops, and share health status data and other information. View configures the VIPA
interpod communications channel when you initialize the Cloud Pod Architecture feature.
Configuring and Managing a Cloud Pod Architecture Environment
You use the lmvutil command line tool to configure and manage a Cloud Pod Architecture environment.
lmvutil is installed as part of the View installation. You can use View Administrator to view pod health and
desktop session information.
Cloud Pod Architecture Limitations
The Cloud Pod Architecture feature has certain limitations.
n
This release does not support using the HTML Access feature. With HTML Access, end users can use a
Web browser to connect to remote desktops and are not required to install any client software on their
local systems.
n
This release does not support using remote Windows-based applications hosted on a Microsoft RDS
host.
Administering View Cloud Pod Architecture
8 VMware, Inc.