This configurable MOM/EM extension allows customers to assess their license compliance for per-agent licensing.
APM Enterprise Manager 9.x, 10.x
APM Agent 9.x, 10.x
lease follow the following steps to configure the tool on a MOM or standalone EM:
The tool provides two different counts, for Java Agents and .NET agents. It produces a licenseable count for each group under the node:
- The attached file Agent_Based_License_Checker_Tool.zip contains 2 files: com.wily.swat.supportability.licensing_9.1.0.jar & supportability.licensing.properties
- Add the extension jar to the ‘<EM Install Directory>/product/enterprisemanager/plugins' directory: com.wily.swat.supportability.licensing_9.1.0.jar
- Add the configuration file to the '<EM Install Directory>/config' directory: supportability.licensing.properties
- Restart the MOM/EM
SuperDomain*|Custom Metric Host (Virtual)|Custom Metric Process (Virtual)|Custom Metric Agent (Virtual)|Enterprise Manager|Licensing
The configuration of the Java Agents is:
- Count agents that have the metric "Java Version"
- Discard those that have any "EPA" metrics
- Discard those that have "JMX" or "EPA" in the full agent process name.
The configuration of the .NET agent is:
- Count agents that have the metric ".NET Version"
- Discard those that have "Perfmon" metrics (this will wrongly remove older .NET agents that have a perfmon folder). NOTE: this option is currently disabled – see comments in file supportability.licensing.properties
- Discard those that have "Perfmon" in the full agent process Name.
Example shown below with 1 .NET Agent, 1 standalone Web Server Java Agent and 3 Java Agents:
Licenseable Count for .NET Agent shows a value of 1 for the 1 .NET Agent
Licenseable Count for Java Agent shows a value 4 for the 1 Web Server Agent + 3 Java Agents
Credit to Ki Alam (CA APM Engineering Services) for the development of this tool
Please note that the tool is not officially supported and is only intended to estimate license counts. The tool and its methodology are not incorporated into contracts and are not intended to be used as strict measures of license usage. The determination of exactly how things should be counted are based on the customer’s contract and terms (not based on this tool).