Should you upgrade your JD Edwards EnterpriseOne yourself, or should you hire someone else to do it for you? There are many technology components that make up the EnterpriseOne software suite, thus many components to be upgraded: core Tools, updates and ESU’s, database, and operating systems. This article will focus on upgrading your EnterpriseOne software from one major release to another; for example Applications 8.10 to Applications 9.0, which usually entails a Tools release upgrade as well.
Before you upgrade, perform an assessment of your internal skill sets to see if you have what it takes to get this task completed in a timely, predictable manner. Let’s say your internal technology team members have a great knowledge of JD Edwards architecture and system administration (Configurable Network Computing, or CNC). They are confident they can perform the task because they have managed the system for years, are comfortable with the technology and know that they have successfully expanded the boundaries of their skills throughout their career. This is how great technology people are created—by addressing challenges through education and experimentation.
The questions to ask are: What is the cost of developing those skills and how often will those skills be employed? When will you have to upgrade again? What is the value to the organization of developing the skills required to upgrade a JD Edwards release level?
The JD Edwards EnterpriseOne major release cycle is a new release about every eighteen months, with full support for that release (patches, fixes, upgrade scripts, tax and regulatory updates) for five years. Tax and regulatory updates are delivered for one additional year. On average, JD Edwards customers upgrade major release levels within the support window. If you upgrade more frequently—sticking more closely to the release cycle rather than the support window—you may opt to build much of the upgrade skill set internally. If you tend to upgrade based on the support window the skills that you develop to perform an upgrade will not be maintained through practice and the risk of an unsuccessful upgrade increases dramatically.
Sometimes there are changes to the upgrade process, as there was between Tools Release 8.97 and 8.98. Regardless of your upgrade cycle, you should consider getting outside assistance with planning and preparing for your upgrade to make sure you are aware of any changes and are properly prepared for the execution. Also, even if you are planning to outsource the upgrade, there are steps in the process where your normal JD Edwards EnterpriseOne administrative skills can be deployed, reducing the amount of outside assistance required and lowering the overall cost if you are willing and able to participate in the process.
So you are going on your own…that is excellent, let me give you some simple best practices to follow.
- Take your Time and be Meticulous – Time might not be one of your luxuries but it is essential for your first pass. If you are already resource constrained, a self-upgrade project may not be your best option.
- Research – There are many components to the EnterpriseOne software package and they work harmoniously together. The Upgrade Manual is a good place to start but it often does not include important information or resolutions to issues discovered after it was written. Be sure you know all about the upgrade process before you begin, including any supplemental documentation or Response Line calls opened.
- Minimum Technical Requirements – Go through them carefully and do a formal hardware sizing to make sure you deploy the proper infrastructure.
- Document, Document, Document your entire process – (Take notes)
- Have a ‘Plan B’ – Know who you can call for help and communicate with them while you are still in the planning stage.
For more information on planning your upgrade project, contact brij to schedule a JD Edwards EnterpriseOne Upgrade Planning session.