SOLUTIONS ARE PROVIDED ON AN "AS IS" BASIS. NEITHER FLEXERA NOR ITS SUPPLIERS MAKE ANY WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. LICENSEE MAY HAVE OTHER STATUTORY RIGHTS. HOWEVER, TO THE FULL EXTENT PERMITTED BY LAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, WILL BE LIMITED TO THE SHORTER OF (I) THE STATUTORILY REQUIRED PERIOD OR (II) THIRTY (30) DAYS FROM LICENSEE’S ACCEPTANCE OF THE AGREEMENT.
Citrix consumption is often related to metrics that cannot be managed by ITAM (concurrent users, named users). The Citrix Console provides all relevant data about license consumption by Citrix server.
Being able to aggregate the consumption data across Citrix servers brings visibility and is worth an integration. A Citrix API (Get-LicInventory) exposes the Console data. Please note that the concurrent consumption data exposed is not the peak (over e period) but the current concurrent consumption at the time the API is called.
The integration works in two steps:
The implementer is expected to manage the scheduling of the Citrix data collection, the csv files transfer and renaming / archiving. Every week for the next allocations, each Citrix Server’s consumption data should be added to a unique file that will contain all allocations to perform.
The PowerShell below needs to be run from a beacon.
Each script will query one Citrix Server. All results should be appended to the same file.
The weekly processing of the allocation data should take the csv file, process it and rename / archive it so that the next PowerShell data collection re-creates a new file.
A variant of the implementation is to run multiple time (Every 30 minutes?) the API calls, feed the csv file with redundant measurements and extract the data with the (Max) of each Product / Server / Metric. Thus, concurrent usage license will have the peak of weekly consumption allocated.
The PowerShell code is embedded in the Word document attached to this article
The Business Adapter Studio reads the CSV generated by the PowerShell and requires a SQL step to
This SQL step could be performed in a SQL staging database if the Business Adapter Studio has no direct connection to the database (ITAM Cloud).
The next steps do the following (that can be tuned):
(Files are embedded in the Word Document attached to this article).
Use this BAS mapping xml file.
It reads a CSV file that has the format of the sample below.
The steps of the integration are visible below.
Notice the SQL Server step the performs the consumption aggregation.
Notice the use of the data transformation feature to align the license names (as reported by the concatenated Localized License Product Name and License Model) and the actual license created.
Finally, notice the update rule that will lead into allocations for licenses in scope of the import matching exactly the ones in the csv file.
Aug 30, 2023 10:16 AM - edited Aug 30, 2023 10:17 AM