96% & 79%
Of endpoints running / licensable Java
Back to Success Stories
CLIENT SUCCESS STORY · ORACLE JAVA LICENSE ASSESSMENT & RISK REMEDIATION
96% of Endpoints Touched by Java — Just 8 Production Servers Confirmed at Risk
How Rizen's Oracle Java license assessment turned a sprawling, estate-wide compliance question into a small, defensible remediation list — before it could trigger an all-employee licensing exposure.
8 Servers
Confirmed Production Risk, Out of a 6,500-Asset Estate
Pinpointed through full production/non-production and approved-use qualification across the client's entire Java footprint.
16% & 2%
Of servers running / licensable Java
SUPPORTING DETAIL
5,912
Endpoints assessed
593
Servers assessed
14 → 8
Servers with licensable Java, after Dev/UAT exemption
JDK/JRE 8
Most common licensable version
Client Snapshot: A large telecommunications infrastructure company running Java across a sprawling IT estate of nearly 6,000 endpoints and close to 600 servers, with no centralized visibility into which installations were free versus commercially licensable.
The Challenge
Oracle's 2019 shift to an Employee-based Java licensing metric means that even a handful of commercially licensable Java installations, anywhere in an organization, can trigger a requirement to license every employee in the company — regardless of how minor or contained the actual usage is.
With Java deployed on 96% of endpoints across the estate and no clear inventory separating free versions from paid ones, the client faced the risk of an enterprise-wide Java licensing bill triggered by a small number of overlooked installations buried in a 6,500-asset environment.
Our Approach
Full-Estate Version Classification
Rizen ran a full Oracle Java license assessment across 593 servers and 5,912 endpoints, classifying every installation as licensable or free based on version and release date against Oracle's current licensing rules.
Qualification Down to a Defensible List
Each licensable instance was cross-referenced against production/non-production status, approved use alongside other licensed Oracle programs, and third-party application bundling. Development and UAT systems were tested against Oracle's allowed development-use exemption, narrowing the estate-wide footprint down to a precise list of production systems requiring action.
The Results
A sprawling exposure, right-sized to 8 servers. Java was present on 96% of endpoints and licensable versions on 79% — but after full production/non-production and approved-use qualification, only 8 production servers were confirmed to need remediation.
Of the 14 servers running licensable Java, 6 development/UAT systems qualified for Oracle's allowed development-use exemption, cutting the real remediation list in half.
Despite Java's presence on the vast majority of endpoints, licensable versions were confirmed on just 2% of the server estate — turning a company-wide question into a two-percent problem.
Because Oracle's Employee metric can apply company-wide from even minor licensable use, pinpointing and remediating this small footprint heads off exposure that could otherwise scale to the client's entire workforce.
Every Java release found in the estate classified as licensable or non-licensable against Oracle's current rules, giving IT a reference to prevent future drift.
The 4-Step Remediation Path
| Step | Action |
|---|---|
| 1 | Review whether Java is used as part of an already-approved Oracle program (e.g. EBS, Forms & Reports) |
| 2 | Confirm whether Java is bundled by a third-party ISV application — and get contractual confirmation the ISV covers the license |
| 3 | Validate genuine business need before deciding whether a paid Java SE subscription is warranted |
| 4 | Remove licensable Java or upgrade to a No-Fee version, with ongoing monitoring of support windows |
Not sure what's really running in your Java estate?
Rizen Technologies helps enterprises map their real Oracle Java exposure, separate free from licensable use, and build a defensible remediation plan before Oracle comes asking.