IBM License Metric Tool

IBM License Metric Tool is a free, on-premises system for discovering IBM software and measuring license use. It is best for organizations that run IBM products, particularly those using virtualization and sub-capacity licensing. Its focused audit support is useful, but the setup and record-keeping obligations take real planning.

Overview

The tool scans infrastructure for core-based IBM software, identifies installed versions, and measures required product licenses in full-capacity and virtualization sub-capacity environments. IBM recommends it for full-capacity licensing and requires it for sub-capacity licensing, so it is a practical fit for organizations that need IBM-specific license records rather than a broad inventory of software from many vendors.

Version reporting can help teams manage IBM deployments and identify software relevant to security patching. License utilization thresholds and email notifications provide a way to spot usage approaching or exceeding a threshold; sub-capacity audit reports support compliance work.

Key features

Discovery and compliance

Inventory and measurement are built around IBM products and their license metrics. For sub-capacity compliance, customers must generate audit snapshots every quarter and retain them for at least two years. They must also install and begin using the tool within 90 days of deploying their first eligible sub-capacity product. Those requirements make the reports useful only if teams establish a regular process for setup and retention.

Deployment and integrations

Three installation modes are available: License Metric Tool Lite, License Metric Tool with Ansible, and License Metric Tool with BigFix. BigFix integration and a REST API support connections to external systems, but data must be retrieved through the API rather than directly from the tool’s database. IBM support covers the disconnected scanners and tool server, not the Ansible platform itself.

The tool collects hardware and software data needed to identify IBM software and license metric use. Data is sent externally only when IBM Software Central integration is configured, and then on demand. IBM updates the tool quarterly and advises customers to use the latest version.

Containers and database requirements

It can discover software in Docker and Podman containers under stated scanning conditions. For software running on Kubernetes or Red Hat OpenShift, IBM directs customers to IBM License Service instead.

A Linux server installation requires DB2, included at no charge for use only with this tool. Windows installation requires the customer’s own MS SQL Server instance; MS SQL Server Express is supported for environments under 500 endpoints. These prerequisites affect the infrastructure and database planning needed before rollout.

Pricing

IBM License Metric Tool: free. The plan is free and downloaded from Passport Advantage, while customers supply the hardware and installation services. It suits organizations prepared to run the software on their own infrastructure; the free price does not remove the deployment and compliance work.

Platforms

The listed platforms are API, Linux, self-hosted, web, and Windows. Deployment is on-premises, giving organizations control of the environment while requiring them to provide the hardware and installation services. Database needs differ by server operating system.

Who it's for

Choose it if your organization runs IBM software and needs license measurement, especially when sub-capacity licensing makes IBM’s required tool and audit snapshots part of compliance. It can also help teams track installed versions and utilization thresholds. It is a poor fit for teams seeking general-purpose, cross-vendor asset inventory, or for Kubernetes and OpenShift software discovery.

Pros and cons

• Pros: Free software for IBM license measurement, with full-capacity and sub-capacity coverage.
• Pros: Version reporting, utilization alerts, and sub-capacity audit reports support day-to-day tracking and compliance.
• Pros: Three installation modes, BigFix integration, and a REST API allow different deployment and connection approaches.
• Cons: Customers provide infrastructure and installation services, and must meet a 90-day setup deadline for eligible sub-capacity products.
• Cons: Quarterly snapshots must be retained for two years, adding an ongoing compliance task.
• Cons: Linux requires DB2; Windows requires a customer-provided SQL Server instance.
• Cons: IBM support does not cover the Ansible platform, and Kubernetes or OpenShift discovery points to a separate IBM tool.

Alternatives

For general software asset management comparisons, see Software Asset Management Software.

• LICENSEWARE may suit readers who want a freemium option with a free tier limited to 10 rows per table, or consumption-based PAYG at $1 a month billed one-off.
• LAMUM (License Asset Manager with Usage Monitoring) is an option for readers whose needs fit Parser Lite’s free allowance: up to 3 licenses, 50 parser users, 10,000 parse lines, 30-day data retention, and 1 admin user.
• Labs64 NetLicensing may fit readers seeking a freemium option with a Basic plan at €80 a month, billed annually.
• AWS License Manager is a free alternative with no additional charge for the tool; AWS resources used with it are billed separately.
• Eracent Software License Management is another paid enterprise software license management option, with custom pricing.
• Matrix42 FastViewer is a paid alternative at €540 a year per concurrent session, plus 19% VAT.
• Open iT LicenseAnalyzer is a paid alternative with three functionality levels: Runtime Usage, True Active Usage, and Managed Usage.
• SAP Cloud ALM is a free alternative for eligible support customers, with one tenant per customer number and stated memory and API transfer allowances.

Verdict

IBM License Metric Tool is the right choice for organizations managing IBM software that need license measurement and sub-capacity audit support at no software cost. Its IBM-focused reporting is the main reason to choose it; the customer-owned infrastructure, database prerequisites, setup deadline, and long-term snapshot retention are the main reasons to look elsewhere.