SRM: After upgrading SRM, the update-manager still has the previous version of Java installed

• After upgrading SRM, the update-manager on the Frontend server contains the previous version of Java that was used before the upgrade:

/opt/APG/Tools/Update-Manager/[version]/data/Sun-JRE_[version]/

/opt/APG/Tools/Update-Manager/7.4.1/data/Sun-JRE_8.0.311/

• SRM does not use the update-manager JRE installation. This is only used for the update-manager during the upgrade process. 
• SRM has the correct version of Java post upgrade:

/opt/APG/Java/Sun-JRE/[version]

/opt/APG/Java/Sun-JRE/8.0.321

• The update-manager installs the current version of Java during the upgrade process (that is, the Java version used before the upgrade). This is used during the upgrade.
• After the upgrade, the update-manager does not clean up the Java installation that is used for the upgrade process, hence why the previous version of Java is still present. 

1. Log in to the Frontend server.
2. Run the manage-modules script to remove the update-manager service:

/opt/APG/bin/manage-modules.sh remove update-manager

3. When prompted, select "yes" to remove, and "yes" to purge the module, similar to below:

[root@sirius01 ~]# /opt/APG/bin/manage-modules.sh remove update-manager
Modules to be removed, in processing order:
   [1] D update-manager '7.5' v7.5
 ? Enter the step to modify, 'yes' to accept them, or 'no' to cancel the operation [yes] > yes

Starting removal of update-manager 7.5...
 * Gathering information...
 * The module installed in '/opt/APG/Tools/Update-Manager/7.5' will now be removed.
 ? Do you want to completely purge the module Update-Manager 7.5 out of the system, including data files, configuration files and restore points? (yes/no) [n] > yes
 * Removing files... 100%
 * Finalizing removal...
Removal complete.
[root@sirius01 ~]#

4. Once complete, verify that the update-manager and its Java installation are removed.