Oracle Products Bundling Java SE Licenses

Oracle Products Bundling Java SE Licenses

Oracle’s licensing policies allow certain software products to include a Java SE license as part of their standard entitlement.

If licensed for those products, you can use the necessary Java SE runtime (and updates) without purchasing a separate Java SE subscription, as long as it’s used only to run that Oracle product.

Below, we outline the key products (beyond just the Schedule A/B lists) that bundle Java SE, with details on the Java versions, usage scope, and references to official Oracle documentation.

Bundled Java SE in Oracle Products – Overview

• Oracle Business Applications: Many Oracle enterprise apps (e.g., E-Business Suite, PeopleSoft, JD Edwards) include a restricted-use Java SE license. The bundled Java is typically the version required to run that application (for example, Java SE 8 for current PeopleSoft/PeopleTools​). Usage is limited to running the Oracle application – using Java outside of that (or using a different Java version than provided) requires separate licensing​​.
• Oracle Middleware & Servers: Oracle’s middleware products (WebLogic Server, Oracle Application Server, Coherence, etc.) also include Java SE entitlements:
  • WebLogic Server – All editions bundle Java SE but with different levels:
    • WLS Standard Edition includes Java SE (standard JDK). This entitlement covers the Java Development Kit (JDK) and Java Runtime (JRE) needed for WebLogic, generally without additional restrictions​.
    • WLS Enterprise Edition includes Java SE Advanced, which is restricted to WebLogic use. Java SE is provided only to run WebLogic Server and its client apps​. (Java SE Advanced adds features like Mission Control/Flight Recorder.)
    • WebLogic Suite includes Java SE Suite, restricted to that suite’s components (WebLogic Server, Oracle Containers for J2EE, Coherence)​. Java SE is included solely to enable client applications that access those server components​.
  • Oracle Coherence – All editions (Standard One, Enterprise, Grid) include a full-use Java SE license​. In other words, if you are licensed for Coherence, you can use Java SE for that deployment without separate Java licensing. (This is an exception where Java SE use is not strictly limited to only the product’s internal operation.)
  • Oracle Internet Application Server (IAS) EE – Includes the right to use Java SE (for running the Java EE environment)​to support forms, reports, and other Java runtime needs of IAS.
  • Oracle GlassFish Server (commercial): This includes the right to use Java SE (GlassFish, like WebLogic, requires a JDK)​.
• Development and Administration Tools:
  • Oracle SQL Developer – Oracle SQL Developer (a no-cost tool) is listed as an approved product that entitles the use of Java SE​. It typically ships with or requires a Java SE 8 JDK. Use of Java is free when running SQL Developer.
  • Oracle Forms/Reports and related clients – Oracle Forms (part of Oracle Fusion Middleware) and any applications built with Oracle Forms can run on Java SE without a separate license​. The Java runtime here is restricted to running the Forms-based application (for example, an insurance application built with Oracle Forms)​.
  • Oracle JDeveloper – (Not explicitly in Schedule A/B, but JDeveloper is a free IDE that requires Java. Oracle typically allows it to be used with the Java SE OTN license for development.)
