Hi HomerJ,

You'll want to stop the services and restart the server (not just the services) after the changes are made as you will need to update the Environmental Variable on the windows system to point to the correct path location for the Java as the path will change with the newly installed JAVA as the build number is part of the path structure when JAVA installs.  Without this restart of the services the old JAVA will still be cached and the path is being pointed to.  Also if you uninstall the other version then the path can't be found because it is designated in the Environmental Variable and after uninstalling it will no longer exist (even though Java is installed and running).  Change the Environmental Variables here:  https://eyeontesting.com/answers/alm-15-5-required-java-isnt-updating-and-starting-after-upgrade/#gsc.tab=0

We also see some issues with certain versions of JAVA above a certain build number that may have issues.  We have not received guidance on that particular but if it happens there was a fix for ALM 12.60 that required the following:

Summary

If Java update is greater than 255, ALM service cannot start. This is issue with log configuration in web.xml under ALM deployment (Default path is ProgramDataMicro FocusALMwebappsqcbinWEB-INF)

Solution

1. Locate the web.xml file in deployment path (Default path is ProgramDataMicro FocusALMwebappsqcbinWEB-INF)

2. Change the following log level to OFF
     <!-- BIRT PARAM: Report engine log level. -->
     <context-param>
     <param-name>BIRT_VIEWER_LOG_LEVEL</param-name>
     <param-value>OFF</param-value>
     </context-param>

3. Save the change and restart ALM service.

You may not have such an issue but Microfocus doesn't test with the various and newer builds so we don't always know which may cause issues and which may not (for this reason it is not recommended to just upgrade to have the newest and latest without certain needs and requirements for it).