White paper ii · Oracle

Java SE Universal Subscription, and the Employee metric.

The 2023 pricing change moved Oracle Java SE off the Named-User Plus and Processor metrics onto a single Employee metric that counts every employee, contractor and consultant. Twenty-two pages on the metric reading, the deployment count, the OpenJDK transition case and the BATNA posture at renewal.

FormatWhite paper, gated
Pages22
AudienceCIO, CTO, Procurement, SAM
PublishedApril 2025
UpdatedApril 2026

A senior Admodum advisor will follow up with the requesting executive to confirm receipt and offer a private read of the document. No marketing list. No third-party distribution. The paper is the deliverable.

Contents

Inside the 22 pages.

i.
The 2023 pricing change
The move from Named-User Plus and Processor to the Employee metric, the commercial logic behind it and what changed for the buyer.
ii.
Reading the Employee metric
Employees, contractors, agents, outsourcers and consultants. What counts. What does not. Where the metric definition leaves room.
iii.
Deployment evidence
Where Oracle Java is actually deployed in the estate, how it got there, the Java version reading and the support-version boundary.
iv.
The OpenJDK transition case
Amazon Corretto, Microsoft Build of OpenJDK, Eclipse Temurin, Red Hat OpenJDK and Azul. The migration path, the operational risk and the residual Java SE need.
v.
The BATNA posture at renewal
The OpenJDK alternative, the residual Oracle Java footprint, the Employee metric anchor and the renewal-window posture the buyer takes.
vi.
The compliance posture
Audit notification protocol, scope contestation, evidence boundary and the closing letter under the new Employee metric.
vii.
Common failure modes
Where Java SE buyers over-pay: contractor inclusion errors, residual deployment after OpenJDK migration, support-version drift.
viii.
Reading list and references
Companion papers on Oracle ULA certification, LMS audit defence and OCI commitment design.
Excerpt · Section II

The Employee metric is not a deployment metric.

The Employee metric counts a population. The population is the count of full-time, part-time, temporary employees and the count of agents, contractors and consultants who support the operation of the business. The deployment of Java SE inside the estate is not the measurement; the count of people who could, by virtue of their employment, touch a Java SE-enabled system is the measurement. The reading flattens the buyer's deployment posture into a single number that is largely insensitive to the deployment-reduction work the buyer might otherwise undertake.

The Employee metric closes the gap Oracle had under the old Named-User Plus and Processor metrics. The buyer cannot license under the new construct. The buyer can only choose to renew or to exit.

The commercial implication is binary. The buyer who runs even a residual Oracle Java SE deployment after the metric change is liable for the full Employee count at the new tier price. The buyer who migrates to a supported OpenJDK distribution can exit Oracle Java SE entirely, and pay zero. The buyer who runs a hybrid posture, with some workloads on Oracle Java and some on OpenJDK, is liable at the full Employee count until the Oracle Java deployment is zero.

The paper covers the methodology Admodum applies to the Employee metric reading, the deployment inventory, the OpenJDK transition case and the renewal posture. The methodology is the same one that has unwound forty-one Java SE Universal Subscription renewals across the firm's engagement history.

Request the white paper

Request the 22-page paper.

Corporate email only. The paper is sent by a senior Admodum advisor. No marketing list, no third-party distribution. Submission confirms you have read the independence statement at the foot of this page.

Please enter a corporate email address. Personal addresses (gmail, hotmail, outlook, yahoo, icloud and similar) are not accepted.
Corporate email required · No marketing list · Reply within one business day
Companion papers

Read alongside.

All 30 white papers →
Paper i · ULA
The Oracle ULA at the certification window
Schedule A reconciliation, the eighteen-month preparation cycle, the partitioning defence, exit options at end of term and the closing letter.
Request →
 Paper iii · LMS audit defence
LMS audit defence playbook
Notification response, scope contestation, evidence-gathering protocol, deployment metric verification, virtualisation and partitioning treatment, settlement negotiation and the closing letter.
Request →
 Paper iv · OCI
OCI commitment design
Universal Credits, Annual Universal Credits, BYOL accounting, commitment ramp design, and the reconciliation against Database workload migration plans.
Request →
Independence
Admodum is not a partner, reseller, or affiliate of Oracle, or of any other software vendor. No reseller margin, no referral commission, no LMS audit subcontract. The buyer is the only client.
Software licensing white paper

Bring an advisor to the Java SE renewal.

The Admodum Oracle practice runs Java SE renewals inside the Renewal Programme and audit work inside the Audit Defence Programme. Engagements run as fixed fee, contingency or annual retainer.

Speak with a Senior Advisor Oracle practice