JD Edwards – Why Move to 64-Bit Processing?

Many of our clients are unaware that as of Tools Release 9.2.3, EnterpriseOne now supports 64-bit processing for the Enterprise Server and Development Client and as of Tools 9.2.4, the Deployment Server has been enabled for 64-bit processing. The HTML, AIS, BSSV, and RTE servers already supported 64-bit. When enabled, customers can take advantage of any 64-bit enabled third-party components such as database drivers and Java.

Why Should I move to 64-bit?

Well, the short answer is that many of the underlying components that EnterpriseOne relies on will be phasing out 32-bit support, so you will be forced to move to 64-bit. In addition, Oracle has stated that the latest Tools Release 9.2.5 will be the last Tools Release that supports 32-bit processing. With the move to 64-bit, you will future proof your EnterpriseOne environment by leveraging the underlying 64-bit technology. In addition, with Oracle’s push to move to 64-bit, third-party vendors have started to follow suit and will soon be phasing out 32-bit as well.


  • Compatibility with 3rd party software: Vertex; RF Smart; DCLink; Reports Now; JAVA
  • Database drivers – 32-bit cannot use 64-bit Print drives compilers
  • Browser Compatibility: Chrome; Microsoft Edge; Windows 10; SQL Server 2019
  • Third party vendors of components (which are required for JDE) are currently releasing only 64-bit components
  • Oracle 19C, Autonomous Database, MS SQL Server 19
  • Required for Release 22

Performance Improvements:

  • Improved interactive response times
  • Improved batch processing runtimes
  • Do away with 32-bit emulator (WOW64) overhead
  • Larger memory space means less out-of-memory errors
  • Improves interactive application response time by 6-10%
  • Improves batch applications processing runtime up to 13%

Other Benefits:

Enabling 64-bit future-proofs your IT environment for future technology enhancements and JD Edwards innovation. Other benefits include:

  • Enable support for JD Edwards Digital ERP version
  • System Administration and System Availability enhancements
  • Security strengthened to new industry standards

What is the Impact to my system?

There is no impact to objects that do not have a C code component, such as Applications and UBEs. Oracle has released 64-bit ESUs to handle the standard Oracle components which require retrofitting for 64-bit processing. Furthermore, for any custom objects, Oracle has provided a utility to aid in the conversion to 64-bit processing. These objects may require additional retrofitting by a developer, but the utility should give you a good start in getting those objects converted. The Database Drivers and Java will require an upgrade to 64-bit.

What are some of the considerations in moving to 64-bit processing?

The first thing to keep in mind is that 64-bit processing is only supported as of Applications Release 9.2. Secondly, you need to be using Tools Release version 9.2.3 or newer. If you do not yet have that option, you will need to first upgrade to a 32-bit version of Tools 9.2.3 or later. Once your system is there, you can then move to the 64-bit version of the same Tools Release. This will also require the application of some 64-bit ESUs, as well as running the 64-bit conversion for your custom code. Moreover, Server Manager components will need to be updated to monitor the 64-bit components.

More information on Centrilogic’s JD Edwards Services: https://www.centrilogic.com/services/applications/managed-jd-edwards/