Home / Educational Content / JD Edwards / JD Edwards EnterpriseOne 64-bit Enablement for Enterprise Server

JD Edwards EnterpriseOne 64-bit Enablement for Enterprise Server

With Tools 9.2.3, JD Edwards released 64-bit enablement for the Enterprise Server and Development Client. JD Edwards EnterpriseOne has supported 64-bit hardware, operating systems, databases, Java, and middleware for many years. Multiple JD Edwards components, such as HTML Server, AIS Server, Orchestrator and other Java-based components, are 64-bit enabled. To round out the architecture, JD Edwards now enables 64-bit processing for the Enterprise Server and Development Client as well.

Before diving in, it’s important to understand that making the move to 64-bit processing is entirely optional. It will not impact customers who are uninterested in making the switch. Enabling 64-bit is a seamless migration, and customers have the option to have a staged rollout in one environment at a time instead of all at once.

Enablement of 64-bit is only available in Tools 9.2.3 and is only supported on Applications Release 9.2. Apps 9.2 supports both 32-bit and 64-bit, and ESUs are delivered in separate downloads for either 32-bit or 64-bit. Change Assistant will determine the correct bitness for customers and deploy the correct patches. Tools Release 9.2.3 is only supported with Apps 9.1 and Apps 9.2.

64-bit Enablement for the Enterprise Server

There are three major points that make the 64-bit enablement of the Enterprise Server important.

  1. Vendors are starting to deliver 64-bit components only (i.e. Database, Java, etc.).
  2. It future-proofs your environment for future technology changes and JD Edwards innovation.
  3. There has been a 10-15 percent performance improvement for heavy logic-based processing.

Enablement of 64-bit on the Enterprise Server is a technical uplift. It has zero impact on business logic, business processes, or business data. JD Edwards gives you choice and control over when you want to enable 64-bit on the Enterprise Server. However, it is recommended that you leverage other activities in your system such as an upgrade to Applications 9.2, your code-current strategy, or moving to Oracle Cloud Infrastructure, as an opportunity to move to 64-bit enablement.

Benefits of 64-bit Enablement

In addition to future-proofing your environment and leveraging performance improvements, there are several other benefits of moving to 64-bit enablement.

  1. Customers can uplift at their own pace. Customers who want to move to 64-bit can upgrade their Pathcodes in phases and uninterested customers can simply remain at 32-bit. Enabling 64-bit is entirely optional and is only available on Applications Release 9.2.
  2. Patches are delivered through a single ESU. New ESUs will contain both 32-bit and 64-bit, so customers don’t need to choose. Existing ESUs will remain 32-bit. The Change Assistant determines bitness for customers and will deploy the correct patches.
  3. There is minimal impact on development. JD Edwards will continue to develop in 32-bit, so customers are not being forced to move. This means that customers will have the ability to test in both 32-bit and 64-bit and build either 32-bit or 64-big packages. Installers will automatically handle all registering and deployment will be based on bitness.

For more information on 64-bit enablement, check out the video below, visit www.learnjde.com, or browse the additional Quest resources attached below.