Deployment configurations | Deployments |
Proxied
Virtualization architectures that require an HP thin client to access their virtual desktop via a proxy service provided by a connection broker (such as VMware View Manager) must have an HP Velocity server installed on the connection broker.
In Figure 4, thin clients A and B are connected to their virtual desktops via the connection broker. An HP Velocity server is installed on the connection broker. This results in flows that are protected by HP Velocity between the thin clients and the connection broker.
Figure 4. Example of a proxied deployment
| Client Side | |
Client | Original | HP |
Original | ||
IP packets | Velocity | |
application | IP packets | Client |
Thin Client A |
|
| Client Side | |
Client | Original | HP |
Velocity | ||
application | IP packets | Client |
Thin Client B |
|
Protected flows between thin client and connection broker
| Unmanaged | Connection | |
| Broker | ||
| network | ||
|
| HP | |
|
|
| |
Firewalls |
|
| Velocity |
Routers |
| Server | |
|
| ||
|
|
|
|
Server Side | |
Virtual | Application |
desktop | |
A |
|
Virtual | Application |
desktop | |
B |
|
NOTE: Additional configuration is not required after the HP Velocity server is installed on the connection broker.
HP Velocity Server Side Deployment Guide | 13 |