Future-Proofing Your JD Edwards Investment with 64-bit
EnterpriseOne has supported 64-bit hardware, operating systems, databases, Java, and middleware for many years. Components such as HTML Server, Enterprise Server, Development client, AIS Server, Orchestrator and other Java-based components, are 64-bit enabled.
The Difference Between 32-bit and 64-bit
In short, a 64-bit processor can handle more data at once compared to 32-bit. Specifically, a 32-bit system can natively only use 4 GB of RAM. A 64-bit architecture can access 6.8 million terabytes of RAM. That is over a 4 billion times increase in theoretical scalability.
Why Make the Move to 64-bit
While implementing 64-bit seems like a big undertaking for your organization, it simply eliminates the need for 32-bit compatibility. There is no impact to business processes or business data because the software now runs natively in the 64-bit operating systems. Look at it as a technical uplift within the foundation of JD Edwards.
Across the JD Edwards EnterpriseOne tools releases, Oracle has tested and concluded the following:
- There is an overall improvement in total average interactive response time in the 64-bit version of EnterpriseOne.
- There is an overall improvement in UBE runtime in the 64-bit version of EnterpriseOne.
- There is an overall decrease in Enterprise Server CPU usage in the 64-bit version of EnterpriseOne.
- There is an overall decrease in average C Business Function (BSFN) response time in the 64-bit version of EnterpriseOne.
- There is an overall increase in Enterprise Server memory consumption when moving from 32-bit EnterpriseOne to the 64-bit version.
- The IBM I on Power Systems platform is not discernibly impacted by 64-bit EnterpriseOne processing because this operating system is natively 128-bit.
- Package builds run longer in an EnterpriseOne install which maintains both 32-bit and 64-bit Business Functions.
When to Make the Switch
Going forward, all JD Edwards upgrades will require 64-bit processing. This change is expected by the end of the year. To not get left behind and risk facing hardware and software obsolescence, it is suggested to make the shift by the end of the year.
However, the following must be completed to ensure a seamless 64-bit transition:
- Applications Release 9.2.
- Tools Release 9.2.1 or higher
Future Proof Your JD Edwards Investment
While switching to 64-bit was not a limiting problem when the product was first developed and implemented, the software usage has changed and adapted over the years. To give that same agility to their clients, JD Edwards 64-bit can push the limits of the current 32-bit infrastructure with:
- Increasingly larger datasets.
- Larger queries are being run within batch jobs.
- Enterprise Server Call Object Kernels.
- Results within these processes are stored and utilized.
To pursue a path of digital transformation, adapting to future technology will future-proof your environments. In addition to the cost benefit, transitioning to 64-bit will help avoid risk of facing hardware and software obsolescence.
Vendors of third-party components such as database drivers, which EnterpriseOne requires, may also plan to only provide limited support of 32-bit components.
“The enablement of JD Edwards EnterpriseOne for 64-bit with Tools Release 9.2.3 allows customers to continue their digital journey while future-proofing their investment in JD Edwards.” – Lyle Ekdahl, Senior Vice President JD Edwards for Oracle
How to Plan for 64-bit
Terillium’s JDE 64-bit workshop is tailored to meet your organization’s needs. This 2-hour planning workshop starts with a short session to better understand your goals and requirements. From there, our instructors will lead you through:
- What it means to go 64-bit
- A review of your JDE infrastructure
- Different project options and paths forward
By the end of the workshop, you will have our recommended roadmap for your organization with costs and a well-tested plan to successfully move into the future fully optimized with a 64-bit architecture. Learn More About Workshop