An embedded Java instance in third-party applications often creates confusion around Oracle Java licensing. Many organizations discover Oracle Java bundled with vendor software, leading to questions about licensing responsibility and compliance. Knowing who pays and who is liable for these embedded Java deployments is critical for ensuring Oracle compliance and avoiding unplanned licensing costs.

Understanding Embedded Java Scenarios

Embedded Java refers to Oracle Java Runtime Environment (JRE) or Java Development Kit (JDK) components packaged within vendor-provided software. In these cases, Java may be running silently in the background, not directly installed by your IT team.

Common third-party tools where you might encounter embedded Java include:

• ERP systems
• CRM platforms
• Business Intelligence tools
• Performance monitoring software
• Database administration utilities
• Middleware and integration platforms

Read more in our brief history of Oracle Java licensing.

The key issue: Java licensing responsibility depends on your vendor’s Oracle license agreement, how they distribute their application, and what your contract says.

ISV and OEM Licensing Models

Independent Software Vendor (ISV) Licensing

Vendors embedding Java can choose:

• Oracle Java SE OEM License:
  • Vendor bundles Java with their software.
  • They pay Oracle.
  • You get usage rights — but only for that application.
• Oracle Java SE Embedded License:
  • For embedded/specialized use.
  • Often tied to devices or limited functionality.
  • Cannot be reused elsewhere.

Learn how to manage these licensing types in our Hitchhiker’s Guide to Oracle Java License Management.

Original Equipment Manufacturer (OEM) Arrangements

Hardware vendors sometimes include Java via OEM licenses:

• Java pre-installed on appliances.
• Java bundled in integrated software.
• Custom deployments with Java components.

Determining Licensing Responsibility

When Your Vendor Handles Java Licensing

Sometimes your software includes Java legally through the vendor:

• Included License:
  • Vendor pays Oracle.
  • You receive limited Java usage rights.
  • You can’t reuse Java for other internal needs.
• Pass-Through License:
  • Vendor negotiates discounted rates.
  • Costs built into your purchase.
  • Licensing is application-specific.

Customer Licensing Responsibility

You may need a separate Oracle Java license if:

• Java isn’t included by your vendor.
• Java is included but restricted.
• Java is used elsewhere in your environment.

Learn about potential risks in our guide on Java licensing changes 2021.

Application-Specific Java Licensing Scenarios

Restricted Use Cases

Vendor-provided Java licenses often restrict use to their application:

• Application-only use.
• Prohibited for internal dev or other apps.
• Updates may not be included.

Understand more about version limitations in our post on Java SE licensing and costs.

Oracle’s Schedule A and B Programs

Oracle offers predefined lists of applications:

• Schedule A:
  • Covers Java use in specific apps (e.g., Oracle middleware).
• Schedule B:
  • Permits Java use in dev, test, and academic contexts.

Common Third-Party Application Scenarios

ERP Systems

• SAP: May include Java runtime.
• Oracle EBS: Comes with Java usage rights (Do EBS Users Need a License?).
• Custom ERPs: Often need a separate license.

BI Platforms

• Use Java for:
  • Reporting engines
  • ETL processes
  • Data visualization

Database Tools

• Java used in:
  • Oracle SQL Developer (licensing explained here)
  • Performance monitoring
  • Backup and recovery tools

ISV Responsibility & Customer Protection

What Good Vendors Should Do

• Provide written licensing terms.
• Explain usage rights and restrictions.
• Document Oracle Java licensing agreements.

Customer Best Practices

• Request written confirmation.
• Review vendor’s compliance status.
• Audit Java instances.

More on hidden risks in our blog on Web Start and hidden audit threats.

Audit & Compliance Risks

Oracle Java Audit Scenarios

• Hidden Java via vendor tools.
• Undefined licensing scope.
• Risk of license shortfalls.

Need audit support? Contact our Oracle audit specialists.

Documentation Essentials

• Vendor licensing confirmation
• Scope/limitations
• Usage evidence

Java Licensing During Negotiations

Focus on these:

• Explicit Java inclusion
• Vendor liability for non-compliance
• Indemnification clauses

Java License Optimization Tips

• Consolidate licensing.
• Negotiate enterprise-wide Java terms.
• Consider OpenJDK and alternatives:
  • Amazon Corretto
  • Eclipse Adoptium
  • Red Hat’s OpenJDK build

Learn about license-free platforms in our Java license change 2023 post.

Best Practices for Embedded Java Management

Inventory & Discovery

• Identify all Java installs
• Map vendor-specific Java dependencies

Vendor Management

• Require proof of licensing
• Include Java terms in RFPs

Compliance Monitoring

• Monitor Java usage continuously
• Track vendor license changes

Frequently Asked Questions

Am I compliant if Java is “included” by a vendor?
No. Java is likely limited to that application. Additional licensing may be needed.

How can I verify my vendor’s Oracle Java license?
Request their written Oracle licensing agreement and scope.

What if my vendor loses their license?
You may become responsible for licensing. Negotiate protective clauses.

Can I reuse vendor Java for custom apps?
Usually not. You’ll need separate licensing.

Do Oracle audits include embedded Java?
Yes. Oracle checks all Java usage — even those bundled by vendors.

Should I negotiate Java terms with vendors?
Yes. It ensures clarity and protects against surprise audit costs.

What’s the difference between OEM and ISV licenses?
Learn more here.

Can I migrate from Oracle Java?
Many vendors now support OpenJDK options. Ask about compatibility.

Do updates introduce new Java license requirements?
Sometimes. Always check Java version and support policies.

What if I find unlicensed Java?
Act fast. Seek help to close compliance gaps. Get a free consultation.

Strategic Takeaways

Managing embedded Oracle Java licensing is complex. Never assume your vendor has you covered — verify and plan. Organizations that succeed:

• Maintain software asset management.
• Negotiate clear vendor contracts.
• Monitor Java usage proactively.

Stay ahead of changes by visiting our Java Licensing Pro Tips Blog.

Need expert help? Contact us now for a complimentary 1-hour strategy session on Oracle Java licensing compliance.