The Client SDK for Windows does not ship with its own session client binary; it uses the standard Anyware Software Client for Windows binary instead. Therefore, you must first download and install the Anyware client application, and then invoke it from the SDK.
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:
If you need to support more than 20 USB devices, or if you expect your users to control which devices can be bridged, they can be manually added by opening the client’s USB Devices menu and enabling them.
You may not be able to programmatically modify certain session features due to limitations imposed by the operating systems's user interface.
The Client SDK for Windows provides developers tools to create a custom Anyware client with a unique user interface and workflow, or to embed a PCoIP session into another program or solution. Clients built with the SDK can connect to remote desktops using Anyware agents or Remote Workstation Cards.
The SDK is provided as part of HP Anyware by special agreement with HP.
Brokered Session Connection
If you are using a brokered session, this is handled by the broker libraries automatically.
Before you can establish a PCoIP session with a host desktop, gather the following host desktop details:
You can make the installer and uninstaller calls programmatically from your client application. The return and exit codes you should expect are summarized in the following tables:
The following PCoIP session features can be customized:
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 Custom Branding Package Utility. The Custom Branding Package Utility is located in the following location:
bin\TeradiciBrandingPackageUtility.exe
To create a custom branding package: