E9.2 The Right Sequence to Back Out ESUs

KoalaBaby

KoalaBaby

Member
Only when backing out numerous ESUs with related items is required does the order in which you do so matter. In this scenario, the order of backing out ESUs would be the opposite of the order in which they were applied. This is done to ensure that any items that are connected between two ESUs are rolled back to their pre-ESU state.

Update and uninstall the ESU from the system to get rid of it.

You can do an Update Uninstall to completely delete the ESU from the machine after you've restored the specs from the backup. You shouldn't do the update uninstall, though, if you have installed the ESU in any other environments—like DV—where you haven't restored the specifications from a backup.

Methods For Reversing A Software Update (ESUs and ASUs)

The first step in backing out an ESU from an environment is to restore the specifications. If, during the ESU installation, you made a backup, you can restore the specifications.

The methods to back-out the ESU are listed below if you selected the backup option when installing the ESU (s)

How to Retrace an ESU
  • Enter the JDEPLAN environment and log on to the deployment server.
  • Launch the Electronic Software Updates application from the GH9612 menu (P96470).
  • Locate and choose the ESU that needs to be backed out from the list.
  • To access the environments list, use the 'NEXT' button.
  • Choose the environment you want to back the ESU out of from this screen.
  • From the Row exit, choose the 'Restore Backup' button.
In the event that a backup is made, the restore process will begin, restoring the combined items from that ESU.

Press the "Cancel" button to get back to the main ESU screen after the process is finished.

NOTE: The ESU will be reapplied if you use the "Next" button on step 8 rather than the "Cancel" option. For further information, see the section on the ESU "Restore Backup" button in this page below.

The final Step is to ensure that you have created, built and deployed a full package to reflect the new changes.

Always follow the companies Change Management Procedures before you embark on any changes to the system
 
Last edited:
Back
Top