• Oracle Enterprise Management Products:
  • Oracle E-Business Suite (EBS) – EBS includes a Java SE license for the required runtime (used in forms, OAF pages, etc.). Oracle explicitly states that EBS customers can access Java SE as needed without purchasing separate Java SE support​. This is a restricted-use license: the Java may be used only to run EBS and its components. (Example: EBS 12.2 uses Oracle Forms and OC4J, which run on Java SE 6/7 – those JDK updates are available to EBS users as part of EBS support​.)
  • PeopleSoft (PeopleTools) – PeopleSoft applications rely on Oracle’s PeopleTools, which bundles Java. Java SE (usually Java 8 in current PeopleTools) is included with PeopleTools and intended solely for running PeopleSoft apps​. Suppose you use Java for anything outside of the PeopleSoft environment (or use a different Java version than what is delivered). In that case, that usage falls under standard Java SE licensing (OTN or subscription)​. Oracle docs highlight that this Java license is only for PeopleSoft operation, and using it otherwise requires separate licensing.
  • JD Edwards EnterpriseOne—JD Edwards products also come with Java. Oracle’s license guide confirms that Oracle Java SE is included with JD Edwards EnterpriseOne for running the ERP system​. As with PeopleSoft, this is a restricted-use entitlement—only for JD Edwards applications. Using Java SE outside JD Edwards or upgrading it independently would be subject to normal Java SE license terms​.
  • Siebel—Oracle Siebel CRM isn’t explicitly listed in Schedule A/B, but recent guidance implies Siebel (which can run on Oracle’s middleware) would similarly allow Java SE usage for Siebel components. Siebel can be deployed on WebLogic or Tomcat; if on WebLogic, the WebLogic Java SE license would cover it​.) Siebel customers using Oracle’s provided WebLogic Server should be covered under that WebLogic Java entitlement for Siebel usage.
  • Oracle Demantra, Agile PLM, AutoVue, Secure Global Desktop, etc. – These specific products (mostly legacy Oracle acquisitions for PLM, CAD viewing, remote desktop, supply-chain planning) are called out in Oracle’s “Schedule A” list​. Each includes a Java SE runtime for their operation, and Oracle permits running Java SE for these products without additional license. The usage is restricted to the product itself (for example, AutoVue’s Java can only be used to run AutoVue visualization servers).
• Oracle Business Intelligence and Middleware Suites:
  • Oracle Business Intelligence (OBI/OBIEE) – Oracle BI Enterprise Edition and related BI suites run on Java (WebLogic). Oracle documentation and support notes indicate that Java SE use is permitted for Oracle BI as part of the product license​. In practice, OBIEE includes a WebLogic Server (often “WebLogic Suite for Oracle Applications”), which bundles Java SE for the BI system’s use. The Java entitlement is limited to the BI software operation.
  • Oracle Data Integrator (ODI) – Oracle Data Integrator and related integration suites (which run on Java EE platforms) include Java SE rights. For example, ODI Enterprise Edition includes WebLogic Server Standard Edition under the hood, thus entitling the use of Java SE for the ODI environment​. This Java may only be used for the ODI and its J2EE components.
  • Oracle Identity & Access Management (OAM/OIM)—Oracle’s Identity Manager, Access Manager, Directory Services Plus, etc., run on Java EE servers. Their licenses include Java SE use. Oracle’s licensing experts note that these IAM Suite Plus components include Java SE as part of the package​. Again, Java SE usage is restricted to running the identity management software.
  • Oracle WebCenter Content/UCM – Oracle WebCenter Content and related WebCenter products rely on Java. For instance, WebCenter Content’s document conversion feature explicitly “includes Java SE”​. Customers can use Java SE with WebCenter Content without a separate Java license, but only for that product’s functionality. (As noted above, WebCenter and UCM could run on Oracle Application Server or WebLogic, which carry their own Java entitlements.)
• Engineered Systems and Cloud:
  • Oracle Private Cloud Appliance (PCA) – This Oracle Engineered System (a converged infrastructure appliance) has embedded software, including Java. The PCA license terms state that Java SE 8 (Server JRE) is included with the appliance’s software and intended solely to run PCA components​. If Java SE on the PCA is used for anything else, or if you install a different Java version on it, that usage would fall under standard Java licensing​.
  • Oracle Cloud (OCI) Environments: When using Oracle’s public cloud or Cloud@Customer, Oracle provides Java SE licenses for cloud instances at no extra cost. Per Oracle’s PaaS/IaaS service descriptions, customers get “a free Oracle Java SE license” for any Oracle Cloud instance with OS access​. This allows you to use Oracle Java on your OCI virtual machines or PaaS services for any software running there. The Java SE usage in Oracle Cloud is covered under the Oracle Technology Network (OTN) license (with support provided under your cloud agreement)​. In short, if you run workloads on Oracle Cloud Infrastructure, you do not need a separate Java SE subscription for those cloud-deployed Java instances.

