Managing IBM License Compliance Across On-Premises and Containerized Environments

Why License Compliance Matters

If your organization runs IBM software across virtual machines and Red Hat OpenShift clusters, tracking what is installed and how much you are using is not straightforward. IBM licensing is based on consumption metrics like Virtual Processor Cores (VPC) and Processor Value Units (PVU). During an audit, IBM expects accurate, timestamped records of that consumption.

Without the right tools, teams end up maintaining manual spreadsheets and taking periodic snapshots. That approach breaks down quickly, especially when containerized workloads spin up and down faster than any manual process can follow.

IBM provides four tools that work together to automate this process across both environments.

IBM License Metric Tool (ILMT): For Virtual Machines

ILMT is the foundation for tracking IBM software on virtual machines. It uses IBM BigFix agents installed on your VMs to collect software inventory. ILMT then matches that inventory against IBM's software catalog to identify installed products and calculate license consumption.

One important capability is sub-capacity licensing. If your IBM software runs on a virtualized server that uses only part of the physical capacity, ILMT reports on that smaller footprint instead of the full physical capacity. This can directly reduce your licensing costs.

ILMT stores data in an IBM Db2 database and provides a web console where you can review inventory, generate compliance reports, and download official audit snapshots. These snapshots are what IBM auditors expect to see.

What ILMT gives you:

• Automatic tracking of IBM software on virtual machines
• Sub-capacity licensing support
• Compliance reports and audit-ready snapshots

IBM License Service: For OpenShift Clusters

Traditional agent-based scanning does not work inside containers. Pods are temporary, they scale up and down constantly, and there is no fixed installation point to monitor. IBM License Service was built specifically for this environment.

It runs as an Operator inside your OpenShift cluster and scans all namespaces every few minutes. It looks for IBM product annotations on pods, which are metadata labels that identify the product name, ID, and metric type. It then adds up the CPU limits across all pods running the same IBM product and records that as VPC consumption.

The service provides REST API endpoints where you can retrieve product lists and download audit snapshots in ZIP format. It does not include a visual dashboard on its own. For that, you need IBM License Service Reporter.

What IBM License Service gives you:

• Automatic detection of IBM containerized software
• VPC calculation based on actual pod resource usage
• API access to license data and audit snapshots

IBM License Service Reporter: One Dashboard for All Clusters

IBM License Service Reporter, or LSR, is the centralized dashboard. It collects license data from one or more OpenShift clusters and displays everything in one place, backed by a PostgreSQL database that stores historical records.

Each IBM License Service instance in your clusters acts as a sender, pushing data to the Reporter over HTTPS. The Reporter aggregates that data and shows you peak VPC consumption per IBM product, compliance status indicators, and downloadable audit snapshots covering your entire OpenShift estate.

One important configuration detail: each cluster must have a unique cluster ID when connecting to the Reporter. If two clusters share the same ID, the Reporter will overwrite data instead of combining it, which leads to inaccurate compliance records.

What IBM License Service Reporter gives you:

• Centralized dashboard across multiple OpenShift clusters
• Historical data storage for trend analysis
• One-click audit snapshot downloads

IBM License Reporter Proxy: Connecting Traditional and Containerized Environments

ILMT tracks IBM software installed on traditional on-premises infrastructure, including virtual machines and physical servers. IBM License Service tracks IBM software running inside containerized environments such as Red Hat OpenShift or any Kubernetes-based cluster. Without a connection between them, you still have two separate compliance views.

The IBM License Reporter Proxy solves this. It is a Python script that runs on the ILMT server. It pulls license data from the ILMT API and pushes it to the IBM License Service Reporter over HTTPS, using token-based authentication.

Configuration is straightforward. You provide the ILMT server address and token, the Reporter receiver endpoint and token, and a data source name that will appear in the Reporter dashboard to label records coming from the VM environment. Once configured, you can schedule it to run daily via cron for automated data delivery.

What the Proxy gives you:

• A bridge between ILMT and IBM License Service Reporter
• Secure data transfer over HTTPS
• VM license data visible inside the same dashboard as OpenShift data

How All Four Components Work Together

The diagram below shows the data flow across the complete solution:

Virtual Machines                          OpenShift Cluster
─────────────────                         ──────────────────
BigFix Agents                             IBM License Service
     │                                          │
     ▼                                          │
  ILMT Server  ──► License Reporter Proxy       │
                          │                     │
                          ▼                     ▼
                   IBM License Service Reporter (LSR)
                   ────────────────────────────────
                   Single Dashboard | Audit Snapshots

ILMT scans virtual machines continuously. The License Reporter Proxy pulls that data from ILMT and forwards it to LSR. At the same time, IBM License Service inside each OpenShift cluster pushes container usage data directly to LSR. LSR brings both data streams together into one dashboard.

The result is a single compliance view covering your entire IBM software estate, with all communication secured using token authentication and HTTPS encryption.

What the Complete Solution Delivers

• One view of IBM license usage across virtual machines and OpenShift
• Automated data collection that removes manual tracking effort
• Continuous monitoring that captures usage over time, not just snapshots
• Audit-ready reports available on demand in the format IBM expects
• Hybrid environment support covering both VMs and containerized workloads
• Secure communication between all components

Conclusion

IBM license compliance across a hybrid environment does not need to be a manual process. ILMT handles virtual machines, IBM License Service handles OpenShift, the License Reporter Proxy connects both, and IBM License Service Reporter brings everything into one place. Each component has a clear role, and together they provide the automated, continuous compliance visibility that holds up during an IBM audit.

Have you implemented ILMT, IBM License Service, or IBM License Reporter in your environment? What challenges did you face, and what worked well for your team? Share your experience in the comments below.