IBM MQ messaging and WebSphere Application Server share a complex license metric history. PVU, VPU, ULA, and container metrics each move differently at audit. The buyer side guide for 2026.
IBM MQ and WebSphere Application Server are two of the most widely deployed IBM middleware products. Both ship with a Processor Value Unit baseline metric and an alternative Virtual Processor Core metric for container deployments. Both can sit inside an Enterprise License Agreement or a Cloud Pak for Integration commitment.
The license metric on each environment determines the audit exposure. The Sub Capacity Reporting Tool (ILMT) is mandatory on virtualised PVU deployments. Container deployments under Cloud Pak for Integration use the VPU metric and a different audit posture.
Read this alongside the IBM license models reference, the IBM knowledge hub, the IBM advisory practice, and the Vendor Shield subscription.
The Processor Value Unit metric is the historical baseline on IBM middleware. Each processor core carries a PVU value depending on the chip family. The customer pays per PVU per year for support and per PVU once for the license.
| Chip family | PVU per core | Notes |
|---|---|---|
| Intel Xeon and AMD EPYC | 70 PVU | Most common today |
| IBM Power 9 and Power 10 | 120 PVU | Premium Power tier |
| IBM z Systems | 120 PVU per IFL | Specialty processors |
| ARM Graviton on AWS | 70 PVU | Cloud equivalent |
The Virtual Processor Core metric replaced PVU on most container based deployments. One VPU equals one virtual processor core inside an OpenShift or Kubernetes container.
| Product | Pricing per VPU per month | Notes |
|---|---|---|
| IBM MQ in Cloud Pak for Integration | $120 to $200 | Volume discount band |
| WebSphere Liberty in Cloud Pak | $15 to $25 | Lightweight runtime |
| App Connect in Cloud Pak | $120 to $200 | Integration platform |
| API Connect in Cloud Pak | $120 to $200 | API management |
| DataPower Gateway in Cloud Pak | $120 to $200 | Edge gateway |
Sub capacity licensing on PVU deployments allows the customer to pay for only the virtualised cores assigned to the IBM workload. Without sub capacity discipline IBM defaults to full capacity on the host.
IBM defaults to the full hypervisor capacity when ILMT is not deployed or the quarterly report cannot be produced. On a typical four host VMware cluster running MQ on twelve assigned cores, the full capacity default counts every core on every host. The exposure jumps from twelve cores to sixty four or ninety six cores.
Cloud Pak for Integration bundles MQ, WebSphere Liberty, App Connect, API Connect, and DataPower into a single VPU based commitment. The bundle rationalises the metric across the integration estate.
IBM audit teams target the virtualised PVU estate without ILMT. The 2024 and 2025 audit waves focused on customers running MQ and WebSphere on VMware clusters without sub capacity discipline.
The buyer side has seven specific levers on an IBM MQ and WebSphere renewal. Each maps to one cost line or one risk line.
| Lever | Cost line | Typical saving | Effort |
|---|---|---|---|
| Sub capacity discipline | PVU count | 40 to 70 percent | Medium |
| Cloud Pak conversion | Per workload cost | 20 to 40 percent | High |
| WebSphere ND to Liberty migration | Per workload cost | 50 to 80 percent | High |
| ULA exit and certification | Annual support fee | 15 to 30 percent | High |
| Multi year tier discount | Discount band | 5 to 10 percent | Low |
| Cap the annual escalator | Annual increase | 2 to 4 percent per year | Low |
| Audit waiver clause | Historical exposure | Variable | High |
IBM middleware licensing rewards the customer that runs ILMT correctly and that picks the right metric for each environment. Sub capacity discipline alone often delivers half the renewal saving. The buyer side response is the quarterly review, not the annual surprise.
The eight step checklist is the buyer side starting position on every IBM MQ and WebSphere renewal.
PVU is the historical Processor Value Unit metric on IBM middleware. Each processor core carries a PVU value depending on the chip family. VPU is the Virtual Processor Core metric used on container deployments. One VPU equals one virtual processor core inside the container. VPU is simpler to count.
The IBM License Metric Tool generates the sub capacity report that allows the customer to pay for only the virtualised cores assigned to the IBM workload. Without ILMT the customer must pay for the full hypervisor capacity. The full capacity default doubles or triples the audit exposure.
Cloud Pak for Integration bundles MQ, WebSphere Liberty, App Connect, API Connect, and DataPower into a single VPU based entitlement. One VPU covers any of the five products on a one for one basis. The bundle is sold on a three year term and delivers a twenty to forty percent saving against per product pricing on integration heavy estates.
Yes. WebSphere Liberty Core lists at around ninety dollars per PVU. WebSphere Application Server Network Deployment lists at around fourteen hundred dollars per PVU. The Liberty migration delivers a fifty to eighty percent saving per workload where the application can be re platformed to run on Liberty instead of ND.
The five common audit triggers are MQ on VMware without ILMT, WebSphere ND on Power LPARs without sub capacity reservation, container deployment without Cloud Pak entitlement, quarterly ILMT reports more than two years old, and cluster expansion without ILMT update. Each indicates the customer is at risk on the full capacity default.
Redress runs the IBM middleware engagement inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. The work covers the ILMT inventory, the metric audit, the Cloud Pak conversion math, and the renewal lever pursuit. Always buyer side, never IBM paid.
Redress runs the engagement inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former IBM commercial executive on the buyer side.
Read the related benchmarking, about us, locations, and contact pages.
A buyer side reference on IBM audit defense. The ILMT discipline, the sub capacity rules, the Cloud Pak conversion math, and the renewal lever set across MQ, WebSphere, and the wider IBM middleware estate.
Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying IBM middleware. No IBM influence. No sales kickback.
Open the white paper in your browser. Corporate email only.
Open the Paper →IBM middleware licensing rewards the customer that runs ILMT correctly and that picks the right metric for each environment. Sub capacity discipline alone often delivers half the renewal saving. The buyer side response is the quarterly review, not the annual surprise.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
MQ and WebSphere licensing reads, ILMT discipline, Cloud Pak conversion math, audit defense positions, and renewal levers across every IBM engagement we run.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
