An Early Look at JD Edwards Release 27
JD Edwards Release 27 is shaping up to be another important step in the modernization of the JDE platform, with changes spanning the underlying technology, user experience and future AI capabilities.
The overarching theme is modernization without disruption. JD Edwards Release 27 is expected to modernize key components of the JD Edwards technology stack while maintaining continuity for the business processes and functionality customers rely on today.
The official JDE Release 27 release notes have not yet been published, so this is an early preview of what we know so far. We will provide updates as additional details become available and provide a more comprehensive look at the release once the official information is published.
JD Edwards Release 27: What We Know So Far
64-Bit Architecture Comes to JD Edwards
One of the most significant Release 27 changes is the move toward a 64-bit-only environment at both the Tools and application layers.
For customers that have already transitioned to 64-bit, Release 27 represents another step in the ongoing modernization of the JD Edwards technology stack. Organizations still running 32-bit components should begin evaluating what will need to change.
Your review should include:
- Customizations and custom applications
- Third-party integrations and software
- Database and infrastructure dependencies
- Testing and upgrade requirements
Customers with older JDE environments should determine their current architecture and identify any components that could require remediation before planning a JDE Release 27 upgrade.
Java Modernization: From Java 8 to Java 21
JDE Release 27 will also bring a significant update to the Java technology supporting JD Edwards.
The move from Java 8 to Java 21 represents an important modernization of the underlying technology, with Java 25 also on the roadmap for the future.
For most customers, this change will happen behind the scenes. However, organizations with custom Java applications, integrations or other Java-dependent technologies should evaluate their environments ahead of an upgrade.
Customers should consider:
- Custom Java code and applications
- Java-based integrations and extensions
- Third-party solutions that depend on Java
- Compatibility and testing requirements
Moving to newer Java versions helps keep the JD Edwards technology stack aligned with current technology standards while providing a more modern foundation for future development.
Platform and Infrastructure Changes
Several older technologies are being retired or phased out, including Solaris and AIX, along with full WebSphere. WebSphere Liberty will remain part of the supported technology stack.
The impact will depend on each customer’s current environment. Organizations should take the opportunity to review:
- Operating systems and application servers
- Database and infrastructure dependencies
- Third-party applications and integrations
- Custom code or solutions tied to specific platforms
Identifying these dependencies early can help determine whether infrastructure changes, compatibility testing or additional planning will be needed as part of a Release 27 upgrade.
Redwood UX: A New Look Without Disruption
Release 27 will introduce the Oracle Redwood user experience to JD Edwards, bringing updated fonts, colors and a more modern look and feel.
The important consideration for existing JDE customers is that the Redwood transition is focused primarily on the user experience rather than changing the underlying business functionality.
Key points include:
- Existing fast paths will continue to work
- Event Rules (EVLs) are not changing
- Existing business logic remains intact
Redwood also creates a more consistent visual experience for organizations using both JD Edwards and Oracle Fusion Cloud.
JD Edwards and the Future of Agentic AI
One of the more forward-looking developments surrounding JDE Release 27 is the planned MCP server for JD Edwards.
Model Context Protocol (MCP) provides a standardized way for AI applications and agents to interact with business systems and data. For JDE customers, this will create new opportunities for AI-enabled workflows and automation.
This is relevant for organizations running hybrid JD Edwards and Oracle Fusion environments. As Oracle’s agentic AI capabilities continue to evolve, JDE has the potential to participate in the broader AI ecosystem rather than operating separately from it.
The MCP server is a future development, not an immediately available Release 27 capability. However, it provides an early indication of how JD Edwards could fit into the next phase of enterprise AI and automation.
What “Modernization Without Disruption” Means for JDE Customers
The changes coming with Release 27 point to a broader approach to JDE modernization: modernize the platform without unnecessarily disrupting the business processes built around it.
Three areas are particularly relevant for customers:
- Protect stability – Keep the core ERP environment reliable while creating opportunities for innovation.
- Continuously enable your people – Help users and IT teams adapt as technology and processes evolve.
- Expand the workforce – Use AI and automation to extend what employees can accomplish and support them with new capabilities.
For JD Edwards customers, modernization doesn’t necessarily mean replacing the ERP system. It can mean modernizing the technology underneath it, preparing your people for change and finding new ways to extend the value of your existing JDE investment.
How to Prepare for JD Edwards Release 27
While the complete Release 27 documentation isn’t available yet, there are several steps organizations can take now:
- Assess your 64-bit readiness and identify any remaining 32-bit components.
- Review Java and infrastructure dependencies, including custom applications and third-party software.
- Inventory customizations and integrations that may require compatibility testing.
- Consider your upgrade timeline, particularly around year-end, payroll and other business-critical periods.
- Begin thinking about user enablement as the Redwood experience is introduced.
- Consider your longer-term AI strategy and how JDE could fit into future agentic workflows.
Getting started now can help organizations identify potential issues early and make more informed decisions once the complete Release 27 requirements are available.
