Oracle’s INFOCUS 2026 keynote session has a clear throughline: modernization doesn’t have to mean disruption. From refreshing their UI to adding a 64-bit mandate to the announcement of an MCP server for JDE, the roadmap is moving fast. Here’s what matters most for your environment heading into 2027.
What Oracle Announced
The keynote covered a lot of ground, but four key product updates stood out as the most relevant to organizations in the current JDE landscape.
Release 27 gets a UI refreshment
Oracle is rolling out a modernized interface with responsive design, updated colors, and a sharper overall look. The key reassurance from the product team is that core underlying functionality hasn’t changed. The screens remain the same. Existing automated testing will continue to work. The visual refresh just brings JDE closer in appearance to Oracle Fusion products, which matters if your organization runs or is considering running both.
64-bit becomes mandatory
Following the Release 27 launch, JD Edwards will require 64-bit across both the tools layer and the application layer by the end of 2026. If your environment still has 32-bit dependencies, the planning window is now. Oracle acknowledged that the transition won’t be perfectly seamless and committed to working with customers in early 2027 to address these issues.
JDE is getting an MCP server
Oracle confirmed plans to release a Model Context Protocol (MCP) server for JD Edwards, making JDE accessible to AI agents and external automation platforms as well as internal orchestrations. Available on both AIS and OData pathways, this change means your JDE instance can participate in broader, agent-driven workflows instead of requiring manual integration. For organizations already invested in orchestrations, this is a significant extension of that work: the capabilities you’ve built become composable with whatever AI tools your organization adopts next.
Platform simplification continues
Oracle is continuing to streamline the certified technology matrix, with AIX and WebSphere being phased out as the platform evolves. The direction is leading to a simpler, more modern infrastructure with fewer moving parts.
The Modernization Framework
The keynote also laid out a three-part framework for how Oracle sees JDE modernization succeeding in the modern enterprise landscape.
- Protecting stability: Oracle leaders emphasized creating a clear separation between your production environment and your innovation efforts. This allows your organization to move forward without putting day-to-day operations and application support at risk.
- Continuous enablement: Oracle reiterated that continuous adoption only works if your people can keep pace with it. Organized training and change management make the difference between a successful rollout and a shelf-ware investment.
- Extending the workforce: With AI agents, orchestrations, and the new MCP server offering, Oracle is positioning JDE as a platform that allows routine, repetitive work to be automated. This frees your team to focus on higher-value problems and tasks, enabling them to accomplish more in less time.
By framing this as a formal strategy rather than a set of best practices, Oracle is signaling where their investment and product roadmap are headed in the next year.
What This Means for Your Organization
Audit your 64-bit readiness. The deadline is end of year. You must identify any 32-bit dependencies in your current environment and build a migration plan before it becomes urgent.
Consider the MCP server. If you’re already using orchestrations, the MCP announcement comes as a natural extension of your current tooling. If you’re not, this is a strong reason to start. Either way, it’s worth understanding what agent-accessible JDE looks like for your workflows.
Don’t skip enablement. Successful guide engagement happens when your organization invests in both the people and the technology behind the operations. If your modernization plan doesn’t include a training and change management strategy, it’s incomplete.
Stay current. Oracle’s primary message was that modernization isn’t a one-time project. Organizations that defer updates for years at a time are making it harder and more expensive to catch up later. Continuous adoption is the model now.
This keynote revealed that Oracle is doubling down on JD Edwarads as a strategic platform, not winding it down. For organizations willing to invest in stability, enablement, and the emerging AI toolset, the path forward is well-defined.
If you’re navigating your JD Edwarads modernization roadmap and want to talk through what these changes mean for your environment, our senior–level consulting team works with organizations to plan upgrades, manage transitions, and keep systems running. Contact us to learn more.
