Finding Java in your environment does not automatically mean you need an Oracle license. In Part 1 of this series, we explored why organizations are reviewing Java licensing again. This article looks at the distribution, use and licensing terms you need to establish before deciding whether Oracle licensing applies.

Finding Java Does Not Automatically Mean Oracle Licensing Applies

Java may exist across application servers, developer environments, endpoints, internal tools and enterprise applications. Finding an installation tells you where Java is present, but you still need to determine whether it is.

Organizations need to determine whether they are using:

• Oracle JDK
• OpenJDK
• A vendor-distributed OpenJDK build
• Oracle Java covered by specific no-cost usage rights

That identification determines which licensing terms need to be examined.

Oracle JDK vs OpenJDK

Oracle JDK is Oracle’s distribution of the Java Development Kit. Whether its use requires a commercial subscription depends on the version deployed, how it is being used, and the licensing terms applicable to that release.

OpenJDK is the open-source implementation of the Java Platform, Standard Edition. A Java installation may therefore be an OpenJDK build rather than Oracle JDK.

However, simply identifying OpenJDK does not complete the assessment.

Different vendors distribute and support OpenJDK builds, with variations in areas such as long-term support, security updates, release schedules, and commercial support.

Organizations therefore need to establish which distribution, provider and version they are running. Those details also help them assess how updates and support are provided.

When Can Oracle Java Be Used Without a Paid Subscription?

Oracle has made certain Java releases available under terms that permit no-cost use in particular circumstances.

Organizations may encounter the Oracle Technology Network License Agreement for Oracle Java SE (OTN) and Oracle’s No-Fee Terms and Conditions (NFTC).

Those no-cost rights do not apply to every release or type of use. Downloading Oracle Java without paying for it does not, by itself, establish that every subsequent use is free. To assess the position, establish which release and update were obtained, when they were obtained, how they are used and which terms apply.

Common Java Licensing Misconceptions

“If Java is installed, we need an Oracle license.”

Not necessarily. The distribution, version, usage, and applicable licensing terms need to be established first.

“We use OpenJDK, so there is nothing else to consider.”

OpenJDK may avoid the need for an Oracle Java subscription, but organizations still need to understand the distribution being used and how support, security updates, and compatibility are managed.

“We downloaded Oracle Java for free, so it is free to use.”

Not necessarily. Oracle’s licensing terms vary between releases and usage scenarios.

“Nothing has changed in our Java environment, so nothing has changed commercially.”

Oracle’s Java licensing terms have evolved over time. An unchanged technical deployment does not necessarily mean the licensing position surrounding it has remained unchanged.

Establish the Facts Before Assessing Exposure

Before attempting to calculate potential Java licensing costs, organizations need a clear picture of what actually exists within their environment.

That means establishing:

• Where Java is deployed
• Which distributions, providers, versions and updates are in use
• Why they are required
• Which applications depend on them
• Which licensing terms apply
• Whether Oracle Java is actually required

This provides the evidence needed to determine whether Oracle licensing obligations exist before moving on to the potential commercial impact.

This Article Is Based on the Java Licensing Playbook

This article draws on the Java distribution, licensing trigger, and usage-right guidance within our Java Licensing Playbook.

The full guide provides a broader framework for assessing Java deployments, understanding licensing exposure, conducting discovery, evaluating strategic options, and strengthening Java governance.

Continue the Series

Once an organization has established whether Oracle Java licensing applies, the next question is how the potential cost is calculated.

Part 3 examines Oracle’s employee-based Java licensing model, what counts toward the employee metric, and why the number of Java installations does not necessarily determine subscription cost.