Brokered Session Connection
If you are using a brokered session, this is handled by the broker libraries automatically.
Before you begin, gather the following host desktop details:
The following PCoIP session features can be customized:
Examples show command-line usage
The layout file format used to customize the session client is an UTF-8 XML text file.
The layout schema is a top-level <pcoip-client-branding/> element with a version
attribute describing the schema version, and containing the required elements
described next:
In order to customize your session client, you must create a client branding package using the HP Custom Branding Package Utility. The HP Custom Branding Package Utility can be found in the following location:
To create a custom branding package:
Local Termination of Wacom tablets provides the best user experience in networks with high latency. However, some features of the tablet may not be fully supported with local termination. A HID Local Termination Blacklist has been added to override the preferred local termination mode.
This section includes instructions for building a custom client application by utilizing the SDK.
You can customize the branding of your custom session client in several ways by creating a client branding package. These customizations affect the user’s experience once they have connected to their PCoIP session. The following elements can be customized in the session client:
Establishing a PCoIP session involves a number of key components, including system actors, PCoIP session phases, and connection brokers as discussed next.
There are at least three components that work together to create a PCoIP session:
PCoIP-compatible brokers are resource managers that authenticate users and dynamically assign authorized host agents to Anyware clients based on the identity of the user. Anyware clients can connect to Anyware agents using a PCoIP-compatible broker, called a brokered connection, or directly, called a non-brokered or direct connection. The broker c