WebSphere Network Deployment versus Base edition costs.

Two editions, two cost bases

WebSphere Application Server ships in more than one edition, and the two that matter most under audit are the Base edition, intended for single server application hosting, and Network Deployment, which adds clustering, centralized management through a deployment manager, and the high availability and workload management features that come with running a managed cell. Both are licensed on processor value units, the core-based metric where PVU per core is multiplied by the cores allocated to the software. The difference is the PVU rate: Network Deployment is priced higher per core because of the capabilities it adds. The same hardware therefore produces a very different number depending on which edition is counted against it.

How the edition drives a finding

Because the rate differs, edition classification is a lever an audit can pull, intentionally or by default. The common errors run in one direction more than the other:

• Base counted as Network Deployment. A single server install with no deployment manager and no cell membership counted at the higher Network Deployment rate inflates the PVU figure across every core it runs on.
• Capability assumed from installed binaries. The presence of Network Deployment binaries on a machine does not prove the clustering capability was configured or used, yet discovery can read the binaries as the higher edition.
• Edition drift after a migration. A consolidation or upgrade can leave artifacts that confuse discovery about which edition is actually in service.

Proving the edition you actually run

The reconciliation is about configuration, not file presence. A genuine Network Deployment topology has a deployment manager administering a cell of federated nodes; a Base deployment is a standalone application server with no cell. The evidence lives in the runtime configuration, the cell and node structure, and how the servers are actually administered, not merely in which binaries were installed. Where an audit has assigned the higher edition by default, demonstrating that a deployment is standalone, with no managed cell, moves it to the Base rate and recalculates every core at the lower figure. This is the same kind of methodology challenge that produces the largest reductions: fix the classification once and the correction flows through the whole count rather than a single line.