Summary of Products with Java SE Entitlements

The table below summarizes key Oracle products that include a Java SE license by entitlement, the Java version typically included, the scope of permitted use, and reference sources:

Sources: The information above is drawn from Oracle’s official licensing documentation and support notes, including Oracle’s Approved Product Use list​, My Oracle Support license notes (e.g. Doc ID 1557737.1 on Java in other products), and Oracle product Licensing Guides. For example, Oracle’s PeopleTools and JD Edwards manuals explicitly state that “Oracle Java SE is included” with those products for use with that software​.

Oracle’s Java licensing FAQ and blog posts confirm that customers of E-Business Suite “will continue to have access to Java SE without purchasing Java SE support” for the apps’ needs​. Similarly, the Oracle WebLogic Server licensing guide notes that WebLogic EE includes a Java SE Advanced license restricted to WebLogic, and WebLogic Suite includes Java SE Suite for its components​. Oracle’s cloud service descriptions also clearly provide a Java SE entitlement on Oracle Cloud Infrastructure​.

Important Conditions and Limitations

• Restricted-Use Means Just That: In almost all cases, the Java SE usage is tied to the Oracle product’s operation. You may use Java SE only to install, run, or develop for the entitled Oracle product. Using the bundled Java for any other general purpose or other applications not covered by the product license is prohibited under that entitlement. For instance, if you have Java SE from a PeopleSoft license, you can’t use it to run a separate custom application that’s unrelated to PeopleSoft, which would require a separate Java SE license. Oracle’s support note emphasizes that customers are expected to install Java on servers only for the supported Oracle product’s use​.
• Version Matching: The entitlement typically covers the Java versions the Oracle product requires. If your Oracle software requires (or is certified with) Java 8, your support covers Java 8 updates for that use​. If you opt to use a newer Java version than what the product documentation calls for, you may step outside the bundled license. Always check the product’s certification matrix and use the Java versions that come with the product or are officially supported.
• No Standalone Support: The Java SE updates/patches obtained under an Oracle product license are provided to support that product. Oracle allows you to download Java patches from My Oracle Support for use with the covered products​, and you can file support requests for Java issues through the product’s support channel. Still, you cannot directly contact Java support (unless you have a Java SE subscription). In other words, if Java causes a problem in your EBS environment, you log an EBS support ticket – the Java fix or guidance comes as part of EBS support​.
• End of Product = End of Java Entitlement: If your license or support for the parent Oracle product ends, so does your right to use the included Java SE​. For example, suppose you retire Oracle EBS and are no longer under support. In that case, you are no longer entitled to use Oracle’s Java updates to run EBS. (At that point, if you still need Java for other uses, you’d need to license Java SE separately or use an alternative JDK.)
• Third-Party Applications built with Oracle Tools: Oracle distinguishes Schedule A vs. B products in the Java OTN License context​. Schedule A products (like Oracle Forms, SQL Developer, etc.) can be run on Java SE for any use with no extra license. Schedule B products (Oracle tools used to build apps that are then distributed) allow end-users to run those apps on Java SE. For example, if an ISV develops software using Oracle Forms (a Schedule B product), its customers can run that software on Oracle Java without needing a Java license​. The ISV, however, must maintain its Oracle Forms license. This nuance mainly affects software vendors – typical Oracle customers using packaged Oracle products just need to know that the Java is covered for that product’s use.

Conclusion

For Oracle customers, it’s crucial to identify which Oracle products you have that have already granted Java SE rights. In those cases, you can safely use Oracle Java within that product’s deployment scope without additional fees​. However, suppose you use Oracle Java for anything outside those specific entitlements (so-called “general purpose” use). In that case, you likely need a separate Java SE subscription or should switch to a free OpenJDK distribution.

Refer to Oracle’s official licensing documentation or support notes for your product to confirm the Java SE terms included. This ensures you remain compliant and only pay for Java where necessary while fully using the Java rights that come with the Oracle software you’ve already licensed.

Do you want to know more about our Oracle Java Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

Email *

Company

Message *

Submit