Method and system for configuration management database software license compliance
View Patent ↗A software license engine allows an enterprise to model software license contracts and evaluate deployment of software for compliance with the software license contracts. Deployment of software products in the enterprise is modeled in a configuration management database. The software license engine maintains a license database for connecting software license contracts with software deployment modeled by the configuration management database. Users of the software license engine may use license types that are predefined in the software license engine or may define custom license types. The software license engine may indicate compliance or non-compliance with the software license contracts.
1. A computer-implemented method, comprising:
modeling deployment of a software product and a software license contract for the software product;
storing a first model of the modeled deployment of the software product in a configuration management database (CMDB) by storing information related to the software product as a first configuration item in the CMDB and by storing information related to the software license contract as a second configuration item in the CMDB;
storing a second model of the modeled software license contract for the software product in a license database by generating a license certificate corresponding to the software license contract and storing the license certificate in the license database; and
evaluating the deployment of the software product for compliance with the software license contract, comprising:
connecting and comparing the first model and the second model by comparing the first configuration item with the license certificate and connecting the license certificate with the second configuration item responsive to comparing the first configuration item with the license certificate; and
generating an exception indication if the act of comparing the first model and the second model indicates non-compliance with the software license contract.
2. The method of claim 1 , wherein the act of storing a first model comprises:
storing a third configuration item in the CMDB modeling at least a portion of an organizational structure;
storing a fourth configuration item in the CMDB modeling a hardware element on which the software product is deployed.
3. The method of claim 2 , wherein the act of connecting the first model and the second model comprises:
comparing the third configuration item with the license certificate; and
comparing the fourth configuration item with the license certificate.
4. The method of claim 2 , wherein the act of connecting the first model and the second model comprises:
comparing one or more of the third configuration item, the fourth configuration item, and the first configuration item with the license certificate; and
connecting the license certificate with the second configuration item responsive to the act of comparing one or more of the third configuration item, the fourth configuration item, and the first configuration item with the license certificate.
5. The method of claim 1 , wherein the act of evaluating is performed on demand.
6. The method of claim 1 , wherein the act of evaluating is performed automatically responsive to a change in the CMDB.
7. The method of claim 1 , wherein the act of connecting the first model and the second model comprises:
generating an exception indication if the first model cannot be connected to the second model.
8. The method of claim 1 , wherein the act of connecting the first model and the second model comprises:
generating an exception indication if the first model can be connected to a plurality of models in the license database.
9. The method of claim 1 , further comprising:
outputting a result of the act of evaluating compliance from a license engine computer.
10. The method of claim 1 , wherein the act of evaluating compliance further comprises:
indicating a suggested action for achieving compliance if the act of comparing the first model and the second model indicates non-compliance with the software license contract.
11. The method of claim 1 , further comprising:
generating the second model, comprising:
receiving a selection of a license type corresponding to the software license contract; and receiving license contract data corresponding to the selected license type.
12. The method of claim 11 , wherein the act of generating the second model further comprises:
providing a plurality of predetermined license types.
13. The method of claim 11 , wherein the act of generating the second model further comprises:
allowing a user to define a custom license type.
14. The method of claim 1 , wherein the act of storing a second model comprises:
generating a first license certificate corresponding to the software license contract;
generating a second license certificate corresponding to the software license contract;
generating a master license certificate, grouping the first license certificate and the second license certificate; and
storing the master license certificate, the first license certificate, and the second license certificate in the license database, and wherein the act of comparing the first model and the second model comprises:
comparing the master license certificate with the first model, comprising:
comparing the first license certificate with a first portion of the first model; and
comparing the second license certificate with a second portion of the first model.
15. The method of claim 14 , wherein the act of generating an exception indication comprises:
generating a first exception indication corresponding to the first license certificate if the act of comparing the first license certificate indicates non-compliance with the software license contract;
generating a second exception indication corresponding to the second license certificate if the act of comparing the second license certificate indicates non-compliance with the software license contract; and
generating an exception indication corresponding to the master license certificate responsive to the generation of either the first exception indication or the second exception indication.
16. A system, comprising:
a server computer, comprising:
a processor;
a configuration database, coupled to the processor;
a license database, coupled to the processor; and
a program store, coupled to the processor, on which is stored instructions for the processor, wherein the instructions cause the processor to perform the method of claim 1 .
17. The system of claim 16 , wherein the server computer further comprises:
a database, comprising the configuration database and the license database.
18. The system of claim 16 , further comprising:
a client computer, adapted to communicate with the server computer, wherein the client computer requests the processor to execute the instructions that cause the server processor to perform the method of claim 1 .
19. A non-transitory computer readable medium with instructions for a programmable control device stored thereon wherein the instructions cause the programmable control device to perform the method of claim 1 .
20. A networked computer system comprising:
a plurality of computers on which software products are deployed; and
one or more configuration management database computers, communicatively coupled to the plurality of computers, programmed to perform the method of claim 1 .