How Bundled Java SE Entitlements Work
Under Oracle’s current licensing framework, the Java SE runtime required to operate certain Oracle products is included as part of the product’s licence entitlement. This means enterprises running these products can use Oracle’s Java SE (including security patches and updates) without purchasing a separate Java SE Universal Subscription — provided that the Java usage is limited to running that specific Oracle product and its components. The bundled entitlement typically covers the Java versions required by the Oracle product (for example, Java SE 8 for PeopleSoft PeopleTools, Java SE 6/7/8 for E-Business Suite depending on the version), and Java updates are obtained through My Oracle Support under the parent product’s support agreement rather than through a separate Java support channel.
There are two categories of bundled Java SE entitlements. The vast majority are restricted-use — Java SE may only be used to install, run, and operate the entitled Oracle product. Using the bundled Java for any other purpose (running unrelated applications, general-purpose development, or operating non-Oracle software) falls outside the entitlement and requires a separate Java SE subscription. A small number of products include full-use Java SE rights, meaning Java can be used for any purpose on the licensed servers. Understanding which category applies to each product is essential for compliance. For the full Java licensing context, see Decoding Oracle Java Licensing Changes.
“The most common Java audit finding involves enterprises using a bundled Java SE entitlement beyond its restricted scope. A PeopleSoft customer using the PeopleSoft-bundled Java to run an unrelated custom application, or an EBS customer using the EBS-bundled Java on a server that also runs non-Oracle workloads — both create compliance exposure. The bundled entitlement saves you from purchasing a separate Java subscription, but only if you stay within the product-specific usage boundary.”
Oracle Business Applications with Bundled Java SE
Oracle’s major enterprise applications — E-Business Suite, PeopleSoft, JD Edwards, and Siebel — all include Java SE entitlements because their application servers, forms clients, and tooling depend on Java to operate.
| Product | Java Version Included | Usage Entitlement | Key Restrictions |
|---|---|---|---|
| Oracle E-Business Suite (EBS) | Java SE 6/7/8 (per EBS version) | Restricted — Java used only for EBS components (Forms, OA Framework, OC4J) | EBS customers on support can download Java updates via My Oracle Support. Java use outside EBS requires separate licensing. |
| PeopleSoft (PeopleTools) | Java SE 8 (included in PeopleTools) | Restricted — Java used only for PeopleSoft applications (App Server, Process Scheduler) | Only the Java version delivered with PeopleTools is covered. Using a different version or using Java outside PeopleSoft requires separate licensing. |
| JD Edwards EnterpriseOne | Java SE 8 (included in tools) | Restricted — Java used only for JDE ERP operations (enterprise server, deployment server) | Java SE Suite features are included for JDE usage only. No separate Java licence needed for the ERP system. |
| Siebel CRM | Java SE (via WebLogic deployment) | Restricted — covered under WebLogic’s Java entitlement when Siebel runs on WebLogic | Siebel on WebLogic is covered by the WebLogic Java entitlement. Siebel on Tomcat or other non-Oracle servers would not carry this entitlement. |
The critical point for enterprise applications is that the bundled Java is tied to the product’s support agreement. If you terminate EBS support, the Java entitlement ends with it. If you upgrade EBS to a version that requires a different Java version, you must use the version specified in Oracle’s certification matrix — using a newer Java version than what is certified may step outside the bundled entitlement. For EBS licensing detail, see Oracle EBS Licensing Guide. For JDE licensing, see Oracle JD Edwards Licensing Guide.
Oracle Middleware and Server Products with Bundled Java SE
Oracle’s middleware products carry the most nuanced Java SE bundling rules because different editions include different Java SE tiers.
| Product | Java SE Tier Included | Usage Entitlement | Key Restrictions |
|---|---|---|---|
| WebLogic Server — Standard Edition | Java SE (standard JDK/JRE) | Full Java SE for running applications on WebLogic | Covers JDK, JRE, JavaFX for any applications deployed on that WebLogic instance. |
| WebLogic Server — Enterprise Edition | Java SE Advanced (includes Mission Control, Flight Recorder) | Restricted — Java used only for WebLogic Server and its client applications | Cannot use Java SE Advanced for unrelated Java applications outside the WebLogic environment. |
| WebLogic Suite | Java SE Suite (Advanced + Real-Time) | Restricted — Java used only for suite components (WebLogic Server, OC4J, Coherence) | Java entitlement supports only clients of WebLogic Suite components. |
| Oracle Coherence (all editions) | Java SE — Full Use | Unrestricted — Java SE can be used for any purpose on licensed Coherence servers | Unique exception: Coherence includes full-use Java SE rights, not restricted to Coherence operations only. |
| Oracle Internet Application Server EE | Java SE (Java EE runtime) | Restricted — Java used for IAS operations (Forms, Reports, Java EE) | Covers Java runtime needs of IAS components. |
| Oracle GlassFish Server (commercial) | Java SE (JDK) | Restricted — Java used to run GlassFish | GlassFish requires a JDK; the commercial licence includes Java SE for that purpose. |
The WebLogic tier distinction is particularly important for audit defence. WebLogic Standard Edition includes standard Java SE with relatively broad usage rights for applications deployed on that instance. WebLogic Enterprise Edition and WebLogic Suite include more advanced Java SE tiers but with stricter usage restrictions — Java may only be used within the WebLogic environment. If you run Java applications outside of WebLogic on the same server, those installations require separate Java licensing. For middleware licensing detail, see Oracle Middleware Licensing Guide.
Oracle BI, Integration, and Identity Products
| Product | Java SE Included Via | Usage Entitlement |
|---|---|---|
| Oracle BI Enterprise Edition (OBIEE) | WebLogic (Oracle Apps edition) bundled with OBIEE | Restricted — Java used only for Oracle BI server, WebLogic, and BI Java components |
| Oracle Data Integrator (ODI) | WebLogic Standard Edition included with ODI EE | Restricted — Java used only for ODI and its Java EE components (agents, console) |
| Oracle Identity & Access Management Suite | WebLogic/Java EE platform included with IAM | Restricted — Java used only for IAM components (OAM, OIM servers) |
| Oracle WebCenter Content | Java SE 8 included directly | Restricted — Java used only for WebCenter services (Content Server, document converters) |
| Oracle SQL Developer | Java SE 8/11 bundled or user-provided | Unrestricted for SQL Developer use — free development/DBA tool |
| Oracle Forms/Reports | Java SE included as part of Fusion Middleware | Restricted — Java used to run Forms-based applications (including third-party apps built with Oracle Forms) |
A significant nuance applies to Oracle Forms: applications built by third parties using Oracle Forms (a Schedule B product) can be run by end-users on Oracle Java without those end-users needing a separate Java licence. The ISV or organisation that built the Forms application must maintain its Oracle Forms licence, but the downstream users of the Forms-based application are covered. This distinction mainly affects software vendors distributing Forms-based applications.
Engineered Systems and Oracle Cloud
Oracle Cloud Infrastructure (IaaS/PaaS)
Oracle provides a free Java SE licence for any Oracle Cloud instance with OS access. You can use Oracle Java on OCI virtual machines or PaaS services for any software running there — not restricted to Oracle products. This is an unrestricted, no-additional-cost entitlement that applies to all OCI customers. If you run workloads on Oracle Cloud Infrastructure, you do not need a separate Java SE subscription for those cloud-deployed Java instances.
Oracle Private Cloud Appliance (PCA)
The PCA includes Java SE 8 (Server JRE) as part of the appliance software, but it is restricted to running PCA system components only. Using the included Java for other applications on the PCA, or installing a different Java version, requires standard Java licensing. The entitlement covers PCA management and integrated software only.
Legacy Products (Demantra, Agile PLM, AutoVue, etc.)
Oracle’s Schedule A list includes specific legacy products (mostly from acquisitions) such as Oracle Demantra, Agile PLM, AutoVue, and Secure Global Desktop. Each includes a Java SE runtime for its operation — restricted to running that specific product only. For example, AutoVue’s Java entitlement covers only AutoVue visualisation servers.
Important Conditions and Limitations
Understanding the boundaries of bundled Java SE entitlements is as important as knowing which products include them. The following conditions apply universally.
Restricted-use means exactly that. In almost all cases, Java SE usage is tied to the operation of the specific Oracle product. You may use Java only to install, run, or develop for the entitled product. Using the bundled Java for general-purpose computing, running unrelated applications, or operating non-Oracle software on the same Java installation falls outside the entitlement and requires a separate Java SE subscription. Oracle’s support documentation explicitly states that customers must install Java on servers only for use with the supported Oracle product.
Version matching is required. The entitlement covers the Java versions required by and certified with the Oracle product. If your Oracle software requires Java 8, your support covers Java 8 updates for that use. Opting to use a newer Java version than the one specified in the product’s certification matrix may step outside the bundled licence. Always use the Java versions that come with the product or are listed in Oracle’s official certification documentation.
Support is through the parent product. Java updates and patches obtained under an Oracle product licence are provided through the parent product’s support channel. You download Java patches from My Oracle Support for use with covered products, and you file support requests for Java issues through the product’s support ticket system (e.g., if Java causes a problem in EBS, you log an EBS ticket). You cannot contact Oracle’s Java support directly unless you have a separate Java SE subscription.
End of product support ends the Java entitlement. If your licence or support for the parent Oracle product terminates, so does your right to use the included Java SE. If you retire Oracle EBS and are no longer under support, you are no longer entitled to use Oracle’s Java updates for EBS. At that point, continued Java usage requires either a separate Java SE subscription or migration to an OpenJDK alternative. For migration strategies, see Java Licensing Cleanup Guide.
Schedule A vs Schedule B distinction. Oracle distinguishes between Schedule A products (which can be run on Java SE without additional licensing) and Schedule B products (Oracle development tools whose output — applications built with those tools — can be run by end-users on Java SE without those users needing a Java licence). Schedule A covers most packaged Oracle products. Schedule B primarily affects ISVs and organisations distributing applications built with Oracle Forms or similar development tools. For CFO-focused cost analysis, see Java Licensing Costs — 20 Things Every CFO Needs to Know.
Compliance Strategy: Using Bundled Entitlements Effectively
Bundled Java SE entitlements represent a significant cost-avoidance opportunity — but only if they are documented, tracked, and applied correctly. The following approach ensures maximum value from bundled entitlements while avoiding compliance risk.
1. Inventory all Oracle products with Java SE entitlements. Cross-reference your Oracle product licence portfolio against the bundled entitlement tables above. For each product, confirm that you hold active support (since the Java entitlement depends on the parent product’s support being current) and document the Java version covered.
2. Map every Java installation to a specific entitlement. For each Oracle JRE or JDK installation in your environment, determine whether it is covered by a bundled product entitlement, covered by a separate Java SE subscription, or unentitled (and therefore creating compliance exposure). Installations that cannot be mapped to a specific entitlement are the source of audit risk. See Java Audit Risk Assessment.
3. Enforce version and scope boundaries. Ensure that Java installations associated with bundled entitlements use only the certified Java version for that product and are not being used to run non-Oracle workloads on the same server. A common audit finding is a server running EBS with the bundled Java 8 that is also running an unrelated custom application on the same Java installation — the custom application’s Java usage is not covered by the EBS entitlement.
4. Replace non-entitled Java with OpenJDK where possible. For Java installations that are not covered by any bundled entitlement or Java SE subscription, evaluate whether they can be replaced with an OpenJDK alternative (Adoptium/Temurin, Amazon Corretto, Azul Zulu). This eliminates the Oracle licensing obligation entirely for those installations. Most enterprise applications work identically on OpenJDK distributions. See Java Licensing Cleanup Guide.
5. Document everything for audit defence. Maintain a register that maps every Java installation to its entitlement source (bundled product, Java SE subscription, or OpenJDK). This register is the single most important defence asset in any Oracle Java audit. Without it, Oracle’s default position is that all Oracle JRE/JDK installations require the employee-based Universal Subscription. See Java Audit Defense Tactics.