A new year is fast approaching. You’re taking stock of your systems, your inventory, and getting ready for new challenges. Are you upgrading to the next JD Edwards release, Release 25? Are you prepared to say goodbye to certain applications if you do?
Because with Release 25, you won’t be able to run your 32-bit applications on a 64-bit release. You also won’t be able to access new features in the release, as they’re just for 64-bit.
Obviously, this could cause problems. Customers might not be ready to transition up to a 64-bit-compatible release because it’s not in the budget, their 32-bit operation is running smoothly, or they want to get the full value of their existing hardware.
So, can users still operate on 32-bit in 2025? The answer is “yes, but there are a few catches.”
Three main issues with continuing to operate on 32-bit this article will cover are:
- Lack of application compatibility
- Security risks
- Performance limitations
By the end of this article, you’ll understand the issues surrounding using 32-bit, and whether it’s possible to keep doing so in 2025 – and beyond.
32-bit: A Brief Background
32-bit, 64-bit; there’s even a 128-bit. The AS/400, or IBM I, platform is already running on 128-bit. The “bit” refers to how many bytes of data a processor or software can process at a time.
Most modern software has moved to 64-bit compatibility. Generally, 32-bit is still supported and can still run on many different software types. But increasingly, many companies are moving to a 64-bit standard base, which means they are no longer compatible with 32-bit.
The amount of “bit” can have different implications:
- Bigger amounts of bit mean processors can work faster and accelerate performance gains.
- Smaller bit systems like 32-bit are generally less efficient for modern applications.
- Certain applications and operating systems are designed for one bit size and not compatible with the other.
This is when users will need to make some tough decisions.
Why Running 32-bit Applications Can Spiral Into Bigger Problems
Historically, users have been able to run 32-bit applications on both 32-bit and 64-bit operating systems. But when a vendor moves away from 32-bit altogether, the user loses access to new features and functionalities. The last three JD Edwards releases, 23, 24 and 25, are not 32-bit compatible. The latest version of the Oracle Database, 23ai, is also not compatible with 32-bit.
This can pose a serious problem for JDE users. Take workflows, for example. This function is essential to JD Edwards. Traditionally, workflows have been created through a Windows client. With the debut of the Workflow Studio app on release 9.2.6.x, workflows can now be done through a web-based interface.
This simplifies and expedites the workflow creation process. This simplicity also means anyone can use it, not just IT developers. But that release requires 64-bit, so 32-bit users must continue to use a decade-old workflow process.
Compliance is another issue that can arise with older 32-bit systems. There could be regulatory standards a company needs to meet with their data. If those standards aren’t available on their older software and databases, a company could find themselves in serious trouble.
Solution: A migration from 32-bit to 64-bit. This is a one-time move that requires your system to be recompiled, but once it is completed, these worries are eliminated.
Outdated Security: Why 32-bit Makes Your Business an Easy Target
Security risks go hand in hand with compliance issues. To keep the data you’re working with safe, you’ll need the latest security features and patches. These come out periodically with the latest versions of operating systems and databases – and aren’t accessible on 32-bit.
You also need a strong security support team available to you if you run into a problem. With JDE, that team is Oracle. But if you’re not on the latest release, and you’re running an outdated version of your apps, they can’t help. Oracle would no longer be certified to resolve those issues.
You’re also vulnerable to outdated encryption standards, specifically Transport Layer Security or TLS. Older 32-bit systems may use outdated TLS versions, like 1.0 or 1.1. These can be more easily cracked compared to the newer TLS 1.2 or 1.3 standards on 64-bit systems.
Solution: Having a good handle on your existing security will help mitigate your risks, but nothing will replace the most-current security features available on 64-bit.
Why Performance Drops on 32-bit Systems
The broader technology ecosystem is moving away from 32-bit, too. For example, Windows 11, the most recent version of that operating system, no longer supports 32-bit. Microsoft announced support for Windows 10 32-bit ended on September 30, 2024. After that, just like with JDE, users can no longer receive product updates.
Running applications on any system requires sufficient memory capacity. Because 32-bit has less memory space, there are limits to how well apps and programs can perform. Regular business functions, like batch processing, become much more tedious.
Additionally, there is some amount of overhead required for operating systems to remain 32-bit compatible. This compatibility is called an emulation of subsystems. When that same application is run on 64-bit, there are marked performance gains, anywhere from 5 to 20%.
Solution: Performance gains or losses can be subjective, but at a certain point, it becomes obvious to user when there are lag issues. Running on 64-bit resolves performance issues.
Not If, But When: The Unavoidable Move to 64-bit
Long story short, users can still operate on 32-bit. But there are risks that need to be considered.
If the risks of 32-bit outweigh the benefits, it could be time to move to 64-bit.
This move requires strategic planning, but it is a one-time migration that will align your technology with modern standards. Before you make any decisions, dig deeper into the benefits of 64-bit.
Topics:
