HP Anyware Components

HP Anyware deployments are built from several distinct components that all work together. This page introduces the most common components you'll need to understand.

What is PCoIP Technology?

The PCoIP protocol provides remote desktop access to physical or virtualized computers, enabling fully interactive, visually seamless, and secure computing anywhere as a progressive alternative to a local deployment model.

Supported Xencelabs Pen Displays

Xencelabs Pen Displays are supported in the locally terminated mode, where peripheral data is processed locally at the Anyware Client. It is also supported in the bridged mode, where peripheral data is sent to the desktop for processing.

Support is available when a connection is initiated from a Windows Client to a Windows Graphics or Standard agent.

The following table contains a brief description of the header files included in the Anyware Client SDK for Windows:

Windows Build Procedure

Wacom Tablet Support

The Session Client SDK for Windows supports Wacom tablets in two configurations: bridged, where peripheral data is sent to the desktop for processing, and locally terminated, where peripheral data is processed locally at the Anyware Client.

The Collaboration Broker Client Example

The SDK package comes with a sample command line pre-session client called the Collaboration Broker Client Example, which calls the included broker client libraries and enables you to join a PCoIP collaboration session. The Collaboration Broker Client API Example demonstrates the success path for joining a PCoIP collaboration session.

The Broker Client Example

The SDK package comes with a sample command line pre-session client called the Broker Client example, which calls the included broker client libraries and establishes a PCoIP connection. The Broker Client API example demonstrates the success path for establishing new PCoIP sessions.

Using the Branding Package

Once you have created the branding package, it can be used by the session client. The pre-session client is responsible for verifying the package and passing it to the session client executable.

To use the branding package: