Oracle Products with Java SE Licenses: A Guide for CIOs and CFOs

Oracle Products with Java SE Licenses: A Guide for CIOs and CFOs

Overview: Java SE Licensing in Oracle Products

Oracle’s Java Standard Edition (Java SE) is a core component for many Oracle products. However, the rights to use Java SE can vary widely depending on your Oracle contracts. Some Oracle software includes Java SE licenses (entitlements) as part of the purchase, often with restricted-use rights.

This means you may already have permission to use Java (the JDK/JRE) for specific purposes without a separate Java SE subscription – but only within the scope of the Oracle product in question.

Misinterpreting these entitlements can lead to compliance issues and unexpected costs​. It is therefore crucial for CIOs and CFOs to understand exactly which Oracle products grant Java SE rights, and under what conditions.

Oracle’s standard license agreements (whether the older Oracle License and Services Agreement (OLSA) or the current Oracle Master Agreement (OMA) framework) typically do not explicitly name “Java SE” in every contract.

Instead, Java usage rights are often defined in ancillary documents, such as Oracle’s Licensing Information user manuals or the Oracle Technology Network (OTN) license terms for Java.

Notably, Oracle uses “Schedule A” and “Schedule B” lists to identify approved products that convey Java SE use rights under the Oracle Technology Network (OTN) Java license.

In practical terms, if you own certain Oracle products, you likely have some level of Java SE entitlement bundled. Still, those rights are usually restricted to use with that Oracle product and not full, unlimited Java licenses.

Oracle Schedule A vs. Schedule B Entitlements

Oracle’s OTN Java SE license defines “Oracle Approved Product Use” through two schedules: Schedule A and Schedule B. These schedules list which Oracle products include Java SE for use with those products​.

If Java is used within the confines of these products, it’s considered an approved use (no separate Java license needed for that use).

Below are the products in each schedule, as published by Oracle:

• Schedule A Products (Java SE bundled for specific tools):
  • Oracle SQL Developer – Oracle’s database IDE (includes a Java SE runtime for the tool itself).
  • Oracle Cloud Infrastructure – Oracle Management Agent (MACS Agent) – The OCI on-premises agent (includes Java SE for the agent’s operations)​.
• Schedule B Products (Java SE bundled for enterprise products):
  • Oracle Forms (and any applications that contain Oracle Forms)​ – Forms is a Java-based technology, so its runtime includes Java SE.
  • Oracle E-Business Suite (and applications that contain Oracle E-Business Suite)​ – Oracle’s ERP suite uses Java (for Oracle Forms, web services, etc.), and Java SE is included to support those components.
  • Oracle WebLogic Server client applications​ – Client-side software provided with WebLogic (e.g., web start clients or other Java components) includes Java SE for connecting to the WebLogic Server environment.
  • Oracle Coherence client applications – Client libraries and applications using Oracle Coherence (an in-memory data grid) typically use Java SE for this purpose.
  • Oracle Agile Product Lifecycle Management (Agile PLM) client apps​ – Components of Agile PLM that run on Java are entitled to Java SE.
  • JD Edwards products – Oracle’s JD Edwards ERP software includes Java SE for its operation. (JD Edwards tools run on a Java-based platform.)
  • Oracle AutoVue products – Oracle’s 2D/3D visualization tools include Java SE, which is used for applets and viewers​.
  • Oracle Secure Global Desktop – This remote access software includes Java SE for its client and server functionality.
  • Oracle Demantra products – Oracle’s demand planning tools include Java SE to support their Java-based modules​.

Important: Oracle explicitly states that, aside from the products in these schedules, no other programs include Java SE usage rights under the Oracle Technology Network (OTN) agreement.

In other words, only the products listed above (Schedule A or B) are officially recognized as bundling a Java SE license. Any other use of Oracle Java outside of these products would require a separate license or subscription.

Restricted-Use vs. Full-Use Java SE Licenses

When Java SE is bundled with an Oracle product, it is almost always provided under a restricted-use license, not a full-use license. Restricted-use means you can use Java SE only to run that specific product (and related components), as documented in your license.

You are not allowed to use the included Java for unrelated applications or general-purpose needs. In contrast, a full-use Java SE license (such as a standalone Java SE subscription) permits use of Java for any purpose on a server or PC.

For example, if you have Oracle JD Edwards EnterpriseOne, you can use the Java SE that comes with it solely to run JD Edwards applications.

Oracle’s documentation is explicit: “Oracle Java SE is included with JD Edwards EnterpriseOne products and is intended only for use in conjunction with running JD Edwards… If you use Java SE in any other way or use a different version than that provided, your use of Java SE is subject to the standard Java SE license terms.”​

Similarly, PeopleSoft customers have Java included via PeopleTools, with the license stating that it can only be used to run PeopleSoft applications.

Using it outside of PeopleSoft or upgrading it independently would invoke separate licensing requirements.

Even Oracle’s middleware products impose restrictions. For instance, WebLogic Server Enterprise Edition includes the rights to Java SE Advanced, but only for enabling client applications to access the WebLogic Server​.

This means the WebLogic license allows you to use the included JDK/JRE (and even advanced features like Java Flight Recorder), but only in service of WebLogic Server – e.g., for running WebLogic and the applications deployed on it, or client code that interacts with that WebLogic instance.

It’s not a blanket Java license for anything you want. WebLogic Suite similarly bundles the Java SE Suite (which includes even more features), but restricts it to WebLogic, Coherence, and Oracle Containers for J2EE components within that suite.

None of the Oracle products’ bundled Java SE entitlements grant unlimited, general-purpose usage. They all tie the Java usage to the specific product environment. From a compliance perspective, these are restricted-use Java SE licenses in every case.

CIOs should assume that any Java SE bundled with an Oracle product is intended for use only with that system. The only way to get full, unrestricted Java SE rights is via a separate Java SE license or subscription purchased from Oracle.

One nuance: a few Oracle products historically bundled Java in a way that made the entire Java platform available. (For example, Oracle Coherence includes the full Java SE platform in its installation​.)

However, “full platform” does not mean “full license” – Coherence’s license still restricts Java to running applications within the Coherence data grid environment​. Always check the exact wording of the restricted-use clause for each product.

Finally, note that using Oracle Java under a restricted-use license typically does not grant direct support rights for Java SE itself, such as opening support tickets specifically for Java bugs. You receive support for Java only as it relates to the Oracle product.

For instance, you can file a support request for an issue in E-Business Suite that involves the JRE, but you cannot file a ticket against Java SE in isolation unless you have a separate Java support contract​.

Oracle Products That Include Java SE (No Separate Subscription Required)

The following is a breakdown of major Oracle products – both current and legacy – that grant entitlements to Java SE components (JDK and JRE) as part of their license agreements.

If you own these products, you do not need a separate Java SE subscription to use Java for the product’s intended purpose. We group them by category for clarity:

Middleware and Platform Software

• Oracle WebLogic Server (Standard Edition) – Includes the right to use Java SE (the JDK and JRE) for running WebLogic and its applications. WebLogic Standard Edition users are entitled to the full Java SE platform, including the JDK, JRE, JavaFX, and other components, as needed to support WebLogic. (Usage is limited to WebLogic; you shouldn’t use the WebLogic-supplied Java to run other unrelated servers.)
• Oracle WebLogic Server (Enterprise Edition) – Includes Java SE Advanced, which is Java SE plus commercial features like JRockit Mission Control/Flight Recorder, with usage restricted to WebLogic Server operations. In practice, this means Java is licensed for running WebLogic EE and Java client applications that access WebLogic Server​ , such as Java programs connecting to the WebLogic server. It is not a license to deploy Java for other purposes.
• Oracle WebLogic Suite – Includes Java SE Suite (Java SE Advanced + JRockit Real Time) for use with WebLogic Suite components​. This Java SE Suite entitlement is also restricted; it can only be used with WebLogic Suite, which encompasses WebLogic Server, Oracle Containers for J2EE, Coherence, and more​. WebLogic Suite for Oracle Applications (a special bundle for Oracle E-Business applications) similarly includes Java SE Suite for use with those Oracle Applications.
• Oracle Internet Application Server (Oracle iAS) Enterprise Edition – This older middleware suite, precursor to WebLogic in Oracle’s stack, includes the right to use Java SE for its Java-based components. If you purchased Oracle iAS EE licenses in the past, you were entitled to use Java SE (JDK/JRE) to run the application server and related features.
• Oracle GlassFish Server – Oracle’s Java EE server (now legacy) includes a Java SE license, allowing you to run GlassFish and applications on it. As with WebLogic, the included JDK/JRE is only licensed for use within the GlassFish environment.
• Oracle Coherence (Standard, Enterprise, and Grid Editions) – All Coherence licenses include Java SE for running Coherence clusters and caches​. Coherence is a Java-based data grid, so Oracle bundles Java to ensure you can run its nodes. The Java usage is restricted to applications hosted on Coherence – i.e., the Java VM running Coherence and cache clients. You could not use the Coherence JVM to run an unrelated app server without violating the license.
• Oracle Identity Management Suites – Oracle Identity and Access Management Suite Plus, Oracle Identity Governance Suite, and similar products run on WebLogic and thus require Java. Oracle includes Java SE with these identity management products to support their operation. The Java license is confined to running the identity management software components. (For example, Oracle Access Manager or Oracle Identity Manager will come with a bundled Java runtime, which should only be used for those applications.)
• Engineered Systems Software (Ex, Oracle Private Cloud Appliance) – Some Oracle engineered systems bundle Java. Notably, Oracle Private Cloud Appliance includes Oracle Java SE 8 (Server JRE) for use with the appliance’s integrated software​. This Java is licensed only to run the appliance’s management services and related Oracle applications on that appliance​. Using it beyond the appliance (or upgrading it independently) would require a separate license.

Oracle Enterprise Applications (ERP, CRM, etc.)

• Oracle E-Business Suite (EBS) – Oracle EBS, a suite of ERP and HR applications, includes Java SE rights to support its technology stack. EBS uses Oracle Forms (for professional user interfaces), Oracle Reports, and other Java-based components, both on the server and client sides. The license for EBS grants you the right to use Java SE for servers running EBS and for client PCs that access EBS. For example, you can install the required JRE on end-user machines to run EBS forms and update it as needed, without a separate Java license. (Using that same JRE for non-EBS applications, however, is only “incidental use” and not supported or licensed beyond the EBS context​).
• PeopleSoft Applications – All Oracle PeopleSoft licenses include a restricted-use Java SE license as part of PeopleTools​. PeopleSoft’s architecture uses a Java-based application server (Tuxedo and WebLogic with PeopleTools), so Oracle provides Java SE for that purpose. The PeopleTools licensing notes state that Java SE is included solely to run your PeopleSoft application environment​. If you were to use that Java runtime for anything else, or upgrade it outside of PeopleSoft’s distribution, you’d fall outside the entitlement.
• JD Edwards EnterpriseOne – Oracle JD Edwards (JDE) ERP software includes Java SE in its Technology Foundation. As noted, the Java license is intended only for running JD Edwards applications. This covers using Java on the JDE enterprise server, deployment server, and JDE client workstations as required by the software. If you install JDE, the Java runtime provided can be used without a separate subscription, but only for JDE. Running other Java programs on those machines would not be covered.
• Oracle Siebel CRM – (Not Java-based) Siebel is a notable Oracle application that does not use Java SE, because its architecture does not require the Oracle JVM. Siebel runs primarily as a C++ application and uses a different web server for the UI, so unlike the other Oracle applications, you don’t get a Java license with Siebel. CIOs should be aware that not all Oracle apps bundle Java. Siebel users, for instance, would need to license Java separately if they installed it on their servers for any reason.
• Oracle Agile PLM – Oracle’s Product Lifecycle Management software (Agile) has client and server components that run on Java. The Agile PLM license includes Java SE for those components​. This ensures you can run the Agile application servers and client applets without a separate Java license. Java should only be used for Agile PLM functionality, such as product data management processes.
• Oracle Hyperion (EPM Suite) – Oracle Hyperion financial planning and consolidation tools run on web application servers (commonly WebLogic). Oracle’s licensing for Hyperion includes the necessary Java SE to run the web applications and reports in that environment​. For instance, Hyperion Planning and Essbase Administration Services are deployed on Java application servers – the Java needed for these is bundled with the Hyperion license. As always, Java SE use is restricted to the Hyperion EPM system.
• Oracle Demantra – Part of Oracle’s supply chain planning suite (often used alongside EBS), Demantra uses Java (for its client applets and perhaps server components). As listed in Schedule B, Java SE is included for Demantra​. Use of Java under this entitlement is only to support Demantra’s forecasting and planning tools.
• Oracle BI Suite (OBIEE) – Oracle Business Intelligence Enterprise Edition and related BI products are Java-based (they typically run on Oracle WebLogic). OBIEE licenses include a restricted-use Java SE license to run the BI platform​. This covers the OBIEE services and supporting components. The included Java cannot be used to run other custom applications except those part of your OBIEE deployment.
• Oracle AutoVue – AutoVue (for viewing CAD files and documents) often runs as a client-server system with Java applets. As noted in Schedule B, AutoVue products come with Java SE to support those applets and server components​. This Java is only for use within the AutoVue visualization environment.
• Oracle Secure Global Desktop (SGD) – SGD is a remote access solution that utilizes Java for its client and web interfaces. Oracle includes Java SE with SGD so that you can deploy remote desktop servers and clients. Again, you may only use it for the SGD functionalities – e.g., launching the SGD client applet or running the SGD server services.

Development and Utility Tools

• Oracle SQL Developer – Oracle’s free SQL Developer tool is listed as a Schedule A product, which includes Java SE. In practice, SQL Developer comes bundled with an Oracle Java Development Kit (JDK), so it can run out of the box. This bundled JDK is licensed for use with SQL Developer only. (SQL Developer is a client-side development tool, so the risk of misuse is low, but technically,y you shouldn’t use the included JDK to run other apps or for general development.)
• Oracle JDeveloper and ADF – Oracle JDeveloper, an IDE, and the Application Development Framework both require Java. Oracle typically ships JDeveloper with a Java SE binary for convenience. If so, that would be considered a restricted-use inclusion similar to SQL Developer. Ensure that any such Java is used only for running the Oracle development tools.
• Oracle Enterprise Manager – Oracle Enterprise Manager (OEM) uses Java for its console and agent. While OEM itself is free for licensed Oracle customers, the Java used on the server side is part of WebLogic, which is included with OEM. So indirectly, OEM includes a Java license via its bundled WebLogic Server. This Java is restricted to running the OEM application.
• Oracle Cloud Infrastructure Agent – As mentioned in Schedule A, the OCI Management Agent includes Java SE. This is a small utility that uses Java to monitor on-prem systems for Oracle Cloud. The Java runtime it contains is licensed only for the agent’s use.
• Other Utilities – Various Oracle installers and configuration tools (for database, middleware, etc.) use Java. Still, Oracle’s policy is that if it’s needed to install or run a licensed product, they will provide it under that product’s license. Always check the “Licensing Information” documents; many have a section listing “Entitled Products and Restricted Use Licenses,” which will call out Java SE if applicable. For example, Oracle WebCenter Content’s licensing notes explicitly state: “Java SE is included with Oracle WebCenter Content and is intended only for use in conjunction with running Oracle WebCenter Content applications…”​.

“Unrestricted” vs. “Unsupported” Java Usage

It’s important to distinguish unrestricted use (full license) from unsupported use of Java. If you use Java beyond the restrictions of your Oracle product license, you are effectively unlicensed (and unsupported) for that usage.

For instance, if you took the Java runtime from your EBS server and used it to run a separate custom application, that would be unrestricted use without a license – a compliance violation.

