Oracle Products That Include a Java SE License: A Detailed Overview
Oracle licenses Java SE in two main ways:
- Standalone Java SE subscription—requires separate purchase.
- Bundled licenses are included with certain Oracle products.
Many Oracle customers aren’t aware that their existing Oracle software licenses already include Java SE rights.
Understanding bundled Java licenses can help reduce unnecessary licensing costs.
Below is a clear and structured breakdown of Oracle software products that currently include Java SE licenses as part of their standard entitlements.
Oracle Middleware Products Bundling Java SE
Oracle’s middleware and infrastructure software often requires Java to function, so Oracle includes Java SE usage rights with these products.
Key examples include:
- Oracle WebLogic Server (Standard, Enterprise, Suite) – All editions of WebLogic include rights to use Java SE for running WebLogic and its applications. For instance, WebLogic Standard Edition includes a Java SE JDK for the server, while Enterprise Edition comes with Java SE Advanced features. These Java licenses are limited to WebLogic Server environments and any client applications that directly connect to WebLogic.
- Oracle Coherence – Oracle’s in-memory data grid, Coherence, uniquely provides a full-use Java SE license. This means that a Coherence license entitles you to use Java SE not just for Coherence components, but also for other general purposes. This is an exception; most other bundled Java licenses are restricted-use.
- Oracle Internet Application Server (IAS) – Oracle’s older middleware suite (for running Forms, Reports, etc.) includes Java SE for those components. If you have IAS licenses, the Java runtime needed for Oracle Forms and Reports is covered under that license (restricted to those Oracle components).
- Oracle GlassFish Server (Commercial) – The commercial edition of GlassFish (Java EE server) comes with Java SE rights to run applications within the GlassFish environment. This covers the JDK/JRE needed to host Java EE applications on GlassFish.
- Oracle Identity & Access Management – Products like Oracle Access Manager (OAM) or Identity Manager (OIM) run on Oracle’s middleware platform. When deployed with Oracle’s supported configuration (typically on WebLogic), the necessary Java SE usage is included as part of the license. Again, this Java use is only authorized for the identity management components.
- Oracle WebCenter Content – This content management system includes Java SE for its internal functions (such as document conversion and indexing). The Java license is strictly bundled for running WebCenter Content servers and services.
Oracle Enterprise Applications (ERP/CRM) and Java
Oracle’s major business applications also bundle Java SE licenses to support their technology stack.
These large ERP/CRM systems rely on Java for certain features, and Oracle provides the needed Java rights with the application license:
- Oracle E-Business Suite (EBS) – EBS includes Java SE (often specific versions, such as Java 6, 7, or 8) as part of its standard installation. This allows you to run Oracle Forms, Oracle Application Framework (OAF) pages, and other Java-based components within the EBS environment without a separate Java license. For example, if users launch Oracle Forms from EBS, the JRE needed on client machines is covered. However, using Java outside of EBS (e.g., developing custom standalone Java apps) is not covered by this entitlement.
- PeopleSoft – Oracle’s PeopleSoft applications are built on an underlying technology layer called PeopleTools, which requires Java. A Java SE 8 runtime is bundled with PeopleTools to run the application server, batch scheduler, and other components. This means all Java needed for PeopleSoft’s web and process scheduler servers is licensed through your PeopleSoft licenses. Java use is restricted to PeopleSoft operations; any other Java deployments in your organization would require separate licensing.
- JD Edwards EnterpriseOne – JD Edwards (JDE) utilizes Java for certain components of its enterprise server and deployment server. Oracle includes Java SE rights with JDE, allowing you to run the necessary JDK/JRE on those servers. As with other apps, this Java license applies only to JDE’s environment. If you were to use the JDK from JDE to run unrelated applications, that would fall outside the permitted use.
- Siebel CRM – Siebel is often deployed on Oracle’s middleware stack (for example, using Oracle WebLogic as the web server). When running Siebel with Oracle’s recommended configuration, the required Java SE is licensed via the WebLogic (or other Oracle middleware) entitlements you have. In short, if you’re using Siebel on Oracle infrastructure, you do not need a separate Java SE subscription for the Java that runs Siebel’s components.
Oracle Development and Analytics Tools with Java
Several Oracle development tools and enterprise analytics products also embed Java and include usage rights so customers can run them out-of-the-box:
- Oracle SQL Developer – This free database development tool is a Java-based application. Oracle distributes SQL Developer with an embedded Java SE runtime, and using Java within SQL Developer is permitted under the tool’s license. You don’t have to separately license Java SE to run SQL Developer on your desktop or server.
- Oracle Forms and Reports – Oracle Forms (for building data entry applications) and Reports are built on Java. When you deploy an Oracle Forms application, the Oracle Forms Server includes a Java SE license for running the Forms runtime and associated applets. This is restricted to running applications built with Oracle Forms/Reports.
- Oracle JDeveloper – JDeveloper is Oracle’s Java IDE for developing applications (especially for Oracle Fusion Middleware). It comes with a Java SE Development Kit bundled under Oracle’s free developer license terms. This means you can use the JDK within JDeveloper for development purposes without needing a paid Java SE subscription. (Note: this covers internal development only – if you deploy Java applications outside of development, production use of Java may require licensing unless covered by another entitlement.)
- Oracle Business Intelligence (OBIEE) – Oracle’s OBIEE suite runs on a WebLogic Server and uses Java for its middleware layer. The OBIEE license includes Java SE usage via the bundled WebLogic Server license. In practice, when you install OBIEE, it comes with WebLogic and Java, all of which are licensed for use with the BI system. Java is only licensed for OBIEE components (for example, running the BI Presentation Services and analytics dashboards).
- Oracle Data Integrator (ODI) – ODI is a data integration platform that also runs on Java (its scheduling agent and web application run in a Java EE server). Oracle includes a restricted-use WebLogic Server Standard Edition with ODI, which in turn provides the needed Java SE. So if you’re using ODI, the Java running the ODI agent and console is covered. Java usage is limited to the ODI environment; using it for other applications would require a separate license.
(Other Oracle tools like Oracle Enterprise Manager or Oracle GoldenGate may also use Java internally, but the general rule applies: if Java is needed solely to run the Oracle product, Oracle typically provides the necessary license as part of that product.)
Oracle Engineered Systems and Cloud Platforms
Oracle’s hardware appliances and cloud services can also include Java SE rights as part of their offering, especially when Java is integral to their operation:
- Oracle Private Cloud Appliance (PCA) – This on-premises engineered system (used for running virtual machines) includes Java SE in its internal management software. Specifically, Oracle provides a Server JRE (Java Runtime Environment) with PCA, allowing all the appliance’s management consoles and tools to run without additional licensing. This bundled Java is meant only for PCA’s internal use. If you were to run other Java applications on the PCA beyond its management tools, those would not be covered by the PCA’s Java license.
- Oracle Cloud Infrastructure (OCI) – Oracle’s public cloud has a special benefit: an OCI tenancy includes licenses and support for Java SE on any Oracle Cloud VM or service. In other words, if you deploy Java applications on Oracle’s cloud, you do not need to purchase a separate Java SE subscription for those cloud instances. Oracle treats Java as an included service on OCI. For example, running a Java web application on an OCI Compute virtual machine is fully covered for Java licensing as long as you are an OCI customer. (This benefit applies only to Oracle’s cloud – if you run the same Java workload on AWS or Azure, you would need to license Java separately.)
License Scope and Restrictions
While these Oracle products include Java SE licenses, it’s crucial to note the restricted scope of most of these entitlements. The Java license from an Oracle product generally covers only the use of Java within that product’s environment.
Key points to consider:
- Restricted Use Only – Bundled Java SE rights are typically tied to a specific use. For instance, Java included with WebLogic can be used for WebLogic and its client apps, but not for unrelated applications. If you exceed the allowed use (for example, using the WebLogic-provided JDK to run a separate custom application), you are out of compliance.
- Version and Update Limitations – Often, the Java version included is the one certified for that Oracle product. Using significantly newer Java versions for the product might not be covered. For example, if Oracle EBS is certified on Java 8, your EBS license covers Java 8 for EBS. If you decide to run EBS on Java 17 (not certified), that could fall outside the entitlement (and also risk breaking support). Always check the product documentation for which Java versions are approved.
- No Standalone Support – Support for the Java that comes with an Oracle product is provided through that product’s support contract (not via a separate Java support contract). This means that if you encounter a Java issue within EBS or WebLogic, Oracle will assist you under your EBS or WebLogic support. However, you don’t have standalone Java SE support to call upon for issues unrelated to the product.
- Additional Licensing Required for Other Uses – If your organization uses Java for purposes beyond the scope of these Oracle products, you’ll need to obtain a separate license for those deployments. A common example is using Java SE on desktops for internal applications or servers running non-Oracle software. Such use would require an Oracle Java SE subscription (or another authorized Java distribution). The included licenses won’t cover general-purpose Java usage in the enterprise.
Cost Implications of Bundled Java vs Separate Licensing
Understanding these Java-inclusive licenses is financially important. Oracle’s changes to Java licensing have made standalone Java SE subscriptions expensive for large firms, so leveraging bundled entitlements can yield significant savings:
- Oracle’s Java SE Universal Subscription (as of 2023) is now priced per total employees in the organization. For example, a company with 2,000 employees would pay around $24,000 per month (at roughly $12 per employee) for a full Java SE subscription covering all users. That’s nearly $288,000 per year.
- If the same company’s Java usage is primarily for Oracle products, such as WebLogic, PeopleSoft, and Oracle Database tools, much of that cost could be avoided. The Java needed to run those Oracle systems is already included in the product licenses. The company would only need to license Java separately for any additional non-Oracle Java applications.
- Avoid Double Paying – Oracle sales reps might push Java SE subscriptions broadly, even when you’re already entitled under other licenses. Always review your existing Oracle contracts and the included rights before agreeing to a separate Java deal. For instance, if you run Oracle EBS and nothing else in Java, you shouldn’t be paying extra for Java SE on those EBS servers or user PCs running EBS forms.
- On the other hand, ensure you remain compliant: if you do have significant Java deployments outside of Oracle products (for example, custom applications, third-party software, or Java running on cloud platforms other than OCI), budget for the appropriate Java licenses. Non-compliance can lead to costly back-license fees in an audit scenario (even though we focus on avoiding audits, being properly licensed is the best prevention).
By carefully identifying where you already have Java rights through Oracle products, you can optimize your spend and only pay for Java where it is truly necessary.
Recommendations
- Audit Your Oracle Installations – Identify all Oracle products in use (databases, middleware, applications) that might include a Java SE license. Make a list of these entitlements to understand where you already have coverage.
- Map Java Usage to Entitlements – For each Java runtime in your environment, determine if it’s supporting an Oracle product that has bundled rights. If yes, document that linkage to justify not purchasing a separate Java subscription for it.
- Avoid Redundant Java Purchases – If an Oracle product covers a particular Java deployment, do not pay twice. For example, if WebLogic or OBIEE includes Java, leverage that and avoid buying a separate Java SE subscription for those servers.
- Stay Within Permitted Use – Use Java only as authorized under the product license. If a bundled Java is limited to a product’s components, do not use it to run other software. Develop internal policies to prevent administrators or developers from repurposing Oracle-supplied JDKs for general use.
- Monitor Version Compliance – Keep your Java versions up to date with the versions supported by Oracle for each product. If you update Java (for security or performance), ensure the new version is still covered or officially supported for that Oracle product, or get clarification from Oracle.
- Plan for Other Java Needs – For any Java usage not covered by an Oracle product license, evaluate your options to determine the best approach. You might purchase Oracle’s Java SE Universal Subscription for those or consider third-party Java distributions if appropriate. The key is to only pay for Java where necessary, and use the included rights wherever possible.
- Educate Stakeholders – Ensure your IT procurement and operations teams are aware of these Java entitlements. Often, organizations purchase licenses simply due to a lack of awareness. Educating teams can prevent unneeded spending.
- Get Confirmation in Writing – When in doubt, ask Oracle (or consult Oracle’s official policy documents) to confirm that a given product includes Java and what the exact terms are. Having written confirmation can be useful if questions arise later.
- Leverage Oracle Cloud for Java Workloads – If you have flexibility and significant Java usage, remember that Oracle Cloud Infrastructure includes Java licenses. Migrating some Java workloads to OCI could be a strategic move to reduce licensing costs (while also meeting other strategic goals for the cloud).
Checklist
- Inventory Oracle Products – List all Oracle software your organization uses (middleware, databases, ERP, etc.) and mark which ones inherently include a Java SE license.
- Document Java Installations – For each Java installation in your environment, record what it’s used for. Link each Java instance to either an Oracle product (entitled) or note if it’s for a non-Oracle use (requiring separate licensing).
- Verify License Scope – Check the license terms or Oracle’s official documentation for each product to confirm the scope of the included Java usage. Note any restrictions (e.g., version, specific servers, client-use only) for compliance purposes.
- Assess Gaps – Identify any Java deployments not covered by an Oracle product license. Plan how to address these (purchase Oracle Java subscriptions, use an alternative Java distribution, or possibly eliminate/upsize to OCI if that’s an option).
- Review Contracts and Support – Keep copies of Oracle agreements or Oracle’s public license guides that state the Java entitlements. During contract renewals or negotiations, ensure these entitlements remain in place and clarify any doubts about Java coverage in writing.
FAQ
Q1: Does having an Oracle Database license mean I have a Java SE license?
A1: Generally, no – an Oracle Database license by itself does not include Java SE for general use. The database does use Java internally (for Java stored procedures, etc.), but Oracle treats that as an internal feature of the database, not as a full Java SE entitlement, allowing you to run other Java applications. Only certain Oracle products (mostly middleware and applications) explicitly grant Java SE rights. Always refer to Oracle’s licensing documentation to determine if Java is included; if it’s not, assume you need a separate Java license for external Java usage.
Q2: How can I tell if a product I’ve licensed includes a Java SE entitlement?
A2: Oracle’s official price lists and licensing documents often footnote which products include Java. Look for phrases like “includes the right to use Java SE” or check Oracle’s Approved Product Use List if available. Additionally, product documentation or installation guides may sometimes mention the use of a bundled JDK or JRE. If you are unsure, consult with Oracle support or licensing specialists – it’s essential to have clarity in writing. The list in this article provides a starting point for known products with Java entitlements.
Q3: Are the Java licenses included with Oracle products full licenses or restricted?
A3: They are typically restricted-use licenses. This means Java is licensed only to run the specific product (and sometimes closely related components). For example, Java included with PeopleSoft can run PeopleSoft processes, but you can’t use that as a general corporate Java license for other apps. An exception is Oracle Coherence, which includes a full-use Java license (allowing broader use), but such cases are rare. Always assume it’s restricted unless Oracle explicitly states that it’s for full use.
Q4: What if I use a different Java version than the one that came with the Oracle product?
A4: Using a different or newer Java version doesn’t automatically void your entitlement, but it can raise support issues. Oracle’s included license covers the Java needed for the product, usually the version they ship or support. If you upgrade to a newer Java version for improved performance or security, ensure that Oracle supports that version for the product. If Oracle hasn’t certified it, they might not support issues on that configuration. From a licensing perspective, if the product license includes Java, using an alternative Java binary (Oracle or OpenJDK) to run the product should still be covered, as long as it’s solely used for the product. However, clarify this with Oracle if you plan major version changes.
Q5: How have Oracle’s Java licensing changes affected this bundling?
A5: The bundling of Java with certain products remains in effect despite Oracle’s changes to Java SE subscriptions. Oracle’s 2023 switch to employee-based Java licensing primarily affects organizations that require standalone Java SE licenses. The included Java rights with Oracle products are still honored under those product agreements. These bundled rights are now more valuable, as standalone Java is pricier; leveraging the Java that comes with your Oracle middleware or applications can save a significant amount of money. Just be cautious when using it within the allowed scope. Also note that Oracle will honor existing agreements – if your company had an older Java license (e.g., Java SE Advanced under processor licensing) tied to a product, Oracle will continue to recognize it until the contract ends. Always stay updated with Oracle’s official communications, but so far, the bundled entitlements have not been revoked by the new model.
Read about our Java Advisory Services.
