Building a Java Estate Inventory Before Renewal

Why Build a Java Inventory Before Renewal at All?

You build a Java inventory before renewal because Oracle's renewal proposal is an opening position, not a measurement of what you owe. Without your own evidence, you are negotiating against Oracle's numbers with nothing to counter them. With a defensible inventory, you can show precisely where Oracle JDK runs, prove the rest of the estate is free OpenJDK, and challenge any inflated Employee Metric count line by line.

A Java estate inventory is a complete, classified record of every Java runtime across your organization — its vendor, version, environment, and the license it was obtained under. The reason it matters so much under the current model is that the Java SE Universal Subscription is priced on total employee headcount, so the central question at renewal is binary: do you run any Oracle JDK that obliges you to subscribe, and if so, for which legal entities? The inventory answers that question with facts.

The cost of skipping this work is real. Across our engagements, enterprises that arrive at renewal with an independent inventory reduce the proposed count by 15–40% compared with those who accept Oracle's figure (Oracle Licensing Experts, 2026). Our Java Licensing service builds this inventory for clients, and the broader method sits inside our Oracle Java Licensing Guide.

How Do You Scan the Whole Java Estate?

You scan the whole estate by discovering every Java runtime everywhere it can hide — not just the production server farm. Java embeds in places teams forget: desktops, VDI golden images, CI/CD agents, container base images, cloud marketplace images, third-party application bundles, and developer laptops. A scan that misses any of these leaves a blind spot that Oracle's LMS team will happily find for you.

Effective discovery combines several sources rather than relying on one. Endpoint management and software inventory tools (SCCM, Jamf, Tanium) catch installed runtimes; filesystem scans for java, release, and java -version output identify embedded JDKs that package managers miss; container registry scans surface JDKs baked into images; and cloud configuration scans catch instances launched from images with bundled Java. Java is frequently embedded inside third-party applications, so application bundle directories must be scanned as carefully as standalone installs.

For cloud-heavy estates, pair this discovery with the counting rules in our companion guide on Java SE cloud counting, which explains how the Employee Metric and legacy Processor models treat cloud instances differently.

How Do You Separate Oracle JDK From OpenJDK?

You separate Oracle JDK from OpenJDK by recording the vendor of every Java binary, because only Oracle JDK in production commercial use creates a subscription liability. OpenJDK distributions — Amazon Corretto, Eclipse Temurin, Microsoft OpenJDK, and Azul Zulu — are free for production use. Two installs can run identical Java code; one costs you a subscription and the other costs nothing, and only the vendor string tells them apart.

Oracle JDK is Oracle's branded Java SE distribution, which requires a Java SE subscription for production commercial deployment. OpenJDK is the open-source upstream project from which Oracle JDK and every free distribution are built. The fastest reliable signal of vendor is the runtime's own output: java -version and the release file name the implementor and build, distinguishing an Oracle build from a Corretto or Temurin build. Record that string verbatim for every host — it is the evidence that a given install is, or is not, Oracle's.

This classification is also what makes a migration decision rational. Once you know exactly how many production hosts run Oracle JDK, you can decide whether to migrate them to OpenJDK and drop the subscription entirely. We cover that decision in depth in our broader Java guidance and in the Java SE Universal Subscription per-employee math, which shows why even a small amount of stray Oracle JDK can oblige a full-headcount subscription.

How Does the Inventory Scope Your Employee Count?

The inventory scopes your employee count by establishing which legal entities actually run Oracle JDK and which corporate entities and contractors fall inside the Employee Metric. Because the subscription is priced on total headcount, the highest-value part of the inventory is often organizational, not technical: which subsidiaries, affiliates, and contractor populations does Oracle want to include, and which can you legitimately exclude?

The Employee Metric counts every employee of the subscribing entity plus contractors performing services for the organization, and typically extends to subsidiaries more than 50% owned. Oracle's renewal team will push for the broadest possible reading of every boundary. A well-built inventory pairs the technical Oracle JDK footprint with a corporate-structure map, so you can argue that an entity running no Oracle JDK should not be swept into the count, and that contractors merely providing a service to you are not "performing services" for you. We define these boundaries precisely in what counts as an "employee" for Java SE.

This scoping is where negotiation leverage is created. When you can demonstrate that Oracle JDK is confined to a defined set of entities, you change the conversation from "license your whole global headcount" to "license the population that actually uses Oracle Java." Combine that evidence with the tactics in our Oracle Negotiation Guide to hold the line at renewal.

How Do You Turn the Inventory Into Audit-Grade Evidence?

You turn the inventory into evidence by producing a per-host record that documents vendor, version, patch level, environment, and download license, plus a reconciliation of corporate entities and contractors against the Employee Metric. Evidence is what distinguishes a negotiating position you can defend from a guess Oracle can dismiss. The record must be reproducible — captured with your own tooling, timestamped, and retained.

Crucially, build this with independent tooling before you let Oracle's scripts touch anything. Oracle's LMS and measurement scripts collect data that becomes the foundation of Oracle's compliance claim; once submitted, that data is hard to walk back. Run your own discovery first, understand your true position, decide on any migration, and only then engage Oracle. If an audit is already underway, our Oracle Audit Defense team reviews script methodology before any output leaves your organization.

1. Per-host record — vendor, version, patch, environment, download license.
2. Migration status — which Oracle JDK hosts are slated for OpenJDK, with target dates.
3. Entity map — which legal entities run Oracle JDK; which are clean.
4. Contractor analysis — who genuinely falls inside the Employee Metric.
5. Assumptions log — every counting decision, documented and defensible.

The payoff is concrete. In the Telecom Java Audit Defense case study, a disciplined inventory and migration record reduced Oracle's claim from $4.2M to $0 — because the evidence proved the production estate had already moved off Oracle JDK.

When Should You Start Before Renewal?

Start at least six months before the renewal date. A defensible Java inventory takes weeks to scan, validate, and reconcile, and any OpenJDK migration you decide to make needs lead time to complete and document before the renewal conversation begins. Leaving it to the final month forces you to negotiate from Oracle's numbers because you have no time to build your own.

A practical timeline runs roughly: months six to five for full discovery and vendor classification; months five to three for entity and contractor scoping plus the migration decision; months three to one to execute any migration and capture evidence; and the final month to finalize your counting position and open the renewal discussion from a documented baseline. This sequencing keeps you in control of both the data and the calendar — the two things Oracle's renewal cycle is designed to take away from you.

Java Inventory Before Renewal: Frequently Asked Questions