Oracle may require you to purchase Java SE subscriptions for those deployments if they are discovered. In addition, since that scenario is outside of your Oracle product agreement, you would have no Oracle Support coverage for any Java issues in the custom app.

Another scenario is if your Oracle product is no longer supported. Oracle’s Java entitlement is tied to having a valid license and support for the parent product.

Oracle clarifies that if your entitlement to the Oracle product ends, your entitlement to use Java SE under that agreement also ends​. In practical terms, if you stop paying support or decommission the Oracle software, you are supposed to cease using the Java that came with it (or at least lose the right to receive updates and patches).

Running an outdated, unpatched Java without a support contract can pose serious security risks and potential non-compliance if Oracle audits your environment.

Additionally, Oracle’s support note on Java SE usage (My Oracle Support Doc ID 1557737.1) emphasizes that customers without a standalone Java SE support contract have a “more constrained set of rights” for Java​.

You are entitled to download and install only the Java updates necessary for the Oracle product, and only on systems running that product. You cannot, for example, take the latest Java 11 and deploy it broadly just because you own WebLogic – you’d only be allowed to use the Java versions that WebLogic specifically requires.

Also, you would route any support needs through the WebLogic support team (not Java support directly), which may limit help to scenarios that impact WebLogic.

In summary, any Java use outside the narrow boundaries of an Oracle product license is “unsupported” and likely non-compliant.

The financial risk of such misuse can be high – in an audit, Oracle could demand backdated license fees or subscriptions. Likewise, failing to realize you do have Java rights could lead to unnecessary spending on subscriptions. Both are undesirable outcomes for CFOs.

Verifying Your Java SE Entitlements

How can you confirm if your organization already has Java SE rights through existing Oracle products?

A few practical steps:

1. Review Oracle’s official lists and documentation: Cross-check your Oracle product portfolio against the Schedule A/B list above and Oracle’s published resources. Oracle’s website and support FAQ confirm which products include Java SE​. If a product you use appears there (or in the examples we’ve listed), it likely has a Java entitlement.
2. Check the Licensing Information documents for your software: Oracle provides Licensing Information User Manuals for most products. These often contain a section on “Restricted Use Licenses” or “Included Components.” Look for mentions of “Java SE” or “JDK” in those docs. For example, the PeopleSoft PeopleTools Licensing manual explicitly states that Java SE is included with PeopleTools for use with PeopleSoft apps. Similar wording can be found in Oracle WebCenter Content’s licensing guide​ and others. This is solid evidence of your entitlement.
3. Inspect your Oracle ordering documents or agreements: In some cases, the ordering document (the contract you used to purchase the software) may list the included licenses or components. Sometimes Java might be referenced in footnotes or a section describing bundled programs. While the OMA/OLSA itself is generic, your specific order for, say, WebLogic Suite may include the Java SE Suite. If you have these documents, review them for any clauses about included programs or “Schedule B” references.
4. Utilize Oracle’s support resources: Oracle’s support site has relevant notes, such as Doc ID 1557737.1, mentioned earlier, and FAQs. These can clarify entitlements. The Oracle Java SE Licensing FAQ and OTN License FAQ are useful for reading to understand the official stance. (Note: Some support notes may require an active support login to view.)
5. Ask Oracle or a licensing expert: If in doubt, engage Oracle License Management Services (LMS) or a third-party licensing consultant. They can help interpret your contracts. For CIOs and CFOs, a brief discussion with Oracle representatives, asking, “Do our licenses for Product X cover Java SE usage?” can provide written confirmation to file away. Always get it in writing or refer to an official document.

By verifying these details, you may discover that you already have the right to use Java in certain areas, meaning you can avoid paying for a separate Java SE subscription for those.

Conversely, you might also discover that some Java deployments in your environment are not covered by any entitlement, alerting you to a compliance gap that needs to be addressed proactively.

Recommendations and Best Practices for Java Licensing Compliance

In light of the above, here are concrete recommendations for CIOs and CFOs to manage Java SE licensing and remain compliant, while minimizing unnecessary costs:

