Video Screencast Help

EM L07: Thinking Outside the Box with Complex Software Licensing

Created: 21 Nov 2012 • Updated: 21 Nov 2012 | 1 comment
Language Translations
LeslieMiller's picture
0 0 Votes
Login to vote

Explore a methodology that can be utilized to extend the out-of-the-box supported software license types in Asset Management Suite.  Create a report that will display how many licenses are in use of software applications that are using Per Processor Licensing, and discuss how this methodology can be extended to Disk Based Licenses.

Comments 1 CommentJump to latest comment

paulhicks's picture

We are hoping to exploit the solution described under Exercise 1 for multiple license models, but thinking about the implications, it appears that we would have to build a report and CMDB rule for each software license, for each model. I'm trying to work out a way of reducing the work and removing the need for SQL expertise, which our users do not have.

The Model Provided: 1 product = 1 Report/CMDB Rule

e.g. the example includes a query with a hardcoded "%SQL 2008 License%" search of the item table.

So if you're coding a report for SQL Server 2008 licensing by a "Per CPU" model, this would require 1 report and 1 CMDB Rule.

Our requirements: Multiple Products for each model = 1 report/CMDB Rule

If you have multiple products that fit the same "per CPU" licensing model and method of obtaining the counts, we could hardcode the SELECT of the subquery for multiple conditions (although the SQL would have to be rearranged slightly I think).

FILTERS: A real bonus would be to enable our users to build their own filters. If you had one FILTER per licensable product that could encapsulate the search rules, could we use the same SQL for 1 report that would feed 1 CMDB rule per license model with all products that fit that model?

This could be extended with filter hierarchies where 1 filter = 1 product, but a parent filter combines a group of similar products (e.g. All Microsoft Per CPU products).


All nice in theory, but I haven't coded a report capable of doing this yet. If anyone has tried this and has a solution I'd love to hear from you, otherwise I'll post something when I have it.

Login to vote