Architecture
BMC PATROL for Citrix XenApp and XenDesktop enables you to monitor the Citrix Site environment and resources. It also enables you to determine how to effectively use these resources. A typical architecture for BMC PATROL for Citrix XenApp is as follows:
Data collection details
- The KM launches a .NET client process (BTK.exe – .NET WinRM Client) on the PATROL Agent server.
- This .NET process establishes a WinRM session with the user configured Delivery Controller, through PowerShell remoting and fetches inventory data, like, the Site name, additional Delivery Controller details, Delivery Groups, Machines, Catalogs and Published Applications.
- This data is then populated in the PATROL and BPPM.
- After all the Delivery Controllers are discovered, the KM connects to each of these Controllers to collect their performance metrics.
BMC PATROL for Citrix XenApp collector details
The following table lists different BMC PATROL for Citrix XenApp collectors and explains how they work:
Collectors (Collection interval) | Explanation |
|---|---|
btkConsumer | Launches the powershell process (BTK.exe – .NET WinRM Client) and reads all the data coming from this process |
btkInventory | Discovers all the components in the Site and sets their configuration parameters |
btkPerformance | Collects performance data of the Delivery Controllers |
btkStatistics | Collects data for all session parameters and for the running instance parameter of Citrix Application |
btkLicensing | Collects licensing information from the license server |