• Take an inventory of Java usage: Identify all instances of Java installed in your organization. Map each instance to either an Oracle product entitlement or another licensing source. If you find Java installed on servers that do not have an associated Oracle product from Schedule A or B, flag those for further review – they may require a separate license or removal.
• Leverage existing entitlements first: If you do own Oracle products that include Java SE, ensure you are using those entitlements. For example, if you have WebLogic licenses, you shouldn’t be paying extra to license Java on the same servers running WebLogic – the WebLogic license already covers it. Use the Oracle-provided Java (and specific version) that you’re entitled to for that product. This can save costs by avoiding duplicate licensing.
• Respect the boundaries of restricted use: Ensure that your IT staff understands that the Java SE bundled with an Oracle product can only be used for that specific product. Do not use the included JDK to run other applications, even if it’s technically possible. Enforce this policy via configuration management – e.g,. Keep Java installations that are tied to Oracle products separate from general-purpose Java installations.
• Stay within supported configurations: If you rely on an Oracle product’s Java entitlement, use the Java versions that Oracle permits for that product, as specified in the documentation. Don’t upgrade to a new major Java release expecting Oracle to support it without confirmation. For instance, if Oracle says E-Business Suite is certified with Java 8, stick to Java 8 for that product unless Oracle updates its policy. Using a different version of Java may not be licensed (and could void support).
• Monitor Oracle support status: Only active support grants you the right to updates and patches for the included Java​. If you plan to lapse support on an Oracle product but continue using it, recognize that you also lose access to Java updates under that agreement. This might be a reason to either budget for a Java SE subscription or upgrade to a version of the product that doesn’t require Oracle Java.
• Don’t double-pay if not needed: Oracle’s recent Java SE subscription models can be expensive. Before purchasing Java licenses enterprise-wide, cross-check against your Oracle product licenses. You might find, for example, that all your critical servers running Java are hosting Oracle software, such as WebLogic, Oracle Database (with OEM), or Oracle applications that provide Java rights. You could then scope any Java subscription to only the machines not covered by those entitlements, potentially saving significant costs.
• Budget for Java where you truly need full use: For any Java deployments not covered by an Oracle product license (or if you need the freedom to use Java for any purpose on a system), you should budget for a Java SE Universal Subscription or consider alternative Java distributions that are free/supportable. The key is: be intentional. Choose where you pay for Java, and use your Oracle-included rights where applicable elsewhere.
• Document your Java license position: Maintain documentation of how each Java instance is licensed. For those with Oracle product entitlements, keep copies of the Oracle documentation, such as the excerpts cited in this article, that prove Java SE is included with your product. In the event of an Oracle audit or review, you can demonstrate that certain Java installations are legitimately covered under existing licenses. This can quickly dispel any claims of non-compliance.
• Train your technical teams: Ensure that your database administrators, middleware admins, and developers are aware of Java licensing constraints. They should know, for instance, that they can’t just update the JDK on a server without checking entitlement, or deploy a new Java-based tool without considering licensing. A bit of internal education can prevent accidental compliance issues.
• Consult experts when in doubt: Oracle licensing, including Java, is complex and constantly evolving. If there’s uncertainty – for example, with legacy products or new Java licensing changes – seek advice. This could be from Oracle directly or independent licensing consultants. Given the high financial stakes (Oracle’s Java pricing and audit penalties can be steep), a small investment in expert advice can protect your organization from a costly mistake.

In summary, CIOs should incorporate Java licensing into their IT governance and asset management processes. CFOs should verify that the company isn’t overspending on licenses it doesn’t need (or conversely, exposing itself to liability by not licensing what it does use).

By fully understanding the Java SE entitlements that come with Oracle products, you can optimize compliance and cost, using what you’ve already paid for, and only paying extra when necessary.

Remember, Oracle will hold you to the letter of your agreements, so clarity on “unrestricted vs. restricted” Java rights is essential to avoid compliance surprises and to make informed financial decisions regarding Java in your enterprise.