CTRM4JDE to 64 Bit (In English)
JD Edwards on 64 Bit
In recent years, JD Edwards has focused on a shift towards a continuous delivery model (i.e. elimination of major releases). The pace of change has accelerated with foundational technology transformation, such as JD Edwards 64-bit, and new approaches to integration, like Orchestrator.
Oracle’s JD Edwards EnterpriseOne has supported vendor 64-bit hardware, operating systems, databases, Java, and middleware for many years. Additionally, multiple JD Edwards components, such as HTML Server, AIS Server, Orchestrator and other Java-based components, are 64-bit enabled. Now, to round out the architecture, JD Edwards will enable 64-bit processing for the Enterprise Server and development client. This empowers you to move completely from 32-bit to 64- bit processing. You might be asking yourself why you want to make that move. The answer is that you have quite a bit to gain. There are several reasons why you would want to move to 64-bit processing:
- Moving to 64-bit enables you to adopt future technology and future-proof your environments. If you do not move to 64-bit, you incur the risk of facing hardware and software obsolescence. The move itself to 64-bit is the cost benefit.
- Many vendors of third-party components, such as database drivers and Java, which JD Edwards EnterpriseOne requires, are delivering only 64-bit components. They also have plans in the future to end or only provide limited support of 32-bit components.
- It enables JD Edwards to deliver future product innovation and support newer versions of the required technology stack.
- There is no impact to your business processes or business data. Transitioning to 64-bit processing is a technical uplift that is managed with the JD Edwards Tools Foundation.
Oracle has recently announced that tools release 9.2.5 is the last 32 bit supported version, after which only 64 bit is supported in newer tools releases.
From 32 bit to 64 bit
The migration from 32 bit to 64 bit can be implemented quickly and with relative ease. As of this moment little impact is to be expected in regard to CTRM4JDE. Our colleague Alaric Schraven has recently published on how this would work and what the benefits are in his blog Oracle JD Edwards 64 bit processing: To be 64bit or not to be?
Cadran and its Redfaire International partners gladly help you modernize your JD Edwards environment and install the newest tools release.
CTRM4JDE is an Oracle Validated Integration. This means that we hold ourselves to Oracles’ development practices and that Oracle has validated this integration. Cadran is committed to retain this certification as to support its customers with the highest standard. In order to stay OVI certified, we need to certify our solution on 64 bit and need to migrate our software development to 64 bit. In light of the above announcement, we will shift our development of CTRM4JDE to 64 bit as of January 2021 and with release 3.7 and will stop supporting the 32 bit version of CTRM4JDE as of December 31st 2021. After December 31st 2021 we will continue to be able to support you, but will ask you to upgrade to the latest tools release under JD Edwards 9.2. Any bugs reported will be tested against our 64bit version internally to verify if the same bug appears in this version. As of this moment we don’t foresee differences here, but limits could arise.
Interested in this release?
Would you like to receive more information about the CTRM4JDE to 64Bit Release? Contact your Cadran Solution Architect or Mark Kamphuis or fill in our contact form via the button below.