Hi AmilaK,
Licensing is based per Asset, you would only require one license for the asset itself and no additional licenses for the applications or sessions running on the asset.
Regards,
Donnie
@droache Thanks for quick response.If we add multiple AD integrated applications (RDS) & mapping manage accounts using directory service (domain accounts to applications).In this scenario license count is one right ?
Further ,Where we can track the license usage,In all assets page or all manage systems ?
Regards,
Amila
@AmilaK That is correct, in that scenario the license count would be one. The best place to track the license usage is the Assets page.
Regards,
Donnie
@droache However if we don’t create assets in asset page & manually create manage systems without creating assets then how the BT licensing servers track it ?
Further In one database server if we have multiple database instances ,How many licenses we need.
Hi @AmilaK I clarified this internally. I misspoke earlier when I said the licensing was Asset based, it is technically asset based, however it is based on the Managed Systems not the Assets. I apologize for the confusion.
So in the scenario where you have multiple databases on a single system, that would require a license for each database instance that is onboarded because each database is a separate managed system. For the scenario where you have a SSH connection to the OS, a web-based session to the application, and a desktop-based session to the database for the same virtual machine with the same IP address, this would consume 2 licenses (one for the SSH managed system, one for the database, and none for the application because this is not a separate managed system). In order to use an application, the system needs to be onboarded first so this would require a license, but you wouldn’t need an additional license for the application itself.
To get an accurate license count use the Managed Systems grid instead of the Assets grid.
Regards,
Donnie
@droache Thank you for the information.