# JD Edwards Tools Release Upgrade Checklist > Source: https://netray.co/tools/jde-tools-release-upgrade-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A phased checklist for moving JD Edwards EnterpriseOne to a newer tools release, from certification checks to post-cutover monitoring. ## Category oracle ## Erp Oracle JD Edwards EnterpriseOne ## Audience - JDE CNC administrator - IT operations - Project manager ## Tool **Kind:** checklist **Scoring Note:** Tick items as you complete them. Critical items are the ones that most often cause outages or rollback if skipped. A tools release changes the runtime, not your application data, but it still touches every server. **Groups:** #### Planning and certification **Items:** **Text:** Confirm the target tools release is certified for your application release, database, operating system and browser versions **Critical:** true **Text:** Read the release notes and known issues for the target and every release you are skipping **Critical:** true List all servers affected: deployment server, enterprise servers, logic servers, HTML and AIS servers, Server Manager Check hardware, disk and memory against the requirements for the new release Check that third party components (web server, Java, middleware, printers) are supported Agree the change window, rollback point and decision maker **Text:** Inventory customisations, custom BSFNs and C code that must be rebuilt **Critical:** true #### Backups and safety net **Items:** **Text:** Back up the database, including system, control tables, object librarian and central objects **Critical:** true **Text:** Back up path code directories and package files from the deployment server **Critical:** true Save the jde.ini files, JDBJ and JAS configuration and Server Manager settings Record the current tools release and package names in each environment **Text:** Prove you can restore a backup, not just take one **Critical:** true Keep the old tools release installers available for rollback #### Non-production upgrade rehearsal **Items:** **Text:** Apply the new release to a sandbox that mirrors production configuration **Critical:** true Upgrade Server Manager agents and managed instances in the planned order Update the deployment server and verify it can build packages **Text:** Run a full package build in the sandbox and review the build log for errors **Critical:** true Deploy the package to the enterprise server and logic server Verify HTML server and AIS server start and serve pages Confirm Orchestrator Studio and orchestrations still respond if you use them Record elapsed times for each step to build the cutover plan #### Testing **Items:** **Text:** Run regression scripts for order entry, purchasing, receipts, vouchers and shop floor **Critical:** true **Text:** Run key batch jobs (UBEs) and compare output with the previous release **Critical:** true Test integrations: business services, REST calls, EDI, interfaces to MES and WMS Test custom applications, reports and any code that was rebuilt Check printing, PDF output and email delivery Test security with a representative set of roles Test mobile or tablet access if used Have business users sign off on the results #### Production cutover **Items:** **Text:** Announce downtime and freeze object changes **Critical:** true **Text:** Stop scheduled jobs and confirm the job queues are empty **Critical:** true **Text:** Take a fresh backup immediately before the change **Critical:** true Upgrade production servers in the rehearsed order Build and deploy the production package **Text:** Run smoke tests: sign in, open key forms, submit a small UBE, run an integration call **Critical:** true Restart the scheduler and release held jobs Announce go-live and the support contact #### After go-live **Items:** Monitor logs, response times and failed jobs closely for the first days Review Server Manager alerts and enterprise server logs daily Log issues in one list with owner and severity Update runbooks and documentation with the new release Hold a lessons learned review and schedule the next planned update Retire old tools release installers and sandbox copies when safe ## Content **Intro:** A tools release upgrade replaces the runtime that every JD Edwards EnterpriseOne screen, batch job and integration runs on, so it deserves the same discipline as an application upgrade. This checklist walks a CNC administrator through planning, backups, a rehearsal, testing, cutover and aftercare. **Sections:** #### How to use the checklist **Body:** Work through the groups in order and tick items as they are completed. Critical items are those that, if skipped, usually cause an outage or block rollback. Export the list to PDF or Excel and attach it to your change request so the approver and the team see the same plan. Add rows in your own copy for custom interfaces and local controls. #### What a tools release actually changes **Body:** The tools release delivers the runtime, the development tools, Server Manager and the web components. It does not by itself change your application data or business objects, but it requires rebuilt packages and may affect custom C code, Java components and integrations. Because many servers are involved, the order of operations and the rehearsal matter more than any single step. **Bullets:** - Check certifications before downloading anything - Rehearse with real package build times - Plan for custom code recompilation - Keep a rollback path until testing completes #### Testing that finds real problems **Body:** Tests should follow your business cycle: take an order, purchase and receive, voucher, issue to a work order and ship. Add batch jobs with production size data and the integrations that connect JDE to other systems, since interfaces often fail quietly after a runtime change. Compare results with the previous release rather than judging by feel. #### Common mistakes **Body:** Teams often test only screens and forget batch, printing and web service paths. Others take a backup but never try to restore it, or schedule the upgrade at month end. Do not skip the rehearsal on a production like environment: package build time alone can double your window if the sandbox was small. **Cta:** If your upgrade plan also includes migrating custom reports or interfaces, Netray can help review the objects and integration points first, with an on-prem workflow if your data cannot leave your network. **Faq:** #### How often should we update the tools release? **Answer:** There is no single answer. Many sites update at least when the current release approaches the end of its support window, or when they need a fix or feature. Review Oracle support policies and your own risk appetite, and avoid long gaps between updates. #### Do we need a full package build after a tools release update? **Answer:** Generally yes, because the compiled objects must match the new runtime. Follow the release notes for your specific update, as requirements can vary. A rehearsal tells you how long it takes. #### Can the deployment server and enterprise server be at different levels? **Answer:** They should be aligned according to Oracle guidance for your release. Mixed levels are typically only acceptable briefly during a rolling change and are described in the documentation. Check the certification and release notes. #### What is the most common cause of a failed upgrade? **Answer:** Missing prerequisites, such as unsupported components or insufficient resources, and untested customisations. Checking certifications and rehearsing in a production like environment catches most of these early. ## Search terms jde tools release upgrade, jd edwards tools release checklist, jde 9.2 tools upgrade steps, jde cnc upgrade checklist, jde server manager upgrade, jd edwards package build after tools release, jde tools release planning, jde upgrade testing checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json