The sample Collaboration Broker Client demonstrates how the APIs can be used to customize and control the pre-session and session phases of the Collaboration connection. Invoking the Collaboration Broker Client API is a two-step procedure, where as a first step, the Collaboration Broker Client Example is built.
Invoking the Broker Client API is a two-step procedure, where as a first step, the Broker Client Example is built. The second step consists of running either a prebuilt PCoIP binary, or a prebuilt AWS binary.
Finding the Latest Information
Transferring non-HID USB devices from the client to the host is called bridging. Both the Anyware agent on the host machine and the Anyware client must enable bridging before devices can be transferred. Administrators can globally disable USB bridging support, or enforce device whitelists or blacklists, using GPO variables on the host machine. Clients cannot bridge devices that are disallowed by the agent.
Once you have successfully established a session between a Anyware Software Client and an Anyware host, you can start developing your own Anyware client. To begin, set up your client development environment, as discussed next.
To set up your client development environment:
Before developing your custom client, you should set up a working Anyware system. HP recommends establishing a small proof-of-concept system for custom client testing, consisting of a host machine with an installed Anyware agent.
License Requirement
The following table outlines the system requirements for the Anyware Client SDK for macOS:
HP Anyware's support team may request a support file from your system to help troubleshoot and diagnose PCoIP issues.
Customizable Script
This script can be customized, in the case where the log files are located in a different location the script should be updated appropriately.
To create a support file:
There are two phases in a PCoIP session:
The steps indicated below are used and documented in the bundled sample code. Refer to the code for specific function calls, expected return values and error-handling requirements. The example C++ code can be found in the SDK package located here:
The core library allows an application developer to integrate a PCoIP session directly into an application. The core library facilitates connection to a remote host, decoding PCoIP image data directly into an application supplied frame buffer as well as remoting audio, keyboard and mouse events and supported USB devices.